Question 1

What is DataInbox in one sentence?

Accepted Answer

DataInbox connects business events to current data, state, domain context, knowledge, and rules, then governs the actions humans, systems, and AI agents may perform.

Question 2

Why is DataInbox needed now?

Accepted Answer

AI made emails, documents, conversations, transcripts, images, and free text machine-interpretable. That creates new operational power, but companies still need to determine what AI may see, understand, propose, change, and send. DataInbox turns that input into governed business context and permitted operations.

Question 3

Which problem does DataInbox solve?

Accepted Answer

Business messages and context are fragmented across applications, documents, channels, databases, and manual work. DataInbox gives each relevant message a governed path from arrival to outcome, so people, systems, and AI operate with the right context and the same company-defined conditions.

Question 4

Where should a company start?

Accepted Answer

Start with one important business message where incomplete context, slow answers, manual handling, or uncontrolled AI already creates measurable friction. Common starting points are customer questions, order events, payment validation, case handling, documents, and agent proposals.

Question 5

What is a business message?

Accepted Answer

A business message is a traceable representation of something that happened, was requested, changed, arrived, or was decided. It can originate from structured data, free text, a document, a customer interaction, a system event, or an agent result.

Question 6

What is an Inbox?

Accepted Answer

An Inbox is a configurable, governed operating environment that turns events into business outcomes. It resolves current data, state, history, domain context, and knowledge before company-defined schemas, permissions, rules, and approval paths determine what may happen.

Question 7

Does all company data go into one Inbox?

Accepted Answer

No. Each Inbox is a governed operating environment for a specific outcome. Customer, order, payment, consent, content, and case information can remain inside separate Inboxes with their own schemas, access, retention, rules, and evidence.

Question 8

Can separate Inboxes form one dossier?

Accepted Answer

Yes. Inboxes can exchange permitted messages, references, and results. The current operation receives only the context it is allowed to use, so a traceable dossier can form without one Inbox owning every underlying record.

Question 9

What happens after an action or AI result?

Accepted Answer

The result returns to the relevant Inbox as a structured business message. It can update state, remain available as evidence, or trigger the next deterministic rule and approval path.

Question 10

What is DataInbox Agent Runtime?

Accepted Answer

Agent Runtime coordinates the business messages, context, deterministic policies, approved capabilities, people, agents, results, and evidence around an operation. Intelligence can change while business authority stays with the Inbox.

Question 11

Does AI make the final policy decision?

Accepted Answer

No. AI can interpret input, enrich context, prepare work, and propose or perform allowed tasks. Deterministic configuration and rules decide which context may be shared, which capabilities may be invoked, and which actions may proceed. Human approval can remain mandatory where judgment is required.

Question 12

What is a Companion?

Accepted Answer

A Companion makes an external service provider available to one or more authorised Inboxes as a governed operational capability. Your organisation chooses the provider, the Inboxes that may use it, the context it may receive, the operations it may perform, the limits and approvals that apply, and the evidence it must return. The provider supplies the capability. DataInbox keeps authority and control inside your conditions. The AI Companion layer is included with every plan. Payment and Identity are available specialist Companions. Delivery and Voice Companions are coming soon.

Question 13

Can we choose AI per Inbox or for the whole company?

Accepted Answer

Yes. The included AI Companion layer can approve a direct provider, router, managed platform, or private model for one specific Inbox. The same approved AI options can also be exposed through shared company policy and then narrowed by each Inbox. Provider usage remains subject to the selected provider contract.

Question 14

Can agents operate payments or identity management?

Accepted Answer

Yes. Assign the payment or identity service provider you choose to any Inbox you authorise. A Payment Companion can execute a permitted payment from a webchat conversation, through an authorised agent, or in response to a defined business action. Inbox policy controls who or what may initiate it, its purpose and amount, limits, and approvals. The payment outcome returns as a governed business message. An Identity Companion can verify a person, resolve an account, or control access to a personal Inbox while the Inbox records purpose, authority, consent where required, permitted context, outcome, retention, and evidence. Availability depends on the selected provider, connector, credentials, and agreed scope.

Question 15

Does DataInbox require one AI provider?

Accepted Answer

No. Policy can select a direct provider, router, managed multi-model service, or private model according to data sensitivity, sovereignty, output requirements, capacity, and cost. Core business logic remains independent from the provider.

Question 16

Can MCP services and existing agent frameworks connect?

Accepted Answer

Yes. An MCP service or external agent can provide a capability through an Inbox-defined contract. DataInbox determines which context may leave, which tool may be used, what result is accepted, and how that result becomes a governed business message.

Question 17

Which controls can be configured per Inbox?

Accepted Answer

An Inbox can govern schemas, classifications, identities, purposes, permissions, allowed actions, approvals, escalations, retention, deletion, Companion access, result contracts, and evidence for its own operating context.

Question 18

How are rules enforced?

Accepted Answer

Routing, validation, approval, escalation, rejection, and permitted actions are enforced through explicit, deterministic configuration and rules. AI can help interpret information or propose work, but it does not silently rewrite enforcement policy.

Question 19

What evidence remains available?

Accepted Answer

The runtime can retain the original message, its source and context, applicable rule and configuration versions, approvals, invoked capabilities, result, and subsequent state changes as traceable business-message records.

Question 20

Does DataInbox make a company compliant with NIS2, GDPR, or the EU AI Act?

Accepted Answer

Software alone does not make an organisation compliant. DataInbox provides configurable controls and evidence that can support NIS2, GDPR, EU AI Act, and internal-policy requirements. Applicability still depends on the organisation, use case, role, risk classification, configuration, contracts, and operating procedures.

Question 21

How is customer consent handled?

Accepted Answer

Customer data can be connected to identity, source, purpose, consent, retention, permitted channels, and allowed actions. AI and downstream systems receive only the customer context and authority permitted for the current purpose.

Question 22

What can connect to DataInbox?

Accepted Answer

Services, business applications, streams, queues, databases, warehouses, files, devices, APIs, webhooks, SDKs, adapters, and MCP capabilities can participate. Actual availability depends on protocol, credentials, deployment, adapter, and the contracts of the source and destination.

Question 23

Can DataInbox translate messages for another system?

Accepted Answer

Yes. The receiving Inbox can validate the source message, map fields and context, and deliver a message that follows the contract expected by the next Inbox or third-party system. Delivery results return as traceable business messages.

Question 24

Does DataInbox replace an integration platform?

Accepted Answer

Not necessarily. An integration platform moves data between systems. DataInbox governs whether the resulting business message is valid, permitted, and usable for the current operation. Existing integration platforms can remain connected where they are useful.

Question 25

Does DataInbox replace CRM, CDP, or workflow software?

Accepted Answer

It can coexist with those systems. When DataInbox takes over customer context, validation, rules, approvals, and operational execution, organisations may be able to consolidate overlapping CRM, CDP, customer-service, workflow, and automation capabilities. The actual replacement scope depends on the required records, processes, integrations, and user experience.

Question 26

Can DataInbox support high-volume interactions?

Accepted Answer

DataInbox is designed around message-based operations and can support high-volume customer and system interactions. Required capacity, ordering, latency, retention, and availability are established for the specific workload and deployment.

Question 27

Where does the managed DataInbox runtime run?

Accepted Answer

The managed SaaS runtime is currently configured on DigitalOcean. Shared platform and infrastructure controls support the Inboxes running there.

Question 28

Can DataInbox run in another region or customer-controlled environment?

Accepted Answer

Other regional, data-centre, or customer-controlled arrangements are architecture and service-scope decisions. They are evaluated against residency, network, identity, availability, support, and operational requirements.

Question 29

How are configuration changes controlled?

Accepted Answer

Inbox configuration can follow a gated flow: validate the proposed change, inspect the difference, run a validated dry-run, and only then apply. Reusable templates can be validated, expanded, dry-run, and applied through the same controlled approach.

Question 30

Does DataInbox require replacing the current stack first?

Accepted Answer

No. A first Inbox can connect to the current systems around one valuable operation. The scope can expand message by message as the company proves value and decides which overlapping tools should remain, integrate, or be retired.

Question 31

How quickly can a first use case be defined?

Accepted Answer

The discovery can begin with one message, the context needed to understand it, the conditions that must remain authoritative, and the outcome the business wants. Delivery timing depends on source access, contracts, integrations, security requirements, and deployment scope.

Questions first. Straight answers.

Six subjects. One consistent operating model.

Start here

Business messages and Inboxes

AI, agents and Companions

Rules, security and compliance

Connectors and existing systems

Deployment and adoption

Still deciding where DataInbox fits?