Only the name now. Everything else (their first person, a number, calling and their CRM) is a checklist on the customer's own page and can be done in any order.

Everyone who signs in to any customer's inbox, and as whom. The same address may exist in several workspaces as separate accounts with separate passwords. Open a row to manage the person inside their customer.

Everyone who signs in to a customer's inbox. The same address in two workspaces is two accounts, each with its own password. Open a person to manage them in their workspace.

Every phone number this gateway answers for, across all customers. 10DLC campaigns are registered in each carrier's own account, not here.

Every phone number this deployment answers for, across all customers. Numbers are assigned on the upstream: turn on Text messaging under a customer's Messaging and its numbers appear here.

Every number on the platform, across customers. Open one to see it in its workspace.

A number here replied STOP and cannot be messaged from the number shown until it replies START. Removing a row records consent given somewhere this gateway cannot see (a form, a phone call) and is your assertion, not a way to resume messaging someone who asked you to stop.

Numbers that replied STOP. They get no texts from that number until they reply START. Remove one only when the person agreed again somewhere else, such as on a form or a call.

Every carrier Sonaline supports, from its own setup instructions. Connect the platform's own accounts here; each workspace's admin connects the workspace's own from its admin center.

The one number every verification code goes out from, for every customer (never a customer's own number), so codes stay out of their conversations. Texts sent to it reach no customer: STOP, START and HELP get the standard answers, and anything else gets the reply below, once a day per sender. Codes are never shown here, and the other end shows as its last four digits.

What a phone sent when its owner turned on Settings → Debug logging and a call ended: the call's diagnostics and every SIP message, word for word. Use it to see what a call that went wrong actually did. Logs hold phone numbers and call details, and are deleted after two weeks. Newest first; times in your time zone.

What a phone sent after a call when its owner turned on debug logging: the call's details and every signal, word for word. Open one to read it. Kept two weeks.

How long the apps take on real phones and in real browsers: starting the Android app, each screen until what it shows is on it, and the web inbox until its conversations are on the page. Half of all opens were faster than the median, nine in ten faster than the 90% figure. Only numbers, the app's version and the phone's model or browser are kept, never who or what. Kept 30 days.

Every message the gateway has carried, newest first. Filter by customer, business number (DID), customer number (CID), direction or status. What people wrote is never shown here: this ledger is metadata only: who, when, size, outcome. CRM is the delivery ledger's verdict on telling that customer's system about it. Times are UTC. Click a row for the delivery story.

Every text the platform carried, newest first, without what was written. Times are UTC. Open one to see how telling their system went.

Events a customer's system is still owed, or that gave up in the last seven days. Retry now puts one back in the cron's path immediately, for when their endpoint is fixed and the backoff shouldn't be waited out.

Events a customer's system is still owed, or gave up on in the last seven days. Retry now sends one again at once, for when their end is fixed.

Everything one customer's system was told, told or owed, newest first.

Everything one customer's system was sent, newest first.

The usage ledger priced with each customer's own rate card, set on their Billing page. There is deliberately no gateway-wide default price.

Billable messages per customer for one month. A message counts when the provider accepted it, delivered or not; a webhook retry counts nothing twice. Months roll over in the gateway's own timezone.

For every inbound message in the last 30 days: minutes until the thread's next outbound reply, averaged per customer. The one number that says whether an inbox is being worked or merely filling.

Who may administer this gateway, which customers each may see, and what they may do. The admin key is one shared bearer token with no name on it: everything done with it is recorded as key. An operator account can be narrowed or disabled on its own, and everything they change carries their email in the audit trail.

Who may run this console, which customers each may see, and what they may change. Everything they change carries their email in the audit.

Your account: your name and password, your two-factor and the passkeys that sign you in. Changing who may see and do what takes an operator who manages operators.

A partner is another system (a reseller, or a sibling deployment of this software) that creates customers here with its own key and sends and receives through the ordinary SMS API as them. It reaches only the customers it made, which are named <partner>_<workspace> and run as API-only relays. You assign their numbers, caps and prices exactly as for any customer.

An edge is a box of the phone system's own (Kamailio, rtpengine and the call agent) that the apps register through. There is one today. A second is a DNS record, an sbc.env with SBC_EDGE_NAME, one install.sh run, and a row here (docs/sbc-failover.md has the runbook). A wrong door takes every phone down: add an edge off, turn it on once its box answers here, and let it take new registrations last. Blank URLs mean the voice worker's own settings.

A content filter that checks encrypted traffic answers for our addresses with its own certificate, and the Android app refuses it. Phones report the ones they refuse, and they wait here. Approve one only when you know whose filter it is: that filter can then read Sonaline's traffic on the phones that installed its certificate, sign-ins included. A phone accepts an approved certificate for Sonaline's own addresses only, and only when its owner installed that same certificate; nothing else changes.

A feature still being built ships hidden behind a switch and is turned on here: for every customer, or for one workspace to try it first. A workspace's own setting wins over the one for every customer; a switch nobody has set is off. The switches are named in the code (platform/src/switches.ts), and one goes away once its feature is finished.

Every change made through this console and the operator API, with who made it. Reads are not recorded: they would bury the writes, and the writes are what anyone goes looking for. A customer's own slice is under their Activity, as Changes.

Every change made in this console or through the operator API, and who made it. Looking is not recorded.