Knowledge plus interaction
A knowledge base can answer a question. An Expert in the Box can also watch relevant events, recognise when the situation changes, propose the next step, and return the result to the Inbox.
The interaction works in both directions. An event can activate an expert, and an expert can send a structured proposal, action request, answer, or result back as a new governed event.
That closed loop keeps knowledge, action, evidence, and accountability connected.
The two-way event loop
The model or agent may change. The business objective, current state, conditions, decisions, and evidence stay with the Inbox.
A price changes, a policy is updated, a campaign converts, a question arrives, or an external agent reports a result.
The Inbox connects the event to approved knowledge, data, state, ownership, audience, and applicable conditions.
Your agent or an approved specialist agent receives only the context and capabilities required for this objective.
The expert can answer, recommend, escalate, or invoke an authorised action without redefining business authority.
The decision, action, evidence, and resulting state return to the Inbox and remain available for the next interaction.
Example experts
These are starting points, not fixed agent products. Combine domains, connect your own agents, and define the information, capabilities, limits, approvals, and outcome for each expert.
Answer customer questions in your own branded webchat, using only the business context you approve.
Make voice conversations as controlled and useful as every other business interaction.
Keep prices relevant without losing margin, policy, or accountability.
Keep financial decisions aligned with current records and authority.
Keep every campaign and message relevant, permitted, and measurable.
Keep advice and operations aligned with the applicable rule and source.
Keep decisions connected to what customers, products, and operations are doing now.
Web Chat SDK · available on npm
0.1.0-beta.2 · Public previewBuild a web agent that fits your website, with the DataInbox Web Chat SDK. Bring the conversation to the approved business knowledge and current context you choose to make available. Your configured Inbox determines what the agent may answer, look up, prepare or hand to a person.
Choose the colours, layout, tone and interaction. The headless JavaScript / TypeScript SDK connects the conversation without imposing a chat window.
Select the documents, fields and source context permitted for the task. A public chat session does not unlock private Inbox data or your entire company.
Define allowed tools, limits, approvals and human handoff in DataInbox. A model response cannot grant permission or approve its own next action.
Included with your DataInbox licence. No separate SDK licence fee.
Your existing message, runtime and storage allowances apply. AI/provider usage and optional implementation work remain subject to their existing terms.
Customer questions · Product advice · Sales requests · Service triage
See the SDK overview for developersWeb agents with a specific job
Explain healthcare information, book an available asset or start a payment. Your brand shapes the interface; your sources, rules and connected systems govern the conversation.
Application patterns · configured per environment
Make approved medication information and clinical care pathways understandable. Your organisation decides which sources, process steps and escalation routes the agent may use.
The agent does not independently diagnose, select medication or decide a dose. Clinical decisions remain with the healthcare professional.
Connect a planning bridge for current availability, capacity and reservation rules. Let customers book assets, equipment, time slots or services, from rentals to passenger transport.
A proposal is not a reservation. Only the connected system confirms the booking; an uncertain status stays visible.
Riveer is a Ferryon case study. A chat connection for scheduling, tickets and payments is configured per channel.
Explore Riveer at FerryonLet a customer start a payment from the conversation. The connected system supplies the amount and order reference; the payment provider processes payment on a secure checkout page.
No card or bank details in the chat. The agent reports ‘paid’ only after a confirmed status from the payment provider.
These are integration patterns, not default activated SDK features. Planning bridges and payment providers are configured and tested separately. Provider contracts, transaction fees and any implementation work still apply separately.
Personal healthcare data requires a separately authenticated and authorised environment. A public chat token is not access to a patient record.
Connect your own agents
Connect an internal agent, specialist service, preferred AI provider, or agent framework to one or more authorised Inboxes. DataInbox prepares the permitted task and receives the structured result.
State, knowledge, rules, responsibilities, and evidence remain available as agents change.
The agent interprets, monitors, proposes, or performs only the capability assigned to it.
Purpose, fields, actions, limits, approvals, and refusal paths determine what may happen.
Answers, proposals, actions, exceptions, and evidence become traceable business messages.
Start with one recurring question, signal, decision, or action. We shape the smallest useful expert interaction and keep every next step inside the evidence and authority of the Inbox.
Box your expert use case
