Getting started
How to Use Zoril SMS
Set up your gateway, prepare authorised recipients, send or schedule messages, and check the results.
Set up and send your first message
You’ll need an Android phone (Android 8 or newer), an active SIM with SMS airtime or a bundle, and an internet connection. Messages are sent through your SIM.
Create your account
Sign up at sms.zoril.app, confirm your email when requested, and sign in. Check that you are in the correct organisation and that an administrator has assigned an active plan. If you were invited, use the email address on the invitation.
Install the Android gateway
Download the gateway app onto an Android phone with an active SMS SIM. Allow Phone and SMS permissions, and let the app run in the background.
Download Android appPair your phone
Open Devices and follow Add device to obtain the gateway credentials or QR code. In the Android app, use https://sms.zoril.app and enter or scan the supplied connection details. Confirm the device appears online and choose the correct SIM on a dual-SIM phone. Keep credentials private; a temporary disconnection does not require deleting the device.
Send a test SMS
Open Send SMS, enter a number you own and a short message identifying your organisation, then review and send. Check Messages for its status and confirm receipt on the recipient phone. A simulator/test-key result is not a real SMS delivery test.
Sending from your own software?
An API key is only needed for integrations, not for sending from your workspace. You can create one in API Keys when you need it. See the API documentation when you’re ready.
Everyday messaging tasks
Build your contact list
In Contacts, add people individually or import a CSV with names and phone numbers. Use international numbers such as +256784777801, check the import result and duplicates, and retain only necessary custom fields. Add tags and groups for useful audiences. On a contact profile, record the source and separate marketing/transactional consent with evidence; inspect opt-out and communication history. Use protected fields only where necessary and authorised.
Send to selected group members
Open Groups, choose a group and select the members you want to reach. Search or filter the list, edit contact details when needed and choose a saved template or write a message. Insert supported member fields, supply fallbacks for missing values and preview several recipients. Review duplicate, invalid-number and opt-out exclusions, SMS parts, the selected SIM and final recipient count before confirming. Use a test send before a large personalised batch.
Schedule and repeat a campaign
Choose a future day, date and time in the group-send or campaign form. Verify the displayed timezone and preview the recipients before saving; choose daily, weekly or monthly recurrence only when wanted. Review the saved schedule in Campaigns. Pause, edit or cancel work that has not yet been handed to the gateway. Delivery can be later than the scheduled time if the phone is offline, the queue is busy or a limit is reached. Recently sent lists let you recall recipients, compose a new message or save a group.
Use templates and automation carefully
Templates are editable starting points, not approved legal notices. Check names, dates, recipient fields and sender identification before use. For Automations, choose the trigger and actions, test the rule on a controlled conversation and inspect its activity before enabling it widely. Avoid reply loops and repeated promotions. A campaign is treated as marketing unless your available settings explicitly support another category; never use an automation to bypass opt-outs.
Review replies and delivery
Read replies in Inbox and message results in Messages. Queued is not sent; sent is not confirmed delivered; delivered requires a recorded delivery report. Review failures and attempt history before sending again. Gateway Status shows queued work, age, gateway health and campaign progress. Analytics labels measured values and estimates; link clicks are not proof of purchases, payments or appointments.
Manage plans, payments and access
Billing & Usage shows your assigned plan, trial/renewal information, available credits and limits. Administrators control available plans and assignments. For a Yo! Uganda top-up, follow the displayed mobile-money instructions and wait for verified payment; use the reference if it remains pending, rather than paying again immediately. SIM airtime and bundles are separate. Team members should have only the access they need; revoke old keys and remove former members. Configure contact/message retention under Deliverability → Compliance.
For worked examples, read the practical guides. For integrations, use the API reference.
Loading additional help…
Common questions
Do I need an API key to send from the workspace?
No public API key is needed for normal workspace sending. Use API Keys for your own server integrations; gateway pairing supplies its own connection details. Never share those credentials.
Can SMS come from my business name?
A paired SIM normally sends from its phone number. Include your organisation name in the message text. An alphanumeric originating sender ID requires an approved compatible network/provider route; typing a name into a template does not change the SIM sender.
Are SMS messages end-to-end encrypted?
No. The web connection is protected, but ordinary SMS is processed by the gateway and mobile network and can be read on the receiving phone. Super Admin message monitoring shows counts, not message bodies. Do not send passwords or highly sensitive information by SMS.
What must I check before marketing?
Record consent and evidence, clearly identify your organisation, include the appropriate unsubscribe instruction and exclude suppressed recipients. Honour STOP replies. Check carrier and destination-country rules, including permitted times. A saved phone number alone is not permission to send promotions.
Troubleshooting
Verification or reset email is missing
Check your email address and spam folder, then use the available resend option. Open the newest link once. If an email cannot be sent or the link fails, contact support rather than creating several duplicate accounts.
Gateway offline or messages stay queued
Check phone internet, power, SMS/phone permissions, foreground service and battery optimisation. Confirm the server address is https://sms.zoril.app and that the device is connected to the correct organisation. Reconnect using its existing identity; do not delete it as a first troubleshooting step.
Sent, but not received
Verify the recipient number, SIM selection, airtime/bundle and network coverage. Try one ordinary SMS directly from the gateway phone to an authorised test number. Inspect delivery reports and errors before repeating a send; a sent status alone does not confirm receipt.
A plan or usage limit blocks sending
Review Billing & Usage and the account's plan/trial status. Check daily organisation and device usage and any next-reset time shown. An administrator can review the plan or suspension; a top-up only helps when the relevant allowance supports credits. API rate limits require backoff, not a rapid retry loop.
A CSV import or personalised preview is wrong
Use a real CSV under 5 MB with no more than 50,000 rows. Check column headings, international phone numbers and the import summary. Inspect custom-field names and supply missing-value fallbacks. Resolve duplicates and exclusions before sending; do not upload unnecessary sensitive fields.
Need more help?
Contact the Zoril team if you need help with your account or gateway.
Contact Zoril support