/
/
Find the Shopify story behind bad Zendesk ratings
For support and CX leaders who want each bad Zendesk rating traced to the customer's Shopify orders, by asking their AI assistant.
On this page
Connector
Connect Shopify, pick your AI tool and paste the prompt.
The problem
Bad ratings rarely say what actually went wrong
A bad satisfaction rating in Zendesk rarely says what went wrong, and the answer is often in Shopify: a late parcel, a refund dispute or a failed payment. Matching each rating to orders by hand takes too long, so the pattern and the revenue at risk go unseen.
Without PopdockAI
- Export bad ratings from Zendesk
- Find each requester's orders in Shopify
- Check fulfillments and refunds around the rating
- Guess at the pattern across customers
With PopdockAI
- Bad ratings are read and each requester identified
- Shopify spend, orders, fulfillments and refunds are pulled
- Each rating gets one likely cause, ranked across all ratings
- The five highest-spend unhappy customers are named, read-only
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Review the bad Zendesk satisfaction ratings from the last `{lookback-days}` days (default 30). For each one, find the customer's Shopify orders, and report what went wrong and how much revenue the unhappy customers represent.
**Step 1: Bad ratings**
Call `zendesk-get-satisfaction-rating` with score set to bad (check the tool schema for the exact value) and created.from set to `{lookback-days}` days ago. Note satisfaction-rating-id, ticket-id, ticket-subject, comment, requester-id, assignee-name, group-name and created-date.
**Step 2: Who they are**
For each distinct requester-id, call `zendesk-get-user` filtered by user-id and note name and email.
**Step 3: Their Shopify history**
For each email, call `shopify-get-customer` filtered by email and note total-spent, orders-count and last-order-name. Then call `shopify-get-order` filtered by email, created-at.from 60 days before the rating, and note each order's name, financial-status, fulfillment-status and cancelled-at.
For orders that are unfulfilled, partly fulfilled or refunded, record why: call `shopify-get-fulfillment` or `shopify-get-refund` filtered by order-id as needed. Keep this light, one or two calls per order.
**Step 4: Classify**
Give each rating one likely cause, from the ticket subject, the rating comment and the order state: late or missing delivery, damaged or wrong item, refund dispute, payment problem, product question, not order-related.
**Step 5: Report**
* A summary: ratings reviewed, customers found in Shopify, their combined lifetime spend.
* Causes ranked by count.
* A table: ticket-id, customer, total-spent, orders-count, cause, the related order and its state, assignee.
* The five highest-spend unhappy customers, with the one follow-up each most needs.
**Rules & Guidelines:**
* `zendesk-get-satisfaction-rating` and `zendesk-get-user` are on the zendesk server. `shopify-get-customer`, `shopify-get-order`, `shopify-get-fulfillment` and `shopify-get-refund` are on the shopify server.
* This prompt is read-only. Do not call `zendesk-add-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-ticket`, `shopify-update-customer` or any other write tool.
**Validation:**
* If there are no bad ratings in the period, say so and stop.
* If a requester is not a Shopify customer, keep the rating with cause not order-related unless the comment says otherwise.Who it's for
One answer, three teams that use it
Support team leads
Find the cause behind bad ratings
Causes are ranked, so you can see whether delivery, wrong items or refunds drive most complaints.
What caused our bad Zendesk ratings in the last 30 days? Check the customers' Shopify orders.
Customer experience managers
Call the customers who matter most
The five highest-spend unhappy customers are named with the follow-up each needs.
Which high-spend Shopify customers gave us bad ratings in Zendesk this quarter?
Operations managers
Fix the order problems behind complaints
Late deliveries and wrong items tied to ratings show where fulfilment needs work.
How many bad Zendesk ratings last month were caused by late Shopify deliveries?
How it works
What PopdockAI does when you ask
You name a lookback period, and your AI assistant traces each bad Zendesk rating to the customer's Shopify orders. It only reads both systems.
01
Ask
You name a lookback period.
02
Read
It reads bad Zendesk ratings and identifies each requester.
03
Trace
It pulls their Shopify spend, orders, fulfillments and refunds around the rating.
04
Report
You get causes ranked and the five highest-spend customers to follow up.
What PopdockAI provides
The tools behind the answer
Ready made tools for Shopify and one secure connection to your AI tool. No code, no exports.
zendesk-get-satisfaction-rating
zendesk-get-user
shopify-get-customer
shopify-get-order
shopify-get-fulfillment
shopify-get-refund
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.
The outcome
Know what drives bad ratings and who to call first
Related use cases
More ways to put this data to work
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.

.webp)
