Support Automation #3328: Dunning Management with Zendesk + Slack + Twilio

Problem

Agents switch between Zendesk and Slack to complete dunning management, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

Zendesk ticket event → classify/priority rules → update Slack → ping channel in Twilio.

Tools Used

• Zendesk
• Slack
• Twilio

Setup Steps

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

Expected Outcome

• A repeatable dunning management path for support teams.
• Less context switching between Zendesk and Slack.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: High ROI tier · Easy difficulty · ~16 min setup estimate.
• Reduces manual dunning management steps between Zendesk, Slack, Twilio.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Batch non-urgent dunning management 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.