Document agents, queues, calls, analytics, and call-center workflows as a coherent product

The current public OpenAPI mirror already includes substantial call-center coverage. The portal should organize that surface into agent management, queue operations, call control, analytics, and workflow orchestration.

Docs mode

Reference and guide

Keep the task clear, the example nearby, and the next step obvious.

Back: USSD Next: OTP Verification

Product slices that matter

Agent management

Queue operations

Outbound and inbound calls

IVR and flows

Analytics and reports

AI-assisted processing

Representative endpoints

POST /api/v1/callcenter/calls/outbound

GET /api/v1/callcenter/queues

GET /api/v1/callcenter/agents

GET /api/v1/callcenter/analytics/dashboard

GET /api/v1/callcenter/ivr/flows

Portal guidance

Do not dump every call-center endpoint onto one reference card. Lead with high-level workflows and route developers into the specific API reference pages when they need lower-level queue, agent, or flow controls.

Voice docs Full reference

USSD

OTP Verification

Contact Center

Agents, queues, calls, analytics, and AI-assisted call-center workflows

The current public contract already includes extensive call-center APIs. Present them as product surfaces for agents, queues, calls, analytics, and workflow operations instead of dumping the full endpoint matrix into one page.

Endpoint

POST /api/v1/callcenter/calls/outbound

Outbound call

curl --request POST {BASE_URL}/api/v1/callcenter/calls/outbound \
        --header "Authorization: YOUR_API_KEY"   --header "Content-Type: application/json" \
  --data '{
    "to": "+251900000000",
    "queueId": "queue_123",
    "flowId": "flow_123"
  }'

Quick links

Voice docs Call-center reference Operational support

Ask the assistant

How do I create an outbound call?