GoHighLevel lead routing: the right phone, not a shared inbox

A text nobody owns is not routing

Speed-to-lead without routing is a text that nobody is responsible for. Routing without speed-to-lead is a named owner staring at a lead that went cold an hour ago. You need both. The clock is five minutes. The name on the contact is who we will ask about the stall.

GHL can assign users, round-robin, notify, and move pipelines. What it cannot do is invent a salesperson you do not have. If no human can take a booked conversation, this is the wrong product — I will say that on the diagnostic. Who it is for is operators who already get inbound and lose the minutes after the hand-raise.

Pick a routing rule and write it down

Sticky owner: if they already had a conversation, they go back to that person. Right for membership intros, high-ticket, and any close where repeating the story is disrespect. Wrong when that person is in the field with no backup and the lead is a same-day visit.

Round-robin (or weighted): fair load across people who can actually close this offer. Right for site visits with three closers. Wrong if only one of them is allowed to quote. Weights should match skill and hours, not politics.

Source or offer based: stays go to hospitality, workshops go to the farm shop, ads from campaign A go to the closer who knows that offer. Right when the close is a different sport. Wrong when it is an excuse to build eight inboxes again.

After-hours: the workflow is the owner for the first reply; a human is the owner in the morning, or a night-shift phone is named. Missed-call text-back is routing for the oldest channel. A voicemail box is not routing. It is a grave.

Notifications that buzz vs notifications that decorate

Email to a shared inbox is how 9:41pm dies. App push, SMS to the owner, or a phone call for high-intent offers — pick one that reaches a pocket. Internal GHL notifications should include source, offer, and a link to the contact. “You have a new lead” with no context is how people ignore the app.

Do not route by putting every lead in a WhatsApp group. Groups are not assignment. Nobody owns a group. The CRM owner field is the assignment. Chat can be a copy of the ping, not the system of record. CRM setup is where users exist as people, not as info@.

Office-hours tables in GHL are only useful if they match the closer’s real life. A 9–5 table on a homestay that takes inquiry calls at 8pm is how nights get assigned to a workflow that thinks it is “closed” and waits until morning. Either extend hours or name the after-hours owner. “We’ll check the app” is not a table. If the closer is in the field, the catch workflow still texts; the human still owns the thread when they have signal. That is the farm constraint, not a special feature.

If two people get the same lead, you will double-text. If zero people get it, you will praise the workflow while the human shops the next tab. Test routing by submitting as a stranger after hours, not by asking the team how they “usually handle it.”

Routing is a workflow, not a vibe

Implementation is a workflow: on enroll, assign user, notify, set SLA stage, optionally create a task with a due time that matches the five-minute line. If they book, assignment may stay sticky for the appointment. If they no-show, the same owner recovers unless you have a recovery specialist — say so.

Pipeline stages should show whether the owner acted. A card in “new” with an owner and a timestamp is honest. A card in “new” with no owner is the leak. See pipelines. Reporting on Core looks at stalled cards by owner, not only by stage. That is uncomfortable and it is the point.

Lead scoring on Growth is only useful after routing is true. Scoring into a shared inbox is a ranked pile. Scoring onto a named closer with an SLA is a queue.

• A written rule: sticky, round-robin, source-based, or after-hours split
• Users as people, with phones that buzz
• Workflow assignment + notification on the catch
• No shared-inbox-as-owner
• A stranger test after hours before we call it live

Agencies, round-robin, and “we’ll take anything”

If you are an agency using GHL as the OS, routing might mean account managers, not sales closers. Same rules: named human, SLA, no group chat as CRM. If you sell for multiple locations, location tags plus routing matter or you will send a downtown closer to a coastal listing.

We are not a generic white-label staffing desk. We install routing in your account. You keep the conversation when a human should jump in. If you wanted us to answer every guest chat as your brand 24/7, say that on the diagnostic — that is a different job than a lead system.

Where this sits on Setup, Core, and Growth

Setup includes the catch path and tagging so source stays attached, plus pipeline owners as part of structure. Simple routing (one owner, or a small round-robin that matches reality) ships with the install. Core operates assignment hygiene and the report that shows stalled by owner. Growth adds missed-call text-back, chat widgets into GHL, scoring, ads that must land on the same routing rules so a $40 click is not assigned to nobody.

Ad spend still sits on your ad accounts. We will not scale spend into a routing hole. Catch and routing before traffic is the whole leak argument.

Worked example: one closer, two listings, nights

A homestay operator has two properties and one human who can confirm stays. Sticky owner is that human. Round-robin would be a lie. After hours, the catch workflow texts both listing inquiries in minutes with the right listing tag and a calendar or two-question path (dates, guest count). The owner field is still the human. Morning is a conversation tab filtered to last night, not a shared inbox called bookings@.

If they hire a second closer for one listing, then we split on listing tag: listing A sticky to person A, listing B to person B, with a backup if someone is on site without signal. Calendar round-robin must match that split or the ping goes to the person who cannot actually confirm the room. This is the same rule as a two-location service business. Source tags (Google vs Instagram) do not get their own owners unless the close is actually different.

Missed calls at 9:41pm: Growth text-back creates the contact with source = missed call, listing unknown until they reply. Routing still assigns the default closer. When they name the listing, a workflow can reassign. Do not wait to text until the listing is known. The ring was the hand-raise. Silence is the other listing’s closer.

Failure modes

Round-robin includes a user who left the company. Sticky owner is someone on leave. After-hours routing emails a desktop Outlook. Facebook lead ads create contacts without a phone so SMS routing silently no-ops. Calendar round-robin and lead round-robin disagree, so the person who got the ping is not the person who got the booking.

These are operate bugs as much as setup bugs. Monthly operate is how we see them in days. If your only routing doc is a Notion page last edited in 2024, you do not have routing. You have folklore.

Next step

If inbound already exists, we timestamp the first reply, name the owner, and put assignment in a workflow. That is diagnose plus automate. Apply — four steps, 20-minute diagnostic, no retainer required on that call. shaz@shazmethod.com if you already know the shared inbox is the leak.

FAQ