EKA Examples
Every captured run of the Enterprise Knowledge Assistant in one place — 20 of them. Each has its recording, its screenshots and a transcript, says how it was captured, and links to the page that explains it.
The reasoning behind them is in the EKA Guide; the interface they are shown in is on the Agent Experience page.
20 examples.
Evidence and authority
Answers built from governed reads, each fact labelled with where it came from.
What do we owe Bharat Polymers?
“What do we owe Bharat Polymers, across how many invoices?”
Measure selection, identity resolution and currency-aware calculation.
Why was the warranty claim rejected?
“Why was WCL-2026-000002 rejected, and what does the warranty policy say?”
Structured evidence and document retrieval, kept apart.
What do we owe Bharat Polymers? — second capture
“What do we owe Bharat Polymers, across how many invoices?”
A refused plan, repaired once, and a run that says which steps were limited.
A second capture of chapter 06's question.
Why was the warranty claim rejected? — second capture
“Why was WCL-2026-000002 rejected, and what does the warranty policy say?”
A source record and a document passage answering one question without merging.
A second capture of chapter 07's question.
A recorded continuation into ERP
“Did CRM opportunity OPP-2026-900001 continue into ERP? Show the recorded handoff.”
A cross-system journey backed by an explicit operational link.
Absence and limits
What EKA says when something is not there, not recorded, or not a question it can answer.
Closed Won, but no ERP continuation
“This opportunity is Closed Won. Why hasn't it reached ERP?”
Absence is established. Cause is not.
A canonical amount that is not present
“Show canonical sales order SO-2026-000001 and tell me its total value.”
Feature availability and result state are different concepts.
A canonical amount that is not present — the companion question
“What is the canonical total value of SO-2026-000001?”
The same order asked for its canonical total instead: the measure is not present, so the whole request is unavailable.
A canonical amount that is not present — second capture
“Show canonical sales order SO-2026-000001 and tell me its total value.”
The record is available and the canonical measure is not.
A second capture of chapter 08's question.
A canonical amount that is not present — second capture
“What is the canonical total value of SO-2026-000001?”
The feature registry settles the question before anything is retrieved — one step, no evidence.
A second capture of chapter 08's question.
EMPTY is not failure
“Show Kestrel's open invoices and total their open amount.”
Nothing matched, and the request still completed.
A policy version on a date
“Which version of the warranty policy was effective on 2026-07-15?”
Five readable passages, and a question about a date none of them records.
Resolving a name is not finding the record
“Show me the account for the customer named Kestrel.”
The entity resolved; the requested source record stayed ambiguous.
Access and saved conversations
Who is reading decides what is shown — now, and when a conversation is reopened.
Asking from a page
The Sidecar beside a Day-0 record: the same runtime, the same rules, a page's context.
Contextual Ask — SC-GOLD-001
“Did CRM opportunity OPP-2026-900001 continue into ERP? Show the recorded handoff.”
The page's record reaches the governed runtime as the turn's context, and is shown. Ask EKA on a CRM opportunity: the chip names the opportunity, and the answer is the recorded operational handoff to ERP.
Context remains explicit — SC-GOLD-002
“Did CRM opportunity OPP-2026-900001 continue into ERP? Show the recorded handoff.”
Navigating the host page does not change the thread's context; only the reader does. Move to another opportunity: the thread still carries the first, the new page is only offered, and it becomes the context when the reader chooses it.
Continue in Workspace — SC-GOLD-003
“Who is Bharat Polymers?”
One conversation survives the move from the Sidecar to the Workspace, and a reload. Ask in the Sidecar, open the thread in the Workspace, reload: the same saved conversation every time.
Access still governs — SC-GOLD-004
“Show this person's HR employment record.”
Asking from a page grants nothing: what the reader may not read never reaches the answer. On a person whose name is HR-restricted, ask for their HR employment record: the Sidecar knows the page, and the read is refused.
Mobile changes layout, not meaning — SC-GOLD-005
“Did CRM opportunity OPP-2026-900001 continue into ERP? Show the recorded handoff.”
On a phone the Sidecar is a full-height overlay with the same context and the same answer. The same contextual Ask as SC-GOLD-001 at phone width: the overlay covers the page and answers the same; closed and reopened, it starts from the same record.
Stop means it does not come back — SC-GOLD-006
“Who is Bharat Polymers?”
A turn the reader stopped is not saved: reopening shows only the turns that completed. Complete one turn, stop the next, open the thread in the Workspace: the stopped turn is gone and the conversation still answers.