- Product
- Support
Support that already knows the customer’s whole story.
Tickets, queues, SLAs, and a built-in customer portal — wired into the same data graph as your Sales, projects, and financials. Routing rules send each ticket to the right team.
What Support does for you
Support tickets that already know about the customer’s account, the open project, the unpaid invoice, and the history of past tickets — in one query, not six.
Tickets, queues and SLAs
Standard helpdesk shape, multi-tenant by default. Queues, assignment rules, SLA timers, and macros work out of the box.
Customer portal included
Every customer gets a portal at no extra seat cost. Tickets, docs, invoices, and projects in one place for them too.
Routing and saved replies
Routing rules assign tickets to the right team, and saved replies and templates speed up answers. Ask Cyril can find, open and update tickets for you.
KB tied to docs
The Docs module is your KB. Public articles render at the customer portal; internal articles power agent answers.
A ticket isn’t just a ticket.
When a ticket comes in, Cyril’s agents already know who the customer is, what they pay, what project they’re on, and what the last three tickets said. That’s the context most "AI for support" tools spend integration time trying to assemble.
- Account, deal, project and past tickets in one query
- Permissions match the org-wide model — no separate auth
- Open tickets are listed on the customer’s Sales record
Request for a project update
Could you confirm where phase 2 stands before our board meets?
The customer
A whole class of ticket is the customer asking where something is.
Every customer gets a portal at no extra seat cost, showing their own tickets, documents, invoices and projects in one place. The questions it answers — is my invoice paid, where is the project, what did you say last time — are the ones that otherwise arrive as tickets and consume an agent to look up four systems.
- Tickets, docs, invoices and projects in one customer view
- Portal users are free and unlimited, not staff seats
- Public KB articles are the same Docs pages agents use internally
Halloway Dental GroupClient portalCommon Support questions
Do customers need a separate login for the portal?
They get a magic-link or email-password login on the portal at no extra cost. Portal users are not staff seats and never count against your seat limit.
Do support agents need a full staff seat?
Yes, and that is deliberate: a seat carries the cross-module context this page describes rather than a cut-down helpdesk view. Customers using the portal are free and unlimited, so the seat count is your team rather than your customer base.
Can we keep our existing helpdesk and connect it?
You can connect most things, but that arrangement is what this page argues against — a connector moves records without giving the helpdesk a shared model of the customer, which is where the cost sits.
What about phone support?
Voice is described on this site as coming soon rather than shipped. Treat it as absent when deciding, and if inbound telephony is a hard requirement, say so early and we will tell you plainly whether to wait.
Be one of the first to use Cyril.
Join the waitlist for early access. We’ll only email you when there’s something real to share.
One email when your place opens. Nothing else.
