AI conversations inside your Dialpad call routing

Use Dialpad’s API Call Router to decide which calls go to Simple, then route or transfer the conversation to the right Dialpad destination.

Talk to our team

From Dialpad to Simple and back

Dialpad requests a routing decision

Simple handles the conversation

Dialpad receives the handoff

What you can do with Dialpad

01 / CALL ROUTING

Choose which calls reach Simple

Use an API Call Router to forward selected calls to an external number while keeping a Dialpad fallback target.

02 / TRANSFERS

Return calls to the right destination

Transfer an active call to a Dialpad target, another call, or a phone number when an agent is needed.

03 / EVENT DATA

Keep systems informed

Attach custom data to a transfer and receive it through subscribed Dialpad call events.

Hand off without losing the thread

Route to the right Dialpad team

Send the call to a contact center, department, office, user, or other configured target.

Track what happened

Use call-event subscriptions and custom data to keep downstream systems aligned with the transfer.

Built around Dialpad routing and call APIs

Dialpad’s API Call Router can route calls to an internal target or forward them to an external E.164 number. The Call Transfer API can move an active call back to a Dialpad destination.

Dialpad’s public documentation does not define a native third-party AI-agent node, so this integration should be designed as a routing, forwarding, transfer, and event connection.