The queue your teamwill actually open.won’t dread on Monday.runs itself by Friday.
Shared inbox, live chat, help center, ticketing, and a customer portal. Unlimited tickets. Email, chat, and the portal create a ticket automatically. On Growth, new tickets are assigned to agents automatically. SLA and routing from $24 per agent a month, billed annually.
Klevrio sits between the inbox, the company on the ticket, and the customer who is waiting.
$24 Growth, per agent, annual
$120 five agents, per month
Inside the desk
One place to take the work, not five tools taped together.
Monday morning, 40 emails and three chats from overnight.
They all sit in the same list. You open one thread and you already have the company, the last reply, and who owns it. Nobody asks “which inbox was that in?”
Email, live chat, and portal in one queue
The company and earlier tickets sit on the thread
Internal notes stay off the customer email
Shared Inbox · email & channels
The widget is small. The history isn’t.
Drop it on the site. Common questions get an answer. When someone needs a person, that person already sees what they typed five minutes ago — and last Tuesday.
A short auto-reply for the questions you hear every day
Hand off to an agent, with the history already on the ticket
The same thread if they write in later by email
Live chat · history attached
Most “how do I change my plan?” tickets shouldn’t be tickets.
Put billing, onboarding, and the plan limits on a public help center. When they still write in, the portal already has the thread, so you’re not starting from zero.
Your domain and your type
Folders and articles on a public help center
A portal so they can check the status themselves
Help center · self-service
A ticket number, an owner, and a status. That’s a ticket.
Email, chat, and the portal create the ticket on their own. On Growth, new tickets are assigned automatically — round robin, the agent with the fewest open tickets, online agents only, with a cap. Dispatch rules and an SLA sit on that same plan. Macros cover the reply you send every day.
Manual tickets when email isn’t the start
Tags your team already uses — not a taxonomy project
Macros for the replies you send every day
Ticketing · owners & tags
They shouldn’t need your login page to check a ticket.
Give customers a portal for your workspace — your logo, your colors, their conversation history. They open a status page that looks like your brand, not a generic help desk.
Logo, colors, and workspace branding
Ticket status and reply history without another inbox
Help Center articles and portal in the same place
Customer portal · your brand
Service levels
A clock on the first reply and on the resolution.
On Growth, one SLA tracks first response and resolution. High and urgent can have tighter targets than the default. You can count only business hours. Starter does not include an SLA.
First response and resolution
Tighter targets for high and urgent. Priorities are low, normal, high, and urgent.
New tickets get an owner. More than one address still lands in one queue.
On Growth, new tickets go round robin or to the agent with the fewest open tickets. Assignment can stay with agents who are online, and stop once someone is at their open-ticket cap. Starter leaves assignment to the team.
Round robin, or fewest open tickets. Online agents only, with a cap.
A routing rule on Growth can match the address that received the mail and assign that ticket to one agent. It can also add a tag, set the priority, or notify agents.
One support address on Starter, five on Growth, twenty on Business. billing@ and support@ share the queue.
Volume, response time, and satisfaction, plus the rest of the overview.
Every plan includes the support overview. Custom dashboards are on Growth, up to three, and unlimited on Business. SLA and satisfaction stay empty until those settings are on.
Numbers: created, resolved, unresolved, pending, open 7+ days, open 14+ days, average first response, average resolution, first-response SLA, resolution SLA, and satisfaction.
Charts: created versus resolved by day, tickets by channel, priority, and agent, and first-response SLA by week.
Filters: date range, channel, status, priority, agent, and tag. A saved report can also break down by type or company.
These describe how a team uses the desk. They are examples, not customer reviews.
Example
A billing email and a chat from the app land in the same list. The company is already on the thread, so I send the plan-change macro and the SLA clock is visible.
Support lead6-agent SaaS team
Example
An employee emails the help address and a ticket opens on its own. On Growth it goes to whoever has the fewest open tickets. The client company stays on the thread.
IT leadInternal team plus a client portal
Example
I still open a ticket by hand when the request starts in a meeting. Everything that arrives by email, chat, or the portal already has a number, an owner, and a status.
Ops lead5-agent team on Growth
Pricing
Straightforward pricing for teams that reply.
Per agent, per month, on annual billing. Unlimited tickets on every plan. This is the seat rate, not a flat price for the product.
starter
Shared inbox, email, chat, portal, and help center for small teams.
SaaS teams, agencies, and ecommerce stores that answer by email and live chat and want a company on the ticket, macros, an SLA, and an owner. Phone, WhatsApp, SSO, and HIPAA are not in the product. SaaS · Agencies · E-commerce
Is there a free trial?
Not right now. You choose a plan at checkout and are billed for the seats you add. You can cancel anytime from billing settings.
Can I switch plans anytime?
Yes. You can upgrade, downgrade, or cancel your plan at any time from the billing settings. Changes are prorated automatically. Checkout is self-serve. A demo is a walkthrough, not a required contract.
Which channels does Klevrio support?
Email, live chat, and the customer portal, in one inbox. Klevrio does not include phone, SMS, WhatsApp, or social channels.
Do you offer migration from other help desks?
Yes, as a mailbox cutover. Create the workspace, connect the support address, embed chat, invite agents, forward the old address, and rewrite the macros you send. The old ticket archive, phone numbers, social channels, and SSO do not move. Most small teams finish in an afternoon. See the steps
Bettercustomersupport,startingtoday.
Connect the support mailbox, embed chat, and invite the team. The cutover is an afternoon.