Pathors Inbox
One inbox for everycustomer conversation
Phone, LINE, Messenger, Instagram, WeChat, email — all in one place, with AI that drafts, routes and hands over to your team. Built to work with your Pathors voice agents, not beside them.
The problem
Your customers use six channels. Your team uses six tabs.
Every channel keeps its own login, its own history and its own rules. So the customer explains the same thing three times, and nobody can tell whether it was already handled.
Phone
LINE
Messenger
Scattered history
The same customer arrives as a stranger in every channel.
Repeated context
People re-explain their problem each time the conversation moves.
No shared view
Two agents answer the same question, or each assumes the other did.
Calls fall outside
Phone conversations never reach the written record at all.
One inbox
Every conversation lands in the same place
Inbox merges the channels you already use into one queue, with the whole history attached to the person rather than the app they happened to open.
- Phone
- LINE
- Messenger
Pathors Inbox
One thread per customer
Channels collapse into a single history, so context survives the switch from chat to phone to email.
AI drafts first
Replies are written from your knowledge base and waiting for review, not composed from scratch at 9am.
Humans take over cleanly
Your team steps in mid-thread with everything the AI already said and did in front of them.
One knowledge base
The same sources answer chat, email and phone, so the three never drift apart.
With your voice agents
The call ends. The case is already open.
This is what Inbox does that a standalone helpdesk cannot: your Pathors voice agent and your written channels share one record and one brain.
Call ends
Case opened
Calls log themselves
Every conversation the voice agent handles arrives as a case, with transcript, outcome and extracted fields.
One source of truth
Voice and text answer from the same knowledge base, so a policy change lands everywhere at once.
Follow-up continues anywhere
A call can end in an email, a LINE message can end in a callback — the thread stays intact.
Deployment
Cloud, on-premise, or hybrid
Run Inbox where your data belongs. Your models, your environment, your existing stack.
Pathors cloud
Pathors cloud
On-premise
Your environment
Hybrid
Your environment
Pathors cloud
Pathors cloud
Fastest to stand up. We run and monitor it.
On-premise
Deployed inside your environment, with data staying there.
Hybrid
Keep sensitive workloads in your environment, burst the rest to cloud models.
Rollout
Scoped, built, deployed — with an engineer alongside
Inbox is deployed with you, not handed over as a signup link. A Forward Deployed Engineer works with your team from the first scoping call through to production, connecting the channels and systems you already run.