Settings
Tenant, senders, limits, quiet hours, roles and the demo service connection.
Workspace & roles
| User | Role | Can |
|---|---|---|
| Lucía Herrera | Campaign operator | Draft, submit, release, pause, cancel |
| Martín Quiroga | Independent reviewer | Approve a frozen revision they did not draft |
| Provincial communications lead | Content owner | Owns public content and accuracy (role, not a user in v1) |
Separation of duty: a drafter cannot approve their own revision. Production requires MFA-backed sessions and server-side authorization.
Sender accounts & channels
| Channel | Sender | Status | Notes |
|---|---|---|---|
| Moris (candidate government-owned sender) | UNRESOLVED | Solution Provider eligibility and exact template approval pending | |
| SMS | No contracted route | SIMULATION | Connect the demo service below to test real SMS |
WhatsApp requires a Solution Provider, entity eligibility and exact template approval. SMS requires contracted routes through a licensed operator and a lawful purpose per campaign. Confirm sender ID rules with the operator and ICTA before a live test.
Limits & pacing
At 80 messages per second, 10,000 recipients need about 3 minutes of ideal submission time. Provider quotas, retries and handset availability come on top.
Quiet hours
Quiet hours are off. Turn them on to hold non-urgent sends overnight.
Demo service API · real SMS
Not connectedA small Node service in demo-sms-api/ implements the PRD campaign API and sends SMS through Twilio to an allowlisted test list. It starts in dry-run mode. WhatsApp stays in simulation until provider eligibility is resolved. Mauritius test contacts use E.164 +230 numbers. Confirm Twilio's Mauritius SMS guidelines (sender ID registration, route availability) before a live test.
Credentials stay in memory for this tab only. The console never receives raw phone numbers; the API masks every endpoint it returns.