Skip to main content

Guide: organize callbacks to dissatisfied customers

Automatically spot every dissatisfied customer, hand them over to the right person, call them back on time and measure the results.

F
Written by François Forest

Goal: every dissatisfied customer is called back quickly by the right person, who has their contact details and the context, and you track the handling time.

Who it's for, and before you start

Who it's for

The customer service or network manager who organizes callbacks (Admin or Editor)

Prerequisites

Feedback with a way to contact the customer again (email or phone) and a scope attribute (store, branch)

To prepare

Who calls back whom, and how quickly

Time

One hour

The steps

1. Define what a customer "to call back" is

Create a segment, for example: NPS from 0 to 6, or satisfaction below 40%, or the "Complaint" topic. See Filters, periods, segments and FQL.

With AI: topics and sentiment are assigned automatically by AI to each feedback, including reviews and tickets with no rating. A "negative sentiment" or "Complaint topic" segment therefore also catches unhappy customers who didn't leave a score. See Text Analysis.

2. Protect contact details

Set the email and phone attributes to Visible to assigned users, with a time limit if needed: only the person calling back sees them, and only during handling. See Attributes and referentials.

3. Prepare the people who call back

  • Invite them with the Restricted Viewer role: they only see the feedback assigned to them.

  • Turn on assignment emails in Settings → Advanced settings → Notifications.

4. Automate assignment

Create an automation triggered by the segment, with the Assign a user action. For a network, create one automation per store, or filter the segment on the store attribute. See Automations, alerts and action plans.

5. Call back and close

The assigned person opens the feedback in the feed, reads the verbatim, calls the customer back, adds a comment about the conversation, then changes the feedback's status to mark it as resolved. See Dashboard and feedback feed.

Before the call, the topics detected by AI on the feedback show the reason for dissatisfaction at a glance (waiting, price, quality…), even when the verbatim is long.

6. Measure

Create a resolution time KPI with the formula resolutionTime() / 3600 (in hours), and track it by store in a score table. See KPI formulas.

To understand what comes up most in callbacks, ask Ask Feedier: "What are detractors' main reasons for dissatisfaction this month?". See Ask Feedier and AI agents.

Example

Element

Setting

Segment

"Detractors to call back": NPS from 0 to 6, with a phone number

Phone visibility

Visible to assigned users

Automation

Assign to the store manager, notify by email

Target

Callback within 48 hours, tracked every week

Common mistakes

Mistake

Consequence

What to do

Leaving contact details public

Personal data visible to everyone

Visibility limited to assigned users

Not closing feedback

Skewed resolution time, no way to track

Change the status after each callback

A segment that's too broad

Too many callbacks, teams disengage

Start with the most severe detractors

Going further


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?