Answer tickets about systems you didn't build
The ticket says "the reactivation campaign isn't sending." You didn't build the reactivation campaign. You don't know if it's one workflow or four, what starts it, or what else touches the same contacts — and the person who built it isn't answering Slack.
The walkthrough
The steps
- 1
Ask Patchy the ticket's actual question. "How does the reactivation workflow work?" The answer comes from this account — its real workflows and settings, not generic GoHighLevel knowledge.
Ask about the account, get an answer grounded in the account. - 2
Follow up like you'd grill the colleague who built it. "What starts it?" "What else sends SMS to those contacts?"
- 3
Check the map before you answer. Everything that feeds the workflow, everything it touches downstream. This is what keeps you from confidently repeating a wrong answer.
The workflow in context — everything that feeds it and everything it touches. - 4
Reply with specifics. Which workflow handles reactivation, what kicks it off, where the behavior in the ticket would come from.
- 5
Then fix it in GHL — arriving at the exact spot, already knowing what's connected to the thing you're about to touch.
Why this changes the ticket
The default way to understand an unfamiliar system is twenty minutes of scanning workflow lists, opening every candidate, and holding the branching in your head — for a two-minute answer, and that's a good day, on a well-named account. The loop above takes minutes, and your reply names real workflows instead of hedging. Knowing what's connected before you touch it is also exactly what prevents the fix on this ticket from generating the next one.
For the team, it means any rep can take any account's ticket. Everyone runs the same loop against the same shared picture of the account, so nobody re-derives the same system knowledge ticket after ticket — and one teammate's vacation stops being a coverage hole. System knowledge stops living in individual heads and starts living somewhere with a search box.
The takeaway
You stop re-learning someone else's system one ticket at a time. Any rep can take any account — and answer with specifics instead of hedges.
FAQ
Does the chat know about our specific account or just GHL in general?
Your specific account. It pulls from what was connected — the workflows, funnels, fields, calendars, and the links between them. "Here's what this account's reactivation workflow does," not "here's how reactivation campaigns generally work in GHL."
What if the account changed since it was connected?
Refresh it. Teams that touch client builds regularly make it part of the routine — after a change sprint, before a busy support week.
Can PatchyHub fix the issue in GHL for me?
No. It tells you what the system is and how it connects; the fix happens in GHL, by you. Nothing in the GHL account gets modified.