Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
AI Automation Society Plus

3.7k members • $129/month

AI Automation Agency Hub

333.7k members • Free

Agency Owners

20.7k members • Free

AI Agent Developer Academy

2.9k members • Free

GoHighLevel w/ Robb Bailey

13.5k members • Free

Automatable Free

23k members • Free

AI Automation Society

448.9k members • Free

Agentic AI Content

310 members • $58/month

27 contributions to GoHighLevel w/ Robb Bailey
First outreach gone wrong?
I positioned my offer as a i am a beginner but full of energy vibes and i got lot of responses but as time went on i realised the ones that i selected didnt followup at all, didnt give me really anything to work with, just empty promises for weeks, how would i filter these people? I wanted to start with a strong beggining but i feel its a hit or miss that i trust them or not..
1 like • 1d
The positioning is what did this to you. Leading with beginner but full of energy gets a lot of replies precisely because it costs the other person nothing to say yes. People with no budget and no urgency will happily let an eager beginner hang around for free. So you did not get bad luck, you got exactly the people that offer selects for. The filter that works is not reading character, it is asking for something small and concrete early and watching what happens. Not necessarily money. Pick a specific time on a specific day and make them confirm it. Ask them to send you their last three months of leads, or give you access to their account. Anyone who will not do a two minute thing is never doing the twelve hour thing. That single test sorts almost all of them and it takes a day, not weeks. The other half is on your side: stop chasing after two follow ups. Send the second one, then say something like sounds like the timing is not right, I will leave it with you, and actually leave it. Half of the empty promise people come back when the pressure of you chasing is gone, and the other half were never going to. And charge something, even small. Free means nobody on their end has to justify the project to themselves. The first client I charged a real deposit was also the first one who answered my messages the same day.
How did your database reactivation go?
For everyone who's done a database reactivation before. How did your first campaign go and what did you learn? Would love to hear your experiences.
1 like • 2d
The messaging advice above is right, so I will add the boring part that actually bit me. First DBR I ran was for a med spa. Replies were fine. The campaign still fell apart because nobody at the front desk was ready for it. We sent to roughly 1,800 contacts in one shot, a wave of replies landed inside twenty minutes, and the receptionist was already buried with walk ins. Half those people never got answered, which is worse than not sending at all, because you just reminded them that you ignore them. Now I drip it a few hundred a day and I make the client tell me who is actually on the phone that day before I switch anything on. Other thing nobody warns you about is list hygiene. Dead numbers, landlines and people who opted out through some older system will wreck your deliverability quickly. Scrub before you send, and warm a new number over a few days instead of blasting from it cold.
Past Clients Review Requests
Hi guys, i want to ask about review automation, i just can't wrap my head around it for some reason, lets say i got a client, do i send review requests to his old happy clients via email or sms? and most importantly, how? what access do i need? what kind of info do i need from him? do i need his google account details so i can send messages from his email? The main thing which is the automation itself i think is easy, but these things inside i can't understand and i already did research and watched some video. Thanks
2 likes • 5d
Some do, mostly because it sounds like you are asking for tax paperwork out of nowhere. Two things killed that friction for me. EIN is not really sensitive, it sits on public state filings, so I say that up front and it stops being a big deal. And for DNS I never ask for the registrar login. I send them the exact records to add and tell them to forward it to whoever built their site, five minutes and they keep control of the domain. The framing that works is that this is not you wanting their data, it is the carriers and the inbox providers requiring the business to be verifiable before they let anything through. Once it reads as compliance instead of an agency asking for stuff, they hand it over fast. The one that actually stalls you is a client with no EIN. Sole prop 10DLC exists but the throughput cap is way lower, so find that out before you promise a send volume.
1 like • 3d
@Moe Zuh Anytime man. One last thing that saved me a bunch of back and forth: put the DNS records in the message body as plain text, not a screenshot or an attachment. Half the time they forward it straight to their web guy and a screenshot means he has to retype it and typo the value. Good luck with the reactivations.
What's your Biggest Roadblock?
Curious what's actually holding y'all up right now. Not the textbook answer, the real one. Is it: - Knowing WHO to reach out to in your niche - Actually getting on the phone/DMs and saying the thing - Tech setup (workflows, automations, GHL) - Just plain confidence, imposter stuff Drop it below. No wrong answer, and I promise somebody else in here has the exact same one and just hasn't said it yet. Bonus points if you tell us what niche you're in when you comment, let's see who else is playing in your space.
What's your Biggest Roadblock?
1 like • 7d
Honest one: the gap between building and selling. I am on the dev side, so when a week gets uncomfortable I will happily go refactor something instead of talking to a person, and it feels like progress because there is a commit at the end of it. Nothing gets built by accident. Conversations do. The thing that actually broke it for me was making the day's scoreboard a conversation count instead of a to do list. Not calls booked, not leads, just did I say something to a real human today. Below three and the day did not happen, no matter what got shipped. I mostly work with agencies and service businesses on the automation and backend side. @Remy Thevenot on the procrastinating one, home services is a good spot for this because your list is public and finite. Pick one trade in one city and just write down twenty names by hand tonight. Procrastination for me was almost never fear of the call, it was not knowing exactly who was next when I sat down. A named list of twenty kills that entirely.
The operational stack that keeps our GHL fulfillment from bottlenecking
When you are scaling a GoHighLevel business, closing clients or bringing in sub-account users is only the first step. The real challenge is managing day-to-day fulfillment, keeping track of custom snapshots, and ensuring client projects actually cross the finish line without operational chaos. Once you have multiple sub-accounts spinning up, bouncing between fragmented spreadsheets, task trackers, and chat channels can completely stall delivery speed. The lean tool stack that keeps the back end running cleanly while GHL handles the front end: - GoHighLevel – Managing the core engine: high-converting funnels, automated follow-up sequences, snapshots, and client CRM management. - Floment – A unified workspace and community setup that tracks daily to-dos, project cards, and build progress so team execution stays on pace without getting lost. - Loom – Fast async walkthroughs for snapshot handoffs, sub-account setup reviews, and training clients without booking endless alignment calls. - Notion – Centralizing agency SOPs, onboarding frameworks, and snapshot documentation vaults so the fulfillment team always has quick access to reference assets. - Make / Zapier – Connecting custom webhook logic and passing external data into GHL workflows cleanly. - Keeping client pipeline management separated from a dedicated, distraction-free execution workspace makes scaling up sub-accounts significantly easier. For those managing multiple sub-accounts and client builds, what does your back-end fulfillment stack look like right now?
0 likes • 10d
Snapshot drift is the one that cost me the most hours, and what finally fixed it was giving up on the idea of a single master snapshot. Now the base snapshot only holds the stuff no client ever touches. Pipeline stages, custom field names, the calendar shell. Everything client specific gets pushed as separate workflows. Because the base barely changes, a push stops nuking work somebody did last Tuesday. One thing I would bolt onto that stack: a plain changelog per sub account, one line every time anyone pushes anything. Reads like busywork right up until a client says the automation stopped working and you can tell in ten seconds whether that is real or somebody on their team toggled a workflow off. Before that I was reconstructing it from memory and usually guessing wrong.
1-10 of 27
Vedant Heda
3
42 points to level up
@vedant-heda-7202
22 y/o entrepreneur from Dubai | more than five figures in developed systems | Software developer building AI-driven products & automation tools

Active 11h ago
Joined Jun 23, 2026
Dubai
Powered by