Monitor
Infra health, aggregate error rates, what's happening right now.
Right now
Infra health …
Cost / margin per client
Per-client error rates (aggregate)
| Client | Calls | Avg dur. | Failed | Missed | Provider errors | Lang-detect fallbacks |
|---|
Support
Find a client, see their status, act on it.
Select a client.
Business
Usage trend and growth — separate from the urgent view on purpose.
Clients
Call volume, last 30 days
Cost tracking estimate, not billing
| Date | Client | Duration | LLM | TTS | STT | Total | Notes |
|---|
Invoices …
Business (bank transfer) invoices. Nothing in this system can see that money arrived — confirming one is a human checking the bank account and recording what they matched against.
| Invoice | Client | Plan | Total | Issued | Due | Status |
|---|
Numbers …
Numbers customers have asked us to connect. Each arrives inactive with the carrier instructions the customer was shown — configure the trunk, watch a real call arrive, then switch it on. Activating without seeing a call is how a customer finds out it is dead by missing a caller.
| Number | Client | Carrier | Country | Company key | Added | Status |
|---|
Pipeline
Onboarding and purchase requests, merged — both answer "who's on the way to becoming a paying, working customer."
Where every client stands in draft → pending review → approved → published. Select one to configure it in Support.
| Client | Stage | Trial ends | Last call |
|---|
A preview account submits one of these when it wants to buy a plan. No payment happens in this system: contact them within a day, send the invoice (bank transfer), and Activate here once the money has arrived. That is the only action that unlocks the account.
| Organization | Plan | Contact | Note | Status | Requested |
|---|
Automatic setup after payment: each client's step on the way to a live number. Blocked clients are listed first; Retry runs the failed step again with the same key, so nothing is created twice.
| Client | Step reached | Blocked by | Steps | Updated |
|---|
Connect a CRM organization
For a client setup did not link: an older client, a CRM that could not be reached, or a name match nobody has checked. Pick the client and paste the id of their CRM organization (CRM admin → Организации). Their "Open CRM" works once this is saved, and a client stuck at crm_create moves on at the next worker pass. Every link is in the audit log with your reason.
Numbers we hold for new companies. The setup worker gives a free number to a company that may use the new engine, tests it with an automatic call and only then marks it live. Adakam's line is never a pool number. Ordo's line can be loaded only with the take-over tick above it.
| Number | State | Company | Last error | Updated |
|---|
Load numbers
Only numbers Adamard holds and no customer uses (here or in the CRM). Each one is added to the voice server's pool, where it answers "not in service" until a company gets it. Refused while the pool is switched off.
Test go-live (payments off)
For an internal (test) organization only: moves its setup job on as a paid purchase would, without touching payments. The worker then links the CRM and, with the pool on, gives it a number.
New-engine profiles
Every company's engine profile: whether it may use the new engine and why not, the last push to the voice server, and its CRM setup. A failed push is retried by the worker; one the voice server refused waits for the next publish.
| Company | Revision | Eligible | Push | CRM setup | Number |
|---|
Versions
What the engine and each company's profile are running, what came before, and how to go back. A rollback needs the highest ops role and a typed confirmation, and is written to the audit log before and after.
Roll back engine
Installs an earlier release on the voice server. The voice server waits until no call is up (up to 2 minutes), then switches the release and restarts the engine, so a rollback can take several minutes. Pick a release; you will type its confirmation phrase before anything is sent.
Only the highest ops role can roll back.
Each company's latest profile revision, the revision the voice server has accepted, and whether it may use the new engine. Revisions are kept forever; a rollback stores the old one again as a new revision. Only the highest ops role can roll back; everyone else can read and compare revisions.
| Company | Latest / applied | Push | Eligible | Engine |
|---|
People
Two real systems, one screen. DzAIn accounts (this platform's own users table) and CRM accounts (crm.adamard.am's own Supabase Auth — a separate database entirely) are genuinely different backends; resets are audited on both sides regardless.
DzAIn / AI-operator accounts
| Org | Role | Last login |
|---|
CRM accounts
| Org | Role | Last sign-in |
|---|
Governance
What each plan actually grants, the record of who changed what, and erasing a caller's data on request. Plan capabilities and the audit log belong together: a capability is only as trustworthy as the trail showing who last altered it, and every change made anywhere in this zone writes a row you can read in that log. Erasure joins them here as the third compliance tool, not a fourth top-level zone.
Plan capabilities
Only gate_* keys are enforced. The other entries in a plan's features are human-readable marketing copy rendered on pricing cards, and are deliberately not editable here — changing what a customer is told is a different act from changing what they get.
Audit log …
Written in the same transaction as the action it describes, which is what makes it worth reading. Read-only — there is no edit path, by design.
| When | Action | Who | Org | Resource | Detail |
|---|
Erasure GDPR Article 17
Keyed on the caller's phone number, not on any one client — the same person may have called more than one company line, and a real erasure request covers all of it. Spans six real locations: the platform database, the voice server's call log and turn transcripts, its recording and QA-TTS audio files, and the CRM's own copy of the transcript and recording. Load a preview first — nothing is deleted until you confirm, and the confirm step tells you exactly which of the six actually succeeded, never a blanket "done" that could be wrong about one of them.
Retention GDPR Art. 5(1)(e) — storage limitation
Redacts call content (transcripts, recordings, summaries) once a call is past its retention deadline — 90 days — while keeping the call row, its number and timestamps, so the call-history log and metrics survive. This is the automatic counterpart to erasure: erasure removes one person on request, retention clears old content for everyone on a schedule. Load a preview first — nothing is redacted until you run it, and each store reports its own outcome. It spans the platform database, the CRM's transcript copy, and the voice server (call transcripts and recordings).