15 intake channels, one queue
Wherever a request comes from, it becomes a numbered ticket linked to the requester, their organization and branch, and handled by the same routing and SLA rules. No more requests lost between inboxes and phones.
The channels
| Channel | Best for |
|---|---|
| Every message becomes a ticket; replies are threaded | |
| The channel closest to requesters; replies sent from the system | |
| SMS | Quick reports and critical alerts |
| Customer portal | Submitting, tracking and rating |
| Employee portal | Internal IT and department services |
| Agent console | Logging on behalf of callers |
| Website form | Embedded on your site |
| API | Tickets from your own apps |
| Mobile app | Requesters and technicians |
| Contact center | Ticket created during the call |
| Front desk | Walk-in reports |
| External systems | ERP, HR and CRM events |
| Monitoring | Alerts open incidents |
| QR code | Device or room location prefilled |
| Service catalog | Structured requests with approvals |
What happens on arrival
Identify
Requester recognized by email, number or account.
Create
Numbered ticket and reference sent back.
Route
Category, priority and team by rules.
Track
Updates go back on the same channel.
Which channels do your requesters use?We connect them to one queue in the demo.
Channels questions
Do we need a new WhatsApp number?
A dedicated official support number connected via an approved provider is recommended.
Can each mailbox go to a different team?
Yes, multiple mailboxes with their own routing.
Do replies go back on the same channel?
Yes, the requester is answered where they wrote.
One queue for every channel
No request lost between inboxes and phones.
- Email and WhatsApp
- Portal and QR
- Unified routing