SSiddiq.in
Bots that know when to shut up

Every bad chatbot has the same fatal flaw: it doesn't know what it doesn't know.

We build the opposite. Grounded in your content, honest about its limits, and wired to hand off to a human the moment confidence drops. What you measure at the end of month one: fewer tickets, faster resolution, and zero embarrassed-founder screenshots on Twitter.

The confidence ladder

Four rungs. One is "hand off." One is "shut up."

01
High confidence

Retrieval returned 3+ relevant chunks. Answer + citation.

Answer directly
02
Medium

Some retrieval, gaps in coverage.

Answer + offer human
03
Low

Retrieval weak or ambiguous.

Ask clarifying question
04
None

No relevant chunks. Out of scope.

Refuse + hand off
Handover triggers

The seven signals that route the user to a human.

Explicit request

User says 'talk to a person' or 'agent'. Never argue.

Frustration signal

Two consecutive negative sentiment turns. Escalate quietly.

Confidence collapse

Retrieval score falls below threshold two turns in a row.

Refund / cancel / complaint

Regex + intent classifier. Humans handle money-and-anger.

Repeat question

Same intent asked 3× → the bot's answer isn't landing.

Long conversation (10+ turns)

Something's not resolving. Bring a person in.

High-value session

Logged-in enterprise user or cart above threshold. Priority queue.

Weekly report card

You'll get this email every Monday.

Chatbot report · week of Nov 18
Conversations
1,847
Containment
72%
↑ 4pp WoW
CSAT (bot-only)
4.4 / 5
Handovers
518
72% resolved
Top 3 unanswered questions this week
  1. "Does the plan include a dedicated IP?" — not in our docs, add FAQ
  2. "Refund after 30 days?" — policy exists but bot can't find it, re-index
  3. "Can I pay in AED?" — 12 asks, worth answering

Chatbot FAQ

Three numbers we report weekly: containment rate (% of conversations resolved without a human), CSAT on bot-only conversations, and hallucination-flag rate (answers the bot marked as low-confidence). No CSAT drop, no vanity metric wins.

System prompt anatomy

Eight rules the bot reads before every reply.

The prompt is the product. If it's five lines of 'You are a helpful assistant', you don't have a chatbot — you have a leak.

Role + scope
'You are the support assistant for [brand]. You only answer questions about our products, pricing, and orders.' — bounds the surface.
Refusal clause
'If the retrieved context does not contain the answer, reply exactly: I don't have that in my sources.' — no improvisation.
Citation format
Every claim ends with [source: doc-slug]. Users see it. Trust compounds.
Tone lock
One sentence: 'Direct, warm, no exclamation marks, no emoji.' Tone drift kills brand.
Tool-call rules
'When user asks to book, call schedule_meeting(). Never invent slots.' Structured over generative for actions.
PII redaction
'If the user shares an email, phone, or card, thank them and confirm — never echo it back.' Log-safety by prompt.
Length ceiling
Hard cap at ~120 words unless the user asks for detail. Long answers = lost skimmers.
Escalation cue
'If the user seems frustrated or asks for a human, hand off immediately without justifying the bot.' Ego belongs elsewhere.

A chatbot with a report card, not a demo reel.

Book a scoping call
Right tech, honest advice

Not sure if this is the right stack for you?

Tell us your goals — we'll recommend the right technology honestly, even if it isn't this one.

  • Personal reply from Siddiq within 24 hours
  • Honest advice — no pushy sales, no fake urgency
  • Clear next steps, timeline, and estimate

We only use your details to reply to this enquiry. Privacy.