Questions, answered.

Businesses that message customers in Uganda and East Africa by SMS, WhatsApp and email, from a workspace or from their own software.

No. You can send, upload CSV lists, run campaigns and reply in the inbox from the workspace. The API is there when you want to send from your own system.

A sandbox simulation takes a minute. Live SMS needs a funded wallet. WhatsApp needs your business number connected and templates approved by Meta. Email needs a sender, and your own domain needs DNS records.

Yes. You connect your Meta business number in the console, and SavaraFlow syncs your approved templates. Replies from customers land in the shared inbox.

Yes, in Uganda. Request a branded sender ID in the workspace and it is registered with the networks. Until it is approved, messages use the shared SavaraFlow sender.

It can’t. A batch reserves its full cost before anything is sent. If the balance is short, the whole batch is declined and nothing goes out.

If a provider rejects a message before accepting it, the charge is refunded. Once a provider accepts a message, the attempt may remain billable even if delivery later fails. The console and API show the exact charge for each message.

Yes. Sandbox keys and simulations never touch your wallet. You can try delivered, rejected and low-balance outcomes before you top up.

Each contact records the channels they agreed to. API sends require consent: true, and fallback only uses channels with recorded consent.

Mobile money through a hosted checkout that shows the amount in Ugandan shillings before you approve. Credit is added to your USD wallet once the payment is verified.

No. Pay as you go from a prepaid wallet. An optional monthly platform plan is available if you want it.

No. You pay as you go from a prepaid wallet. The monthly platform plan is optional.

No. Sandbox keys and workspace simulations never touch your wallet.

Provider rates vary by destination and route. The console shows a live quote using your workspace’s configured rate before each send.

Depending on your setup, your workspace pays Meta directly or SavaraFlow includes the provider estimate in the wallet quote.

If a provider rejects a message before accepting it, the charge is refunded once. After a provider accepts a message, the attempt may remain billable even if delivery later fails.

SMS is billed per segment. Messages over 160 GSM-7 characters split into 153-character parts. An emoji or non-Latin character switches to UCS-2, with 70 characters per message and 67 per part.

Yes. Pass maxCostMicros with an API send or batch, and the request is refused if the quote is higher. Campaigns also have their own spending cap.

US dollars. Mobile money top-ups show the amount in Ugandan shillings before you approve, and credit is added once the payment is verified.

Only a verified payment adds credit. Pending top-ups are checked automatically, and owners can request a check from the wallet.

A single SMS holds 160 GSM-7 characters. Longer messages are split into parts of 153. One emoji or non-Latin character switches the whole message to UCS-2, which holds 70 characters per message and 67 per part.

If the provider rejects the message before accepting it, the charge is refunded. Once a provider has accepted it, the attempt can remain billable even if the carrier later reports a failure.

WhatsApp only lets businesses start a conversation with a template Meta has approved. Once the customer replies, your team can answer freely for 24 hours.

Template status updates from Meta are received on the WhatsApp callback. You can also sync templates manually from the workspace.

Once your DNS records are published, the operator checks the DKIM record and confirms signing on the relay. Allow time for DNS to propagate before the check.

No. Sent means SavaraMail accepted the message. Inbox placement depends on the receiving provider, so test with a mailbox you control during rollout.

Split it into batches of 250, or use a campaign for larger audiences with a spending cap.

The file is read in your browser. Only the recipients you choose to send to are submitted with the batch.

No. It suggests a draft, translation or triage label. An agent edits and sends every reply.

A limited view of the current customer’s conversation and, if you add them, redacted answers your team has approved.

Messages already sent stay sent. Top up or raise the cap, then resume to continue with the remaining contacts.

No. Campaigns only send to contacts with recorded consent for the chosen channel.

No. The outside-hours trigger starts at most once per contact per local day.

Yes. Active runs keep using the version they started with. New runs use the updated flow after you activate it.

Send the same Idempotency-Key and payload, and you get the original message back with 200 instead of a second send. A different payload with the same key returns 409.

Each workspace can make 60 API requests per minute. Over the limit you get 429 with Retry-After: 60.

Register an HTTPS webhook and verify each signed message.status event, or check the message status endpoint.