Support Automation #3614: Sentiment Analysis with Salesforce + Slack + Telegram

Problem

Agents switch between Salesforce and Slack to complete sentiment analysis, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

Salesforce ticket event → classify/priority rules → update Slack → ping channel in Telegram.

Tools Used

• Salesforce
• Slack
• Telegram

Setup Steps

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

Expected Outcome

• A repeatable sentiment analysis path for support teams.
• Less context switching between Salesforce and Slack.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Low ROI tier · Hard difficulty · ~43 min setup estimate.
• Reduces manual sentiment analysis steps between Salesforce, Slack, Telegram.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

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

Troubleshooting

• Pause the workflow before rotating API keys, then resume after credentials update.
• Confirm ticket status enums match between helpdesk and downstream tools.
• Test reopened tickets to avoid duplicate threads.