Follow-up that runs itself.

It starts when something happens in your CRM: a new lead, a Facebook Lead Form, a Smart Form, a lead filling in a form again, a tag, a stage or status change, a booking or cancellation, a reply, a custom field changing, or another tool posting to your private webhook. Then it runs your steps: text or email the lead (or let the AI write the message), wait, split into paths, drip leads through a few at a time, tag, move the stage, assign an owner, add a note, pause the AI, stop follow-ups, alert your team, or send the lead to another tool.

Nothing to build or run, on every plan from $19/mo, and the AI builder and copilot are free too. You only pay for what they send, from your plan's credits like any other message: 0.125 credits a text (per 160 characters; 0.25 with a picture) and 0.03 an email. An alert to your team by text costs the same as a text; app alerts, waits, tags, notes, stage moves and webhooks cost nothing.

Yes. On the Automations page, type what should happen and when, like “When a Facebook lead comes in, text them. If they haven't replied in 2 days, email them and text Mike.” You can also drop in up to 3 screenshots of a workflow from another tool. The AI builds the trigger, steps and messages from your own stages, calendars, custom fields and email senders, and opens it in the editor for you to check before you save. Inside the editor, the AI copilot changes it on request or explains what it does and why steps fail.

Add an If / else step and pick when each path is taken: They replied, They booked, Hot / urgent lead, We have an email, Marked won or Nobody owns it yet, or build your own rule on any lead field, tag or custom field (all of them must match, or any one). Leads who match no path take “None of the above”. A path can hold its own split, and the paths can end or join back up for the steps after them.

Yes. A wait set to a time before or after the appointment is timed against the booking itself. Move the appointment and the reminder moves with it. If it's cancelled and the lead booked a new time, the reminder follows the new one; if not, the rest of the run is skipped, so nobody gets a reminder for an appointment that's gone.

It lets only so many leads through to the next step in a set time, like 5 a day or 10 an hour. The first ones go straight through; everyone after waits in line in the order they came in. New rounds only start in your texting hours, so leads never pile up overnight, and a lead who leaves while waiting (they replied or you took them out) frees their place. It's how you text a list of old leads without burying your team in replies.

Yes, both ways. Each automation with the Inbound webhook trigger gets a private web address: when Zapier, Make, a website form or another CRM posts to it, it finds the person by phone or email, or adds them as a new lead, and every field it sent can go in your messages (say, {project}). The Send outbound webhook step sends the lead to any https address, with your own headers and extra fields.

Turn on Stop when the lead replies, or set a goal like They book, and the run ends as soon as it's true. You can also open the leads in an automation and take one person, a few or everyone out, which cancels everything still queued for them. People who replied STOP are skipped.

Yes. Test workflow runs it on a lead from your CRM, skipping the waits and sending no texts, emails or alerts, and you can read each step in the Execution logs. Preview run shows the path a real lead would take and the messages they'd get. Templates open turned off, and you can add leads who are already in your CRM whenever you're ready.