burneh
Bots

A support agent that knows when to step back.

It reads the message, uses your tools to answer, and hands the conversation to a human the moment confidence drops, with the whole thread attached.

Drive it yourself — tap a message or type your own, and watch it classify, use a tool, and either answer or hand the thread to a person.

support agent · operator console
recording
Move my Tuesday booking to Thursday
read_bookings · #B-4471
Done — your Tuesday 2pm is now Thursday 2pm, same location. Anything else?
classification
Booking change
confidence96%
tools called
read_bookings()update_booking()
route
above the bar · agent answered

One message, the whole path.

What you just operated is one pass through this. A message from any channel is classified, grounded in your real data, checked against policy, and then answered or escalated. The same path, every time, fully recorded.

webtelegramwhatsappgatewayone identityclassifyintent · confidenceretrieveyour live datadecidebar + policyknowledgetools / APIsmemoryansweragent replies→ humanfull thread attached0102030405
01
Ingest

Every channel lands on one gateway with one identity and one memory.

02
Classify

Intent and a confidence score, computed before anything is allowed to act.

03
Retrieve

It pulls the live order, booking, or doc the answer actually depends on.

04
Decide

Checks the score against the bar and the message against policy.

05
Route

Answers, or hands the whole thread to a person — nothing dropped.

The gate that decides to step back.

This is the whole product in one diagram. Every message runs two gates before it can answer. Fail either one and it doesn't improvise — it escalates, with the full thread, so a person picks up exactly where it left off.

It moves money

Refunds, charges, payouts. Never guessed, never fired on a hunch.

It changes an account

Cancellations, plan changes, anything a person would want to confirm.

Confidence is below the bar

If the classifier isn't sure enough, that alone routes it to a human.

There's no tool for it

If it can't ground the answer in your data, it doesn't invent one.

incomingany channelconfidence ≥ bar?gate 01moves money / account?gate 02answeragent replies→ humanfull threadpassnolowyes

One brain, every channel.

Web, Telegram, and WhatsApp all run off the same agent, the same tools, the same memory. A person doesn't get a worse answer for using a different app, and every message and tool call is recorded and replayable.

01
Web widget

Embedded on your site, themed to match, no page reload.

02
Telegram

The same agent behind a bot, with inline buttons and jobs.

03
WhatsApp

Business messaging on one number, real workflows behind it.

The value isn't that it answers. It's that it knows when not to.

Any model can produce a confident-sounding reply. The hard part, and the reason you can put this in front of your customers, is the gate: it answers only what it can ground in your data and is allowed to touch, and it escalates the rest to a person with the whole thread, instead of guessing on a refund or a cancellation. We build the agent, and we build the line it won't cross.

A support agent that knows when to step back.

It answers what it can from your tools and docs, escalates what it shouldn't touch with the whole thread attached, runs the same across every channel, and records every step.