Skip to article
Bridge

Use an AI agent to bring Zendesk tickets into customer meetings

Customers remember their open support tickets even when the account team doesn't. This agent looks up the people in an upcoming meeting in Zendesk and lists their tickets, open ones first. Its instructions keep it to reading, and Bridge never changes anything in Zendesk without your confirmation.

The job: know the open tickets before the call

A customer call goes badly when the customer raises a ticket nobody on your side knew about. The context existed, just in Zendesk.

This agent closes that gap before the call. It finds the tickets tied to the people you're meeting and summarizes them. It doesn't reply, update tickets or promise anything.

  • Collecting feature requests from calls for the product team is a different job; see the customer feedback agent.

What it reads in Zendesk

With Zendesk connected, Bridge can read three kinds of support context. This agent uses all three.

  • Search tickets by keyword, status, priority, assignee, requester, tags or date.
  • Open a ticket: its subject, status, priority, tags, requester and assignee, plus a summary of the conversation, internal notes included.
  • Look up people: find customers or agents by name or email.

Keep it read-only

Zendesk also lets Bridge act: add internal notes, update a ticket's status, priority, assignee or tags, create tickets and reply to customers. This agent doesn't need any of that, so its instructions tell it to read only.

Two safeguards apply either way. Bridge never changes anything in Zendesk without your confirmation. Ticket content is treated as information only, and instructions written inside a ticket are never followed.

Set it up

  • Connect Zendesk from the Connectors page, under the Support category. Zendesk asks for your Zendesk subdomain before you authorize.
  • Select Create Agent from the sidebar. In Identity, name it, for example Ticket Context, and paste instructions like the ones below.
  • In Tools, select Zendesk under Connectors.
  • In Triggers, keep @mention, which is always on. Creating and using agents needs a paid Bridge plan.

Example instructions

These instructions are illustrative. Adjust the time window and fields to how your support team works.

  • "Only read Zendesk. Never add notes, update, create or reply to tickets."
  • "Look up each customer in this meeting in Zendesk by name or email."
  • "Search tickets where that person is the requester, from the last 90 days."
  • "List open tickets first, with subject, status, priority and what the customer is waiting on. Then list solved tickets in one line each."
  • "If you find nothing, say so. Never suggest a fix date or make a promise."

Run it before the call

Open the Assistant on the upcoming meeting. It's scoped to preparation: participants, prior conversations and connected-tool history. Type the agent's @handle and ask for the ticket summary.

If you also want it during the call, add the Proactively during meetings trigger. It contributes privately through the Assistant while Join meetings and talk is off. Leave that ability off for this agent, so its ticket summaries stay private to you.

Example: a renewal call

This example is illustrative. Before a renewal call with Acme's operations lead, you @mention the agent on the upcoming meeting.

It returns two open tickets: a failed data export and a billing question waiting on your finance team. You raise both at the start of the call, before the customer has to.

Limits

  • Zendesk only for now. Intercom isn't available yet.
  • Read-only is an instruction, not a setting. The safeguard Bridge applies is your confirmation before any Zendesk change.
  • Check the first few summaries against Zendesk before you rely on them in front of a customer.

Sources & further reading