← DAX Labs / Case studies
Support automation project — interactive case study

Concierge.
A support assistant with human handoff.

DAX built a grounded support assistant that answers known questions, shows its reasoning and routes uncertainty to a person. The live chat below proves the delivered behavior.

6 intents 1 handoff gate 0 libraries 0 login specimen CNC-01
meet the concierge
01 Delivered support system

Test the assistant. Inspect the handoff.

Use the chat box to test the completed system. The panel on the right shows why DAX designed it to answer or pass the question to a person.

CUSTOMER HELPER example shop
live
idle
Concierge
online · scripted demo
try one · or type your own
intent router · console what the buyer never sees — visible here
signals · none yet
awaiting input confidence awaiting first message
65%
40 · answer more90 · escalate more
below the gate the bot refuses to answer — it pages a human with the transcript instead of guessing
playbookplaybooks/—.yaml
  1. send a message and the matched playbook loads here
grounded in · —
+ embed this — one tag
rebrand the widget and the snippet rewrites itself. what you see on the left is what the tag installs.
brand accent
the launcher your visitors see —
recolors with your pick
copy · paste before the closing body tag
<script src="https://cdn.daxlabs.dev/concierge.min.js"
  data-bot="Concierge"
  data-accent="#bd775e"
  data-gate="0.65"
  data-handoff="team@yourco.example"
  async></script>
data-gate syncs with the slider above · data-handoff is where low-confidence threads land · the production tag points at your playbooks
Scripted classifier over keyword playbooks — the production build swaps in your model + retrieval over your content; the routing UX ships as-is · no libraries
02 the offer

Priced to ship, not to meter.

Three fixed scopes, fixed day counts, your own API key. Every claim below has a visible counterpart in the demo you just drove — the grounding lines, the gate, the handoff.

Starter
$903 days
  • FAQ bot trained on up to 20 Q&As
  • Website widget embed
  • Basic branding
  • 2 revisions
  • 7 days post-delivery support
live above → the scripted playbook replies
most commissioned
Business
$2806 days
  • Trained on your website + up to 50 docs
  • Website + 1 messaging app (WhatsApp/Messenger/Instagram)
  • Retrieval — answers cite your real content
  • Lead capture to email/CRM
  • Full custom branding
  • Unlimited revisions · 14 days support
live above → grounded replies + the confidence gate
Pro
$65012 days
  • Unlimited docs + product catalog
  • Website + up to 3 messaging apps
  • Retrieval + in-chat calendar booking
  • Lead capture + CRM push
  • Conversation handoff to a human
  • Unlimited revisions · 30 days support
live above → the low-confidence human handoff
add-ons Extra messaging channel $60 Monthly maintenance & answer updates $120 Voice/phone bot (Twilio) $200 Multi-language support $80
03 the gap

What the market gets wrong.

The recurring failure modes of cheap chatbot builds — and the way this one is engineered so they can't happen here.

01 · invention

"It quoted a 30% discount we've never run. The bot didn't know our policies — so it wrote its own."

the dax answer

From the Business tier up, every answer is retrieval-grounded in your real content and cites it — you watched each reply above carry its source line. Below the gate the bot refuses to guess and pages a person instead. Invented policies are a routing failure; the router is the product here.

02 · wiring

"The delivery was a demo link and a login. Getting it onto our actual site was apparently my job."

the dax answer

Delivery is the one-line tag you just personalized, installed and verified live on your pages — widget styled to your brand, every tier. Wiring it in is the job, not an upsell.

03 · ransom

"A two-line wording change? That'll be another invoice. Our own bot's script was held hostage."

the dax answer

Every package ships with a short handover doc, and the playbooks are plain files your team can edit without me — you saw the file path on every playbook card above. The maintenance add-on exists for convenience, not dependency.

04 · the meter

"The build was cheap. The surprise was the API bill two months later — racked up on a key we didn't even own."

the dax answer

You connect your own API key and pay the provider at cost — no markup, no locked account. Before launch you get the expected monthly running cost in writing, sized to your traffic.

commission

Put a concierge on your front door.

Fixed scope, fixed days — a working support agent on your site in 3 to 12 days, from $90.

← Back to case studiesTell us what you need →