Email with a copilot
Reads the failure notice.
It can extract the amount, summarise the email and draft a reply. A person or another integration still has to find the current account state and decide what to do.
How DataInbox works
An operational Inbox for events, context and action.
Email keeps a conversation in one channel. A DataInbox brings the permitted CRM, ERP, product and interaction data around a customer, employee or process into one operational context. So people and agents can provide the right help through any channel, and perform only the actions they are allowed to take.
Why now
Reading content is only the first step.
Text, OCR, extraction and summaries are widely available. Business operations need more: knowing that something happened, what changed, which customer or process it concerns, what is true now and what may happen next.
Order placed
Payment status changed
Customer context updated
Agent action proposed
One simple example
A failed payment is not just a message.
DataInbox
Handles the PaymentFailed event in context.
It links the customer, invoice, contract, retry history and current status; evaluates the recovery rules; permits the next action; and records the new outcome as evidence.
One customer, every channel
The experience follows the context, not the channel.
A DataInbox can bring permitted data and references from CRM, ERP, product systems and previous interactions into the current situation. Whether someone arrives through chat, email, voice, an app or an internal service desk, the relevant context is already there.
CRM data
Identity, relationship, preferences, consent, and interaction history.
ERP data
Orders, invoices, fulfilment, service status, and operational state.
Product data
Products, availability, entitlements, contracts, and current conditions.
Every channel
Web, email, chat, voice, app, service desk, system, or agent.
The operating model
One continuous path from event to accountable outcome.
- 01
Event
Something relevant happens in a person, system, database, device, document, or agent.
- 02
Context
The Inbox resolves current data, state, history, domain meaning, and knowledge.
- 03
Decision
Schemas, rules, permissions, limits, and approvals determine what may happen.
- 04
Action
A person, system, agent, or Companion performs only the permitted operation.
- 05
Evidence
The decision, action, state change, and outcome return as new traceable events.
A second real implementation
Medication knowledge becomes usable context, with its sources still attached.
The current BenzoMoe DataInbox is not a loose collection of documents. Its implemented source library accepts structured and unstructured material and classifies it as medicines, guidelines, ATC references, recommendations, contraindications, escalations, tapering knowledge and quality exceptions.
What is implemented, and what comes next
The source and knowledge layer shown here is implemented. The visitor answer, applicability checks and professional escalation depict the governed interaction this layer is being prepared to support. That distinction remains visible so the visual is evidence-led, not a generic product promise.
A different operating layer
DataInbox governs the work between your existing categories.
Not an email copilot
Copilots read, summarise, and draft. DataInbox connects an event to live state and governs the action that follows.
Not a workflow builder
DataInbox governs messages and decisions while specialist workflow tools can keep orchestrating complex chains.
Not one giant data store
Independent Inboxes exchange only the messages and references their policies permit.
Not a connector catalogue
Connectors move messages. The receiving Inbox determines whether they are usable and what may follow.
Federated by design
Complete context without one Inbox owning everything.
A customer, order, payment, policy, or agent operation can remain in its own policy boundary. Inboxes share only the messages and references required for the current outcome.
Explore the architecture