A blast to 400 people and a ninety-day multi-phase call cadence are not the same job, and shouldn't use the same tool. SellifyGPT gives you six campaign types that share one contact list, one opt-out ledger, and one timeline.
A straightforward SMS or email send to a set of contacts, throttled to a steady pace so you don't trip carrier filters. Pause or stop it mid-run and it stops where it is.
A timed sequence of texts — minutes, hours, or days apart — with merge fields and its own quiet-hours window. Exits automatically when someone replies or opts out.
A visual builder with eleven node types: send SMS or email, place a call, wait, branch on a condition, update the contact, move the deal, assign an agent, or split-test. Branches can run in parallel.
The deep one. Multi-phase call cadences with their own attempt limits, intervals, and voicemail rules per phase. Covered below.
Bulk email to a large list, sent at a deliberately steady rate so you stay on the right side of the filters.
The AI works the list for you over text and email, answering questions and following up until someone's ready to talk. See the AI suite.
A fresh lead deserves four calls in the first hour. A ninety-day-old lead deserves one a week. Most tools force one interval for the entire life of the lead. Phases let each stage have its own rules.
Call every thirty seconds for the first hour. Hang up on voicemail rather than leaving one — you want a conversation, not a message.
Twice a day for a week. Start dropping a voicemail from the second attempt on, so they hear your voice without you waiting through the greeting.
Once a week, indefinitely, with a text after each unanswered call. Set an attempt limit per phase or leave it unlimited.
| Per-phase control | What it does |
|---|---|
| Attempt limit | Cap the calls in this phase, or leave it unlimited |
| Interval | Minutes between attempts — fractions allowed, so 30 seconds is valid |
| Duration | How long before the contact graduates to the next phase |
| Start delay | Wait before this phase's first call fires |
| Voicemail action | Hang up, or drop a recording — and from which attempt onward |
| Automations | Fire an SMS or email on a specific attempt number |
Attach an automation to attempt three and the AI writes that text knowing a call was just placed and went unanswered — in your voice, following the same rules as the rest of your AI. Not a canned template with a first name slotted in.
The message is written against the actual state of the contact: which attempt this is, that the call wasn't answered, and what's already been said to them.
The same voice, tone, and length rules that govern every AI message on the platform — including the rule that it never sounds like software.
Automations take a fixed message or a template instead. The AI is an option, not a requirement.
The fastest way to make someone hate your company is to keep dialing after they've booked. Campaigns exit on the events that mean the job is done.
| Exit trigger | Fires when |
|---|---|
| Replied by text | They text back |
| Replied by email | They email back |
| Call answered | The call bridges to a rep |
| Spoke with prospect | The rep confirms it was a real conversation — not a voicemail the detection misread |
| Appointment booked | They pick a time |
| Opted out | They ask to stop, on any channel |
| Status changed | You move them out of the working set |
Exits fire on the event. But webhooks get dropped and deploys happen mid-campaign, so about once a minute a sweep re-checks the ones it can read back from your data — opt-outs, replies by text or email, and appointments booked. If one of those is ever missed, it repairs itself instead of quietly calling someone who already opted out.
A drip is a fixed sequence of texts on a timer. A flow is a visual builder where you branch, wait, call, update records, and split-test across SMS and email. An AI campaign has no fixed sequence at all — the AI decides what to send and when, within limits you set, and writes the replies itself.
No. An opt-out suppresses that person across the dialer, drips, and flows, and it reaches past the single row — every contact record carrying that number as its main or mobile number goes quiet. Exits also get re-checked about once a minute so a dropped webhook can't leave someone enrolled.
Not yet — campaigns are launched when you launch them. Multi-phase dialer campaigns do have a configurable delay before a phase's first call fires, and drips and flows run on their own timers once started.
Yes, and in the contact's timezone rather than yours, inferred from their state or area code. A reply that comes in at 3am is held until morning rather than firing a text back overnight. Booking confirmations and appointment reminders are treated as transactional and can bypass the window.
Yes, two ways. Advanced Flows have a split node that routes contacts down weighted branches. There's also a standalone A/B tool for comparing SMS and email variants and reviewing the results — you pick the winner yourself; it won't declare one for you.
Start free today — bring your contacts, fire up the dialer, and let the AI coach do the rest.