Product · Send · Sequences

Line up the whole arc - release it on your terms.

Multi-touch sends, staged ahead of time. A later touch can branch on what someone did with an earlier one. Nothing here goes out on its own - each touch waits for you.

1
Vote reminderDay 0
Polls in District 4 close at 8pm Tuesday. Find your site: txa.at/vote
Sends to all · ~2,140
2
Day-of pushDay 5
Today's the day. It takes ten minutes: txa.at/vote
Branch · didn't click
3
Volunteer thank-youDay 6
However it shakes out, you showed up for District 4.
Volunteers · ~612
The problem

Follow-up dies in the calendar. The welcome goes out, the reminder never does, and the day-of push gets written at 6am on the day.

How it works

How Sequences works.

1

Draft the arc

Describe the goal in a sentence. Txtra plans the touches using your real tags. Staging the plan never sends anything.

2

Set the branches

A touch can wait on a click, a gift, or a tag. The day-of push can go only to the people who didn't click the reminder.

3

Release each touch

You approve and send. Organizers draft, owners and admins release. The logic runs; the sending stays with a person.

Why it matters

What you actually get.

Plan in plain English

Describe a three-touch GOTV arc for District 4 and get a staged draft back, built from tags you already have.

Branch on behavior

Reach the people who didn't act without re-pulling a list. The sequence reads the behavior for you.

Nothing fires without you

A sequence touch is released by a person. And Autopilot runs only a plan you approved that morning. Automation brings the hours. The authority stays yours.

Behavior triggers.

An event stages the next touch for one person, a tap, a gift, a tag, a link clicked or left unclicked. A gift can stage a volunteer ask three days later. Tapping "I'm in" can stage a welcome. Staging is automatic. Sending stays with you.

Gift → volunteer askTap → welcomeClick / no-clickWaits & delaysStaged, not sent
GiftVolunteer askwaits 3d
Tapped I'm inWelcomeinstant
No click · 48hNudgeonce
Every sequences send runs on the compliant floor.Consent, quiet hours, STOP and HELP, verified sender. On by default, before a single message leaves.
See the compliance model →

Put Sequences to work.

Left or right, Txtra is the sender your carriers trust and your lawyers approve.

This sits on the floor. Consent, quiet hours, STOP status, and sender verification check every send from this screen before it leaves.

See it on your race.

Questions

Asked and answered.

What is a text message sequence?

Staged touches with waits between them. A welcome, a follow-up three days later, a volunteer ask the week after. Each step runs itself or waits for a human.

Do sequences respect opt-outs mid-flow?

Instantly. A STOP anywhere in a sequence closes the contact to texting across the account, and every remaining step cancels.

Can a sequence run against a saved group?

Yes, and the group re-resolves at each step, so people who no longer match drop out and the audience stays current.