Customer Success Automation #1777: NPS Collection with Mailchimp + Salesforce + Twilio

Problem

CS teams track nps collection across Mailchimp, Salesforce, Twilio, 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 Mailchimp → business rules for nps collection → write to Salesforce.

Tools Used

• Mailchimp
• Salesforce
• Twilio

Setup Steps

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

Expected Outcome

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

Benefits & ROI

• Library metadata: High ROI tier · Medium difficulty · ~25 min setup estimate.
• Reduces manual nps collection steps between Mailchimp, Salesforce, Twilio.
• 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

• Re-authenticate OAuth tokens if the flow stops unexpectedly.
• Compare field types between source and destination mappings.
• Inspect execution logs for HTTP 429 rate-limit responses.