Skip to main content
A follow-up is a later message to the people a project or campaign has already reached. Follow-ups are a section of a text project or an email campaign, not a separate type: you write the first message as usual, then add up to nine more, each sent a set time after the one before. A survey cannot have follow-ups. An email campaign can have them whether it is a broadcast or a triggered campaign.

Text follow-ups

Open the Follow-ups section of a broadcast or triggered text project and choose Add a follow-up. For each one:
  • The message. Write it as you would the first message. Merge fields work. A follow-up carries pictures only on an MMS project.
  • The wait. Choose a number of days (1 to 365) or hours (1 to 72) after the message before it. A wait of days sends at a time of day you choose, in a time zone you choose (Eastern, Central, Mountain, Pacific, Alaska, or Hawaii), so each follow-up lands at the same hour. A wait of hours sends that many hours after the previous message, whatever the clock says. For waits longer than three days, use days.
  • Quiet hours. A text that comes due between 10 PM and 8 AM in the recipient’s time zone is held until 8 AM. This only ever moves a follow-up later.

When a person stops getting follow-ups

Under Stop sending follow-ups, turn on at least one:
  • Stop when they reply.
  • Stop when they click a link. A click on a tracked link in any message of the project.
A person who texts STOP or otherwise opts out always stops, whatever you choose. A person whose first message failed to deliver gets no follow-up. A person is sent a step at most once.

Cost

Each follow-up is charged when it sends, as any other text is, and not when you start the project. A person who replies, clicks, or opts out before a step is never sent, or charged for, that step.

Starting, and changing things afterwards

  • A broadcast with follow-ups is scheduled for a time, or sent now. Sending it by hand, a batch at a time, does not send follow-ups and is refused. If a follow-up waits days, schedule the project in the same time zone as the follow-ups.
  • A triggered project starts each person’s follow-ups from their own first message, so people who join on different days each have their own timing.
  • The steps are locked once the project has started. Their text, order and waits cannot be changed or removed. To change them, end the project and copy it.
  • The time of day and the time zone can still be changed. People already waiting keep their place and get their next message at the new time. Nothing already sent is sent again.

Email follow-ups

Email follow-ups work on a broadcast or a triggered campaign: later emails, each a number of days after the one before at a time you set. They are chosen when you create the campaign. Email follow-ups wait whole days, never hours. On a triggered campaign each person is on their own clock: a follow-up goes the chosen number of days (at least one) after the calendar day that person’s previous email was sent, in the campaign’s time zone. Steps cannot be added or removed once a triggered campaign has started; copy it to change them. Starting, pausing, resuming or ending the first email does the same to every follow-up, and ending it skips everyone still waiting. See Follow-ups in Campaigns and deliverability for templates, threading, and reporting. Email can stop on a reply, a click, or both, and an unsubscribe always stops.

Reporting

A text project’s report shows each step: messages sent, delivered and failed, people waiting for it, and people who left before it. People who left are counted by reason: replied, clicked, or opted out. A person skipped because their first message failed is counted as not delivered.

Over the API

  • Text: follow_ups on POST /v1/projects and PATCH /v1/projects/{id}, returned on GET /v1/projects/{id}. It is {"steps": [{"message_text": "...", "wait": {"unit": "days", "amount": 2}}], "stop_on_reply": true, "stop_on_click": false}. A step can carry media_ids. When any step waits days, send scheduled_timezone and sequence_send_time (HH:MM) in the same request. PATCH with follow_ups: null removes them. A changed value after the project has started returns 409.
  • Email: the sequence object on POST /v1/email/campaigns, with stop_on_reply and stop_on_click. Beside a trigger, each step’s delay_days must be 1 to 365; on a broadcast 0 is allowed.
See the API reference.