Purpose
1.2. Automates tracking and assignment, ensuring all customer issues (delivery delays, parcel queries, address changes) are systematically ticketed and routed based on topic, urgency, and customer segment.
1.3. Enables scalable automation, integrating multichannel communication, so no customer request is lost, while supporting audit trails for compliance and resolution analysis.
Trigger Conditions
2.2. New message or inquiry posted via website chat widget.
2.3. Missed call logged by virtual call system or PBX with voicemail/email alert.
2.4. Keyword, attachment, or call duration meeting pre-set automation rules.
Platform variants
3.1. Gmail API
• Feature/Setting: Automating webhook on new email; configure using watch for messages plus labels for routing.
3.2. Microsoft Outlook API
• Feature/Setting: Automator watches for new mail in support folder; triggers automated flow to ticketing system.
3.3. Zendesk
• Feature/Setting: 'Create Ticket' endpoint accepts input from email/chat/call automators; map fields via API.
3.4. Freshdesk
• Feature/Setting: 'Tickets API' for automated ticket creation, configure automating rules for channel inputs.
3.5. Twilio
• Feature/Setting: SMS/Webhook for missed calls; automate parsing call data into ticket fields via REST API.
3.6. Intercom
• Feature/Setting: 'Conversations API' pulls new chats; automate new ticket by creating case in helpdesk.
3.7. Slack
• Feature/Setting: Support channel webhook triggers automation; message parsing fills ticket fields.
3.8. Microsoft Teams
• Feature/Setting: Message webhook integration automates extraction of support requests to ticket creator.
3.9. Zoho Desk
• Feature/Setting: Email-to-ticket automated configuration, API mapping for chat/call data.
3.10. Help Scout
• Feature/Setting: Beacon API detects new chat or email, automates setup of ticket with structured data.
3.11. Jira Service Management
• Feature/Setting: Mail/REST API create-issue endpoint; automate field mapping from email/chat/call sources.
3.12. Salesforce Service Cloud
• Feature/Setting: Case creation API; automate mapping of all channel inputs to case data.
3.13. HubSpot Service Hub
• Feature/Setting: Conversations API for email, live chat and inbox integration, automating ticket creation.
3.14. LiveChat
• Feature/Setting: Webhook on new chat; automates POST to backend ticketing via API.
3.15. RingCentral
• Feature/Setting: Missed call webhook triggers; automate handler generates ticket using metadata.
3.16. Genesys Cloud
• Feature/Setting: Conversation API webhook on missed call/chat; mapping user/contact data to ticket.
3.17. Front App
• Feature/Setting: Automated rules convert emails/chats/call logs into support tickets via rules engine.
3.18. ServiceNow
• Feature/Setting: Inbound email action and REST API; automate ticket setup with structured subject/body mapping.
3.19. Kayako
• Feature/Setting: Messenger and Email channel API; automates creation of new conversations and tickets.
3.20. Tidio
• Feature/Setting: Chat event webhook; automates API call to helpdesk to seed ticket from chat session.
Benefits
4.2. Improves traceability, analytics, and SLA compliance via automation of intake and routing.
4.3. Automatedly logs every customer interaction, ensuring no support request is missed or mishandled.
4.4. Enables scalable automation for growing courier businesses, supporting high inquiry volumes.
4.5. Strengthens customer relationships through prompt, automated acknowledgment and assignment.