The support week, with no ticket left ownerless.
Tickets, conversations, wiki and the client record on one base. Sara finds what's about to breach SLA and drafts the reply — you approve before it goes out.
14-day trial · No card · Then a free plan
Sara, Support: “Any urgent tickets?”
Two tickets breach SLA in 1 h. For Lumen's, I drafted a reply with the wiki article. The other one needs you. Reply to Lumen's ticket with the wiki article. Replied. The answer is on the ticket and on Lumen's history.
Studio Bravo is a demo company. Made-up data.
The week of whoever answers clients, before and after
The urgent ticket has had no owner since Friday, in a tab nobody opened.
Every ticket lands in the right department and gets an owner by rotation or workload.
The deadline passes and you find out when the client complains.
First-response and resolution deadlines, with an alert before they're breached.
WhatsApp on a phone, email in another inbox, the ticket in a third place.
WhatsApp, email and the portal become tickets in one queue, with the client's history.
The same question is answered from scratch every week.
The answer rests on the wiki, and AI drafts it for the team to review.
The week's work, one block at a time
From the first message to the client's score.
Queue
Every case with an owner and a deadline
A queue with statuses, priority and history per client. Department routing and SLA deadlines with an alert before they're breached.
- Assignment by rotation or workload
- First-response and resolution SLA
- Your own fields per department
Channels
One inbox for the whole team
WhatsApp through Meta's official API and email in the same inbox. Every conversation has an owner, internal notes the client never sees and quick replies.
- Team inbox with an owner per conversation
- Support email becomes a ticket
- A portal for clients to open and follow cases
Answers
The wiki as the source, AI as the draft
AI triages every new ticket and drafts the reply from your knowledge base. The team reviews before sending.
- Triage of every new ticket
- Drafts the team reviews
- Internal or public knowledge base
Customer success
Know how every client is doing
When a ticket is resolved, the client rates it 1 to 5, and low scores alert the team. Wait time and volume per agent stay visible.
- A 1-to-5 score on resolution
- Alert on a low score
- Wait time and volume per agent
Support that sees the whole client
Modules you can switch on today
Read from the same catalog as the module store: if it's listed here, it's in the product.
- Ticketsfree plan available
- Support portalA support portal where the client opens and follows their own tickets.
- SLAFirst-response and resolution deadlines, with an alert before they blow.
- Autonomous AI agentThe AI answers customers on its own when the reply rests on verified sources, and hands the ticket to a person when it does not.
- Omnichannel Inboxfrom R$49/month
- Connected channelsConnect your company's WhatsApp and Telegram and receive everything in one box, with the AI agent answering while you sleep.
- Shared inboxYour team works the same box: every conversation has an owner, internal notes the customer never sees, tags, quick replies and snooze.
- Official WhatsApp (Meta)Connect through Meta's official API, with a verified number and approved templates — the path that carries no ban risk.
- Roadmap, Changelog & Wikifree plan available
- RoadmapA public product roadmap showing what is in flight and what comes next.
- ChangelogA release changelog to announce every delivery to your users.
- WikiA knowledge base and documentation, internal or public.
Does the agent answer clients without me seeing it?
By default, she drafts and you approve. On higher plans you can let her answer on her own when the reply rests on verified sources — and hand over to a person when it doesn't.
Do we need a finished wiki to start?
No. The queue and SLA work without it. The wiki comes in when you want answers to rest on it.
We already have a helpdesk. Can we bring the history?
WHMCS tickets come in by import. For other tools, book a diagnosis and we'll look at it together.
Does the client need to install anything?
No. They write on WhatsApp or by email, as they already do, or open a case in the portal.
Be the owner again.Not the integrator.
Start with the area that hurts most. In 14 days you'll know whether BaseOS stays — no card, and a free plan afterward.
14-day trial · No card · Then the free plan