Scriptera
Enkod and Salesforce automations — Tickets & Requests
Ready-made scenarios where Enkod and Salesforce work for you (tickets & requests): pick one — a copy appears in your account and runs on its own.
31 scenarios
- New tickets in Salesforce — Updating records in Enkod
- Updated tickets in Salesforce — Records in Enkod
- New tickets in Salesforce — Records in Enkod
- New tickets in Salesforce — Sending SMS in Enkod
- Updated tickets in Salesforce — Updating contacts in Enkod
- New tickets in Salesforce — Running workflows in Enkod
- New users in Salesforce — Running apis in Enkod
- Updated contacts in Salesforce — Tickets in Salesforce
- New emails in Enkod — Tickets in Salesforce
- Updated tickets in Salesforce — Records in Enkod
- New records in Enkod — Tickets in Salesforce
- New tickets in Salesforce — Orders in Cdek
- New tickets in Salesforce — Sending emails in Enkod
- Deleted contacts in Enkod — Updating tickets in Salesforce
- New tickets in Salesforce — Sending SMS in Enkod
- Urgent messages from Telegram — into Telegram and Salesforce
- Chat messages — into support tickets
- A form request into a tracker issue
- Customer emails become support tickets with a spreadsheet log
- Support emails become tickets with a priority attached
- Stuck tickets, followed up automatically
- Smart support triage with Salesforce
- A summary of support tickets — topics and customer mood
- Support ticket replies drawn from your own FAQ list
- SLA monitoring that warns before a ticket breaches
- Tell customers their bug is fixed — the moment the issue closes
- Payment issue handling: a reply to the customer, an escalation to the team
- A full new-client welcome after the form
- Website enquiries: contact, ticket and reply with no manual entry
- Support tickets turned into a prioritized engineering backlog
- AI support across every channel, grounded in your docs
