Tasks: follow up on every session, piece of feedback or conversation.
A detractor, a replay full of rage clicks, a conversation where your AI agent failed: Screeb turns it into a task, assigns it to the right person, follows up until it is closed and measures whether the customer came back. The loop is closed.
- Five triggersResponses, widgets, replays, AI agents, users
- Reminders and escalationBefore pickup and the due date
- The effect, measuredThe respondent’s score, before and after
A signal left unanswered is a customer you lose twice.
Sharing negative responses in Slack or by email tells everyone without making anyone responsible. Tasks turns every piece of feedback that calls for action into a task, with an owner, a due date and a history, until the loop is closed.
One rule, and every piece of feedback that matters becomes a task.
When, if, then: a follow-up rule is set up in a single window, without development. It applies to the feedback that arrives once it is saved.
When
What the rule watches
Each response to some surveys, to a journey or to all your surveys; a report widget that crosses a threshold; a session replay; an AI agent conversation; or a user, after a delay. A rule also follows up the in-app messages it names.
If
The conditions to meet
The same filters as for your surveys: score given, language, response tags, hidden field. They are checked once the response ends, on the complete response. The rule can also wait until the same respondent comes back several times.
Then
The task and its owner
A title, an action plan to check in order, an expected pickup and a due date. The task goes to a teammate, in turn, to the owner read from the response, or to nobody. The response can also go to a connected tool, such as Jira. Or the rule only sends an alert, without a task.
Notify
Who hears of it, and when
An email to the assignee for each task or as a daily digest, email addresses, a Slack or Teams channel. If the task runs late, the escalation tells a manager.
Start from every signal, where it shows up.
A rule watches your responses, your reports, your sessions, your AI agents’ conversations or what your users did not do. And you create it from the page where the signal shows: a survey’s menu, the replays list or a replay, an AI agent’s dashboards, a widget’s menu. It then starts from the page’s filters.
-
Each response
A low score, a detractor, a response about payment, in your surveys and in the in-app messages the rule names.
Feedback & Surveys -
A report widget
A score or a topic share that goes above or below a threshold, over 24 hours, 7 or 30 days, group by group if it has a breakdown.
Reporting -
A session replay
With the filters of the replays list: lots of rage clicks, an error at checkout. Read once the replay is analyzed.
Session Replay -
An AI agent conversation
A violated safeguard, a critical risk, on all your agents or only some. Read once the conversation is analyzed.
Agent Analytics -
A user, after a delay
They saw a survey or a message, or triggered an event; once the delay is over, they still have not answered, or still have no paid plan.
-
Or a response, by hand
In a survey’s responses, “Create a task” hands the follow-up of that response to a teammate, who gets notified.
A collective alert when a metric drops.
In any report, a widget’s menu offers “Create an alert”. You choose the threshold, in either direction, the period and the minimum number of responses. If the widget has a breakdown, by branch or by store, the rule reads each group separately.
- Checked every hourThe rule waits for the minimum number of responses over its period, then reads the value the widget shows.
- The responses behind the alertThe task lists the widget’s responses over the period, lowest scores first.
- The right ownerAn owner table, in the follow-up settings, links each branch or store to a teammate: the task goes to them.
Every task, from pickup to closing.
The task opens in a panel with what you need to act: the full response, the session replay, the AI agent conversation or the user’s activity, depending on what triggered it.
- Four statusesTo do, In progress, Done, Dismissed. Lateness shows separately, in red.
- An action planThe rule’s actions, to check in order. The first one checked picks up the task.
- The full historyAssignments, actions, reminders, escalations and comments, newest first.
- A closing with a reasonMark as done or Dismiss, with a reason and a note for whoever reads the task later.
- Your tasks at handThe number of your open tasks shows next to Tasks in the sidebar, in red as soon as one is late.
- Wherever the feedback isThe task shows on the response, in the survey’s responses, and in the respondent’s activity.
No one forgets a task.
The assignee gets an email for each task, or a daily digest, as they choose in “My task emails”. If the task is not picked up in time, or the due date arrives, they get a reminder.
- The pickup reminderSent if the task is still to do once the delay set by the rule is over.
- The due date reminderSent when the expected resolution date is reached.
- EscalationA manager is told when a task runs late. It always reaches them, whatever their email choice.
- Your channels and toolsAlerts also go to Slack or Teams, and the task.created and task.updated webhooks send every change to your tools.
Measure what closing the loop changes.
When the respondent answers the survey again after the task is closed, the task compares their score before and after. For a collective alert, Screeb measures the indicator over the next 30 days.
- A ready-made reportThe Report button on the Tasks page opens Closed loop: alerts, tasks created, time to pick up and to resolve, tasks closed on time, recovered respondents.
- By assignee, rule, journey, tag or reasonTo see who follows up on what, which rules produce the most tasks, and why they end.
- Widgets like any otherThe report is edited like any report, and any report can show follow-up data.
- On your chartsA task closed after a collective alert is marked on your report charts, like a release.
What your teams do with it.
Customer service, product, operations or sales: each team follows up on the feedback that concerns it, with its own rules, action types and close reasons.
-
Call back every detractor
Any score below 7 on the satisfaction survey creates a task, in turn across customer service reps, with the same action plan for everyone.
-
Run a network of branches or stores
When a branch’s NPS drops below a threshold over 7 days, the task goes to that branch’s owner, read from the owner table.
-
Fix a product friction
A replay with rage clicks on the checkout page becomes a task for the product team, with the replay inside the task.
-
Escalate reported bugs
A response that mentions a bug goes to Jira, and its task stays open until someone gets back to the customer.
-
Keep an eye on your AI agent
A conversation where a safeguard was violated creates a task for the team that runs the agent, with the conversation inside the task.
-
Follow up at the right time
Fourteen days after a trial starts, a user still without a paid plan becomes a task for the sales team.
Your questions.
How is it different from sharing responses in Slack or by email?
Sharing informs. A task commits: it has an owner, a due date, an action plan and a history, reminders when it drags on, and a measure of its effect once closed.
Can we create a task by hand?
Yes: from a response, in a survey’s responses, with “Create a task”. It is assigned to a teammate, who gets notified.
Who can see and change tasks?
Seeing tasks, creating them, changing them and managing rules are separate permissions of the workspace roles. Analysts change their own tasks and the unassigned ones; editors change any task.
Does a rule apply to responses already received?
No: it reads responses that end after it is saved. Rules on replays and conversations read them once they are analyzed and are checked every five minutes; an alert on a widget is checked every hour.
How do we know the follow-up worked?
When the respondent answers the survey again after the task is closed, the task shows their score before and after. The Closed loop report counts recovered respondents, time to pick up and to resolve, and tasks closed on time.
Can we send tasks to our own tools?
Yes: the task.created and task.updated webhooks send every task creation and change, and a rule can forward the response to a connected tool such as Jira.
Is Tasks included in every plan?
Tasks is an add-on. Without it, the Tasks page in Screeb shows what it brings and how to turn it on.
The other building blocks of the Digital Adoption Platform
Never leave feedback unanswered again.
In 30 minutes, watch your own feedback become tasks: assigned, followed up and tracked until they are closed.