Solve · Customer support
A deflection number is a fraction, and almost every reported one has the wrong denominator. The bot sits on web chat, the rate is measured on web chat, and the customer who bounced off it and sent an email becomes a new ticket on a different dashboard. J Labs builds the measurement first, then the automation, on the helpdesk you already run.
Summary
J Labs builds customer support automation that can be measured honestly. The common failure is not a bad assistant, it is a fraction with the wrong denominator: the assistant is deployed on one channel, the rate is calculated on that channel, and volume that shifts to email or the phone is counted as a new ticket somewhere else. The second failure is quieter. Conversations the assistant does not resolve reach a human who now has less context, and if nobody is watching handover time, reopen rate and the time to a first human reply, a pilot can report a win while the queue behind it degrades. So the order of work is the scoreboard first, then the automation: a baseline across every channel, agreed definitions of what counts as resolved, and a hold-out so the comparison is against something. The build itself goes on the helpdesk already in place rather than replacing it, routes what it can answer from your own material, shows its source, and hands over the rest. Judgement stays with the team. Engagements are fixed scope, fixed timeline and fixed price.
What we automate
Web chat, WhatsApp, Instagram, Telegram, Viber and email landing in one inbox with one history per customer. This is also the measurement: you cannot see volume shifting between channels while each channel has its own dashboard.
Order status, opening hours, delivery windows, policy answers, the same five questions that fill the queue. Answered from your own material, with the source shown, and routed to a person when the material does not cover it.
When a conversation reaches a human it arrives with the transcript, the customer record and what was already tried. Most of the hidden cost of deflection is an agent restarting a conversation the customer has already had once.
Resolution without a human, cross-channel volume, time to first human reply, reopen rate and escalation handling time. Agreed before the build, so the result is a measurement rather than an argument.
A slice of traffic left on the old path for the first period. Without one, every improvement is indistinguishable from a quiet month, and every regression from seasonality.
Fit
This is for you if
You already run a helpdesk and the queue is the problem. Tickets arrive on more than one channel, the same questions recur, and the team is answering them by hand. The automation goes on top of the helpdesk you have; nothing is replaced.
Somebody can say what "resolved" means. One person who can settle whether a customer who stopped replying counts as resolved. That definition decides whether the number is worth anything, and it is a decision your business owns rather than a setting.
You want the measurement even if the answer is unflattering. The baseline sometimes shows the current process is better than expected, or that the real cost sits in a channel nobody was watching. That is a useful result and we will report it as one.
This is not for you if
You want a number to put in a board pack. We can build you a system and measure it honestly. If what is needed is a high figure by a particular date, a vendor dashboard will produce one faster, and we would rather say so now than be the people who did.
You want the assistant to handle complaints and judgement calls. Refunds outside policy, a customer threatening to leave, anything about one person’s circumstances. Those reach a human on every engagement. An assistant that rules on them does not reduce cost, it relocates it into a complaint.
There is no written material to answer from. If the answers live in the heads of three experienced agents, writing them down is the first piece of work and it is not this one. Automation on top of nothing produces confident wrong answers at scale.
Systems
The ones you already run. We don't insist on rip-and-replace: the automation layer goes on top of the systems in place, and if a system is genuinely past saving we say so on the discovery call and show our working.
Engagement options
| Engagement | Price | Timeline | What you get |
|---|---|---|---|
| The Spec | €5,000, fixed | Fifteen working days | One clearly defined outcome, designed, built and tested: the baseline across your channels, the agreed definitions, one defined set of questions answered from your own material, and the handover rules. A free assessment confirms it fits before you pay. |
| Messaging, set up and run | From €750 setup | Ten working days | All five messaging channels plus web chat in one inbox, configured on your own account and run by J Labs, with the assistant and the human handover in place. The licence stays in your name, paid direct at cost. |
| Support operations build | Fixed price, quoted after discovery | Typically four to eight weeks | The scoreboard and the automation in production on your helpdesk, with weekly check-ins, open staging, documentation written as we go and a post-launch support window. |
None of these is an off-the-shelf product. There is no J Labs software to install: every system is specified in the brief, built for your stack, and owned by you. Every engagement is fixed scope, fixed timeline and fixed price, with acceptance criteria agreed before work starts. See how we work and the Spec.
The product that fixes it
J Labs Concierge · from 750 EUR setup + 140 EUR / quarter
Concierge is the J Labs implementation of Wexio: five messaging channels plus web chat in one inbox, an assistant that answers from your own material, and human handover as the default rather than an escape hatch. Set up and run on your own account, with the licence in your name.
Live availability
Live slots from our team calendar, weekdays, European working hours. A 20-minute intro or a 45-minute working session, your choice, on Google Meet. You get a one-page summary within 24 hours.
How much time do you need?
Step 1 · Pick a date
Loading availability…
Frequently asked
Or start with our brief templateWe reply within one business day.