Recipes
Copyable workflow builds: missed call → text back, the 5-second lead text, quote follow-through, reminder cadences, no-show recovery, and after-hours triage.
View as MarkdownThe builds every business starts with. Each is a few minutes in the editor; the playbooks show which ones matter most for your vertical.
Missed call → text back
The single highest-ROI automation in the product. 85% of voicemail callers never call back — this catches them in the seconds they're still deciding.
Starts when: A call goes unanswered (+ A voicemail is left)
Step 1 Notify → SMS
"Sorry we missed you at {{business}} — reply here and
we'll get you booked."
Step 2 Notify → Help desk ticket "Missed call from {{phone}}"
(so a human owns the call-back if the text goes quiet)The 5-second lead text (speed to lead)
Starts when: A form is submitted (or: The AI captures a lead)
Step 1 Notify → SMS "Got your request — this is {{business}}.
Want me to get you booked now?"
Step 2 Notify → Email owner alert with the form's fields
(The SMS agent takes the reply conversationally from there.)Quote follow-through
Starts when: A card moves to column "Quoted"
Step 1 Notify → Email the quote recap, same day
Step 2 Wait 3 days
Step 3 Notify → SMS "Any questions on the quote? Happy to
adjust — just reply here."
Step 4 Notify → Ticket if still in "Quoted": human follow-upReminder cadence (kills no-shows)
Starts when: A card moves to column "Booked" Step 1 Notify → Email confirmation at booking Step 2 Wait until the day before Step 3 Notify → SMS day-before reminder Step 4 Notify → SMS morning-of reminder (Reminders like these cut no-shows 30–50%.)
After-hours voicemail → morning queue
Starts when: A voicemail is left
Step 1 Notify → Help desk ticket
requester: the caller · body: the transcript
(The morning shift finds a triaged queue, not a full mailbox.)Missed call → WhatsApp win-back
Starts when: A call goes unanswered
Step 1 Notify → WhatsApp
inside 24h window: session text, AI finishes the booking
outside it: your approved "sorry we missed you" template Publish one at a time
Ship the missed-call text-back first and watch its run log for a day. Then add the next. Each recipe is independently valuable — you never need a big-bang rollout.