Live Data Guide: Let Your AI Voice Agent Check Orders, Bookings and Payments During the Call
Live Data lets your AI agent check your own system during the call — order status, a booking, a payment — and tell the caller the answer right away. You add a lookup on the agent: a name, when to use it, what to ask the caller, and your URL. During the call the agent says “one moment”, your URL answers, and the agent speaks only what your system sent.
How a lookup works on a call
- The caller asks something — “where is my order?”
- The agent asks for what the lookup needs — for example the order ID.
- The agent says a short holding line (“एक सेकंड, मैं चेक करती हूँ”). At the same moment TaskVox sends the details to your URL.
- Your system answers within 4 seconds.
- The agent tells the caller the answer, in the caller's language — only from what your system sent.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#how-it-works
Step 1 — Turn it on
- Paid account: Live Data is already on. Go to Step 2.
- Free account: recharge once (from ₹500) under Billing. Live Data turns on by itself.
- Open Agents → your agent → Edit. Scroll to the Live Data card.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#turn-on
Step 2 — Add a lookup
- Press + Add lookup.
- Start from: pick a template — Order status, Booking / appointment or Payment status — or Custom.
- Name: a short name, for example “Order status”. It is sent to your URL as
order_status(small letters, spaces become_). - When should the agent use it? one plain sentence — “The caller asks where their order is, or about delivery”.
- Fill the next two boxes (Steps 3 and 4) and press Save lookup.
- Need more? Add up to 5 lookups per agent — one for each question type.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#add-lookup
Step 3 — Choose what the agent asks
- In What to ask the caller, write the details your system needs, separated by commas — for example
Order IDorSchool name, City. - Up to 5 per lookup. Keep it short: ask only what you really need to find the record.
- Under the box you see the exact names your server gets — “Order ID” →
order_id, “customerName” →customername. Read these names on your side. - Do not add the phone number. The caller's number is always sent by itself.
- The agent can only send the fields you listed — nothing else from the call leaves TaskVox.
Tip: name fields in plain words with spaces (“Order ID”, “Customer name”). They become clean names like order_id and customer_name.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#fields
Step 4 — Make your URL (your API, Make or n8n)
Each lookup has its own full URL, for example https://api.yourshop.com/taskvox/order-status. It must start with https:// and be reachable on the internet.
No server yet?
- On the Order status, Booking or Payment template, click Use the demo URL. It answers with sample data, so you can try a real call today.
No developer? Use Make or n8n:
- Create a scenario that starts with a Webhook (Make: “Custom webhook”; n8n: “Webhook”). Copy its URL into the lookup.
- Add a step that searches your Google Sheet or CRM by the field — for example
inputs.order_id. - End with Webhook response (Make) or Respond to Webhook (n8n) that sends back the row's status.
Your own API:
- Add one endpoint that accepts a POST with JSON (format below in What your URL receives).
- Find the record using
inputs(andcall.callerPhoneif you look up by phone). - Answer with short JSON — only the facts the caller needs.
- Answer fast: under 1.5 seconds is best, 4 seconds is the limit. If your server sleeps when idle, keep it awake, or the first call of the day can time out.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#your-url
Step 5 — Test it
- On the saved lookup, press Test.
- Type a sample value (for example a real order ID) and press Send test request.
- You see what your server answered and how many milliseconds it took.
- Then make a real test call to the agent and ask the question.
- After the call, open it in Call Logs — every lookup shows what was checked, how long it took and whether it worked.
Common fixes:
| What you see | What to do |
|---|---|
| “did not answer within 4 seconds” | Make your server faster, or keep it awake. Make/n8n: check the scenario is switched on. |
| “must start with https://” | Use the https address of your server or webhook. |
| “points to a private network” | The URL must be public on the internet — not a 192.168.x / office-only address. |
| HTTP 401 / 403 | Your server refused the request — check your signature code uses this lookup's secret (see below). |
| HTTP 404 | The path is wrong — copy the full URL again. |
| Your server got empty values | Read the field names exactly as shown under the box (Step 3), e.g. order_id, not orderId. |
| The + Add lookup button is missing | Free account — recharge once (Step 1). Or the agent already has 5 lookups. |
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#test
Step 6 — Write the agent's prompt
- You do not need to explain the URL in the prompt. Saved lookups are given to the agent automatically.
- Just tell the agent what it helps with — “You help customers with order status and store locations.”
- Caller's number: do not write
{{caller_number}}. It is not a variable — the number already goes to your URL incall.callerPhone. - Today's date: do not write
{{today}}. The agent always knows today's date and the next few days (India time). {{...}}variables come only from the columns of a campaign CSV — for example{{name}}.- For a question your system cannot answer, use call transfer to a human (agent settings) instead of “your request is recorded”.
Link to this step: taskvox.in/blog/ai-agent-live-data-lookup#prompt
What your URL receives and answers
POST https://your-server.com/taskvox/order-status
Content-Type: application/json
X-TaskVox-Timestamp: 1793090900
X-TaskVox-Signature: <hex HMAC-SHA256 of "timestamp.body" with your lookup's secret>
{ "action": "order_status",
"inputs": { "order_id": "A123" },
"call": { "id": "…", "agentId": "riya-support", "callerPhone": "98XXXXXXXX" } }
action— the lookup's name in small letters with_.inputs— only the fields you listed, with the names shown in Step 3.call.callerPhone— the caller's phone number, always sent.- Answer with short JSON or text, for example
{"status": "Shipped", "expected_delivery": "Friday"}. Up to 8 KB. The agent will not read field names out loud. - Nothing found? Answer that plainly —
{"found": false}— and the agent will say so.
Link to this section: taskvox.in/blog/ai-agent-live-data-lookup#request
Check the signature (recommended)
- On the lookup, press Show secret. Each lookup has its own secret — keep it private.
- On your server, recompute the signature and refuse anything that does not match:
const crypto = require('crypto');
function fromTaskVox(req, rawBody, secret) {
const ts = req.headers['x-taskvox-timestamp'];
const expected = crypto.createHmac('sha256', secret).update(ts + '.' + rawBody).digest('hex');
return expected === req.headers['x-taskvox-signature'] && Math.abs(Date.now() / 1000 - ts) < 300;
}
Link to this section: taskvox.in/blog/ai-agent-live-data-lookup#signature
Limits to remember
- Up to 5 lookups per agent, 5 fields per lookup.
- Up to 3 lookups in one call.
- 4 seconds for your answer; up to 8 KB.
- Only https URLs on the public internet; every request is signed.
- A failed or slow lookup is said honestly — the agent never guesses an answer.
Link to this section: taskvox.in/blog/ai-agent-live-data-lookup#limits
Use cases
- E-commerce / D2C: order status, delivery date, return or exchange status by order ID.
- Clinics and hospitals: “Is my appointment confirmed?” — doctor, date and time by phone number.
- Education: application or admission status; next batch dates.
- Finance and insurance: EMI or premium due date and amount, payment received or not.
- Logistics and courier: shipment location and expected delivery by tracking number.
- Service businesses (solar, AC, automobile): complaint or service-request status, technician visit time.
- Retail with stores: nearest store and timings by city.
Frequently asked questions
How do I turn Live Data on?
It is on for every paid account. On a free account, recharge once (from ₹500) and the Live Data card on your agent's edit page unlocks by itself.
Does the caller wait in silence while the agent checks?
No. The agent first says a short line such as “एक सेकंड, मैं चेक करती हूँ” and the check runs while it speaks, so most answers are ready by the time the line ends.
What if my system is slow or down?
TaskVox waits up to 4 seconds. If there is no answer, the agent says it cannot check right now and offers that your team will call back — it never makes up an answer.
Do I need to send the caller's phone number myself?
No. Every request already carries it in call.callerPhone. Do not add it as a field and do not write {{caller_number}} in the prompt.
Can the agent send any details it likes?
No. Each lookup sends only the fields you listed for it (up to 5), with the names shown under the field box — for example “Order ID” arrives as order_id.
How many lookups can a call make?
Up to 3 per call, and an agent can have up to 5 different lookups (for example order status, booking and payment).
Do I need a developer?
Not always. Your URL can be a Make or n8n webhook that searches a Google Sheet or your CRM and sends back the answer. If you have your own system, a developer adds one small endpoint.
Answer the question on the first call
100 free credits to test · Live Data on every paid account