Sales Automation #974: NPS Collection with Salesforce + Slack + Anthropic

Problem

Reps lose time copying nps collection updates from Salesforce into Slack, which delays follow-ups and skews pipeline reporting.

This pattern connects the stack so sales data stays in sync without manual exports.

Workflow

Salesforce stage change → map pipeline fields → upsert Slack → log activity for nps collection.

Tools Used

• Salesforce
• Slack
• Anthropic

Setup Steps

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

Expected Outcome

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

Benefits & ROI

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

Variations

• Route enterprise accounts to a dedicated owner queue in Anthropic.
• Require manager approval before updating closed-won records in Slack.

Troubleshooting

• Verify lead owner and account IDs exist on both sides of the sync.
• Check duplicate rules before enabling bi-directional updates.
• Test with won/lost opportunities to ensure terminal stages do not re-open.