Customer service counter with a tablet, overlaid by a glowing technical network that converges into a star and a speech bubble shape, fully AI generated and marked with the EU label
All solutions28 / Customer feedback

Customer feedback

Evaluate and route customer feedback automatically

Every review and piece of feedback from online platforms, email or a contact form is automatically sorted by topic and urgency and routed to the right place in the company. Critical feedback reaches the responsible person immediately, instead of sitting unnoticed in an inbox or review platform for days.

Process architecture

From a single review to the right reaction.

The process collects reviews and feedback from every channel in use, recognises topic, tone and urgency, and routes each case to the right place. Non-critical feedback is evaluated in aggregate, critical individual cases go straight to a named person – a reply is always drafted by a person, never automatically by the process itself.

Process diagram

  • 09Nodes
  • 09Connections
  • 03Phases
Environment

01Input

Open quotes and their context come together.

The process starts with silence rather than a message: a quote that has had no answer for days. The leading system supplies the quote, its deadline and the contact, together with the correspondence already attached to the case.

2 Steps

02Process

The right message is derived from the state of the case.

The draft comes from the quote itself, not from a template full of placeholders. The rules then check whether a follow-up is allowed at all; anything outside the agreed frame goes to a salesperson.

4 Steps

03Output

The message goes out and the case stays traceable.

The follow-up sits in the same conversation as the quote, sales sees the current state without asking, and every attempt is documented on the case.

3 Steps

Source01

Capture the feedback

A new review or piece of feedback comes in through a review platform, a contact form or email – via Microsoft Power Automate, Google Apps Script or a custom shared inbox, depending on the environment.Details

Process node 01Source

Capture the feedback

A new review or piece of feedback comes in through a review platform, a contact form or email – via Microsoft Power Automate, Google Apps Script or a custom shared inbox, depending on the environment.

Interfaces
  • Microsoft Graph API
  • SharePoint API
Next steps
Data02

Add context

Existing customer data and earlier reviews from the same person are added from the CRM or the point-of-sale system, where available.Details

Process node 02Data

Add context

Existing customer data and earlier reviews from the same person are added from the CRM or the point-of-sale system, where available.

Interfaces
  • Azure AI Document Intelligence
  • Mistral OCR
  • Dataverse API
Next steps
Action03

Recognise topic and tone

A language model reads the text and assigns it a topic (product, service, delivery, price) and a tone ranging from clearly positive to clearly negative.Details

Process node 03Action

Recognise topic and tone

A language model reads the text and assigns it a topic (product, service, delivery, price) and a tone ranging from clearly positive to clearly negative.

Interfaces
  • Power Automate
  • Azure Functions
  • Microsoft Graph API
Next steps
Decision04

Check urgency

The process checks whether the review, tone and topic exceed the defined threshold for a critical case, for example a very negative review or a publicly visible platform.Details

Process node 04Decision

Check urgency

The process checks whether the review, tone and topic exceed the defined threshold for a critical case, for example a very negative review or a publicly visible platform.

Interfaces
  • Azure OpenAI GPT
  • Anthropic Claude
  • AI Builder
Next steps
Approval05

Present the critical case

Above the threshold, the responsible person receives the text, its context and a suggested reply before any public or direct response is given.Details

Process node 05Approval

Present the critical case

Above the threshold, the responsible person receives the text, its context and a suggested reply before any public or direct response is given.

Interfaces
  • Teams Adaptive Cards
  • Power Apps
Next steps
System06

Classify non-critical feedback

Feedback below the threshold is filed by topic into the ongoing evaluation without triggering an individual case.Details

Process node 06System

Classify non-critical feedback

Feedback below the threshold is filed by topic into the ongoing evaluation without triggering an individual case.

Interfaces
  • Dynamics 365 API
  • Azure Service Bus
Next steps
Result07

Complete the reaction

For critical cases, the approved reply is published on the original channel or sent directly to the person.Details

Process node 07Result

Complete the reaction

For critical cases, the approved reply is published on the original channel or sent directly to the person.

Interfaces
  • Power BI API
  • Teams Webhook
Next steps
Result08

Inform the responsible people

A daily or weekly overview shows the distribution of topics, the tone trend and open critical cases.Details

Process node 08Result

Inform the responsible people

A daily or weekly overview shows the distribution of topics, the tone trend and open critical cases.

Interfaces
  • Power BI API
  • Teams Webhook
Result09

Archive the feedback

Every review is filed with its topic, tone, urgency and the reaction taken, searchable for later evaluation.Details

Process node 09Result

Archive the feedback

Every review is filed with its topic, tone, urgency and the reaction taken, searchable for later evaluation.

Interfaces
  • Power BI API
  • Teams Webhook
  • Standard path
  • Direct path
  • Review required
  • Return

Steps in execution order

System landscape

The same process in three environments.

  • Microsoft

    Microsoft Graph API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    SharePoint API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure AI Document Intelligence

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Mistral OCR

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Dataverse API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power Automate

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure Functions

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure OpenAI GPT

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Anthropic Claude

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    AI Builder

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Teams Adaptive Cards

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power Apps

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Dynamics 365 API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Azure Service Bus

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Power BI API

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Microsoft

    Teams Webhook

    Möglicher Baustein für die Microsoft-Systemvariante.

  • Interfaces in use

    Google Workspace APIs

    Google environment: reads feedback from Gmail and sends notifications through Google Chat.

  • Interfaces in use

    REST API

    Individual environment: reads reviews directly from review platforms and writes them to the CRM.

  • Interfaces in use

    Webhook

    Forwards a new review immediately once a connected platform publishes it, instead of waiting for the next scheduled run.

  • Interfaces in use

    Azure AI Language

    Recognises the topic and tone of feedback in the Microsoft environment.

  • Interfaces in use

    Google Cloud Natural Language API

    Recognises the topic and tone of feedback in the Google environment.

  • Possible apps & platforms

    Microsoft Teams und Microsoft Outlook

    Notification and shared inbox in the Microsoft environment.

  • Possible apps & platforms

    Gmail und Google Chat

    Shared inbox and notification in the Google environment.

  • Possible apps & platforms

    Google Business Profile und Bewertungsportale

    Source of publicly visible reviews, independent of the chosen environment.

  • Possible apps & platforms

    CRM-System

    Holds customer data and earlier feedback in the individual environment.

Implementation in context

What the process does and what it deliberately leaves to people.

The process does not decide the content of a reply – it sorts and routes. What is said in response to a critical review is always decided by a person; the process only presents the case with context and a suggestion.

The environment determines the tools, not the process. In a Microsoft 365 environment recognition and notification run through Power Automate and Teams, in a Google Workspace environment through Apps Script and Gmail, in a self-hosted environment through a custom integration between review platforms and CRM. Which variant fits depends on where the company already runs its customer communication.

The urgency rule is clearly defined: a combination of a very negative tone, public visibility of the channel and, where available, customer value determines whether a case is presented immediately. Ambiguous cases – such as a sarcastic comment that is hard to classify – default to critical rather than being filed automatically into the non-critical collection.

All evaluated reviews remain searchable, filed with topic, tone and the reaction taken. That makes it possible to see over time whether a recurring topic signals a genuine need for action, instead of looking at every review in isolation.

Starting point

Customer feedback today arrives through many channels at once: review platforms, contact forms, email, sometimes social media. Without a fixed structure, each channel is checked separately and irregularly; a critical review on a public platform can go unanswered for days, while positive feedback goes unused because nobody evaluates the topics systematically.

Target picture

Every review is sorted by topic and urgency immediately. Critical feedback reaches the responsible person within a short time with context and a suggested reply, while non-critical feedback flows into an ongoing evaluation of topics and tone trends.

Expected benefits

  • Critical feedback reaches the responsible person within a short time instead of only being found by chance.
  • Reviews from every channel are evaluated consistently by topic and tone, no longer per channel in isolation.
  • The reply to a critical case always remains a human decision; the process only prepares it.
  • Recurring topics become visible through the ongoing evaluation instead of only after a manual summary.
  • Positive feedback is not lost, flowing into the same evaluation as critical feedback.
  • The process adapts to the existing environment instead of making an additional reputation management tool a precondition.

Prerequisites to start

  • 01Access to the review platforms and contact channels in use, from which feedback can be read automatically.
  • 02A defined threshold for which combination of tone and visibility counts a case as critical.
  • 03A named owner for critical cases per channel or topic area.
  • 04A CRM or comparable storage for customer data, if earlier reviews should be taken into account.
  • 05A decision on the environment: Microsoft 365, Google Workspace or self-hosted – and the matching access rights.

Your next step

Which process costs your team unnecessary time every day?

Give us a short outline. We will tell you honestly where automation is useful—and where it is not.

DiscoverBack to top