For customer service

143 contacts. Six causes. Before the second coffee.

Mail, chat and calls classified as they arrive, grouped by cause, with one line your team can use on the next contact.

Today, and with Compethic

What changes on Monday morning.

TodayThe same question in a hundred wordings, each answered from scratch.

With CompethicContacts group by cause as they arrive. One problem with a hundred faces, not a hundred tickets.

TodayCalls live in a recording nobody listens to.

With CompethicRecordings become transcripts, transcripts become classified signals, with the outcome and whether it was resolved.

TodayProduct hears about the outage from the queue, two days late.

With CompethicA Slack or Teams alert the moment a cause spikes, with the contacts behind it.

Today“Is this the login thing again?” asked across the floor.

With CompethicAsk Compethic, and it answers with the count, the channels and the quotes.

TodayThe AI got it wrong and there is no way to say so.

With CompethicCheck our work: a review queue where the team corrects a classification, and the numbers follow.

Try it

Watch the inbox sort itself.

Sixteen contacts from mail, chat and calls. Pick a cause to see who is behind it, alert product, or reassign one you disagree with.

Causes · this morning16 contacts
The cause, in one line your team can use

Login codes expire early on iOS since the 3.2 release. Product is on it; a restart of the app clears it for now.

Contacts behind itMail · chat · calls
  • BankID just spins and logs me out
  • Can't log in, code says expired
  • Locked out since the update
  • BankID error again this morning
  • Login code expired twice
  • Cannot approve payment, BankID
  • BankID spinning on iPhone

Illustrative figures. In the product these are your channels, your customers and your lifetime values.

In the product

What you get.

Cause, not ticket

Mail, chat and calls classified with the same structure as the rest of the company's feedback, then grouped by what actually went wrong.

Calls count too

Every recording transcribed and classified. What a customer says on the phone weighs the same as what they write.

Alerts to Slack and Teams

A cause that spikes, a churn-risk customer who writes in, a critical issue: the alert goes where the team already is.

Check our work

A queue of classifications for the team to confirm or correct. Corrections feed back, so the model learns your vocabulary.

Ask Compethic

The same question the floor asks each other, answered from the data: how many, from where, since when, with the quotes.

Response time and escalations

Mail response time, escalation rate and resolution status per cause, so the queue is measured by what it does, not how long it is.

Everything Compethic does follows one loop.

  1. 01Collect
  2. 02Understand
  3. 03Prioritise
  4. 04Act

Bring one month of support mail. We'll show you the causes.