Skip to main content
Everything that governs your workspace lives under Settings, split into tabs. This page walks each one. Most tabs are owner/admin-only to edit; members see a read-only view.

Members & invites

The Members tab lists everyone in the org with their name, email, role, and the date they joined. Roles, in increasing privilege: Administering the org is role-gated in the dashboard and over MCP alike, so a member can’t route around the UI with an API key.
An API key is scoped to an organization, not to a role: on the REST API anyone holding a key gets that org’s full read and write surface regardless of who minted it. Treat a key as an org-wide credential, which is why minting one is owner/admin-only.
Owners and admins get an Invite member form and a remove control on each row. Removing someone also cuts their programmatic access: any API key they minted and any MCP OAuth token they hold stop working on the next request, so there’s no second cleanup step. An invited person shows up under Invitations with one of three statuses:
Membership requires an invitation. Matching an organization’s email domain does not grant access.

Organization

The Organization tab holds your workspace profile. Owners and admins can edit:
  • Name and logo — how the org is shown across the product.
  • Timezone — an IANA zone (e.g. America/New_York).
  • Default locale — the language new members start in.
  • Companies — enable this optional feature to separate the clients or brands your agents serve and attribute conversations to them. Once enabled, it stays on in customer-facing settings; see Companies for the model and Set up companies for the workflow.
The slug (the /org/<slug> in your URLs) is read-only. Non-admin members see this tab as a read-only summary. Your organization is the workspace and account boundary. If you operate agents for several clients or brands, keep them inside this workspace as Companies; a company does not get separate members, API keys, integrations, or billing.
The timezone here also sets the day boundary for daily reports and day-over-day conversation counts, so set it to where your team actually works.

API keys

API keys are minted under Settings → Integrations → API integration, on a dedicated page above Webhooks. A key is scoped to one organization, and the same key authenticates the REST API and the MCP server — there’s no separate credential per surface. The key list shows each key’s name, prefix, and last-used time. The full secret is shown once at creation — Zelto only stores a hash — so copy it then. Minting and revoking keys is owner/admin-only. A key is a bearer credential for the whole organization: it reads every conversation and transcript, and it outlives the browser session of the person who minted it. Members can read the integration guidance, but the key controls are available only to owners and admins (including platform admins).
A key does not outlive its owner’s access. Every request re-checks the person the key belongs to, so removing them from the org — or banning their account — stops their keys working on the next API call, with nothing to delete by hand. The same re-check applies to MCP OAuth tokens. The check is live, not a deletion: re-adding that person makes their old keys work again, so delete the rows too if you want them gone for good.
For step-by-step minting and the canonical conversation upload shape, see Custom & other providers. For pointing an AI client at your workspace, see MCP. Trace export uses a separate, write-only observability ingest key.

Usage

The Usage tab shows what your organization is charged this month and why. From the top, it has:
  • Due this month so far, the forecast for month end (it needs at least two full days of usage), your AI spend cap and your free credit.
  • What you are charged for: every item as quantity times unit price, with the free credit, any included allowance and your monthly commit taken off, ending in the amount due.
  • Daily usage, and AI spend by benchmark when you have run benchmarks.
  • Volume tiers: which tier you are on, and what this month’s usage would have cost on the others. A tier only lowers unit prices; every feature is on every tier.
  • A price list with every billable unit and what each tier pays, and a What will this cost? estimator that uses the same formulas as the meter.
See Plans, limits and retention for the billing contracts and how tiers work. The same statement is available to your own tools through GET /api/v1/usage/statement and the get_usage_statement MCP tool. When the shared Free contract is active, Usage and Billing show separate USD 5 AI and USD 5 observability balances for the organization, with used, reserved and available amounts and the next UTC reset. These replace Free’s legacy minute/record quotas and evaluation charges; see Free limits. This month and Last month switch the period. Charged is the amount that month adds to your invoice. On the Free plan it is always $0.00: Free is never charged, and when you reach a voice-minute or observability limit new conversations are still received but not analyzed; telemetry exports that exceed the active shared balance are rejected. See What happens at the Free limits. If conversations from a new agent were refused because your plan’s connected-agent limit was reached, a notice at the top of the tab says how many were not stored and links to the plans. Owners and admins also see Conversations to process, which excludes conversations by minimum duration, call direction, or agent. Excluded conversations are stored but use no minutes and are not analyzed; the change applies to new conversations only. On a paid plan they can also set a Monthly conversation-minute cap: leave it blank for no cap, and 0 pauses processing of new conversations. At the bottom, Data sent to Zelto charts the conversations, spans and logs Zelto received. Pick a metric and a month, and read a daily chart (UTC) and a breakdown by provider or service. It updates hourly; before the first update it reads “No data yet”.

Billing

The Billing tab shows your current plan and its monthly price.
  • On the Free plan, Compare plans opens the plan comparison, and Upgrade to Observability sends an owner or admin to a secure Stripe checkout page to enter a card. Improve is not self-serve: use Talk to founders in the comparison or write to hello@zelto.ai.
  • On Observability, Manage subscription and invoices opens the Stripe billing portal, where you manage the subscription. If the subscription is canceled, the organization returns to Free, with Free’s 7-day retention.
  • On a custom Improve agreement, the tab shows your agreement’s monthly price and a short description of what it includes. Start subscription saves your card in Stripe Checkout, and each month you are charged the agreement price plus any usage above your included amounts. The first charge is on the 1st of the next month: that month’s price plus the current month’s usage. If your agreement includes a number of conversations or bills AI at cost, the Usage tab shows your conversations against the included amount and the month’s AI usage.
Members who are not owners or admins see the plan but are asked to contact an owner or admin to manage billing. Owners and admins also see the 12 most recent Invoices, with the date, invoice number, amount, and status (Paid, Due, Processing, Uncollectible, or Void). Invoices come from Stripe, plus any Zelto sent you from Mercury. View opens the hosted invoice (Pay when it is still due); PDF downloads Stripe invoices, and Mercury’s page has its own download. Usage above your plan’s included amounts appears as line items on the monthly invoice. Invoices for custom agreements are emailed to your billing contact, and you pay them on the invoice page by card or bank transfer.

Audit log

The Audit log tab is your own copy of the access trail for this organization: who read a transcript, who opened a conversation, who queried the data, and who changed a setting. It is read-only — there is no way to edit or delete a row from the product — and it shows the 250 most recent events, newest first.
The Audit log tab is not yet visible to customer members; today only Zelto staff can open it. To get the audit trail for your organization, contact hello@zelto.ai.
Each row has five columns:

Access actions

Reads of conversation content are recorded under the phi.* family (phi for protected health information — the naming a HIPAA business associate agreement asks for, and it applies to every org whether or not your conversations are healthcare conversations): One row is written per request, not per record, so a list or a bulk query is a single row carrying how many records it touched rather than thousands of rows.

Change actions

The same trail carries the governance changes, so “who touched this” doesn’t require knowing our naming. The common ones are member.invited, member.removed, member.role_changed, api_key.created, api_key.revoked, mcp_oauth.granted, and org.deleted. Sign-ins are audited too, but they aren’t scoped to an organization, so they don’t appear on this tab.

The Zelto staff marker

A row whose actor is one of our employees is tagged Zelto staff with a shield, next to their email. Anything else is either one of your own people, one of your API keys, or a background job. To enumerate every time we looked at your data, scan for that marker and for phi.cross_org_access.
Recording authorization is logged for every organization. Opening the authenticated audio route records phi.recording_accessed. Managed-storage URLs remain usable for 15 minutes; reusing one does not create another application audit event. An authorization event is not proof of listening, and historical public-URL requests cannot be reconstructed from this trail.
Viewing the tab is owner/admin-only — the rows name each actor’s email and IP, so the trail is itself an access-control surface, and a member who navigates to it gets a 404. Rows are retained for two years, then swept.
  • Reports — the org timezone sets the day boundary for daily counts.
  • Conversations — opening a conversation writes a row to the audit log.
  • MCP — point an AI client at your workspace with an org API key.
  • AI providers — your organization’s own AI provider keys and the bring-your-own fee on Usage.
  • API integration — mint keys and push conversations into Zelto.
  • Quickstart — get your first transcript in minutes.

Send monitor results to your system

Use outbound webhooks to send each new positive monitor result to your database or CRM. Configure destinations under Settings → Integrations → Webhooks, verify a test, and deduplicate received events by their event ID. These per-conversation monitor.matched events are separate from weekly aggregate report webhooks.