The problem: a support inbox without a home

Kniteforce runs a busy UK online store. Their small support team fields a steady stream of pre-sales and post-sales questions — sizing, stock, shipping, returns — that spike hard on release weekends. They tried the obvious off-the-shelf options:

A shared email mailbox. No way to see who was already replying, threads got answered twice, and first-response time crept past a day during busy weeks.
A heavyweight helpdesk. Priced per seat, slow to set up, and far more than a two-person team needed. The bill grew faster than the team did.
A bare free widget. Fine for a single agent, but no assignment, no SLA tracking, no CSAT, and no saved replies to keep answers consistent.

What Embedded Chat changed

One <script> tag in the Kniteforce site template. The widget now sits in the corner of every page, opens on demand, and every conversation lands in one shared agent inbox. Agents assign threads to themselves, leave internal notes with @mentions, and reply live — with the full contact history and custom attributes for each customer right beside the conversation.

What happened next

~55,000 conversations a month through a single shared inbox. Peak weekends push 12,000+ with the inbox keeping up at full sub-second delivery.
Auto-routing sends each new conversation to an available agent, and SLA tracking flags anything approaching the first-response target.
Saved replies handle the repeat questions — sizing charts, returns policy, shipping windows — while AI auto-reply answers FAQs first and deflects the easy ones before an agent ever opens the thread.
No extra headcount. Two agents cover the volume. Tags, priority, and snooze keep the backlog organized; CSAT ratings show the team where to improve.

Quotes from the team

"I can finally see who's already on a conversation." — David Webster, on the shared inbox.

"Saved replies cut our answer time in half on the common questions." — Nikki, after macros shipped.

"I'm glad we could rename the widget header to 'Kniteforce'." — LayerS, on the custom widget title.

Why it works for a lean support team

One shared inbox. Agents see every open conversation and who's on it — no double-replies, no dropped threads.
One-script install. No app, no plugin to maintain. Live on every page within minutes.
Saved replies and AI auto-reply, not just typing. A release-weekend spike with two agents stays manageable — FAQs get deflected, macros handle the rest.
Assignment, SLA tracking, and CSAT when volume surges. The team stays on top of first-response targets without burning out.

If you run a lean support team

The Kniteforce playbook ports cleanly to any team answering customer questions at volume — online stores, SaaS products, service businesses. The inbox lives where your customers already are: your own page, on your own domain, with a shared inbox, AI auto-reply, and a Help Center behind it.