Intern
What you actually do
Day one: SMS, FB, IG, and the phone are four inboxes — put them in Conversations or admit which channel is off-system. Name the owner by hour. Test STOP. Do not add a fifth channel. Threads on the contact.
SMS in GHL, Instagram in Meta, the phone on a cell, WhatsApp on someone's laptop. A reply in one channel never moves the pipeline. STOP is folklore. After hours, nobody owns the queue.
Read it once, then stop negotiating with it. Conversations inbox for franchise systems is a wiring job: channels → rota → write-in → keywords. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Franchise systems do not have a Conversations inbox problem because they lack GoHighLevel. They have it because sMS, FB, IG, and the phone are four inboxes. None of them own the contact.
Wire these objects first: GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification.
Then these edges, in order: Any channel inbound → same contact thread; no orphan Facebook-only ghost · Shift owner → one human per hour; unread is a number · Reply (human or keyword) → opportunity stage moves when the journey says so · STOP/YES → handled across SMS; social still needs a human for the messy middle
Done looks like a test you can repeat: Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak.
Start here: One inbox owner per hour
Franchise systems already have GoHighLevel. The leak is not a missing feature. SMS, FB, IG, and the phone are four inboxes. None of them own the contact. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification. Then connect these edges, in order: Any channel inbound → same contact thread; no orphan Facebook-only ghost · Shift owner → one human per hour; unread is a number · Reply (human or keyword) → opportunity stage moves when the journey says so · STOP/YES → handled across SMS; social still needs a human for the messy middle. If you skip an edge, the next one is decoration. If you add a GoHighLevel feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak. How you know it worked on the board: Owner is named (per block on the rota). If that number is a vibe, do not add traffic.
What to do this week, and only this week: One inbox owner per hour An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: SMS, FB, IG, and the phone are four inboxes — put them in Conversations or admit which channel is off-system. Name the owner by hour. Test STOP. Do not add a fifth channel. Threads on the contact.
Operator
You already feel sms, fb, ig, and the phone are four inboxes. none of them own the contact. SMS, FB, IG, and the phone are four inboxes. None of them own the contact. Protect one sequence for 90 days. The four moves are channels → rota → write-in → keywords. The edges are Any channel inbound → same contact thread; no orphan Facebook-only ghost then Shift owner → one human per hour; unread is a number. One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night.
CEO
This is a money leak, not a preference about tools. SMS in GHL, Instagram in Meta, the phone on a cell, WhatsApp on someone's laptop. Until owner is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Any channel inbound → same contact thread; no orphan Facebook-only ghost.
Before
Tuesday. Someone among franchise systems. SMS, FB, IG, and the phone are four inboxes. None of them own the contact. GoHighLevel is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night. Any channel inbound → same contact thread; no orphan Facebook-only ghost The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in franchise systems already paid for GoHighLevel. SMS, FB, IG, and the phone are four inboxes. None of them own the contact. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. One inbox, one owner per hour, one contact per person. Prove write-in: Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak. This week is one move: One inbox owner per hour If that feels too small, that is the point. Operators fail by starting at move four.
The leak
SMS in GHL, Instagram in Meta, the phone on a cell, WhatsApp on someone's laptop. A reply in one channel never moves the pipeline. STOP is folklore. After hours, nobody owns the queue.
The system
One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night.
Connect the channels you actually use — SMS, FB/IG, Google, WhatsApp if you have it — into Conversations. Then write a rota: who is on the inbox 9–12, 12–5, after hours. A tool without an owner is a pile.
Build two workflows only: inbound creates/updates a contact and notifies the owner; keywords STOP/YES do what they must. Do not automate the conversation until a human can find the thread.
One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night.
SMS, FB, IG, and the phone are four inboxes; none of them own the contact. Conversations is the object that unifies them onto a person, with one inbox owner per hour. A reply moves the pipeline when that is the journey. STOP and YES are handled, and the thread lives on the contact. If IG sits in Meta's inbox and SMS in GHL, you will miss one — that miss is a lead.
Wire channel connections and identity matching (phone, email, FB id). Merge rules when a later form reveals email for an IG lead. After-hours: a truthful auto-reply, still in the thread. Templates per channel tone, but the same CRM stages. Do not let a chatbot close high-ticket without a human path — write that rule.
Two databases: Meta inbox and GHL, or a ring-central app and GHL. The intern watches unread count at shift start and end. They do not 'catch up tomorrow' without a number. If everyone is owner, no one is. The shift roster is the system. Unread at 50 is an incident, not a busy day.
GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification.
Any channel inbound → same contact thread; no orphan Facebook-only ghost
Shift owner → one human per hour; unread is a number
Reply (human or keyword) → opportunity stage moves when the journey says so
STOP/YES → handled across SMS; social still needs a human for the messy middle
Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak.
Day one: SMS, FB, IG, and the phone are four inboxes — put them in Conversations or admit which channel is off-system. Name the owner by hour. Test STOP. Do not add a fifth channel. Threads on the contact.
The channels you use land in one Conversations view.
Named owner per block. After-hours is a person or a text-back.
A new thread creates or matches a contact.
STOP and YES are tested, not assumed.
On one line, for franchise systems: SMS, FB, IG, and the phone are four inboxes. None of them own the contact. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
The channels you use land in one Conversations view. Then wire: Any channel inbound → same contact thread; no orphan Facebook-only ghost
Why: Franchise systems cannot skip this edge. SMS, FB, IG, and the phone are four inboxes; none of them own the contact. If it is not true, GoHighLevel is already a second database.
Done when: Any channel inbound → same contact thread; no orphan Facebook-only ghost is true on a test.
Named owner per block. After-hours is a person or a text-back. Then wire: Shift owner → one human per hour; unread is a number
Why: Franchise systems skip this and the leak returns as a private language. Wire channel connections and identity matching (phone, email, FB id). Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Shift owner → one human per hour; unread is a number is true on a test.
A new thread creates or matches a contact. Then wire: Reply (human or keyword) → opportunity stage moves when the journey says so
Why: Franchise systems feel this as SMS, FB, IG, and the phone are four inboxes. None of them own the contact. Two databases: Meta inbox and GHL, or a ring-central app and GHL.
Done when: Reply (human or keyword) → opportunity stage moves when the journey says so is true on a test.
Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Owner (Per block on the rota), then thread on contact (Or the hire starts from zero). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
One inbox owner per hour
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification.
If objects aren't named, software invents a second database.
SMS, FB, IG, and the phone are four inboxes. None of them own the contact.
The channels you use land in one Conversations view. Then wire: Any channel inbound → same contact thread; no orphan Facebook-only ghost
Franchise systems cannot skip this edge. SMS, FB, IG, and the phone are four inboxes; none of them own the contact. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how franchise systems actually work — not the snapshot demo. Edge: Shift owner → one human per hour; unread is a number
Named owner per block. After-hours is a person or a text-back. Then wire: Shift owner → one human per hour; unread is a number
Franchise systems skip this and the leak returns as a private language. Wire channel connections and identity matching (phone, email, FB id). Spec tags, fields, and states have to be the same objects the next workflow will read.
One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night.
A new thread creates or matches a contact. Then wire: Reply (human or keyword) → opportunity stage moves when the journey says so
Franchise systems feel this as SMS, FB, IG, and the phone are four inboxes. None of them own the contact. Two databases: Meta inbox and GHL, or a ring-central app and GHL.
One inbox owner per hour
Because the login already exists. SMS in GHL, Instagram in Meta, the phone on a cell, WhatsApp on someone's laptop. A reply in one channel never moves the pipeline. A new feature on a missing spec is a second database. Finish this edge first: Any channel inbound → same contact thread; no orphan Facebook-only ghost.
Day one: SMS, FB, IG, and the phone are four inboxes — put them in Conversations or admit which channel is off-system. Name the owner by hour. Test STOP. Do not add a fifth channel. Threads on the contact. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. STOP (This is not optional) is how you stop the leak returning dressed as a new feature. Start with how you actually sell, not with how the snapshot was demoed. Name stages as jobs, not moods. Separate source, offer, and status. If a new hire cannot explain a contact in thirty seconds, you do not have an operating system — you have a database with anxiety on top.
More leads into a leak is a more expensive leak. One inbox, one owner per hour, one contact per person. A reply can change a stage. STOP and YES are handled. The thread is on the contact so a Tuesday hire can read Friday night. Watch owner before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. One inbox owner per hour That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because GoHighLevel is “set up”.
Do this
GHL Conversations (SMS, FB, IG, calls, email if used), shift owner, reply-moves-pipeline, STOP/YES, thread on contact, channel unification.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Any channel inbound → same contact thread; no orphan Facebook-only ghost
Skip this
Calling it done because a screenshot looks busy.
Do this
Send yourself an SMS, an IG DM if connected, and a Facebook message if connected. Confirm they land on one contact if identity matches, or can be merged. Assign this hour's owner. Reply; confirm pipeline. Four inboxes is the leak.
Skip this
Leaving “Keywords” to chance.
Do this
STOP and YES are tested, not assumed.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
The channels you use land in one Conversations view. Then prove write-in: Send yourself an SMS, an IG DM if connected, and a Facebook message if connected.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Any channel inbound → same contact thread; no orphan Facebook-only ghost first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Owner: Named. Per block on the rota. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Owner
Named
Per block on the rota
Thread on contact
Yes
Or the hire starts from zero
STOP
Tested
This is not optional
This week
One inbox owner per hour
One inbox owner per hour
A reply moves the pipeline
STOP and YES are handled
The thread lives on the contact
Want the longer lesson, not the page for this niche? SMS has to be two-way ↗
Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Conversations inbox does not split by niche and city. The wiring is the same: objects, edges, one test conversion. Read a connect map if two tools are already in the stack, or a vertical essay if the language needs to change.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗Locations will edit sacred pipelines unless permissions and a change log exist.
Read ↗New patient, recare, and unscheduled treatment are three journeys. One 'we miss you' is not a DSO.
Read ↗Call volume is national. Booking is local. Drift is how you pay for ads twice.
Read ↗Email and WhatsApp stay open. A call is for installing the system.