Scriptera
Discord and Salesforce automations — Tickets & Requests
Ready-made scenarios where Discord and Salesforce work for you (tickets & requests): pick one — a copy appears in your account and runs on its own.
30 scenarios
- New users in Salesforce — Running apis in Discord
- New tickets in Salesforce — Members in Discord
- New tickets in Salesforce — Posts in Discord
- New tickets in Salesforce — Updating channels in Discord
- New tickets in Salesforce — Sending messages in Discord
- New tickets in Salesforce — Sending messages in Discord
- New messages in discord — Tickets in Salesforce
- New posts in discord — Tickets in Salesforce
- New reactions in discord — Tickets in Salesforce
- New tickets in Salesforce — Sending messages in Discord — variant 2
- New tickets in Salesforce — Sending messages in Discord
- New team members in discord — Tickets in Salesforce
- Updated tickets in Salesforce — Sending messages in Discord
- New tickets in Salesforce — Sending messages in Discord
- Updated roles in discord — Tickets in Salesforce
- New messages in Discord — Tickets in Salesforce
- New messages in Discord — Tasks in Salesforce
- New messages in Discord — Tickets in Salesforce — variant 3
- Emails from mailgun — as tickets in Salesforce and an alert in Discord
- Unassigned support tickets — as a list in Discord
- Urgent messages from Telegram — into Telegram and Salesforce
- A form request — a tracker task and a team alert
- Urgent tickets become tasks and an instant team alert
- A support ticket digest — every morning
- A summary of support tickets — topics and customer mood
- Tell customers their bug is fixed — the moment the issue closes
- SLA monitoring that warns before a ticket breaches
- Payment issue handling: a reply to the customer, an escalation to the team
- Support tickets turned into a prioritized engineering backlog
- A full new-client welcome after the form
