Connectors

/

Zendesk

/

Log a Zendesk ticket for a customer
Write

Log Zendesk tickets for customers without duplicates

For support agents who take requests by phone or email and want them logged in Zendesk once, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Log a Zendesk ticket for a customer
Log a Zendesk ticket for jordan.lee@fabrikam.com: they cannot download last month's invoices from the portal.
Jordan Lee at Fabrikam has no open ticket about invoice downloads, so this will be new. - Requester: Jordan Lee, Fabrikam - Subject: Cannot download last month's invoices - Details: the portal download fails for last month's invoices - Priority: left blank, as this is not an outage Shall I create the ticket?
Zendesk
Sample figures. Your results come from your own account.
zendesk-get-user
zendesk-get-ticket

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

Tickets logged for customers pile up as duplicates

Logging a ticket for a customer who phoned or emailed you means checking they exist and have not already raised the same issue. Skip the check and the queue fills with duplicates to merge.

Without PopdockAI

  • Search Zendesk for the customer
  • Scroll their open tickets for the same issue
  • Guess a priority
  • Merge the duplicates later

With PopdockAI

  • The customer is found, and suspended users stop it
  • Open tickets are checked for the same issue
  • Priority is set only for a clear outage or blocker
  • The ticket is created once after you confirm

The prompt

Use this prompt

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

Prompt
**Objective:** Create a Zendesk ticket for the customer `{requester-email}` with subject `{subject}` and first comment `{details}`, without creating duplicates.

**Step 1: Find the requester**

Call `zendesk-get-user` with email `{requester-email}`.

* Found and suspended is true: stop and tell the user this person is suspended.
* Found: keep the user-id and organization-name.
* Not found: the ticket can still be created with requester-email, and Zendesk will create the user. Say this in the confirmation.

**Step 2: Look for a duplicate**

Call `zendesk-get-ticket` with requester-email `{requester-email}` once each for status new, open and pending. Compare each subject with `{subject}`. If any looks like the same issue, list them with ticket-id, subject and status and ask whether to add to that ticket instead. If the user picks an existing ticket, call `zendesk-add-ticket-comment` once with that ticket-id and body `{details}` (public true) after they confirm, then skip to Step 5.

**Step 3: Confirm**

Show the user the requester (name and organization if known), subject, details, and any priority or type you intend to set. Only set priority when the details clearly describe an outage or a blocked customer (use high or urgent); otherwise leave it blank. Wait for an explicit yes.

**Step 4: Create once**

Call `zendesk-add-ticket` exactly once with subject `{subject}`, comment `{details}`, and requester-id if the user was found, otherwise requester-email `{requester-email}`.

**Step 5: Report**

Call `zendesk-get-ticket` with the returned id and report ticket-id, subject, status, requester-name and group-name.

**Rules & Guidelines:**

* The only writes allowed are one `zendesk-add-ticket`, or one `zendesk-add-ticket-comment` on a chosen duplicate, after confirmation.
* Do NOT call `zendesk-add-user` or `zendesk-update-user`; `zendesk-add-ticket` handles an unknown requester.
* Do not set assignee-id, group-id or tags; routing rules do that.

**Validation:**

* If `{requester-email}` is not a valid email address, stop and ask.
* If `{details}` is empty, ask for it; a ticket needs a first comment.

Who it's for

One answer, three teams that use it

Account managers

Log a customer issue straight from a call

Turn a phone call or email into a ticket on the right requester, without opening Zendesk or checking their history first.

Open a Zendesk ticket for priya@contoso.com, their SSO login fails since this morning.

Support agents

Avoid duplicate tickets from side channels

If the customer already has an open ticket on the same issue, you can add to it instead of creating a second one.

Log a ticket for tom.reyes@northwindtraders.com about missing shipping labels, unless he already has one open.

Customer success managers

Raise issues on behalf of your accounts

Log what a customer told you with the right priority, and let your routing rules send it to the right team.

Create a Zendesk ticket for dana@fabrikam.com: their whole team is blocked from the reporting module.

How it works

What PopdockAI does when you ask

You give the customer email and the details, and your AI assistant checks for an existing ticket on the same issue. Nothing is created until you have seen the ticket and confirmed.

01

Ask

You give the customer email, a subject and the details.

Your AI tool

02

Check

It finds the customer and looks for an open ticket on the same issue.

zendesk-get-user
zendesk-get-ticket

03

Confirm

You see the requester, subject, details and any priority before it is created.

No items found.

04

Create

It creates the ticket once and reads it 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-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-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.
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

One ticket per issue, on the right requester

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