Connectors

/

Zendesk

/

Assign and reply to a Zendesk ticket
Write

Assign Zendesk tickets and reply in one confirmed step

For support agents and leads who want a Zendesk ticket assigned to the right agent and group, with a reply sent, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Assign and reply to a Zendesk ticket
Assign Zendesk ticket 51877 to jordan.lee@contoso.com, set it to pending and reply that we are looking into the export error.
Jordan Lee is not in the Billing group, so the ticket would move to their default group, Tier 2. - Assignee: Unassigned to Jordan Lee - Group: Billing to Tier 2 - Status: open to pending - Public reply: Thanks for your patience, we are looking into the export error and will update you shortly. Shall I make this update?
Zendesk
Sample figures. Your results come from your own account.
zendesk-get-ticket
zendesk-get-user
zendesk-get-group-member
zendesk-get-group
zendesk-get-ticket-comment

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Zendesk

Zendesk
Run it on your own Zendesk data.

Connect Zendesk, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Assigning a ticket takes more screens than replying to it

Assigning a Zendesk ticket fails if the agent is not in the ticket's group, and finding the right agent, group and status takes several screens. Get it wrong and the ticket bounces or the reply lands on the wrong ticket.

Without PopdockAI

  • Look up the agent and check their groups
  • Change the group if the assignment fails
  • Set the status and type the reply separately
  • Reply on the wrong ticket in the rush

With PopdockAI

  • The agent is matched to an active agent or admin
  • The group changes to theirs when needed
  • You see old and new values and the exact reply first
  • One update applies it all and is read back

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Assign Zendesk ticket `{ticket-id}` to agent `{assignee}` (a name or email), optionally set status `{new-status}` (default leave unchanged), and post the reply `{reply}` if one is given.

**Step 1: Load the ticket**

Call `zendesk-get-ticket` with ticket-id `{ticket-id}`. If nothing comes back, say so and stop. If status is closed, stop: closed tickets cannot be changed.

**Step 2: Resolve the agent to an id**

`zendesk-update-ticket` needs an assignee-id, and the ticket only carries a name, so look the agent up:

* If `{assignee}` contains @, call `zendesk-get-user` with email set to it.
* Otherwise call `zendesk-get-user` with name set to it; if that returns nothing, retry with name.contains.

Keep only users whose role is agent or admin and whose active is true. If none remain, stop and say why. If several remain, list them with email and stop.

**Step 3: Check the group**

Call `zendesk-get-group-member` with user-id set to the agent's user-id. If the ticket's current group-name is one of the agent's groups, keep it. Otherwise pick the agent's default-group, call `zendesk-get-group` with that group-name to get its group-id, and plan to move the ticket there, because Zendesk rejects an assignee who is not in the ticket's group.

**Step 4: Confirm**

Show the user: ticket-id, subject, current and new assignee, current and new group, current and new status, and the exact reply text (public). Ask for confirmation and wait. Do not continue without an explicit yes.

**Step 5: Update once**

Call `zendesk-update-ticket` exactly once with id `{ticket-id}`, assignee-id, group-id if it changes, status if `{new-status}` is given, and, if `{reply}` is given, comment set to it with comment-public true.

**Step 6: Confirm the result**

Call `zendesk-get-ticket` with ticket-id `{ticket-id}` and report the stored assignee-name, group-name and status. If a reply was sent, call `zendesk-get-ticket-comment` with ticket-id `{ticket-id}` and show the newest comment.

**Rules & Guidelines:**

* The only write allowed is one call to `zendesk-update-ticket`, after the user confirms. Do NOT call `zendesk-add-ticket-comment` separately; the reply goes in the same update.
* Do NOT call `zendesk-add-group-member` to make an agent fit a group.
* Never change priority, type, subject or tags in this prompt.

**Validation:**

* If the update fails, report the error and do not retry automatically.
* If `{new-status}` is not one of new, open, pending, hold or solved, stop and ask.

Who it's for

One answer, three teams that use it

Support agents

Hand off a ticket and reply in one go

Assign a ticket to a colleague, set its status and send the customer a reply in one confirmed update.

Assign Zendesk ticket 52310 to Maria Lopez, mark it open and tell the customer she will follow up today.

Support team leads

Route tickets without group errors

When the agent is in a different group, the ticket moves to their default group, so assignments do not bounce back.

Give ticket 50998 to sam.patel@fabrikam.com and reply that we are checking the invoice.

Dispatch and triage

Reassign tickets with no guesswork

If a name matches several agents you see the candidates, so the ticket goes to the person you meant.

Reassign Zendesk ticket 51440 to Alex in Tier 2 and set it to pending.

How it works

What PopdockAI does when you ask

You give the ticket, the agent and optionally a status and reply, and your AI assistant works out the right group. Nothing changes until you have seen the before and after and confirmed.

01

Ask

You give the ticket, the agent, and optionally a status and a reply.

Your AI tool

02

Resolve

It matches an active agent and moves the ticket to their group if needed.

zendesk-get-ticket
zendesk-get-user
zendesk-get-group-member
zendesk-get-group

03

Confirm

You see the old and new assignee, group and status and the exact reply.

No items found.

04

Update

It applies everything in one update and reads the ticket back.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Zendesk and one secure connection to your AI tool. No code, no exports.

get-data

zendesk-get-ticket

Returns Zendesk support tickets with their status, priority, requester, assignee, group and organization. Filter by status, priority, assignee, group or dates to find the tickets you need.
get-data

zendesk-get-user

Returns Zendesk users, including end users (customers), agents and admins, with their email, role, organization and when they were last active.
get-data

zendesk-get-group-member

Returns Zendesk group memberships, showing which agents belong to which group and which group is each agent's default.
get-data

zendesk-get-group

Returns Zendesk agent groups, such as support teams and tiers, with their names and descriptions.
get-data

zendesk-get-ticket-comment

Returns the comments on a Zendesk ticket, both public replies and internal notes, with their author and when they were posted.
Read only.Nothing in Zendesk Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

The right agent, the right group, one step

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation