Designing NPS Collection Strategies with Automated Promoter and Detractor Follow-Up Workflows

How-To-Articles
1

Designing NPS Collection Strategies with Automated Promoter and Detractor Follow-Up Workflows

What This Guide Covers

This guide details the architectural design and implementation of a Net Promoter Score (NPS) collection strategy within Genesys Cloud CX. It covers the configuration of survey triggers, the segmentation of responses into Promoters, Passives, and Detractors, and the construction of automated workflows that route Detractors to immediate remediation queues and Promoters to loyalty campaigns. The end result is a closed-loop feedback system that reduces churn risk and capitalizes on brand advocacy without manual agent intervention.

Prerequisites, Roles & Licensing

  • Licensing Tier: CX 2 or higher (required for Survey Builder and advanced Workflow routing). CX 3 is recommended for WEM integration to correlate survey results with agent performance.
  • Permissions:
    • Survey > Survey > Edit
    • Survey > Survey > View
    • Workflow > Workflow > Edit
    • Routing > Queue > Edit
    • Integration > Integration > Edit (if pushing data to external CRM)
  • OAuth Scopes: survey:read, survey:write, workflow:read, workflow:write, routing:read.
  • External Dependencies:
    • A configured Email Channel or SMS Channel for delivery.
    • A dedicated Queue for Detractor Remediation (e.g., “NPS - Detractor Follow-up”).
    • (Optional) A CRM Integration (Salesforce, Microsoft Dynamics) for updating customer records with NPS scores.

The Implementation Deep-Dive

1. Architecting the Survey Logic and Trigger Mechanism

The foundation of any NPS strategy is the survey itself. In Genesys Cloud, surveys are decoupled from the interaction channel until the trigger event occurs. The critical decision here is whether to send the survey via Email, SMS, or IVR. For high-volume B2C environments, Email and SMS offer higher completion rates and richer metadata capabilities than IVR.

Configuring the Survey Builder

Navigate to Admin > Engagement > Surveys and create a new survey. The core question must be a 0-10 scale.

The Trap: Using a standard “Number” question type for the NPS score.
Standard number questions do not automatically map to the NPS calculation engine in Genesys Cloud Analytics. You must use the specific NPS question type. This type forces the 0-10 scale and allows the platform to automatically categorize responses into Promoters (9-10), Passives (7-8), and Detractors (0-6) in the backend analytics database. If you use a generic number field, you will have to write complex SQL queries or use external BI tools to recalculate the NPS, losing the native “Promoter/Detractor” segment filters in the Dashboard.

Configuring the Trigger

Go to Admin > Engagement > Survey Triggers. Create a new trigger.

  • Trigger Condition: Interaction > Type equals Email or SMS (or Voice if using IVR).
  • Timing: Set to “After interaction ends.”
  • Delay: Configure a delay of 15-30 minutes. Sending the survey immediately while the customer is still typing or hanging up leads to skewed results based on transient emotion rather than overall satisfaction.

Architectural Reasoning: The delay serves as a “cool-down” period. In high-stress industries like healthcare or finance, immediate surveys often capture frustration with the wait time rather than the resolution quality. A 20-minute delay allows the immediate transactional friction to subside.

2. Segmenting Responses via Workflow

Once the survey is completed, the response data becomes available in the surveyResponse object within Genesys Cloud workflows. The next step is to route this data based on the score.

Creating the NPS Routing Workflow

Create a new Workflow named NPS_Response_Routing.

  1. Start Node: Survey Response.
    • Condition: Survey > ID equals [Your_NPS_Survey_ID].
  2. Decision Node: Score Classification.
    • Condition A (Detractor): Survey Response > Score is less than or equal to 6.
    • Condition B (Passive): Survey Response > Score is greater than 6 and less than 9.
    • Condition C (Promoter): Survey Response > Score is greater than or equal to 9.

Handling Detractors: The Remediation Path

This is the most critical path. Detractors are customers at risk of churn. The goal is speed-to-remedy.

  1. Action Node: Update Contact Attribute.
    • Set NPS_Score to the response value.
    • Set NPS_Category to “Detractor”.
    • Set Survey_Completion_Date to Current Date/Time.
  2. Action Node: Create Case (if using Genesys Cloud CX Case Management) OR Action Node: Create Task.
    • Subject: URGENT: Detractor Follow-up - Score [Survey Response.Score].
    • Description: Include the verbatim comment from the survey using Survey Response.Comment.
    • Queue: Route to the “NPS - Detractor Follow-up” queue.
    • SLA: Set a high-priority SLA (e.g., 2 hours).
  3. Action Node: Send Email (Optional Automated Acknowledgment).
    • Send a generic “We received your feedback and are reviewing it” email to set expectations. Do not promise a specific outcome here.

The Trap: Routing Detractors to the general “Customer Service” queue.
When Detractors are dumped into a general queue, they are treated with the same priority as a password reset or a billing inquiry. This violates the principle of asymmetric service. Detractors require specialized agents trained in empathy and de-escalation. Mixing them with general traffic increases the risk of a secondary negative experience during the follow-up call. Always use a dedicated queue with specific skill requirements (e.g., Skill: Empathy, Skill: Retention).

Handling Promoters: The Advocacy Path

Promoters are your growth engine. The goal is to leverage their satisfaction.

  1. Action Node: Update Contact Attribute.
    • Set NPS_Category to “Promoter”.
  2. Action Node: Add to List or Update CRM Record.
    • Add the contact to a “Promoter Loyalty” list for future marketing campaigns.
    • If integrating with Salesforce, use the Callout node to push the NPS score to the Customer Account record.
  3. Action Node: Send Email (Referral Request).
    • Trigger a personalized email thanking them and offering a referral incentive.

Architectural Reasoning: Automating the referral request ensures that the “ask” happens while the positive sentiment is still fresh. Manual processes often miss the window of opportunity due to agent workload.

3. Integrating with WEM for Quality Assurance

NPS scores should not exist in a vacuum. They must be correlated with agent performance.

Linking Survey Responses to Interactions

In the Survey Trigger configuration, ensure that the “Associate with Interaction” checkbox is selected. This links the survey response to the original interaction ID.

Configuring WEM Scorecards

  1. Navigate to Engagement > WEM > Scorecards.
  2. Create a new Scorecard or edit an existing one.
  3. Add a Survey element.
  4. Configure the element to pull the NPS score from the associated survey response.
  5. Weight this element appropriately (e.g., 20% of the total agent score).

The Trap: Penalizing agents for Detractor scores without context.
If an agent is penalized for a Detractor score, they may try to game the system by asking customers not to fill out the survey or by only sending surveys to happy customers. This corrupts the data integrity. Instead, use Detractor scores as a coaching trigger. Configure WEM to flag any interaction with a Detractor score for mandatory QA review. The focus should be on learning, not punishment.

4. Advanced: Real-Time IVR NPS Collection

For voice interactions, collecting NPS via IVR requires careful design to avoid hang-ups.

Designing the IVR Flow

  1. Gather Input Node:
    • Prompt: “On a scale of 0 to 10, how likely are you to recommend us?”
    • Max Digits: 1.
    • Timeout: 5 seconds.
  2. Decision Node:
    • Route based on the input digit.
  3. Detractor Path (0-6):
    • Crucial Step: Do not transfer directly to a queue. Use a Transfer Node to a “Supervisor Review” queue or a dedicated “Detractor Callback” queue.
    • Data Passing: Pass the NPS score and the reason (if collected) as custom attributes to the call object.
  4. Promoter Path (9-10):
    • Play a thank-you message and optionally ask if they would like to refer a friend.

The Trap: Asking for a reason in the IVR for Detractors.
Asking “Why did you give us a low score?” in an IVR leads to long, unstructured voice inputs that are difficult to process. It is better to let the agent collect the reason during the callback. The IVR should only capture the score and trigger the routing. Use Speech Analytics (if licensed) on the subsequent callback call to capture the reason automatically.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The “Survey Fatigue” Drop-off

The Failure Condition: Survey completion rates drop below 5%.
The Root Cause: Sending surveys too frequently or too soon after high-friction interactions.
The Solution:

  • Implement a frequency cap in the Workflow. Use a Condition node to check the last survey sent date: Contact Attribute > Last_Survey_Date is less than 30 days ago. If true, do not send the survey.
  • Exclude specific interaction types that are inherently low-satisfaction (e.g., payment failure, cancellation requests) from the NPS trigger, as these skew the data negatively.

Edge Case 2: Data Lag in Workflow Routing

The Failure Condition: Detractor follow-up emails are delayed by several hours.
The Root Cause: The Workflow is polling for survey responses rather than using event-driven triggers.
The Solution:

  • Ensure the Workflow Start Node is set to Survey Response event, not a scheduled poll. Genesys Cloud Workflows are event-driven by default, but if you have migrated from an older integration, verify that the trigger is active.
  • Check the Workflow Status in Admin. If the workflow is “Paused” or “Disabled,” enable it.
  • Verify that the Survey Trigger is associated with the correct Survey ID. A mismatch here causes the workflow to never fire.

Edge Case 3: Duplicate Survey Entries

The Failure Condition: The same customer receives multiple NPS surveys for a single interaction.
The Root Cause: Multiple channels triggering the same survey (e.g., Email and SMS both configured in the same trigger).
The Solution:

  • In the Survey Trigger, use Mutual Exclusivity. Configure the trigger to send via Email only if an email address is available, and SMS only if no email address is available.
  • Alternatively, use a Contact Attribute to flag that a survey has been sent for this interaction ID. Check this attribute before sending.

Official References