- Build small, single-purpose workflows with clear names instead of one large workflow.
- Every outreach workflow needs stop conditions for replies, bookings and opt-outs.
- Start with lead response, booking and no-show workflows; they pay off fastest.
- Internal alert workflows are as valuable as customer-facing ones.
- Test each workflow with a test contact before publishing.
GoHighLevel’s workflow builder can automate almost anything, which is exactly why many accounts end up with dozens of half-finished, overlapping workflows. These fifteen examples are the ones we build most often for service businesses. Each is small, does one job and is named so anyone on your team can understand it.
Lead capture and response
1. Instant reply to new form leads
Trigger: form or survey submitted. Actions: send a personalized SMS and email within a minute, create an opportunity in “New lead,” assign an owner and notify them. Stop: not needed; it runs once.
2. Facebook and Google lead ad response
Trigger: Facebook lead form or Google lead form submitted. Actions: same as above, plus a source tag for reporting. Ad leads cool quickly, so this should fire immediately, around the clock.
3. Missed-call text-back
Trigger: call status is missed or no-answer. Actions: short wait, SMS asking how you can help, internal alert. Full setup in our missed-call text-back guide.
4. 14-day lead nurture
Trigger: tag “nurture” added (by workflows 1 and 2). Actions: spaced SMS, email and call tasks over two weeks. Stop: reply, appointment booked or stage change. We detail the cadence in how to automate lead follow-up.
Booking and appointments
5. Appointment confirmation and reminders
Trigger: appointment status booked. Actions: confirmation now, reminder 24 hours before and 2 hours before, with an easy reschedule reply. Move the opportunity to “Booked.”
6. No-show recovery
Trigger: appointment status no-show. Actions: friendly SMS within 15 minutes with a rebooking link; a task for the team if there’s no reply in a day.
7. Cancellation and waitlist fill
Trigger: appointment cancelled. Actions: notify the team and text contacts tagged “waitlist” that a slot opened, booking the first to accept.
Sales pipeline
8. Quote or estimate follow-up
Trigger: opportunity moved to “Estimate sent.” Actions: check-ins at day 2, 5 and 10 asking if there are questions. Stop: stage changes to Won or Lost.
9. Stale opportunity alert
Trigger: opportunity unchanged in a stage for a set number of days. Actions: internal notification and task for the owner. This catches deals that silently go cold.
10. Lost-reason capture
Trigger: opportunity marked Lost. Actions: require or prompt for a lost reason, add a tag and enroll in a long-term reactivation list after a delay.
After the sale
11. Review request
Trigger: opportunity Won or job marked complete. Actions: thank-you message, review link, one reminder if not clicked. Route negative replies to a manager.
12. Referral request
Trigger: review left or positive reply. Actions: a week later, invite them to refer a friend with a simple message.
13. Recurring service reminders
Trigger: date-based, such as 6 or 12 months after a service. Actions: reminder to book maintenance, a cleaning or an annual checkup.
Internal operations
14. Speed-to-lead alert escalation
Trigger: new lead with no outbound reply after 5 minutes during business hours. Actions: escalate to a manager by SMS or Slack. Pair this with our speed-to-lead automation approach.
15. Daily pipeline summary
Trigger: scheduled daily. Actions: send owners a summary of new leads, booked appointments and stale deals, so nobody has to dig through dashboards.
Which workflows to build first
| Priority | Workflows | Why |
|---|---|---|
| Week 1 | 1, 2, 3, 5 | Instant response and reminders recover revenue immediately |
| Week 2 | 4, 6, 8 | Follow-up and no-show recovery convert more of the leads you have |
| Week 3 | 9, 10, 11, 14 | Pipeline hygiene and reviews protect long-term growth |
| Later | 7, 12, 13, 15 | Optimization once the core is stable |
Testing and maintenance
- Create a test contact with your own phone and email, and run each workflow end to end before publishing.
- Check A2P 10DLC status before relying on SMS; see our A2P registration guide.
- Review workflow history weekly for errors and skipped steps.
- Archive workflows you no longer use, so the account stays understandable.
Want these built and tested for you? See our GoHighLevel automation service or start with the free GHL setup checklist.
Written by Ahmad Ali, GoHighLevel Specialist
Ahmad builds and fixes GoHighLevel accounts: pipelines, workflows, funnels, snapshots and GHL AI, set up so teams can actually run them.