Text the right person the moment a step is done

Add an SMS message to any step in your Workflow. When someone completes that step in a run, Manifestly sends a personalized text — filled in with details from the run — to a number you set or a phone number captured earlier in the run.

Start your free trial. * No credit card required.

Text Message
Today 9:41 AM
Acme Onboarding: the “Contract signed” step is complete. Kickoff for Northwind is now underway — details here: app.manifest.ly/r/8412
Delivered

Stop chasing people to say “it’s your turn”

Email gets buried and status pings get forgotten. A completed step often needs a fast, hard-to-miss nudge — to the next assignee, a customer, or an on-call tech. An SMS message on the step does it automatically, every run, without anyone remembering to.

Handled by hand
  • Someone has to remember to send the update
  • The message gets retyped — and worded differently — each time
  • A missed handoff stalls the whole run
Configured on the step
  • The text fires the instant the step is completed
  • Tokens fill in the run’s own details automatically
  • Every delivery is recorded in the run’s activity

Set it up once, and it sends on every run

1

Add an SMS message to a step

Open a step in your Workflow, choose Send messages, and add a text message. Set who it goes to and what it says. You can add more than one message — SMS and email — to the same step.

2

Personalize it with variables

Drop in tokens for run details, data collected during the run, and links back to the run. Each message is written once on the Workflow and reused by every run started from it.

3

Complete the step — it texts

The moment someone marks that step complete in a run, Manifestly resolves the tokens against that run and sends the text. The delivery is logged in the run’s activity feed.

A simple message, configured on the step

Two fields do the work: To and Body. Pick a country and type a mobile number, or reference a phone number collected in the run as a variable. Then write the message — use the insert variable helper to pull in exactly the tokens available to that step.

  • Send to a fixed number, or to a {{variable}} that resolves to a number in the run.
  • Text one recipient or several — separate multiple numbers with a comma.
  • Messages ride along when a Workflow is duplicated, exported, or shared.
Send SMS on step complete Step: Contract signed
To
US +1 {{Customer mobile}} insert variable
Body
{{organization.name}}: the “{{step.name}}” step is complete for {{run.title}}. Details: {{run.url}}
insert variable Save

Every text is written for that run

Tokens are placeholders that Manifestly fills in when the step is completed, using the data from that specific run. Reference the run’s title, the step, the current date, your organization, and any value someone entered in an earlier data-collection step — then let each run supply its own particulars.

{{run.title}} {{step.name}} {{run.url}} {{organization.name}} {{current_date.full}}
Message on step completion
What you write once
Hi {{Assignee first name}} — the “{{step.name}}” step on {{run.title}} is done. You’re up next.
What a run actually sends
Hi Priya — the “Contract signed” step on Northwind Onboarding is done. You’re up next.

Variables you can drop into a message

The insert variable helper lists exactly what’s available for the step you’re editing.

Run & system details

The essentials about the run and the moment it completes.

{{run.title}} {{run.due_date.full}} {{step.name}} {{current_date.full}} {{organization.name}}
Data collected in the run

Anything captured by an earlier data-collection step — including columns pulled from a Data Table selection.

{{Customer mobile}} {{Order number}} {{Customer.Region}}
Links back to the run

Give recipients a one-tap way to open, review, or check progress.

{{run.url}} {{run.summary}} {{run.percent_completed}}

Send to a number you set — or one the run captures

Hard-code a mobile number when the recipient never changes, like an on-call line or a dispatch desk. Or collect the number during the run — add a Phone Number data-collection field to an earlier step — and reference it as a token in the To field so each run texts the right person.

Earlier stepcollects the mobile To field{{Customer mobile}} Step donetext is sent
  • Delivers to US and Canada mobile numbers (+1), including Puerto Rico and the Dominican Republic.
  • If a number still contains an unresolved token, the text isn’t sent and the reason is recorded — no half-filled messages go out.
  • List several numbers, separated by commas, to reach a small group at once.
Run activity
Step completed — “Contract signed”
by Dana Ruiz · 9:41 AM
SMS sent for step
To: +1 (415) 555–0148
Body: “Northwind Onboarding: the ‘Contract signed’…”
Unable-to-send is logged too — e.g. an unresolved token or a rejected number — so nothing fails silently.

Where a step-completion text pays off

Handoffs between people

The next assignee shouldn’t have to watch the run to know it’s their turn.

Finish “QA sign-off” → the deployer gets a text: “You’re up next on Release 4.2.”

Customer updates

Keep the person outside your team in the loop at the milestones that matter.

Finish “Order shipped” → the customer’s captured mobile gets tracking details.

Field & on-call alerts

Some completions need an immediate, hard-to-miss ping to a phone.

Finish “Dispatch approved” → the on-call tech is texted the site and job details.

Step-completion SMS, answered

The moment the step it’s attached to is marked complete in a run. Manifestly resolves the tokens against that run and sends the message, then logs the delivery in the run’s activity.

Mobile numbers in the US and Canada (+1), including Puerto Rico and the Dominican Republic. You choose a country and enter the number, or reference a number collected during the run as a variable. Multiple numbers can be listed with commas.

Plain text plus tokens: run details (title, due date, links), the step name, the current date, your organization and department, and any value collected in an earlier data-collection step — including columns pulled from a Data Table selection. The insert variable helper shows what’s available for that step.

If the recipient number still has an unresolved token, the text isn’t sent and the run records why — so a message never goes out to a broken number. Any unresolved tokens in a delivered message are noted in the activity as well.

Yes. You can add several messages to the same step — both SMS and email — each with its own recipients and wording. They all send when the step is completed.

Yes. SMS messages are configured on the Workflow’s step, so they travel with it when you duplicate, export, or share the Workflow — and every run started from it inherits them.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Send a Customized SMS Message on Step Completion

With Manifestly, your team will Never Miss a Thing.