SMS approval workflow · teams and rolesYour whole team writes. You have the final say.
One account per department, site or shop, three roles, and a review before anything goes out, whenever you want one. From a handful of colleagues to several hundred.
Updated on · SMS PRO team
New Caledonia's bulk SMS pioneers since 2016: we set up accounts, roles and approval with you before a single text goes out.
140 characters · 1 SMS
Every department, its own voice
Civil registry, the school office, the shop in Koné: each one sends from its own account.
Everyone knows their role
Administrator, supervisor, user: three roles, clear-cut permissions.
Checked before it leaves
A manager approves, edits or rejects. Once it's gone, it's too late.
Everything on record
Activity log, two-factor authentication, data stored in New Caledonia.
It goes to two neighbourhoods at 5 pm. You're the last to read it.
Technical Services have drafted the water cut notice. It lands on your desk before it leaves, because that's how you set things up. Approve it, fix it or reject it.
Above the number of recipients you set, a send waits for review; below it, it goes straight out. Set the threshold to zero and everything gets reviewed.
Above your direct-send threshold: this one needs a review.
Take a close look at the date.
Waiting for your approval
- Drafted
- Approved
- Sent
- Logged
Nothing goes out until you decide.
Activity log
- Technical ServicesSend drafted, waiting for approval
Illustration, fictitious data.
The people who know write the message.
Each from their own account.
Technical Services know when the water goes off, the school office knows the student's name, the shop knows what just came in. Every department, site or shop has its own sends, groups and history, all under one organisation.
You can set a monthly quota per account, and shared templates keep everyone on the same tone. Sender IDs assigned account by account
Three roles. Nobody treads on anyone's toes.
The built-in guide adapts to each person's role, and everyone sees only what concerns them. The school office doesn't send under the principal's name.
Runs the organisation.
Creates accounts, hands out sender IDs, sets the direct-send threshold, enforces two-factor authentication and reads the activity log.
Reviews, and keeps an eye out.
Approves, edits or rejects sends from the accounts assigned to them, and checks their history and calendar.
Drafts and sends.
Works in their own account. Their sends go straight out or wait for review, depending on your settings.
Approve, edit, reject.
Before, not after.
The supervisor fixes a wrong date themselves, or rejects the send, marked “needs changes” or “final”. Below the threshold you set, a small send goes straight out; at zero, everything goes through review.
A send waiting too long? The supervisor gets a reminder, then the administrator is alerted.
An eye on the week,
without slowing anyone down.
Oversight opens an account's history and calendar without holding anything up. A principal sees what the school office sent this week, and what goes out tomorrow.
Approval and oversight can be combined, account by account. Tracking and reports per account
Who did what, and when: it's all on record.
Two-factor authentication you can require for everyone, an activity log with adjustable retention, and IP addresses never kept in plain text in the logs.
“Log in as”
To help a colleague, the administrator can open their account: it's logged, limited to 4 hours, and the account owner gets an email.
Your data stays here
Stored in New Caledonia, in the 
Stratos sovereign cloud. Security and data
Many hands write. One voice arrives.
An alert checked before it reaches the whole town. The school office keeps parents posted while the principal keeps control. Every shop sends its own news, and head office reviews the shared campaigns.
The council checks its alerts
The principal keeps control
Head office reviews campaigns
The club speaks with one voiceA network or federation can also oversee several independent organisations, each with its own contract, its own settings and its own opt-out list. See how councils and local authorities set theirs up.
Your questions, answered.
Can we require a review of every send?
Yes. Set the direct-send threshold to zero: every send from the accounts that need approval then waits for its supervisor, who approves, edits or rejects it before it goes out.
Can a staff member send without approval?
Yes, below the threshold you set: a send to just a few recipients goes straight out. Like every send, it stays attached to its account in the history, which the supervisor can check.
Who sees what?
The administrator sees and manages the whole organisation. The supervisor approves sends from the accounts assigned to them and checks their history and calendar. Users work in their own account, with the sender IDs they have been given.
Can we enforce two-factor authentication?
Yes. Each user picks a code sent by email or an authenticator app, and the administrator can make two-factor authentication mandatory for every account in the organisation.
How many users can we have?
From a handful of colleagues to several hundred. Each department, site or shop can have its own account, with its own settings, within one organisation.
Related pages
Bulk SMS
Groups, a personalised message for everyone, and excluded numbers explained before anything goes out.
Scheduled SMS
Pick the exact time it leaves, or spread a send across a time window.
SMS API
Named keys, restricted by IP address, for your organisation's software.
Many hands, one voice.
Tell us how many departments send texts, and who should review them before they go. With ten years of sending across New Caledonia since 2016, an adviser in Nouméa will show you accounts and approval set up for your case.
50 free SMS to try, no commitment: contact@smspro.nc