WorkAI Chatbots · Enterprise RAG2025 — 2026
A multi-tenant enterprise assistant that answers from each tenant's own documents, spreadsheets and figures — with a citation on every answer.
Delivered by our founding team at AIM Inc., inside the wider Mirlin platform
8
File formats
3
Specialised indexes
10.8K → 500
History compression
< 5s
Fast-path target
The challenge
How do you let business users ask questions of their own knowledge base — including the spreadsheets and figures generic document chat can't see — and trust the answer enough to act on it?
What we built
A conversational agent where tenants upload their own knowledge across eight file formats, and an ingestion pipeline parses, chunks, embeds and indexes it into three specialised search indexes — narrative text, extracted table rows, and figures with vision-generated captions — plus a database row store for pure spreadsheets, so exact-value lookups are a query, not a semantic guess. At question time an intent analyser classifies the question, a router decides whether the answer lives in documents or tables, and the agent fetches the exact rows, passages and figures before it writes a word. Latency was engineered as a programme, not a hope: zero-LLM regex fast paths for follow-ups, conversation history compressed from ~10,800 tokens to ~500, and prompts right-sized per query type.
Key engineering
The decisions that made it work
Three specialised indexes
Text, tables and figures each retrieved by a strategy suited to the content type — the fix for spreadsheets flattened into prose.
Grounded by construction
Document search pre-executed and injected rather than trusted to auto tool-calling; weak matches filtered on reranker score, because a plausible wrong answer is the one failure users cannot detect.
History compression
Follow-up turns carried the whole conversation into every call and produced a 38-second spike; a bounded summary fixed it.
Full-stack platform
Chunked upload via GraphQL, per-tenant configuration, real-time push, resilience policies throughout.
The results
What actually changed
- 1
Eight file formats ingested into production retrieval, spreadsheets and figures included
- 2
Conversation history cut from ~10,800 tokens to ~500 per turn — a 38-second latency spike eliminated
- 3
Sub-5-second answers on the fast paths that dominate real usage
What it doesn't do
Worst-case queries still run 20–30 seconds, which is why the pipeline sends a typing indicator immediately. The sub-5-second target holds for the fast paths, not for every query — and we say so, because that is how the number stays believable.
Stack
- .NET 8
- Semantic Kernel
- Azure OpenAI
- Azure AI Search
- Cosmos DB
- Document Intelligence
- Azure AI Vision
- Bot Framework
- SignalR
- GraphQL
Tell us the pain point. We'll tell you honestly what AI can do about it.
A founder replies within 24 hours. If the answer is 'AI is wrong for this', you'll hear that too — free either way.