# Support Ticket AI Callback: Call the Customer When a Ticket Opens

> Have an AI voice agent call the customer when an urgent support ticket opens, gather details and update the ticket. Edesy Helpdesk setup, costs, limits.

Source: https://edesy.in/blog/helpdesk-ticket-ai-callback-2026

A support ticket AI callback works like this: when an urgent ticket is created in **Edesy Helpdesk**,
its signed `ticket.created` webhook goes to **n8n or Make** (or your server), which looks up the customer's phone,
asks the **AI voice agent** to call, and afterwards updates the ticket's status and tags. The customer
hears back in minutes instead of waiting in a queue, for Rs 6 a minute of agent time on pay as you go.

One honest limit up front: today the call summary can't be posted into the ticket thread through the
Helpdesk API key, so it is stored alongside, linked by ticket number. Details below, and the
click-by-click setup is in the [support ticket AI callback tutorial](https://edesy.in/docs/voice-agent/recipes/support-ticket-ai-callback).

## What is a ticket callback?

Instead of replying to a new ticket by email and waiting, you call the customer. For urgent tickets
(service down, order not delivered, device not working) a call resolves in five minutes what takes
five emails. An AI agent can make that first call for every urgent ticket, the moment it arrives,
including at 8 pm when your team has gone home.

This is a narrower recipe than replacing your support line with AI; for that, see
[AI voice agents for customer support](https://edesy.in/blog/ai-voice-agent-customer-support-call-center-2025).

## Why it matters

Customers who raise an urgent ticket usually also call, WhatsApp and email, because they don't know
whether anyone has seen it. A callback within minutes stops that duplicate contact and tells the
customer someone is on it. In India, where many customers prefer to explain a problem by phone in
their own language, the call often gets better details than the ticket form did.

An **illustrative** example (assumed numbers): an internet service provider gets 150 "no connection"
tickets a month. The AI agent calls each within minutes, walks through the router restart from the
knowledge base, and confirms whether it fixed the problem. About a third close on the call; the rest
reach a technician with the router model, lights status and a convenient visit time already
recorded.

## How the setup works: trigger, voice call, write-back

| Step | How | Status |
|---|---|---|
| Ticket created | Edesy Helpdesk webhook `ticket.created`, signed with `X-Helpdesk-Signature: sha256=…` | Native webhook |
| Filter and look up phone | n8n or Make: condition on priority, lookup by requester email | Via webhooks in n8n or Make |
| AI call | `POST /api/v1/calls` from the same scenario | Via API |
| Update the ticket | Helpdesk public API `PATCH /api/public/v1/tickets/:id` (status, priority, tags) | Via API |
| Store the summary | Google Sheets (native post-call step), Edesy Tables or Slack, keyed by ticket number | Native for Sheets; others via API |
| Native "AI callback" action in Helpdesk, summary on the ticket | Not built yet | Planned |

### 1. Trigger

In Edesy Helpdesk, add a webhook for `ticket.created` pointing at an n8n or Make webhook.
The payload contains the ticket ID and number, subject, status, priority, channel and the requester's
email. Add a condition so only `HIGH` or `URGENT` tickets (or a category you choose) get a call.

The webhook has **no phone number**, so add a lookup step: find the customer by email in your CRM,
Edesy Tables or your own database. If you can, add a phone field to your support form so it is always
there.

### 2. Voice call

Add an **HTTP Request** to `POST https://voice-agent.edesy.in/api/v1/calls` with:

- **Header:** `Idempotency-Key` set to the ticket ID, so a retried webhook doesn't call twice
- **Variables:** `customer_name`, `ticket_number`, `ticket_id`, `subject`, `priority`

Give the agent a knowledge base of your help articles and known fixes, and a **transfer to a person**
action for anything outside them.

### 3. Write-back

Subscribe a second scenario to `call.analyzed`. When it arrives with the disposition, summary and the
`ticket_id` you passed in `variables`:

- **Update the ticket** through the Helpdesk public API with your API key: add tags such as `ai-called`
  and `fixed-on-call`, and set the status (`PENDING` waiting on a technician, `RESOLVED` if fixed).
- **Store the summary and recording link** in Edesy Tables or a sheet with the ticket number, or post
  it to the support channel in Slack, so the agent who opens the ticket can read it.

> **Try it yourself:** [Build a support callback agent free](https://voice-agent.edesy.in/signup?utm_source=edesy.in&utm_medium=blog&utm_campaign=helpdesk-ticket-ai-callback-2026&utm_content=inline) and call yourself with a test ticket.

## A sample call script

> **Agent:** Hello Ms Rao, this is the support assistant from FastNet. I'm calling about your ticket
> 10482, "no internet since morning". Is this a good time?
>
> **Customer:** Haan, subah se net nahi chal raha.
>
> **Agent:** Sorry about that. Kya aap router ki lights check kar sakti hain? Kya red light jal rahi
> hai?
>
> **Customer:** Haan, red light hai.
>
> **Agent:** Thank you. Please switch the router off for 30 seconds and on again. I'll wait.

If the restart doesn't help, the agent books a technician slot and ends with "Your ticket number is
10482 and our technician will call before the visit." If the customer is upset, it transfers.

## What does it cost?

Edesy's published prices, excluding 18% GST. Volumes are assumptions:

| Item | Example |
|---|---|
| Urgent tickets per month | 150 |
| Calls answered | 120 (assumed 80%) |
| Average call | 3 minutes (360 minutes) |
| Pay as you go (Rs 6/min) | about Rs 2,160 |
| Pro (Rs 1,499 incl. 300 min, then Rs 5/min) | about Rs 1,799 |
| Telephony | billed separately |

## Email reply vs agent callback vs AI callback

| | Email reply | Support agent calls | AI callback |
|---|---|---|---|
| Time to first contact | Hours | Depends on queue | Minutes |
| After hours | Next morning | Rarely | Yes, within your calling window |
| Fixes known issues | Slowly, back and forth | Yes | Yes, from the knowledge base |
| Handles angry or complex cases | Poorly | Yes | Transfers to a person |
| Cost driver | Agent time | Agent time | Per minute |

## Consent, DND and calling hours

- **The customer raised the ticket**, so a call about it is a service call. Keep it to the issue.
- **Tell customers you may call** on the support form ("We may call you about this ticket").
- **Calling hours:** 9 am to 9 pm IST, unless the customer asked to be called at another time. Set the
  agent's calling window.
- **Verify before sharing account details** on the call, for example by confirming the registered email.
- **Do-not-call:** if they prefer email, add the number to **Settings → Blocked Numbers** and skip calls
  for their future tickets. Edesy does not check numbers against the NCPR (DND) registry.

Not legal advice.

## What it can't do

- **It can't post the call summary into the ticket thread** through the Helpdesk API key today; it
  updates status, priority and tags, and stores the summary alongside.
- **The webhook has no phone number.** You need it from your CRM or the support form.
- **No built-in Freshdesk, Zendesk or Zoho Desk connector.** Use their webhooks into n8n or Make.
- **Check which channels fire `ticket.created`.** It fires for tickets created in the dashboard or the
  API; test it for email or portal tickets before relying on it there.
- **No native AI callback in Helpdesk yet** (planned); we can set one up [on request](https://edesy.in/integrations/request?ref=helpdesk-ticket-ai-callback-2026).
- **It shouldn't handle refunds, disputes or legal complaints.** Transfer those to a person.

## Related recipes

- [AI payment reminder calls for overdue invoices](https://edesy.in/blog/ai-payment-reminder-calls-overdue-invoices-2026)
- [Google Sheets and the AI voice agent](https://edesy.in/blog/google-sheets-ai-voice-agent-auto-call-2026): a simple
  place to keep call summaries
- [Appointment reminder calls](https://edesy.in/blog/appointment-reminder-calls-clinics-2026): the same pattern for
  technician visit reminders
- Use case: [AI voice agent for customer support](https://edesy.in/ai-voice-agent/use-cases/customer-support)

**Using a different helpdesk?** [Tell us which one](https://edesy.in/integrations/request?ref=helpdesk-ticket-ai-callback-2026)
and we'll suggest the best way to connect it.

## Start free

Follow the [step-by-step ticket callback tutorial](https://edesy.in/docs/voice-agent/recipes/support-ticket-ai-callback),
then [sign up and build your agent](https://voice-agent.edesy.in/signup?utm_source=edesy.in&utm_medium=blog&utm_campaign=helpdesk-ticket-ai-callback-2026&utm_content=footer).
Running a larger support team? [Book a demo](https://edesy.in/demo?product=voice-agent).

## Frequently Asked Questions

### Can an AI voice agent call a customer when they open a support ticket?

Yes. Edesy Helpdesk sends a signed ticket.created webhook for each new ticket. An n8n or Make scenario (or your own server) checks the priority, looks up the customer's phone number, and asks the AI voice agent's Calls API to call. The agent gathers details or solves common issues from your knowledge base, and the workflow updates the ticket's status and tags.

### Does the call summary go back into the ticket?

Partly, today. Edesy Helpdesk's public API (API key) can update a ticket's status, priority and tags, so your scenario can tag it 'ai-called' and set it to Pending or Resolved. Posting the call summary as a ticket reply is not available through the API key yet, so keep the summary and recording link in Edesy Tables, a sheet or Slack, linked by ticket number.

### Where does the customer's phone number come from?

The ticket.created webhook carries the ticket number, subject, status, priority, channel and requester email, but not a phone number. The scenario looks the phone up by email in your CRM, Edesy Tables or customer database, or you collect it on the support form.

### What support issues can an AI callback handle?

Routine ones with clear answers: order or booking status, how-to questions covered by your knowledge base, collecting details for a technician visit, and confirming whether an issue is resolved. Billing disputes, angry customers and anything needing judgment should be transferred to a person.

### How much does an AI support callback cost?

Rs 6 a minute on pay as you go, plus telephony. For example, 150 urgent tickets a month with 120 answered calls of 3 minutes each is 360 minutes: about Rs 2,160 on pay as you go, or about Rs 1,799 on Pro (Rs 1,499 including 300 minutes, then Rs 5 a minute). Prices exclude GST.

### Does this work with Freshdesk or Zendesk?

Through the same pattern, if your helpdesk can send a webhook when a ticket is created: point it at n8n, Make or your server and call the voice agent's Calls API. There is no built-in Freshdesk or Zendesk connector in the voice agent.
