Skip to main content
Lehar agents talk to users over three channels. The same agent configuration (prompt, variables, knowledge base) can drive any of them.

​
Web voice

A browser participant connects to a media room and talks to the agent over WebRTC. You create a session, then connect the returned participant_token with a voice client. Best for in-product voice assistants and click-to-talk experiences.

​
Outbound phone

The agent dials a recipient over SIP and runs the same conversation loop. From your backend, fire one call with POST /calls (API key), or run a voice campaign to place many. To try an agent on a real phone, create a session with call_type: "outbound_phone" and a phone_number — a test path for a signed-in user, one live call per workspace at a time. Requires an outbound SIP trunk on the deployment.

​
WhatsApp

Text conversations delivered through WhatsApp (via the messaging provider). Two campaign types use this channel:
  • whatsapp — the agent holds a text conversation with the recipient.
  • whatsapp_voice — sends an approved template, waits for a reply, decides whether the recipient wants a call, and escalates to the outbound voice path when they do.
WhatsApp sends are governed by the 24-hour customer-service window (free-form messages are only allowed within 24h of the last inbound message; outside it, only approved templates). See the WhatsApp guide.

​
At a glance

Sessions

Web and phone voice calls.

WhatsApp

Templates, windows, and escalation.