Workflow Template
Customer Feedback Follow-Up Workflow
Captures customer feedback and score, classifies it with AI, and routes low scores or high-value customers to an owner for follow-up while logging other feedback. The owner records the action taken, follows up with the customer, and closes the item with a category for reporting.
Most teams collect customer feedback and then let it sit in a spreadsheet until someone remembers to check it — by which time the angry customer has already churned. The Customer Feedback Follow-Up Workflow captures every response, uses AI to classify it instantly, and routes low scores or high-value accounts straight to an owner for action while everything else gets logged automatically. The result: every piece of feedback gets a documented action, a follow-up, and a closure category — with nothing falling through the cracks.
Business Outcomes
- 100% of feedback captured and classified with no manual sorting
- Faster response time to at-risk and high-value customers
- Zero unactioned low-score feedback items
- Full audit trail of action taken, follow-up, and closure category
- Reporting-ready data with consistent category tagging
Workflow Steps
Steps
- 1Create Feedback Recordcreate record
Registers the submitted feedback as a record.
- 2Set Status to Receivedupdate record
Marks the feedback as received.
- 3Classify Feedbackai classification
Uses AI to categorise the feedback content.
- 4Check Classification Confidence
Routes low-confidence classifications to human review.
_ai_clf_classify_feedback_needs_human_review: "true"→Manually Review ClassificationDefault→Route by Score / Customer Value - 5Manually Review Classificationcreate task
Support lead confirms the correct feedback category.
- 6Persist Reviewed Categoryupdate record
Saves the manually confirmed category to the record.
- 7Route by Score / Customer Value
Low scores or high-value customers go to an owner; others are logged.
score: "5"→Assign Owner for Follow-Upis_high_value_customer: "true"→Assign Owner for Follow-UpDefault→Log Feedback - 8Log Feedbackupdate record
Marks the feedback as logged for reporting without follow-up.
- 9Assign Owner for Follow-Upassign user
Assigns a support owner to handle low-score or high-value feedback.
- 10Set Status to Under Reviewupdate record
Marks the feedback as under review by the owner.
- 11Record Action Takencreate task
Owner investigates the feedback and records the action taken.
- 12Persist Action Takenupdate record
Saves the recorded action to the feedback record.
- 13Follow Up With Customersend email
Sends a follow-up email to the customer regarding their feedback.
- 14Close Item with Categorycreate task
Owner selects the final closure category for reporting.
- 15Persist Closure Category and Statusupdate record
Saves the final category and marks the item closed.
Fields
- Customer Name*
- Customer Email*
- Feedback*
- Score (0-10)*
- High-Value Customer
- Feedback Status
- +2 more fields
Forms
Customer Feedback Form
5 fields
Data Views
All Feedback Items
customer_name, customer_email, score, feedback_status +1 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
What happens if the AI classification confidence is low?
The workflow includes a built-in Check Classification Confidence step that flags any low-confidence result for manual review. A reviewer sees the original feedback and the AI's suggested category, corrects it if needed, and the reviewed category is persisted to the record automatically. This keeps your reporting data accurate without requiring manual review of every single item.
Can this handle both low-score feedback and high-value customer feedback with the same logic?
Yes, the Route by Score / Customer Value step checks both conditions and routes the item to an owner if either threshold is met. You can customise the score threshold and the definition of a high-value customer directly in assess.one's workflow settings. Feedback that doesn't meet either condition is automatically logged without needing owner involvement.
What if a customer never responds to the follow-up?
The owner can record the follow-up attempt in the Follow Up With Customer step and still move the item to Close Item with Category, selecting a category such as 'no response' or 'unresolved.' The status and closure category are persisted for reporting, so unresponsive customers are still tracked rather than left open indefinitely. You can add a reminder notification or escalation rule if follow-up attempts need to be capped at a certain number.
Who needs access to this workflow?
Anyone submitting or logging feedback needs access to create a record, while owners assigned for follow-up need edit access to record actions and close items. You control these permissions directly inside assess.one, assigning roles at each step so reviewers, owners, and reporting viewers only see what's relevant to them. No IT ticket or external access request is required.
How do we customise the categories used for classification and closure?
Both the AI classification categories and the closure categories are configurable fields inside the workflow builder. You can edit the category list, add new ones, or retire old ones without touching any code or waiting on a development cycle. Changes take effect immediately for any new feedback entering the workflow.
What if we have multiple teams handling different types of feedback?
You can extend the Assign Owner for Follow-Up step with routing logic based on category, product line, or region so each team only sees the feedback relevant to them. This is configured directly in assess.one's assignment rules, no separate system integration needed. Each team still logs their action, follow-up, and closure category into the same central record for unified reporting.
How long does it take to get this workflow up and running?
This is a ready-to-use template, so publishing it takes minutes, not weeks. Once published, your team can start creating feedback records and running the process live immediately. You can adjust steps, roles, or routing rules at any time without re-implementing anything.
Are approvals or sign-offs required before a feedback item can be closed?
By default, the owner closes the item after recording the action taken and completing the follow-up, but you can add an approval step before closure if your team requires manager sign-off. This is configured directly in the workflow's approval logic inside assess.one. It's commonly added for feedback categorized as high severity or linked to high-value accounts.
Can we get reporting on the feedback categories over time?
Yes, because every item is persisted with its final classification and closure category, you can build reports segmented by category, score, owner, or resolution time. This reporting is available directly within assess.one without needing to export data to another tool. Consistent categorization at closure ensures the reporting stays clean and comparable across periods.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
