A text that sends itself on the weekdays you pick
Auto-blast repeats one message to your groups on a schedule you own. Replies can take someone off later runs, and only one schedule sends at a time.
An auto-blast is a campaign that repeats. You pick groups, weekdays, a time, and how long it should run. Statxt sends the message on each scheduled day until that length is up, then the schedule shows as completed. It is a tab inside Campaigns, and the schedules are personal. You see the ones you created. Teammates do not, and they cannot edit yours.
The builder is three steps, then Activate
New schedule opens the builder. On General, name it or accept a suggestion such as "Auto-blast for Trial Leads", and choose one or more groups. The eligible count leaves out opted-out and DNC contacts. More than 5,000 eligible recipients means each run is split into campaigns of up to 5,000. Auto-pause on reply starts on: someone who texts back is skipped on later runs, which is what you want if the reply is the start of a conversation.
Schedule starts you on Monday, Wednesday, and Friday at 9:00am. Change the days. Frequency is the length, such as 4 weeks or 3 months. The time uses your timezone, detected and shown on that step.
Content is the message, sent as a normal campaign from one of your numbers. Merge fields, the segment counter, and the opt-out footer behave the same way they do on a one-off blast, which is the Send a Campaign guide. Activate sets the first run for the next matching day and time.
What you can still change
The Auto-Blast Center lists every schedule as a card, with Sent, Replied, and Runs, plus a calendar of the next 30 days. Pause Schedule stops future runs. Resume turns them back on. Edit reopens the builder and adds a Runs step with past runs and errors. Delete removes the schedule and does not unsend anything.
Each run reads the groups again, so people you add later are included next time, and people who opted out are not. Leave Exclude them selected on the audience safety gate so someone your team texted recently is skipped. The window for that gate is the Notifications guide. Only one auto-blast sends at a time in a workspace. If two are due together, the second waits. Statxt picks the sending number. If none is available, that run fails and the schedule pauses, which is why a line with a health problem is an auto-blast problem too.
Opt-out language still belongs in the copy. The footer and the DNC list are not a substitute for saying how to stop.
The click-by-click version lives in the Auto-Blast Schedules guide.
Walk through it in the product
The guides cover these same workflows step by step, with the screens you will actually use.