One inbox for Messenger, Viber, email, forms and calls
Every channel lands in the same queue with the customer's history attached, so an agent picking up a Viber message can see the email thread from last week. Phone calls are logged as tickets in a few taps. Nothing depends on whoever happens to be logged into the Facebook page today.
Tickets with an owner, a priority and a status that means something
Assigned, in progress, waiting on customer, waiting on supplier, resolved. A ticket cannot sit unassigned, and "waiting on customer" stops the clock so your response times stay honest. Merge duplicates when the same person messages on three channels about one order.
SLA timers and breach alerts
Set a first-response target and a resolution target per priority — an hour for a payment failure, a day for a general enquiry — and the countdown is visible on every ticket. Agents see what is about to breach at the top of their queue; supervisors get alerted before it does, not in the monthly report.
Canned replies and a knowledge base behind them
Your approved answers for delivery timelines, return policy, warranty terms and payment options, inserted in one click and personalised automatically. The same articles power the public help centre and train the AI assistant, so the answer a customer reads at 11pm is the answer your agent would have given.
Escalation and routing rules
Billing goes to finance, technical faults to the engineer on duty, anything from a key account straight to the account manager. Unanswered tickets escalate to a supervisor after a set number of hours, and out-of-hours items route to whoever is on shift rather than piling up until morning.
The AI assistant on first line, included for life
It answers order status, opening hours, pricing, stock and policy questions from your own content around the clock, in English or Filipino. When it cannot answer, it creates the ticket with the conversation already summarised and hands it to a human — so the customer never repeats themselves.
Reports that show whether support is actually improving
Ticket volume by channel and reason, first response and resolution times, backlog age, agent workload, SLA breaches and satisfaction ratings. The reason breakdown is the useful one: it tells you which product or process is generating tickets so you can fix the cause instead of hiring more agents.