Skip to Main Content
Status Backlog
Categories CSAT Rule conditions
Created by Guest
Created on Jul 26, 2023

More granular conditions to the CSAT rule

This could help increase response rates on surveys by sending them only at times when people are more likely to respond.

Ideally, we would like to keep the current Delay and be able to add additional criteria. For example, it would wait 24 hours after the trigger, and then send the survey as soon as it is after 5 pm on a weekday.

  • Attach files
  • Guest
    Jan 27, 2025

    To add to this - it'd be great if the default "Measure Customer Satisfaction" rule was adjusted to reset timer if survey is cancelled and later set back to pending.

    When using the default "Measure Customer Satisfaction" rule, the "Survey Schedule" tag is added by a team member archiving a conversation (believing it to be settled), and this tag is removed if the customer ends up reopening the conversations by sending another message, and then will only be added back once the team member replies again. However, because the trigger for the default rule is "When Archived" (or resolved), and there's no way to edit the "When" trigger of this rule, that initial countdown to send out the survey based on the first archive keeps running even if the conversation reopens and re-archives/resolves and the tag gets removed/readded. This can lead to the survey message going out far sooner than intended when setting up the rule, as it goes out based on the first archive instead of actual final archive.

1 MERGED

Randomized CSAT Surveys

Merged
The surveys should be limited and randomized to reduce survey fatigue. The surveys should have a capped frequency per account. For example, once every few days or per X interactions to prevent overwhelming key accounts.
5 months ago in CSAT 0 Backlog
3 MERGED

Automatically remove CSAT Survey rule tags after a user defined amount of time

Merged
Currently customers don't have a way to automate the removal of tags used in CSAT rules that send survey templates in app. This causes issues when customers have a large amount of conversations that use a channel type that does not typically creat...
over 1 year ago in CSAT / Workflows 0 Backlog
13 MERGED

CSAT: limit number of survey sent to a given customer in a period of time

Merged
Example: send a single survey per month for a given contact or account.
over 3 years ago in CSAT 0 Backlog
4 MERGED

CSAT survey: Easier rules configuration options

Merged
It’s easy to create a rule to automatically send the survey per conversation, but it requires a more complex custom setup for more advanced configuration. For example with custom fields and custom smart rules to send a survey per contact and no mo...
over 1 year ago in CSAT 0 Backlog