Human-in-the-loop knowledge platform

Every question
answered once
is one you'll
never ask again.

Your team asks. Hikmet answers what it knows — and when it doesn't, it escalates to the right person, then remembers the answer for good. The next person who asks never has to interrupt anyone.

once
0%
of questions asked today have been asked before

Your best people spend their days answering things that should already be answered.

The owner. The manager who's been there longest. The one person who just knows things. They're the ones who get interrupted — by questions that, if written down once, would never need answering again. Hikmet makes that the last time.

The escalation path

It tries everything
before it bothers
a human.

When a team member asks a question, Hikmet works through a hierarchy — from instant to escalated — so humans only get involved when there's genuinely no other option.

💬
Team member asks a question
Via Telegram, the web app, or chat
Path A — Instant answer
🔍
Searches your uploaded knowledge

Scans every document, policy, and past answer by meaning — not just keywords. Finds the most relevant pieces and reads them in context.

Confident answer — replied instantly

If the answer is clear and well-sourced, it replies in seconds with a cited, confident answer. The exchange is stored so it gets faster next time.

Done. No human involved.

This is how most questions end — especially once the knowledge base has been growing for a while.

OR
Path B — Escalation chain
🔍
Searches — but can't find a confident answer

The corpus doesn't have it, or what it has isn't reliable enough. Hikmet tells the employee honestly rather than guessing.

Employee escalates to the Council

One tap. A panel of 20 AI specialists — Researcher, Fact Checker, Critic, Strategist, Policy Analyst — deliberate deeply on the question. They search further, challenge each other, and try to find a resolution.

🤔
Council reaches its limit

Some questions can only be answered by a human — a policy decision, a judgment call, something that requires authority. The Council flags this clearly and stops.

👤
Manager gets a few pointed questions

Not the raw question. Not a long thread. Just what's needed to unblock the answer — could be one question, could be five. The manager replies in under 2 minutes.

Stored forever

The manager's answers feed back into the knowledge graph. The Council uses them to answer the original question — cited, clear, and complete.

Never asked again

The next person who asks the same thing gets an instant answer from the corpus. The manager's workload just permanently shrank.

The manager's view

Not a question dump.
Just what it needs.
Answered once.

The Council doesn't forward the raw question. It does the work of figuring out exactly what it needs to know — and asks only that. Simple, to the point. The manager reads it, answers it, and never sees it again.

Those answers go straight into the knowledge graph. The next time anyone asks anything related, it's answered automatically. The manager's expertise compounds without them being in the room.

"The goal is for your top people to stop being bottlenecks. Not because they're bypassed — because their knowledge has been captured."

Hikmet
Knowledge Platform · just now
To: Alex Rivera, Store Owner
A staff member asked: "Can we honour a gift card that was purchased at the Westfield location, or only ones bought here?"

I couldn't find a confident answer in your documents. Rather than guessing, here's what I need from you:

1.Are gift cards valid across all locations, or only the one they were purchased at?
Your answer…🎤
2.Is there a time limit or expiry on gift cards?
Your answer…🎤
3.Can a staff member make an exception on the spot, or does it need manager sign-off?
Your answer…🎤
Anything else worth knowing?
Optional — add context, nuance, or exceptions…
Your answers will be stored. You won't be asked this again.
Submit answers
Under the hood

The loop is what they see.
Underneath is a whole
knowledge engine.

The escalation story is one chapter. Every question actually runs through a research pipeline most teams would need a department to build — and it gets sharper each time someone asks.

📥
Reads anything you've got

PDFs, scanned paperwork (OCR'd line by line), documents, spreadsheets, web pages — pulled into one searchable memory. The messy filing cabinet becomes instant recall.

🕸️
Builds a knowledge graph

It doesn't just store text. It maps the people, policies and things your documents mention — and how they connect — so it reasons across them, not just within one file.

🔍
Searches by meaning

Three-stage semantic retrieval finds the right passage even when the words don't match. Every answer comes back with its sources attached.

⚖️
Convenes a council

For the questions one model can't settle, a panel of AI specialists — researcher, fact-checker, critic, strategist, risk analyst — deliberate before answering.

🎯
Knows when it's sure

Confidence scoring decides what to answer instantly, what to research further, and what to route to a human — and it recalibrates as it learns your business.

🌿
Keeps knowledge fresh

It tracks when answers go stale as your business changes, and flags knowledge that's started to rot — before it quietly misleads someone.

🔐
Respects who-knows-what

Tiered access means each person only ever sees the knowledge they're cleared for. Built into the core, not bolted on at the edge.

🔌
Fits the tools you use

Telegram, the web, and a full REST + GraphQL API. Drop it into the systems your team already lives in — no new habits required.

Your knowledge, mapped

Everything your business
knows — visible at
a glance.

As knowledge grows, Hikmet organises it into clusters — topics that naturally belong together. You can see where your knowledge is dense, where it's thin, and exactly where the gaps are.

Store Policies
Customer FAQs
Bookings & Events
Products & Pricing
Staff Procedures
Knowledge gap
🔵
Dense clusters = deep coverage

Topics with lots of answered questions form tight, rich clusters. When someone asks something nearby, the answer is instant.

Sparse areas = escalation territory

Thin or isolated points show where the knowledge base is still being built. These are the areas most likely to trigger a human escalation — for now.

Gaps are surfaced automatically

Empty regions in the map are detected and flagged. Hikmet can generate the questions that would fill them — so you know exactly what to address next.

حكمة

Hikmet / Turkish

Wisdom. Not the kind you get from reading — the kind that comes from experience. From questions asked, answers earned, and lessons that stick.

In Turkish and Arabic philosophy, hikmet is the deeper understanding that sits beneath raw knowledge — the meaning behind things, the reason something is true, not just that it is. It's the difference between a fact and wisdom you can actually act on.

That's the distinction this platform is built around. Documents are just information. What Hikmet builds — through every question asked, every escalation resolved, every expert answer stored — is something closer to the real thing: your organization's accumulated wisdom, made accessible to everyone in it.

The Council

Wisdom rarely comes
from a single voice.

For the questions one answer can't settle, Hikmet convenes a council — a panel of AI specialists who research, argue, fact-check and challenge each other across rounds, before a single word reaches your team.

🔬
Researcher

Digs through your documents and the open web for hard evidence.

Fact Checker

Verifies every claim against a source. No citation, no claim.

Devil's Advocate

Argues the other side on purpose, to surface the blind spots.

🔎
Critic

Pokes holes in the reasoning before your team ever sees it.

Strategist

Weighs the second-order consequences of each possible answer.

Risk Analyst

Names what could go wrong if someone acts on the answer.

Ethicist

Checks the answer against fairness, policy and plain decency.

Synthesizer

Weaves the whole debate into one clear, sourced verdict.

Twenty specialists in all. They keep going until the answer holds up to scrutiny — or until the only thing left is a call that a human should make. Then, and only then, it asks one.

The compounding effect

The longer it runs,
the less anyone
gets interrupted.

Every escalation is an investment. A manager spends 2 minutes today and saves the next 50 people who ask the same thing from ever needing to escalate it.

Before Hikmet

New staff member asks: "What's our refund policy for bookings?" → interrupts the owner → waits for a reply → same thing happens next week with a different new hire.

After Hikmet

New staff member asks: "What's our refund policy for bookings?" → answered in seconds from the knowledge base → owner never even knows the question was asked.

Before Hikmet

A question without a clear answer reaches the top. They answer it in a long email thread that nobody will ever find again.

After Hikmet

Same question reaches the top as 3 bullet points. They answer in one message. It's stored permanently. The question is closed forever.

Manager interruptions per week
0
Week 1
0
Month 1
0
Month 3
0
Month 6
0
Year 1

* Questions the corpus couldn't answer automatically. As knowledge accumulates, fewer and fewer escalations are needed.

What's happening over time
Day 1
Only what you uploaded
Week 2
Escalations filling in gaps
Month 1
Most common questions covered
Month 6
Edge cases being filled in
Year 1
Almost self-sufficient
← % of questions answered without a human
Built for more than one location

One answer at HQ becomes
an instant answer everywhere.

Each location runs its own knowledge base — close enough to the brand to be consistent, loose enough to reflect what's actually true on the ground. When a question gets resolved at one location, that answer can flow to all of them.

🏪
Each location, its own brain

Upload the docs specific to each store. Local policies, local staff, local quirks. Hikmet keeps each one separate.

🔗
Core knowledge shared across all

Brand standards, pricing, product info — ingested once at the top, available everywhere. No one has to ask twice.

📡
Push or pull from any location

An answer resolved at one store can be pushed to the network. Or pulled from it. The whole group gets smarter together.

On the roadmap — actively being built.
Where it lives

In the tools your
team already uses.

✈️
Telegram

Employees ask questions just by sending a message. Managers receive their pointed questions the same way — reply in seconds, done. No new app, no login, no friction.

🖥️
Review dashboard

See every pending question, every escalation, every gap in the knowledge base. Approve answers, fill in knowledge manually, see what your team has been asking about this week.

📡
API

Every part of Hikmet is accessible via API. Embed the knowledge base into your own tools, pipe answers into existing workflows, or build a custom interface for your team.

"Every time your top person answers a pointed question,
they're making themselves less needed — in the best possible way."

The idea behind Hikmet's Human-in-the-Loop design

See it for yourself.

We've loaded Hikmet with the handbook of a fictional pottery studio. Ask it anything, watch your question land on its knowledge map, and see who it would route you to.