Connect Callex to your stack.

Overview

Integration happens in three stages. A Callex engineer works alongside your team through each one, so you are not wiring things up on your own.

Before you start

A short checklist of what your team needs in place before the first integration call.

• Phone numbers you can route to Callex over SIP, or a carrier we can connect to.
• Admin access to the systems you want the agent to read from and write to.
• A technical contact on your side. We pair them with a Callex engineer for the build.
• An idea of the calls you want to handle first, so we can scope the initial agent.

Connectors

Connect both sides of the call: the telephony that carries it, and the systems of record the agent reads and updates.

Custom actions

Expose your endpoints as actions the agent can call mid-conversation: look up an account, book a slot, update a record. Agent calls are authenticated, scoped, and logged.

• Scoped, signed requests
• Guardrails on agent actions
• Audit trail

# Action definition
action book_appointment {
  endpoint: POST /appointments
  auth: bearer (scoped)
  params: patient_id, time, clinic
}

Webhook events

Subscribe to call events to keep your systems in sync in real time. Every payload is signed, so your endpoint can verify it came from Callex.

# POST to your webhook URL
{
  "event": "call.completed",
  "call_id": "call_8842",
  "outcome": "appointment_booked",
  "duration_sec": 134,
  "transcript_url": "https://…"
}

Security & data

Callex supports encrypted transport, scoped action credentials, and audit logging for integration calls. Action credentials are scoped and designed to stay separate from transcripts, and integration activity is logged for review where configured.

Guides