Skip to main content

Automations, alerts and action plans

Trigger actions on your feedback (alerts, assignments, recurring reports, Teams, Salesforce) and turn your verbatims into action plans with AI.

F
Written by François Forest

Menu → Automations and Menu → Action plans

In short: an automation runs actions when a feedback enters a segment, or at regular intervals. An action plan is an AI analysis that turns your feedback into prioritized improvement areas.

Who can use them?

Action

Admin

Editor

Viewer

Restricted Viewer

Create an automation

✅

✅

🚫

🚫

Create and edit their own action plans

✅

✅

✅

✅

Edit other people's action plans

✅

✅

🚫

🚫

The Automations and Action plans modules are enabled per role in Settings → Access management. Automations and action plans are only visible in the team where they were created.

Create an automation

  1. In Automations, create a new automation.

  2. Choose the trigger.

  3. Add one or more actions.

  4. Save, then publish.

Trigger

When it runs

Example

Segment

Each time a new feedback enters the segment

Each customer service detractor

Recurrence

At regular intervals (every day, week, month…)

Every Monday at 8 a.m.

Actions

Action

Typical use

Assign a user

Hand each detractor over to the store manager

Email alert

Get notified of each critical feedback, or receive a digest

Feedback feed digest

Receive a segment's new feedback by email

Generate a report

Produce and send a report every month, optionally one per attribute value

Microsoft Teams notification

Post new feedback in a Teams channel

Salesforce actions

Enrich a feedback or create a record in Salesforce. See Salesforce.

Update an action plan

Refresh an action plan's results at regular intervals

An automation only applies to new feedback. Feedback already received doesn't go through automations again, even after a referential change.

One report per manager

  1. Create an Owner-type attribute (for example store), and link one or more emails to each value.

  2. Create an automation with a Recurrence trigger and a report generation action.

  3. Turn on Create multiple reports and select the attribute.

  4. In the Email tab of the Messages block, leave Share reports with owners turned on.

Each owner receives only the report for their value.

Send feedback to Microsoft Teams

  1. In Power Automate, create a flow with the When a Teams webhook request is received trigger (Who can trigger the flow? = Anyone).

  2. Add the Post a card in a chat or channel action (Post as: Flow bot; Post in: Channel), with this card:

{  "type": "AdaptiveCard",  "version": "1.2",  "body": [    { "type": "TextBlock", "text": "@{triggerBody()?['title']}", "weight": "Bolder", "size": "Medium" },    { "type": "TextBlock", "text": "@{triggerBody()?['message']}", "wrap": true }  ]}
  1. Save, turn on the flow and copy the webhook URL.

  2. In Feedier, create an automation on the segment you want, add the Send a notification to Microsoft Teams action, paste the URL, then publish.

Action plans

An action plan analyzes the feedback in a scope and suggests improvement areas, each with its verbatims and two scores:

Score

Scale

Meaning

NPS impact

0 to 100

The expected NPS gain if the area is addressed

Effort score

1 to 5

The difficulty and resources required, estimated by AI

  • Approve the actions you keep: they stay in the plan and its reports.

  • Reject the others: they're crossed out, move to the bottom of the list and drop out of reports. These choices help AI improve.

  • Open an action to see the verbatims that surfaced it.

  • Turn the plan into a report to share it.

The guide Go from verbatims to an action plan details the approach, from choosing the scope to tracking results.

FAQ

My automation doesn't trigger. What should I check?

That it's published, that the feedback matches the segment, and that it arrived after publishing. Feedier provides error handling with the full details of each automation run:

How long does it take for an action to run?

Segment actions run within minutes of the feedback arriving.


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?