New: Legendary Connector is here — get both tools in the Legendary Bundle for $47/mo.
Tutorials

How to use Legendary Messenger CRM

How to use Legendary Connector

Everything the extension does, in the order you will meet it — from your first tracked conversation to split-testing the openers that get replies. Start with the walkthrough, then use the contents to jump to whatever you are stuck on.

Everything the extension does, in the order you will meet it — from saving your first group to reading the numbers a run gives back. If you read one section, make it the governor: it is the part that decides whether you still have an account next month.

Current release: v1.0

Current release: v1.0.1

Overview — the full walkthrough. Nothing is requested from YouTube until you press play.

Overview — the full walkthrough. Nothing is requested from YouTube until you press play.

1  Getting set up

Install, sign in, and tell it what you sell.

The extension runs on desktop Chrome, Edge, Brave or any other Chromium browser. It does not run on a phone — it works by reading the Messenger page you already have open.

  1. Install it. It is on the Chrome Web Store — Add to Chrome, then Add extension. Desktop Chrome, Edge, Brave or any other Chromium browser.
  2. Sign in. Click the toolbar icon and use the email address you bought with. Your password comes from the welcome email — if it has not arrived, use Forgot your password? on the sign-in screen.
  3. Write a script or two. The library starts nearly empty on purpose. Open Scripts and put your real opener in — it is what the / picker reaches for and what the split test measures.
  4. Open a conversation. Go to Messenger and open any thread. The context bar appears above it and an LL button appears in the row of icons beside the message box, next to the emoji picker.
Your data stays on your computer. Contacts, notes, scripts and pictures live in this browser, on this machine, and are never uploaded to us. That also means clearing browsing data takes them with it, so make a backup from Settings once you have a pipeline worth losing.

2  Where everything lives

Four surfaces, one set of records behind them.

The popup

The toolbar button. A compact panel: how many people you are tracking, how many are hot, what is due, one sentence naming your bottleneck, your follow-ups and your hot leads — plus a way straight into Messenger.

The side panel

The full record for whoever's thread is open, in Chrome's own side panel. You open it, from Chrome's side-panel menu — the extension never opens it for you, because a panel that appears on its own is a panel in your way.

The app pages

Dashboard, Contacts, Pipeline, Calendar, Scripts, Images, Links, Products, Facebook Groups and Settings, with one left nav across all of them. Tutorials and Support sit at the bottom of that nav — the corner people look in when they are stuck.

Inside Messenger

The context bar over the conversation, the LL button beside the message box and the record it pops open, stage and HOT labels in the conversation list, and the / script picker in the compose box.

The record has two homes, not two versions. The popout inside Messenger and Chrome's own side panel are the same record UI, so they can never drift apart or disagree about what you are looking at.

3  The pipeline

Eight stages, in the order they actually happen.

UntrackedWhere everyone starts. Not a stage — the absence of one. No label in Messenger, not in any list or count.
New LeadYou decided to work this person. They enter the funnel here.
RepliedThey wrote back. Somebody sitting at New Lead moves here by themselves the moment a reply lands; from any other stage you move them, because further along the funnel a reply is not news.
InterestThey want to know more. Counts as HOT.
Offer MadeYou have put the offer in front of them. HOT.
Call BookedA time is agreed. HOT. Asks when and where.
Deal WonAsks which product and what it was worth.
Deal LostNo scripts section — there is nothing to say to a deal you lost.
Follow-UpAsks when, and writes the reminder. A follow-up with no date is just a note.

Untracked, and why it matters

Opening a conversation is not a decision. Everyone starts Untracked, and someone enters your pipeline when you give them a stage. That keeps the top of your funnel honest: it counts the people you chose to work, not everyone you have ever opened a thread with.

Untracked is still a full record — notes, tags and the thread link all work. It is how you take somebody back out of the pipeline without losing a word you wrote about them. Two things do enrol somebody automatically, because both are decisions you made: importing a CSV, and adding a contact by hand. A reply does not; being messaged is not a decision.

These stages are a starting point, not the product. Open Pipeline → Stages and you can rename any of them, change the colour, decide which count as HOT, reorder them, and add or delete your own. Untracked is the one that stays. What is saved is the difference between your pipeline and this one, so anything you have not touched keeps improving as the defaults do.

HOT is where they stand

HOT is not a questionnaire any more. It is Interest, Offer Made and Call Booked — the three stages where the deal is live. Red means HOT and nothing else, which is why no stage colour is red.

What each stage asks for

  • Deal Won asks which product and what it was worth, because closing is the only moment you reliably know. Skipping is allowed and the deal still counts — the dashboard tells you how many have no figure rather than quietly reporting a total that reads low.
  • Call Booked asks when, and whether it is phone or Zoom. A Zoom booking picks a room from your Links library; a phone booking takes the number and writes it back to their record.
  • Follow-Up asks when, and writes a reminder you will actually see.

4  Working in Messenger

The part you will use most, without leaving the conversation.

The context bar

Sits across the top of the open conversation: their stage, changeable in place, the HOT flag, their tags, and what to say next.

Labels in the conversation list

Every tracked person's row carries their stage — or a HOT flag — plus a stripe down the edge in that stage's colour, so you can see the shape of your pipeline while you scroll the inbox. Untracked people look exactly as they did before you installed anything. You can turn labels off in Settings; they are on by default.

The label is a control. Click it and a stage menu opens right there, Untracked included — so moving somebody, or taking them out of the pipeline, is one click from the row they are on.

The / script picker

Type / at the start of a Messenger message and your script library opens. ↑↓ move, Enter takes the folder you are on and rotates the next variant in, → opens the folder so you can pick the wording yourself, ← goes back and Esc closes. Any pictures attached to the script go in with it. If the script has a blank left to fill you get Fill in {{day}} before you send rather than a half-written message.

Filtering the conversation list

A filter button sits in Facebook's own row of list controls, beside the ··· and the new-message button, and narrows your inbox by stage or tag — every person at Offer Made, say. It reads your own records rather than Facebook's list, so it covers everybody you track and not just the conversations currently on screen, and Facebook's page is not changed to do it. If Facebook is showing a layout with no control row, no button is drawn: a control floating in the wrong place is worse than none.

The LL button

In the row of icons beside the message box, next to the emoji picker. Opens the full record in a popout that floats over the conversation — nothing on the page moves to make room for it.

It never sends anything. Scripts are written into Facebook's own compose box and you press send yourself. There is no automation, no bulk messaging and no scheduling of messages — deliberately, because that is what gets accounts restricted.

5  The contact record

The panel, whichever home you open it in.

Stage, tags and notes

Stage at the top, changeable in one click. Tags de-duplicate and suggest from what you have used before, so your vocabulary stays consistent. Notes are searchable from the Pipeline page, which is how you find “the roofer in Tampa” months later.

Browse scripts

A folder chooser sits above the script with Choose which over it. The ‹ and › arrows walk whatever the chooser points at, wrapping at both ends; All scripts walks the whole library and labels each one with the folder it came from. The folder you chose is remembered as you move between contacts, because working a list of follow-ups means being in one folder for twenty conversations.

Stepping through scripts records nothing. Only Insert counts as a use.

Follow-ups

One field, not two: the next action is what the follow-up is about, and setting a date copies it onto the reminder. The date picker is a month grid with presets — tomorrow, in 3 days, next week, in a month — and a time row.

The Data tab

Phone, email, website, business and address. An empty field is a box you can type in rather than grey text that looks like data somebody already entered. Saved values become actions: a number dials, an address opens a map, a website opens. Ten digits format as (555) 213-8890; anything else — an extension, an international number — is left exactly as you typed it.

You can add fields of your own. A custom field goes on every contact, because a field that exists on one person and not the next is not a field, it is a note.

6  Scripts

Your words, filed your way.

The library starts nearly empty — one folder called Intro holding one script called Greeting, to show you what a folder and a spintax line look like. What you say varies enormously person to person, and a library full of someone else's wording is a library you clear out before you can use it.

Folders, not stages

Scripts used to be filed by pipeline stage. That conflated where somebody is with what you feel like saying, which are different questions — a follow-up nudge is a follow-up nudge whether they are at Replied or Offer Made. Now you name the folders. Scripts, Images, Links and Facebook Groups all use the same folder system.

  • Everything starts unfiled, and Unfiled sorts last — it is where things begin, not where they should stay.
  • Deleting a folder never deletes what is in it. A folder is a label; losing a label must not lose the work. The contents are unfiled and the confirmation tells you how many before you press it.
  • New things land where you are standing. Every Add dialog pre-selects the folder you are browsing — a suggestion, not a decision, since it stays a dropdown.
  • Copying beats moving, sometimes. The same opener often belongs in two folders, so the row menu offers Duplicate and Copy to…. A copy starts with clean results — inheriting the original's reply rate would be a lie the split test then acts on.

Spintax

{Hey|Hi|Hey there} picks one branch each time you insert, and blocks can nest. Write \{ for a literal brace. The editor shows the rendered result live, counts how many distinct wordings the script can produce, and refuses to save an unclosed block.

Merge fields

Three scopes:

  • {{your_name}} — you. Read from the Facebook account you are signed into, so there is nothing to type in and nothing to keep up to date.
  • {{first_name}}, {{their_niche}} — from the record in front of you.
  • {{day}}, {{time_a}} — meant to come out blank and be filled at the moment of sending.

A field with no value and no {{field|fallback}} renders as its own placeholder, and the panel asks you for it before the message reaches the compose box. Nothing silently becomes an empty string, which is how “Hi ,” reaches a customer.

Attachments

A script can carry images, which are handed to Messenger's own file picker, and links, which go in as text. Links are chosen from your Links library rather than retyped — a URL typed from memory is a typo waiting to reach a customer. If an image cannot be attached automatically it goes to your clipboard and the panel says to paste it, rather than claiming success and dropping the one part you cannot retype.

7  Split testing

Which of your openers actually gets replies.

A folder is a split test. Put three ways of asking the same question in one folder and the rotation splits between them. It hands out the least-used variant until each has 30 sends, then leans toward whichever is getting replies while still exploring 20% of the time, and never lets any variant fall below a 5% share — so a variant that started unlucky still gets its chance to come back.

Reading the results

  • Reply rate and stage-advance rate are shown side by side, both attributed within 14 days of the insert.
  • Reply rate drives the weighting because it accumulates fast enough to be useful. Stage-advance sits beside it because it is the number that actually matters.
  • A verdict chip says where the test stands: still rotating, a clear result, or too close to call.
Replies are credited carefully, and deliberately undercounted. A reply counts only when the last inbound message on that thread actually changes, and the first time the extension sees a thread it sets a baseline and credits nothing — so a reply that arrived before you installed it is never credited to a script it could not have earned. The message text itself is never stored and never leaves your machine.

Uses are recorded on insert, never on render. Reading a suggestion and deciding against it is not a send, and counting it would punish whichever variant happened to come up first.

8  Images & Links

The things you send over and over.

Images holds the screenshots, price sheets and before-and-afters you send constantly. Attach them to scripts or drop one into a conversation on its own. The picker files straight into the folder you are browsing.

Links holds your calendar link, your Zoom room, your case study. They insert as text, and they are what a Zoom booking picks from when you move somebody to Call Booked — a new room typed there is saved here, so the next booking is a pick rather than a paste.

In the 340px panel both open on their folders first, then you click into one, with a back row out — the shape of a file browser, because scrolling past thirty images to find one is not a feature.

9  Products

So closing is a pick, not a retype.

Marking a deal won used to ask for a product name and a number, typed fresh every time. The price got retyped from memory at exactly the moment you are least inclined to go and check it — and worse, the same offer reached your totals under four spellings, so nothing could ever be summed by product. The dashboard could tell you what you had earned and never what had earned it.

Save what you sell once — Title, Price, Info — and pick it when you close.

  • The price is a default, not a rule. It fills the amount in and the amount stays editable, because discounts and bundles are normal.
  • A blank price is a real answer. The list says Priced on the call rather than showing a hopeful $0.
  • “Something else…” is always there. A one-off deal must never be unrecordable — choosing it brings the free-text box back.
  • Deleting a product does not rewrite history. Deals already recorded against it keep their name and amount. What you sold is a fact, and it does not change because you stopped selling it.

Info is freeform on purpose — what it includes, who it is for, the objection it answers. It is the note you want in front of you on the call, not a field somebody else designed.

10  The Pipeline page

A list to work from and a board to look at.

List is the default

The board is the better picture of your pipeline; the list is the better place to work, and working is what you open this for. Both pills in a row do something: the stage pill drops the rest of your stages under it and moving asks whatever that stage asks; the tag pills open the tag editor, and a row with no tags shows + Tag rather than a blank cell.

The board

A column per stage, a card per person with their avatar, tags, what happens next and when it is due. Drag a card to move them. Empty stages stay hidden until you start dragging, and every stage is also reachable from a card's menu, so nobody needs a mouse to use it.

Finding people

  • Filter by stage or tag. Stages are an OR — Interest or Offer Made, which is how a row of chips reads. Tags are an AND, because that is what picking two means.
  • Search covers names, tags and note bodies.
  • Sort by last activity, due date, stage, name or recently added.

Bulk actions

Select rows or cards and move stage, or add and remove a tag across the whole selection. Each bulk action is one entry in the undo history, so an accidental sweep is one click back.

11  Contacts

A phone book, not a second pipeline.

The Pipeline answers where is everybody and what happens next. Contacts answers something smaller and far more common: have I talked to this person, and how do I get back to them. So it shows a name, when you last touched it, a way into the record and a way into the thread — and no stage pills, tag pills, hot flags or next actions.

That absence is the feature. A column you have to read past makes finding somebody slower.

Filtering is what earns the page. Narrow by stage or tag, or type a search, and that is when stages and tags appear on each row — you asked about them, so they show.

You can also add someone by hand, for a person you met off Facebook. Give their profile URL and the record merges with the real thread the first time you actually message them.

12  Calendar & follow-ups

Everything you owe somebody, on one screen.

A follow-up is a reminder on a contact — the calendar is a second way of looking at the same rows, not a second kind of thing. A month grid with the agenda beside it.

  • Booked calls are green dots with the room or number on them, not just another follow-up. Booking again moves the existing one rather than leaving last week's time on the calendar beside this week's.
  • Overdue is highlighted, and browser notifications fire for what is due.
  • Follow-through is the one figure on the calendar that is not a count: of the follow-ups that came due in the last 30 days, how many you dealt with. One still sitting there overdue counts against you, because it is.

From the dashboard, anything owed can be cleared with Done, Tomorrow or Next week without opening the record.

13  Dashboard

Your real numbers, built from what you recorded.

The funnel is derived from the event log — every stage change ever written, with its timestamp — rather than from a counter that can drift.

Four conversion rates

Reply rate
New Lead → Replied · target 50%
Interest rate
Replied → Interest · target 50%
Booked call rate
Interest → Call Booked · target 30%
Close rate
Call Booked → Deal Won · target 50%

Four, not six. Friend-request acceptance and show-up rate were dropped because nothing in this pipeline captures them, and a number nothing can ever fill is worse than no number.

The bottleneck sentence

One sentence naming the step costing you the most — the thing to fix this week. A rate behind target is the only other place red appears.

The dashboard also carries your due follow-ups, your hot leads, and a backup nudge once you have a pipeline worth losing.

14  Facebook Groups

The groups you work, and whether they produced anybody.

People who prospect on Facebook live in a handful of groups and keep them in browser bookmarks three folders deep, in the same window they are trying to work in. This is that list, in the tool you already have open — paste a group URL, name it, file it in a folder.

The group's own screen

The name opens the group's screen rather than leaving for Facebook, which is one button away. Two tabs, because there are two questions:

  • Contacts — who came out of this group. Stage and tags do show here, unlike the Contacts page: there you are looking somebody up and the columns get in the way, here the question is whether the group produced anything worth working, which is a question about stages.
  • Posts — a link, a note, whose post it is, and who came out of it. Yours to find out whether anything came of it; theirs to answer tomorrow.

The member count is typed in, and takes whatever the group's page actually says — 13.2K members, 1,197, 8.4k. Fetching it would mean the extension making its own request to Facebook, which is automated collection however small the request. An empty one reads as —, never 0: “nobody has told us” and “the group is empty” are different facts.

Removing a group takes its posts with it, because a post means nothing without the group it was in. It never takes its people — the origin is cleared and the record is left alone.

There is no group discovery, and there will not be. Reading your group memberships would mean enumerating something Facebook has not put on screen — the same line the contact lookup refuses to cross, and the line that keeps this product on the right side of Meta's terms. Every entry is one you pasted in.

15  Settings & your data

Getting your contacts in, and getting everything out.

Bring your contacts across

CSV import recognises its own export, Chatsilo, Genius Messenger and GroupTrack automatically, and will take a plain CSV from anywhere else. You get a preview before anything is written, and any column it could not map is shown rather than dropped. A row with no stage files at New Lead, because importing somebody is the decision to work them.

Take everything with you

  • CSV export of your contacts.
  • Full JSON backup — every contact, note, script, reminder and event.
  • Restore from a backup file.
  • A snapshot from before the last update, taken automatically, in case a migration ever goes wrong.

Other settings

  • Show labels in Messenger — on by default.
  • Your account — sign in and out. Signing out clears tokens and touches nothing else; every contact, note and script stays exactly where it was.
  • Diagnostics — what support will ask for. Copy it or save it to a file, with an option to replace every name with N1, N2… first, so you can send us a log without sending us your contacts. Beside it is a list of every conversation linked to a record and an Unlink button, for the rare case where two people end up sharing one.
  • What it reads, and what it never does — the plain-language disclosure.
If Facebook changes its markup, the extension notices and tells you rather than failing quietly. The banner means it could not read part of the page; a selector update fixes it without you doing anything.

16  Not built yet

Said plainly, so nothing surprises you.

  • Sync between computers. Your account exists and gates the product, but nothing is synchronised yet. Your pipeline lives in the browser you built it in — which is also why the backup in Settings matters.
  • Email reminders. Reminders are in-browser notifications for now.
  • Pushing leads into another CRM. Built and working — one address, and a lead is posted to it when they reach a stage you pick. It is switched off in every copy while the Chrome disclosure and the privacy pages catch up with it, because shipping a feature that sends your contacts somewhere before the page explaining it exists is the wrong order. It asks for permission to your one address when you connect it, never to every site you visit.

Stuck on something that is not here? Write to support@trijohnson.com or call (319) 727-8500, Monday to Friday, 9:00–3:00 Central. This page grows as the product does.

1  Getting set up

Install, sign in, and find the panel.

The Connector panel showing both rows of tabs, with Message Groups selected and a saved message listed.
Two rows of tabs: where you are on top, what gets said underneath.

The Connector runs on desktop Chrome, Edge, Brave or any other Chromium browser. It does not run on a phone — it works by reading the Facebook page you have open and clicking the same controls you would.

After installing, reload any Facebook tab you already had open. Chrome does not inject an extension into tabs that were open before it was installed, so on an old tab the extension is invisible — and it looks exactly like a bug.

Where the panel opens

There is no button on Facebook's page. Click the extension icon in your Chrome toolbar — pin it from the puzzle-piece menu if you don't see it. On a group's Members tab the full panel opens. Anywhere else it tells you where to go and offers a link to your groups.

That is deliberate. The Connector adds nothing to Facebook's page — not an element, not a stylesheet, not one inline style. Nothing to fight their layout, and nothing to break the next time they ship a change.

The two rows of tabs

The top row is where you are and what has happened: Home, Groups, Logs, Requests. The second row is what gets said: Segments, Message Groups, Settings.

2  The groups you work

A short list of yours, not every group you ever joined.

My groups: saved Facebook groups with member counts, each removable and reorderable.
Save a group once and its member list is one click away.

Under Groups, press Save group while you are in one and it joins My groups — one click to reopen its member list next time. Edit group renames it; Remove takes it off the list without leaving the group on Facebook.

Work one group at a time and give it a few days. A run is scoped to the group it started in, and the numbers in Logs only tell you something once a group has had a fair pass.

3  Where to look

Which part of the group the queue is built from.

On a Members tab, Sections on this page lists the sections Facebook is showing. Members, Members with things in common, and New to the group are on by default.

Admins, moderators, group experts and contributors are always skipped, and that is not a choice. They are a small, mostly-known population, and a targeting tool whose first act is to friend-request the moderators is doing something nobody asked for.

Commenters

Open a post inside the group and the panel offers Scan commenters instead. This is the better source when it is available, and the reason is worth understanding: every other surface judges people on what Facebook says about them — an employer line, a bio. A comment is a sentence they chose to write. Somebody who wrote "I need help with this" is a stronger signal than any job title, and your keywords catch it before anything else is loaded.

Run does both jobs in one press: it scrolls the page the way your own scrollbar would, then reads what it has loaded. It used to be two buttons and the pairing had a trap in it — you could scan a set you had not finished loading and read a tally of the wrong thing.

4  Who to keep

The filters, and which of them run where.

Targeting: keyword chips for CEO and Founder, a saved set, match mode, and a negative keyword.
Keywords, negative keywords and saved sets, with the Run button underneath.

Keywords take a list — type and press comma. Choose Any keyword (one match is enough) or All keywords (every word must appear). Negative keywords are absolute: any match drops the candidate outright.

A word matches anything starting with it. market finds marketing, marketer and marketplace — which is usually what you want, and occasionally not. Put it in quotes for that word alone: "market". Worth knowing before you wonder why plumb matched a plumbing supplier and a plumber's mate.

Countries, US states and Gender narrow it further. Leave a list unticked for anywhere, and leave both genders off to send to everyone.

The card decides who is worth opening; the profile is where the filter really runs. A member card carries a location on only a small minority of rows and never labels it, so filtering on the card would throw away most of a good pool as "unknown". Instead, anybody who passes the cheap check gets their profile opened, and country, state and gender are read from the profile's own Lives in line and public details.

Saved sets

A nine-word keyword list tuned against a real group is work. Name this set keeps it; Saved sets… loads it back. A set holds keywords only — not countries, states or gender. Those are geography, not prospect type: the same "Agencies" words get pointed at Iowa this week and the UK next, and a control that quietly rewrites a filter you set for another reason is one you stop trusting.

Check this profile

Open somebody's profile and press Check this profile. It runs the parser against the page in front of you and tells you what it sees — the fastest way to find out why somebody you expected to match didn't. It opens nothing and sends nothing.

5  Preview first

The whole run, minus the sending.

A run in progress: a LIVE badge, the queue at 4 of 38, counts, and a Stop now button.
A preview looks exactly like this — it just never sends. Name blurred.

Preview — no requests paces itself exactly like a real run, opens every profile and makes every decision. It never clicks Add friend. Do this before every new campaign; it is the cheapest way to find out your keywords are wrong.

The tally names the reason for every row it dropped — Cannot be friend-requested, Section always skipped, Section not ticked, Negative keyword, No keyword on the profile, Already requested, Listed twice on this page — and ends with Would be opened, the ones that survived. Follow-only profiles and people you already know are the bulk of what falls out.

Start with the keywords empty and read the tally, then add one word and preview again. You are looking for the word that keeps the right people and drops the rest, and you will usually find it on the second or third try.

6  Starting a real run

Two presses, with the names in between.

Press Start sending… and you are shown the group, today's remaining allowance, the interval, and the first eight people by name. The run only begins when you press I have read the names — start.

That middle step is not friction for its own sake. Chrome's policy bars sending on a user's behalf "without giving the user the ability to confirm the content and intended recipients" — this is that ability, built on purpose rather than argued around afterwards. It also catches a filter mistake before it costs you fifty requests.

The run tab

A run works in its own pinned tab, opened in the background at the far left. The tab you are reading stays where it is. Closing that tab stops the run — nothing is ever half-finished, because the run advances one page load at a time and its state is written down before each step.

A run in progress is visible from any tab, so you can press Stop now without hunting for the one it is working in. Along the way it tells you what it is doing: Reading the member list, Opening a profile, Reading their About tabs, Found a match, Moving on, Sending, Resting between blocks.

7  The governor

The part that decides whether you still have an account next month.

Pacing settings: wait after they accept, a daily message limit, and the interval between messages.
Every limit says what it is protecting you from.

Everything else here is features. This is the one that matters, and the defaults are Ace's own working practice rather than a theoretical margin:

Daily limit50 requests a day, 100 the ceiling.
How oftenOne request every 3–5 minutes, drawn from a log-normal — not a flat timer. Flat is the one shape human behaviour never has.
Warm-upEases in from 10 a day to your full limit over a week. A fresh install sending its whole quota on day one is the most detectable thing this product could do.
Resting between blocksA 30–45 minute break after every 18 requests.
Between messagesIntro messages go slower than requests — 4–10 minutes apart, 40 a day. Outbound messages to people you just met are the most spam-sensitive thing an account does.
Wait after they acceptHow long somebody is left alone before their message goes out, rolled fresh per person between 20 minutes and 4 hours. A message three seconds after an accept is the most automated thing possible; nobody watches their friend list that closely.
Resting after a dry patchForty profiles in a row that all fail your filters and the run takes a real break. Reading fast and sending nothing still looks like reading fast.
The pause after a sendSix to twenty-five seconds of doing nothing before the next profile opens. A request and an instant page load never happen together when a person is at the keyboard.

Hard stops

A run halts and does not retry on any of these: a checkpoint, a captcha, being signed out, a temporary-block notice, or the Add friend control not responding.

Finding more than one Add friend control on a profile used to be a stop as well. It turned out to be ordinary — Facebook draws them for people in the sidebar too — so the run now matches the control to the name it came for, and moves on rather than halting if it cannot. A whole campaign stopping on something normal is worse than skipping one person.

Leave the defaults alone for your first week at minimum. Raising the limits does not make the tool better at its job; it makes the account more visible, which is the one cost you cannot undo.

8  What gets said

Segments, message groups, and the message that goes out when they accept.

Segments grouped under Intro, Body and Outro headings.
Three parts, written once and reused across message groups.

A message is built from three reusable pieces: an intro that greets, a body that asks, and an outro that closes. Write them under Segments. A Message Group names one of each and is what a run actually sends.

Why in parts: the three wear out at different rates. An opener goes stale long before the ask does, and swapping one segment across every group beats editing eight near-identical messages and missing two.

Editing a segment: spintax in the text field, the syntax help beneath it, and a rendered preview.
The editor renders what one real person would receive, before anybody does.

Spintax and merge fields

{a|b|c} picks one branch at send time. {{first_name}} fills in what is known about the person, and {{first_name|there}} supplies a fallback for when it isn't. This is the same syntax as Legendary Messenger CRM, so an opener you have tuned in one product pastes straight into the other.

Nothing ships with a written message. Nobody's best-performing opener is the one that came with the tool, and seeding a default guarantees a hundred customers sending an identical sentence into the same groups — which is exactly how a pattern gets recognised and a template gets burned.
A message group built from an intro, body and outro, with the assembled message shown underneath.
A group names one of each part; the preview underneath is the result.

Preview follow-up renders a group against a sample name so you can read what a real person receives before anybody does. Send intros… works through everybody who has accepted and is still owed one.

9  Requests

Who was contacted, who answered, and how acceptance is worked out.

Requests sent, with counts and a list of pending people showing which keyword matched each one.
What matched each person is kept, so a good keyword is tellable from a lucky one. Names blurred.

The Requests tab lists people a request was actually sent to, in three states:

  • Requested — sent, still outstanding.
  • Accepted, not yet messaged — they are in, and the intro is queued.
  • Resolved, outcome unknown — the request is no longer pending, and Facebook does not say why.

Check sent requests reads your own pending-requests list. Acceptance is inferred by absence: a request that is no longer pending was accepted, declined, or expired, and the list cannot tell those apart. That is why a disappearance only marks somebody resolved — counting every disappearance as an accept would inflate the one number the whole tool is judged on.

If you have the Messenger CRM too, an accept becomes a lead. The moment a request is confirmed accepted, the Connector hands that person to the CRM — name, profile link, the group they came from, what they matched on, and the two dates — and they land at New Lead, ready to work. It goes extension to extension on your own machine; nothing is sent to us, and nothing is handed over for anybody who never accepted.

Withdrawing

Withdraw… cancels requests that are still pending, optionally only those older than a date you pick. Only requests the Connector sent carry a date it can filter on. Withdrawing cannot be undone, and it is paced like everything else — watch the run rather than closing the tab.

10  Logs

What each run actually did.

A run log: rows scanned, requests sent, filtered out, and a timestamped feed of each decision.
Every run keeps its own log. Names blurred.

Logs keeps a record per run: how many rows were read, how many were queued, how many were requested, and where the rest were dropped — including Keyword yield, which is the number to watch when you are tuning a set.

Those counts are recorded as the scan happens, and they have to be: nobody who failed a filter is stored, so the numbers cannot be rebuilt afterwards from data the tool deliberately never wrote down.

11  Your data

It is on your machine, so back it up.

Everything — groups, campaigns, keyword sets, segments, message groups and your sent-request history — lives in your own browser on your own computer. Full backup (JSON) writes all of it to a file and Restore a backup reads one back. Export requests (CSV) is the narrower one — just who you contacted and what happened — for when you want it in a spreadsheet rather than back in the tool.

Uninstalling removes the data with it, and we have no copy to restore — there is no server-side copy of any of this. Take a backup before you change computers, and before you move to a different browser — Chrome keys storage to one browser profile, so a fresh install starts empty.

12  What it never does

The lines, in one place.

  • It never sends without you arming it. Two presses, with the names in front of you.
  • It never keeps anybody it did not contact. People who fail your filters are counted and dropped in memory. There is no member database, on your machine or ours.
  • It never sends anything about anybody to us. The only host it talks to besides Facebook is Google's sign-in service, which is how it knows you are signed in. Your groups, your keywords, your messages and your request history are never sent anywhere — there is nowhere for them to go.
  • It never posts, comments or reacts as you, and it never messages people who have not accepted.
  • It never modifies Facebook's page. It reads, and it clicks the one control you would have clicked.
The risk that is real. This is an independent tool, not affiliated with or endorsed by Facebook or Meta, and it operates outside Meta's terms for automated tools. Sending friend requests at volume carries a materially higher risk of account restriction than anything Legendary Messenger CRM does. The pacing exists to keep that risk small; it does not remove it, and nobody who tells you otherwise is being straight with you.

Stuck on something that is not here? Write to support@trijohnson.com or call (319) 727-8500, Monday to Friday, 9:00–3:00 Central. This page grows as the product does.