Skip to main content
Organization settings apply across the selected workspace. Confirm the intended organization before changing shared defaults, credentials, or exports. Agent-specific behavior belongs in that agent’s settings.

​
Set test and reporting defaults

Open Platform Settings → Preferences. Set Test Phone Number to a destination your team controls and Timezone to the intended organization time zone, then choose Save. The number is a default for test forms; saving it does not make a call. A test action can still place a real call. Reports display the selected time zone, and campaign schedules have their own explicit time-zone settings. Use Outcomes and reports for organization disposition mapping and Observability for telemetry and event exports.

​
Connect an assistant to Athena

  1. Create an Athena API key using Developer quickstart. Use a key belonging to the intended organization.
  2. Open Platform Settings → MCP Server and copy the reachable MCP Endpoint. Hosted integrations use an HTTPS endpoint, with the MCP path /api/v1/mcp/.
  3. In your MCP-compatible assistant, add a Streamable HTTP server using that endpoint and configure the key in the X-API-Key header through the client’s secure authentication settings.
  4. Connect and inspect the discovered catalog. Begin with a read such as listing workflows or reading the node catalog.
  5. Review any proposed create, edit, publish, or call action before authorizing it in the assistant. The API key grants access; a successful connection is not permission for an assistant to change arbitrary agents or place calls.
Client configuration formats differ. Use the endpoint and header above in the client’s current MCP configuration; do not put the key into a public widget or a shared configuration example. If the dashboard shows a loopback/backend address, use the hosted public API origin plus /api/v1/mcp/, or ask your workspace administrator for the reachable endpoint. For the opposite direction—an Athena voice agent using an external service’s MCP functions—follow External MCP tools.

​
External PBX integration

When your account uses a supported external PBX, enable External PBX integrations in Preferences and save to expose its advanced configuration. This toggle alone does not provision a PBX connection. For a configured Asterisk/ARI integration, open the agent’s General settings. Under External PBX Field Updates, choose Add mapping and map a gathered-context field (for example extracted_variables.qualified) to the provider-native destination field your PBX expects. Final values can be written before transfer or hangup. Each mapping needs both fields; destination fields allow letters, numbers, and underscores. Use Lead Fields To Capture to name the inbound lead fields to read, without the transport header prefix. A field must begin with a letter and use only letters, numbers, and underscores. Captured fields are available under initial_context.external_pbx_call.lead, for example {{initial_context.external_pbx_call.lead.customer_reference}}. Save the agent settings and publish after a controlled integration test. Verify the actual PBX write-back as well as the Athena run. Disabling the organization preference preserves existing configuration; it is not a provider-disconnection or data-deletion operation.

​
Billing and usage

Open Billing to inspect the balance, credits or allocation usage, and usage history available for your organization. Confirm the selected period and follow a linked run when reconciling a usage entry. Provider charges and Athena account usage are separate records. Purchase, payment, invoice, and refund options depend on what is enabled for your hosted account. Do not follow legacy upstream sign-up or self-hosting instructions to fund an Athena workspace. If the expected payment option is unavailable, contact your Athena workspace administrator. Only use payment/document actions actually offered by the hosted dashboard; planned billing changes are not instructions for an available checkout.

​
Dashboard overview

Use Overview for a summary of workspace activity, Agent Runs for individual executions, Retries for available manual retry review, and Reports for daily aggregation. Counts can use different scopes and time windows. Open a run or a scoped report to understand a total before comparing it with a campaign or usage period.