Speed to lead is the single biggest lever in travel sales, and an outbound call placed seconds after an enquiry is how you pull it. This guide explains the moving parts: what triggers a call, what the request looks like, how to stay on the right side of consent, and what comes back when the call ends.
Why outbound beats waiting
An inbound assistant helps the people who call you. An outbound trigger reaches the far larger group who filled in a form and went back to browsing. Calling them while the trip is still on screen changes the conversation entirely.
The trigger
Any event in your stack can start a call: a quote form submission, a CRM stage change, an abandoned booking, a payment that failed. Most teams start with the quote form because the intent is unambiguous and the value of speed is highest.
The request
A call is a single authenticated request carrying the number, the agent to use and the context the agent should know before dialling. Include an idempotency key so a retried webhook does not ring the traveller twice.
POST /v1/calls
{
"agent_id": "travel-sales",
"to": "+447700900123",
"idempotency_key": "enquiry-48213",
"context": {
"destination": "Crete",
"dates": "late May, flexible",
"party": "2 adults"
},
"window": {"earliest": "09:00", "latest": "20:00", "timezone": "Europe/London"}
}Respecting consent and hours
Only trigger calls where the traveller has asked to be contacted, record that consent with the enquiry, and enforce local calling hours in the request so a 2 a.m. form submission becomes a 9 a.m. call. These are legal requirements in most markets and good manners everywhere.
What comes back
When the call ends you receive a webhook with the outcome (answered, voicemail, no answer, booked, handed over), the captured fields, a summary and a link to the transcript. Write that straight into the CRM record that triggered the call and the loop is closed.
The best time to call a lead is while they are still looking at your website. The API makes that the default.
