Every question,
one inbox.
Email, text, social and voicemail: every customer message in one place, tied to the customer, answered before it slips.
Built for how you actually work.
One unified inbox
Email, SMS, Facebook and Instagram messages, and voicemail in a single queue. Nothing missed, nothing in five places.
Tied to the customer
Each conversation is matched to the customer's contact, so you answer knowing who they are, and a new enquiry becomes a lead in one click.
First reply targets
Response and resolution targets per priority. See what is waiting and for how long, with warning and breached states on the board.
Saved answers, one keystroke
Type / in the reply box to drop in a saved answer, filtered by channel and team, so the refund policy reads the same every time.
Find any thread
Search by contact, reference or subject, and filter by channel, status, priority, assignee or date: the whole history, not a scroll.
One team, one voice
Everyone sees the thread, you can see who else has it open, and internal notes stay internal. Nobody answers it twice.
A helpdesk sized for a small team.
Everything a ticketing system is supposed to do, without a second login or a second bill.
A ticket the moment it arrives
Every inbound message becomes a ticket with a reference number, and the customer gets an acknowledgment right away: a proper email for email, a short text for SMS.
Response and resolution targets
Set how fast a first reply and a resolution should happen for low, normal, high and urgent tickets. Tickets turn to warning and then breached on the board, with escalation when a target is missed, and business hours so the clock does not run overnight.
Teams and fair assignment
Tickets are assigned by rules to the right team, balanced round robin or least busy, with a maximum of open tickets per person so nobody ends up with the whole queue.
Customers see their tickets
From the customer portal, customers check their open tickets, read the whole conversation and reply, instead of emailing again to ask where things stand.
A rating when it closes
When a ticket is resolved the customer gets a one to five rating link with room for a comment, and the score lands on the ticket.
Built for repair counters
Walk in and call in intake with printable claim tags, parts added to the ticket, and labour plus confirmed parts billed straight to an invoice. Support retainers are tracked and invoiced from the same place.
Straight answers.
Which channels land in the inbox?
Email, SMS, Facebook and Instagram messages, and voicemail. Routing rules decide which messages become support tickets and which stay as sales or social conversations.
Does the customer get a reply confirming we got it?
Yes. An acknowledgment with the ticket number goes out when the ticket is created, per team or globally, and notifications follow when it is assigned, escalated, resolved or closed.
Can a social message become a ticket?
Yes. A Facebook or Instagram conversation, or an email thread, is escalated into Support with one button. It keeps its original channel so the reply still reaches the customer where they wrote, gets a ticket number and starts its clock fresh.
Can we bill support time?
Yes. Labour and confirmed parts on a ticket are billed to an invoice, and retainers are tracked with a retention journal and incident invoicing, so prepaid hours and billable ones stay straight.
It all runs on the same system.
One set of records runs through every tool. Nothing is re-keyed, nothing sits in its own silo.
Nobody falls through the cracks.
Book a call and we'll show you Support on your own inbox.
Book a Consultation