Product Manager

Case study

A Zendesk Platform Case Study: Automating Customer Feedback Workflows in Zendesk

This case study shares the steps to create a repeatable workflow for turning incoming customer feedback into structured product or service intelligence.

The opportunity

Customers often share their best product ideas in support conversations. The challenge is not collecting feedback once; it is consistently validating it, preserving it, routing it to the people who can act, and acknowledging the customer without adding manual work for agents.

The automated journey

Feedback submitted → Ticket created → Customer and product validated → Feedback stored → Product team notified → Customer acknowledged → Ticket resolved

Figure 1. End-to-end Action Flow with verified-customer and Else branches.

What this case study demonstrates

A complete workflow powered by Zendesk Action Flows and Custom Objects.
Connected actions across Zendesk, Google Sheets, and Slack.
A repeatable pattern for converting customer feedback into product action at scale.

The Dronetrix customer story

Dronetrix is a fictional drone company designed to represent a familiar Zendesk customer scenario: a company with registered products, engaged customers, a support operation, and a product team that needs a dependable stream of feedback.

Meet the customer

A Dronetrix customer has purchased and registered a drone. They are happy with the product overall, but they want longer battery performance. They submit a product feedback form through the Dronetrix Help Center.

Their message is simple: the drone is great, but better battery life would make it even more useful.

What happens next

Instead of asking an agent to research the customer, confirm the product, copy the request into a tracker, alert Product, and write a response, the workflow handles the entire sequence.

The feedback becomes a Zendesk ticket.
The flow gathers the ticket and requester context.
The customer's product registration is verified.
The battery improvement request is added to the enhancement log.
The Product team receives the feedback in Slack.
The customer receives a public reply.
The ticket is resolved.

The result

One customer interaction becomes a complete, traceable feedback loop, without depending on an agent to perform every handoff.

What powers the flow

The live automation is supported by six straightforward setup components. Together, they give the workflow the customer context, product context, storage destination, and communication channel it needs.

Step 1. Define the Product custom object

Dronetrix uses a Product custom object to store all the products that Dronetrix sells. Each product record represents a drone model or product offering and provides the product reference used when validating feedback.

Figure 2. Product custom object definition in Zendesk.

Step 2. Define the Registration custom object

Dronetrix uses a Registration custom object to store the products that each customer has registered. Each registration record links a customer to a Product record, so it represents the customer-to-product ownership relationship.

Figure 3. Registration custom object definition in Zendesk.

Step 3. Create Registration records

For each registered purchase, Dronetrix creates a Registration record linking the customer to the corresponding Product record. These records become the source of truth used by the ownership check.

Figure 4. Registration records linked to a customer account.

Step 4. Create the Help Center feedback form

A dedicated Help Center form lets customers submit product feedback and captures the drone in the ticket's Product field. Ticket creation starts the Action Flow; in a production account, the trigger should be scoped to this feedback form.

Figure 5. Product Feedback form configuration in Zendesk.

Step 5. Identify the Google account and Sheet you plan to use to store enhancement requests

Dronetrix uses an existing Google Sheet as a shared product enhancement log. Verified feedback can be appended as a new row with consistent fields.

Step 6. Identify the Slack instance and Product team's Slack channel you plan to connect

The Slack connector gives the workflow a direct path to the team responsible for reviewing and acting on product feedback. Invite the Zendesk Connector Slack application to the channel you would like to notify when new customer feedback is received and stored.

Phase 1: Capture and understand

The first part of the flow turns a customer submission into a fully contextualized Zendesk event.

1. Customer submits product feedback

The customer opens the Dronetrix Help Center form, identifies their drone, and explains that they like the product but would value better battery performance.

Figure 6. Populated Dronetrix Help Center feedback form.

2. Zendesk creates the ticket and starts the flow

The web form submission creates a Zendesk ticket. Ticket creation is the trigger that launches the Action Flow automatically.

Every qualifying feedback request enters the same process at the moment it is received.

3. The flow looks up the complete ticket

The workflow looks up the ticket by Ticket ID so downstream steps can use its Requester ID, Subject, Description, Product value, and received timestamp.

The flow works from complete context rather than a partial event.

4. The flow looks up the requester

Zendesk retrieves the customer associated with the ticket. The requester record provides the identity needed to search for the corresponding product registration.

Customer identity travels with the feedback and powers the validation step.

Figure 9. Look up the ticket requester (customer)

Phase 2: Validate and route

The middle of the flow determines whether the feedback should move directly into Dronetrix's product review process.

1. Search Registration records

The workflow searches Registration records using two filters together: Customer is the requester's Zendesk User ID, and Product is the Product value from the ticket. Results are sorted by Updated at.

Why it matters: Dronetrix can distinguish feedback tied to a matching customer-product registration from feedback that should not enter Product systems automatically.

Figure 10. Registration search filtered by customer and product.

2. Validate ownership

The search returns a Total count. When Total count is 1 or more, the flow treats ownership as verified; when it is 0, the flow enters the Else path. The battery feedback is now grounded in a matching customer-product registration.

Why it matters: The enhancement log stays connected to real product usage and useful customer context.

3. Branch based on the result

The workflow routes the ticket into one of two paths: a verified path when Total count is 1 or more, or an Else path when no matching registration is found.

Figure 11. Ownership branch using Total count ≥ 1.

Verified path

Store the feedback, share it with the right internal teammates, acknowledge the customer, and resolve the ticket.

Else path

Skip Google Sheets and Slack, send a public reply, and resolve the ticket.

Phase 3: Store, share, and close the loop

Once ownership is confirmed, the workflow completes the remaining actions automatically.

1. Append the feedback to Google Sheets

The workflow appends one row to Feedback on Drone Products → Drone workflow with six values in order: Ticket ID, Subject, Description, Requester ID, Product ID, and Received at.

Business value: Feedback becomes durable, organized data that can be reviewed, grouped, and prioritized over time.

2. Post the feedback to Slack

The workflow posts the verified request to #product-feedback with the Product, Subject, Description, and a link to the feedback spreadsheet.

Business value: The right people are notified immediately, without relying on an agent to forward or summarize the feedback.

Figure 13. Slack post configuration for the #product-feedback channel.

3. Reply publicly and resolve the ticket

Zendesk sends the customer a public reply confirming that their battery feedback has been received and shared with the Product team. The ticket is then resolved.

The customer knows their input was heard, where it went, and that the interaction is complete.

The closed loop

The customer's idea is no longer trapped in a support ticket. It is stored for analysis, visible to Product, connected to a verified customer and product, and acknowledged back to the person who shared it.

When ownership cannot be verified

If the search returns Total count = 0, the Else path runs. It does not append the request to Google Sheets or post it to Slack.

The Else path

The workflow sends a public customer reply; it does not add an internal message.
The active configuration currently uses the same gratitude reply as the verified path, even though the feedback was not sent to Sheets or Slack.
The workflow then sets the ticket status to Solved.

This branch keeps unverified feedback out of the Product team's destinations while still closing the customer interaction. For production, use distinct Else-path copy that asks the customer to register the drone or provide purchase details.

Value for Zendesk customers

Less manual work: agents no longer need to copy, paste, route, and acknowledge every feedback request.
More consistent execution: every qualifying submission follows the same validation and handoff process.
Better feedback quality: product ideas are tied to verified customers and registered products.
Faster visibility: Product receives actionable feedback as soon as it is validated.
A better customer experience: customers receive a timely acknowledgment that closes the loop.
A connected system of work: Zendesk orchestrates data and actions across service, customer records, Google Sheets, and Slack.

A reusable pattern for customer intelligence

Dronetrix is fictional, but the workflow represents a common need across industries. Customers routinely share ideas about products, services, policies, digital experiences, packaging, billing, and more. The same pattern can support any organization that needs to collect feedback, validate context, store it consistently, route it to an owner, and respond to the customer.

The pattern

Capture the customer's request in Zendesk.
Enrich it with ticket, customer, and product context.
Validate the relationship or transaction that makes the feedback relevant.
Route verified feedback into a structured system of record.
Notify the team that can evaluate and act on it.
Close the loop with the customer.

Why Zendesk

Zendesk is not only where feedback arrives. With Action Flows, Custom Objects, and connectors, it can orchestrate the entire journey from customer voice to internal action.

For Dronetrix, a request for better battery performance becomes more than a ticket. It becomes verified product intelligence, delivered to the right team and acknowledged back to the customer - automatically.

End-to-end outcome

Capture → Validate → Store → Share → Respond → Resolve

Thank you to Platform Teammates

Solution presented by Lauren Slack-Chen , Principal PM, Platform Applications, in collaboration with Ashwin Raju, Principal PM, Custom Objects, and Vaibhav Ghiware, Senior PM, Connectors.