SMS
Use SMS for reminders, pickup alerts, and other messages that need to reach a phone number. SavaraFlow quotes the destination and segment count before a live send.
Explore SMS← Platform
Workspace capability
Reply, wait and follow up without lifting a finger.
Build a flow that starts from a customer’s first message, a message outside business hours, or a request from your own system. Each step is checked for consent and funds like any other send.
Automations
What you get with Automations
Automations reply, wait and follow up for you. Start a flow from a customer’s message or from your own system, and every step still passes the same consent and wallet checks.
Three triggers
First inbound message, an inbound message outside business hours, or an external API request.
Waits up to 7 days
Pause between steps for a minute or up to a week.
Channel-aware branches
Check whether a contact can receive a channel, then take the Yes or No path.
Safe to edit
Each run uses the snapshot saved when the flow was activated, so edits never affect runs in progress.
Start from your app
Trigger a flow for a known contact with one API call and follow its run state.
Same checks as every send
Each reply queues through consent, suppression and wallet checks.
Automations setup
How it works
Pick a trigger
Start a flow from a first inbound message, an inbound message outside your business hours, or an external API request.
Add steps
Send a reply on a chosen channel, wait between 1 minute and 7 days, or branch on whether the contact can receive a channel.
Activate
Activation validates the flow and saves a snapshot. Runs keep using their snapshot, so editing a flow never changes a run in progress.
Monitor and stop
Each run’s state is visible in the workspace and from the API. Deactivating a flow stops its pending steps.
request.sh1curl -X POST "$SAVARA_HOST/api/v1/flows/trigger" \
2 -H "Authorization: Bearer $SAVARA_API_KEY" \
3 -H "Content-Type: application/json" \
4 -H "Idempotency-Key: $(uuidgen)" \
5 -d '{
6 "flowId": "FLOW_UUID",
7 "contactId": "CONTACT_UUID"
8 }'
Send a scoped key from your server and a stable Idempotency-Key for each distinct send. API reference
Specifications
Limits and details
The exact rules your messages follow, so there are no surprises in production.
- Triggers
- First inbound message, outside business hours, external API
- Steps
- Send a reply, wait, or branch on channel eligibility
- Wait
- 1 minute to 7 days
- Out-of-hours replies
- At most once per contact per local day
- API
- POST /api/v1/flows/trigger, GET /api/v1/flow-runs/{id}
- Stopping
- Deactivating a flow stops its pending steps
Use cases
Where teams use Automations
Questions about Automations
How often does the out-of-hours reply send?
At most once per contact per local day, using the timezone and opening hours you set on the trigger.
Can my app start a flow?
Yes. Choose the External API request trigger, activate the flow, then POST the flow and contact IDs to /api/v1/flows/trigger with an Idempotency-Key.
Will customers get the night-time reply every time they write?
No. The outside-hours trigger starts at most once per contact per local day.
Can I change a flow while it’s running?
Yes. Active runs keep using the version they started with. New runs use the updated flow after you activate it.
What if a contact has no WhatsApp?
Add a branch that checks eligibility for WhatsApp, and send SMS on the No path.
Explore related tools
Connect your Meta business number, send approved templates, and manage customer replies in SavaraFlow’s team inbox.
Explore WhatsAppUse SavaraMail to send receipts, account notices, and other transactional emails. Set a recognizable From name and address for your business.
Explore EmailCheck the cost before you send.
Estimate your usage, then use the live quote for your workspace and destination.