Smart Auto-Response Based on Ticket Content

Respond to routine support requests instantly, even after hours.

Nora reads incoming Zendesk tickets, identifies common issues (password reset, billing, returns), and sends templated responses immediately while queuing for agent follow-up.

When a new ticket arrives in Zendesk, Nora reads the subject and message content. It classifies the issue type based on the text. If the request matches a common category like password resets, billing inquiries, or returns, Nora immediately adds a public reply with the relevant information and next steps. It then appends an internal note with the classification and assigns the ticket to the appropriate agent group for follow-up.

Support agents no longer spend their first hour clearing out routine overnight requests. They log in to a queue where basic inquiries already have an initial response. Agents review the internal notes, handle the complex cases that require human judgment, and adjust priority levels if a customer replies needing further assistance.

Runs real-time as tickets arrive using Zendesk, run by your Customer Support.

How it works

  1. Detect new incoming tickets — Nora polls the Zendesk API to identify newly created support tickets. It retrieves the ticket ID, requester details, subject line, and the full body text of the initial message sent by the customer.
  2. Classify the request content — Nora analyzes the subject and message text to determine the issue category. It checks the content against known frequent request types such as password resets, billing questions, or return authorizations.
  3. Flag ambiguous ticket requests — If the ticket contains multiple unrelated questions or the issue type is unclear, Nora skips the automatic public reply. It adds an internal note indicating the classification failed and leaves the ticket unassigned in the main queue.
  4. Send the public reply — For clearly identified common issues, Nora updates the ticket with a public reply. It inserts the correct response text for that category, addressing the customer's specific question while setting expectations for any necessary agent follow-up.
  5. Update tags and internal notes — Nora applies relevant tags to the ticket based on its classification. It adds an internal note summarizing the action taken and assigns the ticket to the designated support group for review.

What this replaces

Support agents start their shifts by reading through the backlog of tickets that accumulated overnight. They open each ticket, read the request, identify the issue, apply the appropriate macro or copy-paste a standard response, and update the ticket status. They then manually assign the ticket to the correct department or agent.

Rough estimate rather than a measured figure: about 45 minutes a day, on the basis of 30 overnight tickets taking 90 seconds each to read, categorize, and reply.

What it needs to run

Accounts and plans

Access it asks for

What Nora reads

What Nora writes

When it goes wrong

Who this is for

Worth it if

Not worth it if

A worked example

A 30-person software company receives frequent export and invoice requests overnight. Nora is configured to identify these topics, reply with the relevant knowledge base link, and assign them to the Tier 1 support group.

Public reply added to Ticket #49281:

Hi Sarah,

Thanks for reaching out. You can export your monthly activity data by navigating to Settings > Data Export and clicking 'Generate CSV'. I have also assigned this ticket to our billing team to ensure your recent invoice is attached to your account. They will review this and follow up shortly.

Best,
Support Team

Internal note added:
Nora classification: Data Export / Billing. Sent standard export instructions. Assigned to Tier 1 Billing group.

Frequently asked questions

Can I change the text of the automatic responses?

You tell Nora in plain language what you want the response to say. If you need the billing response to include a new link to your payment portal, you send a message in your chat channel asking Nora to update the billing reply template. The change applies to the next matching ticket.

What happens if Nora misinterprets the customer's request?

If Nora sends a password reset link but the customer actually wanted to change their billing email, the customer will reply stating the confusion. This reply goes straight to the human agent's queue. Agents can see the initial auto-response in the ticket thread and correct the issue manually.

Does Nora close the ticket after replying?

No. Nora leaves the ticket open and assigns it to the relevant agent or group. The automation is designed to provide an immediate initial response, not to resolve the ticket entirely. A human agent always has the final review before the ticket status changes to solved.

Will Nora respond to every single ticket that comes in?

Nora only sends a public reply if the ticket content clearly matches one of your defined common categories. If a ticket is complex, vague, or covers a topic Nora does not recognize, it simply adds an internal note stating it could not classify the issue and leaves it for your team.

Connects to

Related automations

Start a 2-week free trial · Browse all automations