Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt

Use this file to discover all available pages before exploring further.

The shipped recipes cover ~80% of what service businesses want from automation. Here’s each one in detail.

​
Appointment reminder

Trigger: an appointment booked event, T-24 hours before the appointment time. What it does: sends the customer an SMS / email reminder of the appointment, with details (date, time, service) and any prep instructions you’ve configured. Default message:
Hi , just a reminder we have you booked tomorrow at for . See you then! —
When to enable: always, basically. Reminders cut no-show rates dramatically (often 30%+ improvement for service businesses). Cost is one extra SMS or email per appointment. Customizations to consider:
  • Add an “address change?” prompt for businesses where the customer’s address might shift between booking and visit.
  • Mention what to expect (“Mike will be there in a marked white van; please make sure pets are secured.”).
  • Add a “reply to reschedule” line if you want to capture last-minute changes.

​
Booking confirmation

Trigger: deal moves to Booked stage (or appointment record is created with status booked). What it does: immediate confirmation message with appointment details. Default message:
Hi ! You’re booked for on at . We’ll send a reminder the day before. —
When to enable: when bookings come in from non-AI sources (manual entry, paper forms, walk-ins). The AI’s own bookings already include a verbal/text confirmation, so this is mostly redundant for AI-booked appointments. Toggle off for orgs that book exclusively via the AI.

​
Lead nurture sequence

Trigger: new contact created (and didn’t immediately book). What it does: 3 messages over 7 days, escalating mild urgency:
  • Day 1, 2 hours after creation: “Hi , just checking in — wanted to make sure you got everything you needed. Reply if I can help.”
  • Day 3: “Hi , didn’t want this to fall through the cracks. Any questions about ?”
  • Day 7: “Hi , last touch from us. We’re here whenever you’re ready — just reply or call us at .”
Stops the moment the contact replies (any reply, on any channel) or moves to Booked. When to enable: for low-volume orgs where every lead matters. For high-volume orgs with thousands of cold leads, this can feel spammy and erode reply rates — turn off and rely on form-AI auto-reply only. Customizations:
  • Change the wording in your business voice.
  • Adjust timing — some businesses prefer 1-day, 4-day, 14-day cadence.
  • Disable Day 7 if you find the “last touch” message generates more opt-outs than bookings.

​
Post-completion review request

Trigger: deal moves to Completed. What it does: schedules a review request 24 hours after completion. Default message: see Sending review requests. Same template; this is just the workflow that fires it. When to enable: always — this is how you build your Google review count. When to use the workflow form vs. the Reputation feature: the Reputation feature is the higher-touch version with the funnel + GBP integration. The workflow form is simpler — just a “send a message after completion” recipe. If you’ve enabled Reputation, leave this workflow off (otherwise you’ll send two messages).

​
Cancellation outreach

Trigger: appointment cancelled (by customer or by you). What it does: sends the customer a polite acknowledgment + open offer to reschedule. Notifies your team. Default message:
Hi , no problem — your appointment is cancelled. Whenever you’re ready to reschedule, just reply or text us. —
When to enable: mostly when cancellations are common in your business (e.g., you do exterior work and weather causes frequent reschedules). For low-cancellation businesses, it’s nice-to-have.

​
How recipes interact

Multiple recipes can trigger off the same event. E.g., a deal moving to Booked fires:
  • Booking confirmation (immediate message)
  • Appointment reminder (T-24h scheduling)
These run independently; no coordination needed. If you’ve turned both on, the customer gets two appropriately-timed messages.

​
Pause vs. disable

  • Pause — temporarily stops a recipe; preserves your customizations. Useful when you’re testing or going on vacation.
  • Disable — permanently turns it off; same effect but you might lose track of which recipes you’d customized.
There’s no hard difference between them; pick whichever makes mental sense for your situation.

​
Custom recipes

Want a recipe we don’t ship? Common requests we’ve built case-by-case:
  • Birthday messages on contact birthday (when birthday data is available)
  • Annual maintenance reminder (on the anniversary of last completed service)
  • Win-back sequence specifically for “Lost” deals
  • Internal team notifications for high-value deals (>$X)
Contact support to spec yours; many of these are quick.

​
Next

You’re done with Tasks & Workflows. Next:

Knowledge Base

Train the AI on your specific FAQs.