Admin Guide | Neo Dialer

The Admin view is where a tenant is configured. It is organised into Administration, Telephony, Reporting & Insights, Configuration and Security.

Users and roles

Administration → Users. The role hierarchy:

Role	Can do
`agent`	Dial, take calls, see their own history
`supervisor`	The above, plus monitor, QA, coaching, compliance
`org_admin`	The above, plus tenant configuration
`billing_admin`	Subscription and billing
`tenant_admin`	Everything in the tenant
`owner`	Everything, including transferring ownership

Roles are enforced server-side. Hiding a page in the UI is not the control; the API refuses the request.

Security

Security → Security. Multi-factor authentication is available to every user and can be required organisation-wide. Turn it on.

Security → Audit Log. Administrative actions, sign-ins and support access. Not user-deletable, deliberately.

Security → API Keys. Note the current state honestly: this screen is a placeholder. API access today uses the bearer token from your session — see API Authentication. Long-lived API keys are not yet issued by this screen, and a key generated here will not authenticate.

Subscription

Administration → Subscription shows your plan, its limits, and your current usage against each of them — seats, concurrent calls, minutes, AI minutes, TTS characters, storage, campaigns.

It also carries your overage policy: block at the limit, allow and charge, or notify and continue.

Recording

Telephony → Recording. Enable or disable recording, choose the recording source, and set retention. Retention is capped by plan — 30 days on Starter, 90 on Growth, up to 365 on Enterprise — and you can set anything below the cap.

Also set the overflow policy for when your storage allowance fills. The default deletes the oldest recordings first.

Feature controls

Telephony → Feature Controls. Turns individual capabilities on or off for the tenant — extensions, inbound routes, ring groups, call queues, IVR menus. Useful for keeping the interface to what your team actually uses.

Integrations

Configuration → Integrations. Connect calendars, sheets and CRM systems. OAuth tokens are held by the application tier only, never by media servers, and are refreshed proactively before they expire.

Configuration → CRM Field Mapping controls how contact fields map between Neo Dialer and your CRM, so imported and exported data lands where you expect.

Automation rules

Configuration → Automation Rules. Trigger actions from call outcomes without writing code — tag a contact, schedule a callback, fire a webhook.

Webhooks

Configuration → Webhooks and Outbound Webhooks. See Webhooks.

Templates

Configuration → Industry Templates shows the templates available to your tenant. Some are available to everyone, some are assigned by the platform, and some are premium.