Intern
What you actually do
Audit the channel vs the record. Fix missing owners. You are not 'keeping Slack tidy'. You are making Slack optional.
Library / Wire / Slack is a hallway. It cannot be the pipeline, the router, or the payment ledger.
Slack (and Teams) feel like speed. They are how routing, lead assignment, Stripe pings, and 'who is taking this' never become objects. Wire Slack as notifications with links to GHL contacts — or as nothing. Assignment, stages, and next dates live on the record. This is the anti-wire: what must stop being a Slack habit, and what a bot is allowed to do.
Slack (and Teams) feel like speed. They are how routing, lead assignment, Stripe pings, and 'who is taking this' never become objects. Wire Slack as notifications with links to GHL contacts — or as nothing. Assignment, stages, and next dates live on the record. This is the anti-wire: what must stop being a Slack habit, and what a bot is allowed to do.
If a new hire cannot reconstruct last week’s pipeline from GHL without Slack search, Slack is the CRM. That is a failure of write-in and owners.
Routing rules belong in GHL (user assignment, round-robin, overflow). Slack is a hallway to hear the bell, not the bell.
Bots that post lead dumps without a contact link train people to work the channel. Every ping should deep-link the record.
Private DMs about a lead are how stolen leads and dropped leads happen. If it must be discussed, the next date still hits the contact.
You will not 'ban Slack'. You will ban Slack as source of truth. The test is whether Monday numbers require Slack archaeology.
Intern
Audit the channel vs the record. Fix missing owners. You are not 'keeping Slack tidy'. You are making Slack optional.
Operator
Hallway vs system. Routing in GHL. Pings are links. Payments are write-in. Do not reward thread memory.
CEO
If the company cannot run a Monday review without Slack search, you do not have a CRM. Owner-on-create and Won-without-Slack are the numbers.
Slack channel, notification bot, GHL contact URL, owner field, opportunity, Stripe/Slack ping (demote), lead assignment rules in GHL, after-hours, search vs record.
Allowed: Slack pings a URL to the GHL contact when a lead arrives — assignment already happened in GHL
Forbidden: first assignment in Slack ('I’ll take it') with no owner on the contact
Forbidden: Stripe paid only in #payments with opportunity still open
Forbidden: lost/won decided in a thread that is not written to lost_reason / Won
#leads, #payments, #routing, founder DMs. What decision happens there that GHL does not see.
Why: Unnamed habits cannot be replaced.
Done when: Inventory of channels and the GHL object they should update.
Round-robin or explicit owner on create. Slack may notify the owner. 'I’ll take it' in Slack is invalid unless they also own the record within minutes.
Why: Channel assignment is how speed-to-lead becomes politics.
Done when: A test lead has an owner without a Slack message. Slack is optional notify.
Rewrite bots: include GHL URL, stage, source. No paste of PII walls that become the working copy.
Why: Working the paste means the record stays stale.
Done when: A test ping is unusable without clicking through — and the record is already complete.
Stripe write-in to GHL is the ledger. Slack payment pings can exist as noise, not as Won.
Why: Celebrating in Slack while the opportunity is open is two books.
Done when: A $1 test Wons in GHL even if Slack is muted.
Show rate, owners, lost reasons from GHL. If someone says 'it was in the thread', that contact is incomplete — fix the record, do not praise the thread.
Why: What you reward (clever Slack memory) is what you will get instead of a CRM.
Done when: A review meeting that does not require Slack. Exceptions are tickets.
Sit in #leads for a day. Every item: is there a GHL owner and URL? Where missing, that is the ticket. Change the bot to link records. Mute working from the paste. Confirm payments Won in GHL with Slack closed.
A Slack workflow builder, more channels, or a 'RevOps Slack app' until assignment and Won exist without the hallway. Paying to make Slack a better CRM is paying to avoid GHL.
Lead Zap to Slack. Humans claim in-thread. Stripe to #payments. Lost reasons never. Monday is archaeology. GHL is for 'when we have time'. That time does not come. That is a hallway with invoices.
Lead owned in GHL without Slack. Ping links the record. Payment Wons with Slack muted. Monday board needs no thread search.
Owner on create is as fast as a ping if assignment is automatic. Slack feels fast because it skips the record. You pay later in dropped leads.
Different object (community). Still: member state in GHL. Community Slack is not the sales pipeline.
After-hours should create GHL state and an honest SMS. Waking a human in Slack is extra, not the system.
This week
This week: inventory Slack-as-CRM habits, GHL assignment first, bots link records, #payments demoted, Monday from the board. No new lead channels.
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 ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.