Webhook tools
Voice agent webhook: data from your system, in the middle of the call
A voice agent webhook is an address in your own system that the Kallina agent calls during the conversation, passing what the customer has told it, to get an answer it can't have in its script: an order's status, a balance, a repair. The agent reads the response and puts it to the customer in its own words. That's how you connect Kallina to any system with an API, even one not on our integrations list.
- ClientI ordered a sofa yesterday. Do you know when it's coming?
- AgentCould you give me the order number? I'll check right now.
- ClientFour, seven, two, eight.
- AgentThe order is at the warehouse and goes out on Thursday; the courier will call you an hour before.
What a webhook tool is for
The script tells the agent how to talk, but it can't hold data that changes from hour to hour. A webhook tool fills that gap: the agent asks your system a short question, gets the answer within moments and carries on with fresh information, without handing the customer over to an operator.
- The status of an order, a delivery or a repair
- Stock for a product, or a price from a list that changes
- A customer's details, found by phone number or by a code
- A request logged in your system while the call is still going
What you fill in for a tool
A tool is defined in the agent editor and has six fields.
| Field | What it's for | Example | |
|---|---|---|---|
| Name | What the tool is called in the agent's instructions | order_status | |
| Description | When the agent should use it, written as you would for a new colleague | Use it when the customer asks where their order is | |
| URL | The address in your system that receives the request | An endpoint on the shop's side, just for the agent | |
| Method | The HTTP request type: POST, GET, PUT or PATCH | POST, the default | |
| Request fields | What the agent asks the customer for and sends, described as a JSON schema | The order number, as text | |
| Timeout | How many seconds the agent waits for the answer | 30 seconds by default, adjustable |
What data moves, and in what order
During the conversation the agent decides to use the tool based on its description. First it collects the fields the schema asks for — an order number, say, or a date of birth — and may read them back to be sure. Then it sends the request to your URL with the chosen method and waits for the answer no longer than the timeout you set.
Your system returns a response, usually JSON, with what the customer needs to know. The agent doesn't read it out word for word: it uses it to put together a natural reply in the language of the call. That's why the response should carry only the fields that matter, with clear names and nothing the agent shouldn't say.
Every use of the tool is kept in the conversation history in Kallina: the tool's name, the parameters sent, the response received, how long it took and whether it succeeded. When a customer says they were told something wrong, you can see straight away whether the mistake came from your system or from how the agent phrased it.
How we launch a new tool
We pick the question
We start with a question customers ask often and that today is answered by someone looking it up in a program.
You prepare the endpoint
Your team builds an endpoint that accepts the chosen fields and returns only what the agent needs.
We write the description
We describe the tool in plain words: when the agent uses it, what it asks the customer and what it does if nothing is found.
We test with calls
We call with real cases and wrong ones, then read in the history what the agent sent and what it got back.
We go live
The tool becomes part of the agent's script on your number, and for the first few days we watch the history together.
Examples from different trades
- Online shop
- A customer asks where their parcel is. The agent asks for the order number, the tool returns the status and the delivery day, and nobody waits in a queue for a single line of information.
- Car service
- The owner wants to know whether the car is ready. The tool looks up the registration number in the workshop's software and reports the stage; the final price still comes from the service adviser.
- Delivery or courier company
- The recipient calls to move a delivery. The tool logs the request in the company's system, and the agent tells them a dispatcher will confirm it.
Keeping the endpoint and the data safe
An endpoint only for the agent
We recommend a separate endpoint that can do no more than what you've asked of the agent: it reads a status, it doesn't change a whole account.
We agree on protection together
The tool form has no separate field for headers. How you protect the endpoint is something we decide during setup — for example with a long, hard-to-guess key in the URL.
Only the fields you need
Whatever your system returns may end up in the agent's reply and stays in the history. Don't send data the customer shouldn't hear.
When the system goes quiet
If the answer doesn't arrive within the timeout, the agent is left without the data it asked for. The description tells it what to do then: take a phone number, or transfer to a person.
What the webhook integration doesn't do today
It doesn't send a webhook after every call
Kallina doesn't currently notify an external system automatically at the end of each call. The outcome gets there through the CRM integrations or a flow.
It doesn't write your code
The endpoint and its response are built by your team or your system's vendor. We spell out exactly which fields the agent sends and what it expects back.
It isn't a public Kallina API
Kallina doesn't have a documented public REST API yet; API access is something we discuss on request. Webhook tools work the other way round: the agent asks you.
Webhook tools and flow trigger URLs
Besides the tools the agent uses during a call, Kallina has URLs that start a flow in the flow builder. The direction is reversed: your system calls Kallina — so that a new form on your website kicks off a series of steps, for instance. The flow can also send a response back to whoever started it.
In short, a webhook tool answers “what do I tell the customer right now?”, while a flow URL answers “what do I start when something happens on your side?”. Many projects use both, each for its own job.
What a webhook integration costs
Webhook tools aren't billed separately: they're part of the agent's monthly package, $99 or $300, with credits consumed by call time. Your side — the endpoint and its response — is built by your team; we specify it and test it during setup.
Try the live agent
The agent on the demo line isn't connected to your system, but it shows you how it asks for a number, reads it back and talks once it has an answer.
Call the live agent: +373 79 325 040In the demo we take one of your questions and sketch the tool's fields together.
Frequently asked questions
What does our system need?
An internet-reachable endpoint that accepts an HTTP request with the chosen fields and returns a short response. If the system already has an API, a thin layer on top of it is often enough.
How fast does it have to respond?
As fast as possible: the customer is waiting on the line. The default maximum is 30 seconds, but a simple question should get its answer within moments.
Can the agent write data too, not just read it?
Yes, if your endpoint allows it — to log a request, for example. We recommend keeping writes few and having a person check them.
How many tools can one agent have?
Several, each with its own name and description. The clearer the descriptions, the better the agent picks the right tool.
Does it work in Romanian and Russian?
Yes. The fields and the response can be in any language; the agent talks to the customer in the language of the call.
Can I see what the agent sent?
Yes. Each conversation's history shows the parameters sent, the response received, the duration and whether the request succeeded.
Where webhook tools are used
- AI delivery operator
The agent answers questions about orders and deliveries from your system's data.
- AI voice agent for online stores
Order status, returns and product questions, over the phone.
- AI voice agent for car services
The stage of a repair, read from the workshop's software through a webhook.
- SIP voice agent
How calls to your number reach the agent.
- Guide: your first voice agent
What to prepare before going live and how to test the script.
- Facts about Kallina AI
The company, languages, integrations and the agents' limits, in one place.
Sources
The tool fields and the call history were checked in the Kallina platform code on 18 November 2026.
Bring the question you answer most often
We'll turn it into a tool together: what the agent asks, what it sends and what it says back.