Recipes
Complete working builds for the four campaigns that produce most of the revenue on this platform, each with the trigger, the timing, the code, and the failure modes.
Each recipe is a whole outcome, not a feature demo: the trigger, the timing that works, the code, and what breaks.
| Recipe | What it fixes | Build time |
|---|---|---|
| Speed to lead | New leads going cold before anyone calls | An hour |
| No-show recovery | Booked appointments that never happen | An hour |
| List reactivation | Old leads and past customers sitting idle | An afternoon |
| Appointment reminders | Reminders that get ignored in email | An hour |
Build them in this order
Speed to lead first. It works on traffic you already pay for, it needs no list, and the effect shows up within a day.
No-show recovery second. Same property: the people already raised their hand, and every recovered appointment is revenue that was already booked.
Appointment reminders third, because they reduce the no-shows you then have to recover.
List reactivation last. Highest volume, highest risk, and the one that most needs the other three working first so you know your reply handling can absorb it.
What every recipe assumes
An API key, a webhook endpoint that verifies signatures, and your CRM record ID stamped into contact custom_fields (plus send metadata) so replies resolve to the right record. The setup is in integrations, and the reasoning is in key concepts.
Two rules carry across all four: no link in the first message, and a human answers replies fast. Neither is negotiable, and both are explained in deliverability.