Questions into content
The six auto-resolution triggers are, in order, the six things your audience most wants explained. Each one is a post, and the volume against each keyword tells you which to make first.
The whole system on one page: every pipeline stage, what fires when somebody enters it, and the exact place in GoHighLevel that thing lives. This is a working map, not a summary. Keep it open beside your account and you can build straight off it, stage by stage.
Five layers, stacked. The pipeline is the floor and nothing above it works without it. Read down, build up.
A stage is a place a person can be, not a label for how you feel about them. If you cannot say what fires when somebody lands in a stage, it is not a stage yet.
| Stage | Entered when | What fires | Exits to |
|---|---|---|---|
| 1. New | Contact created from any source | Source tag applied, contact record built, acknowledgement SMS inside ten minutes. | Routed, on reply |
| 2. Routed | The routing question is answered | Answer tag applied, one of four destinations picked, the matching run starts. | Primed |
| 3. Primed | Routing run begins | The four-message DM framework. Message three gives something unconditionally. | Engaged or Dormant |
| 4. Engaged | Any human reply | All automation halts. The conversation is handed to a person, not a workflow. | Booked or back to Primed |
| 5. Booked | Call appears on the calendar | Confirmation, reminder at 24h, reminder at 1h, pre-call video. Every sequence exits. | Client, or no-show branch |
| 6. Client | Payment clears | Onboarding run: pre-session videos, intake form, first check-in scheduled. | Stays, with CSM layer on |
| 7. Dormant | Eight touches, no reply | Long nurture only. One touch a fortnight, no asks, no countdowns. | Back to New, on any reply |
A person moves stage because something happened, never because you decided they felt warmer. Every row above has an event in the second column. If you add a stage and cannot fill that column, the stage is a feeling and it will rot.
Everything arriving from any source hits the same question, and the answer decides the route. Four answers, four destinations. You build the table once and stop making the decision.
| Answer | Tag | Route | First message out |
|---|---|---|---|
| Just starting out | stage-foundation | Long nurture | The free resource. No call ask for at least a fortnight. |
| Have clients, no system | stage-chaos | Short priming | The pain-point SMS, then the pre-call video. |
| System exists, it leaks | stage-operator | Straight to booking | Booking link in the first reply. No warm-up needed. |
| Silent 48 hours | no-reply-48 | Re-ask once | Same question, shorter. Then the run exits for good. |
Sources feeding this: Instagram comments and DMs, the bio link, the application form, inbound SMS, and the masterclass registration itself. All five land on the same question, which is why one table can route the lot.
Most builds stop at the sale. The stages below are the ones that decide whether somebody is still a client in month three, and they are the cheapest part of the whole system to automate.
It is not a bot handling your clients. Every branch above ends by putting information in front of you faster. The flag on two missed check-ins does not send a message, it tells you to.
A large share of inbound is the same six questions. Each one gets an answer that fires on a keyword and closes itself out. Anything that is not on this list goes to a human immediately rather than being guessed at.
| Trigger | Resolves with | Closes itself |
|---|---|---|
| Price, cost, how much | The pricing page link and the one-line answer | Yes, unless they reply again |
| Reschedule, move my call | The reschedule link, calendar updated on use | Yes |
| Where is my login | Access link re-sent to the email on file | Yes |
| Cancel, refund, pause | Nothing automated. Flagged to a person inside the hour | No, on purpose |
| Is this for me | The routing question from layer two | No, it routes |
| Anything unmatched | Straight to the inbox with the full thread attached | No |
Automate the answer you would give identically every time. The moment the right answer depends on who is asking, it goes to a person. Row four is in this table specifically to say that some things must never auto-resolve.
Once the four layers below it are running, the system knows things worth using: which questions come up most, which objection kills the most deals, which check-in answers repeat. That is a content calendar and a product roadmap, sitting in your CRM already.
The six auto-resolution triggers are, in order, the six things your audience most wants explained. Each one is a post, and the volume against each keyword tells you which to make first.
The objection that shows up most in Engaged conversations becomes touch five of the follow-up run. You are not guessing at what to pre-empt, the pipeline already told you.
The same problem in twenty check-ins is a product. This is the honest version of market research: it is already logged against contacts, it just needs reading.
This layer needs volume underneath it to say anything true. Run layers one to four for a few weeks first. A content calendar generated from nine contacts is a calendar built on noise.
Every piece named above, and the place in your account you actually build it. This is the column people ask for after the session, so it is on the handout.
| The piece | In GoHighLevel | Notes |
|---|---|---|
| The seven stages | Opportunities › Pipelines | One pipeline, seven stages, built before any workflow exists. |
| Source and answer tags | Contacts › Tags | Keep the naming flat and lowercase. Tag sprawl is what makes routing unreadable a year later. |
| The routing question | Automation › Workflows | Trigger on inbound reply, condition on the answer, four branches out. |
| The four-message DM run | Automation › Workflows | Message one left as an editable field on purpose. |
| The eight touch sequence | Automation › Workflows | Build the exit conditions before any of the eight messages. |
| Booking, reminders, no-show | Calendars | The no-show branch is separate. Without it no-shows leave the pipeline silently. |
| Auto-resolution keywords | Automation › Triggers | Keyword in, canned reply out. Unmatched goes to the inbox untouched. |
| Check-in loop and forms | Sites › Forms with Workflows | Answers write back to the contact so layer five can read them later. |
| Drip and countdown | Memberships and Workflows | Relative to join date, never a fixed calendar date. |
| Payment on application | Payments | In-account, so the Client stage can trigger on the payment event itself. |
Five steps. Each one is finished before the next starts, and the second one is the one to do tonight if you only do one.
Seven stages in one pipeline. Move three real contacts through them by hand before automating a single move.
Four answers, four tags, four destinations. Fire it at your own number once before it touches a real conversation.
Four messages, structure automated, sentences yours. Message three gives something with nothing attached.
Exits first, then the messages. Reply, booking, purchase and unsubscribe all end the run.
Booking, both reminders, the no-show branch, then the onboarding run that fires on payment.
Auto-resolution once you can see which six questions repeat. Generation once there is enough volume to read.
This map is the handout. The masterclass walks the same five layers and then builds steps one to five on screen in a real account. Free, 60 to 90 minutes, no live dates.
Read the full sessionAR Funnel · GHL Masterclass · The GHL Second Brain system map · Attendee handout