Customer Success Automation #1768: NPS Collection with Zendesk + Slack + Anthropic

Problem

CS teams track nps collection across Zendesk, Slack, Anthropic, but manual updates mean health scores and account notes drift out of date.

This workflow keeps customer records consistent after each lifecycle event.

Workflow

Webhook or schedule from Zendesk → business rules for nps collection → write to Slack.

Tools Used

• Zendesk
• Slack
• Anthropic

Setup Steps

1. Create credentials for Zendesk, Slack, Anthropic in your orchestration platform.
2. Define the nps collection trigger in Zendesk.
3. Map required fields from Zendesk to Slack.
4. Add error handling appropriate for a Hard workflow.
5. Run a test payload, then enable production execution (~44 min typical setup in our dataset).

Expected Outcome

• A repeatable nps collection path for customer success teams.
• Less context switching between Zendesk and Slack.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Low ROI tier · Hard difficulty · ~44 min setup estimate.
• Reduces manual nps collection steps between Zendesk, Slack, Anthropic.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Batch non-urgent nps collection runs on a schedule instead of realtime.
• Archive raw payloads to a datastore for audit.

Troubleshooting

• Verify health-score or NPS fields accept automated updates.
• Exclude churned accounts with an explicit filter node.
• Log CS owner changes when reassigning accounts automatically.