Callback API: call a customer back from your website
A visitor leaves a number, your team is called first, then the customer, and the two are connected. Custom quote pricing.
Custom quote
Web callback lets a visitor ask to be called back. They enter their number in a form, and your application sends a request to the API.
TELQIO first calls the team member in charge of the callback. When they pick up, the platform calls the customer and connects the two calls. The customer is called only when someone is ready to talk.
You can attach a call flow to handle absences: hours, a fallback queue, a message. Each callback keeps a readable status: ringing, connected, completed or failed.
How it flows
Practical uses
Real estate callback request
A buyer leaves a number on a listing and an agent calls back within the hour.
Automotive contact
A visitor asks for a test drive and the advisor starts the callback when available.
Customer service
Offer a callback instead of a wait on hold.
Lead qualification
Call back forms received outside opening hours the next morning.
Features
- Callback triggered by an API request
- Team called first, customer second
- Attached flow for hours and absence cases
- Readable call statuses for each step
- Callback log by project
- Call events sent through a signed webhook
Limits to know
- A callback needs a valid customer number and a country open to outbound calls in your contract.
- A callback produces at least two calls. Depending on the contract, they can create several usage lines.
- A customer who does not answer or hangs up early had no conversation, even if the call rang.
- The person called must be informed of the callback and must have given their number for that purpose. The exact duty is determined by the service, the country and your role.
curl -X POST "https://api.example.test/v1/calls" \
-H "Authorization: Bearer tq_test_EXEMPLE" \
-H "Idempotency-Key: 7b1d2c4e-0000-4000-8000-000000000004" \
-H "Content-Type: application/json" \
-d '{
"from": "+33199001234",
"to": "+33199001235",
"project_id": "project_a",
"flow_id": "flow_callback_example"
}'
# => { "id": "call_example", "status": "ringing", "simulated": true }Technical details
| Trigger | POST /calls with a callback flow_id |
|---|---|
| Call order | Team first, customer second, then connection |
| Statuses | ringing, connected, completed, failed |
| Events | call.connected, call.completed, call.failed |
Frequently asked questions
Why call the team before the customer?
So someone is ready when the customer picks up. The customer is not left waiting on an unanswered line.
What if nobody on the team answers?
The attached flow can offer a fallback: another person, a queue, or a new attempt. Without a fallback, the callback is marked failed.
Can I schedule a callback for later?
Your application decides when to send the request. The API starts the call when it receives it.
Related use cases
Documentation
Related services
Let's set up your callbacks
Describe your site, your teams and the countries involved. We will prepare a quote and an example journey.