1. The customer asks Van Donzel a question
A conversation enters through the webchat with the channel, conversation, contact, message, date, and source context attached.
Customer case · Woongelofelijk Van Donzel
From iONE ERP transaction to a governed customer answer.
Woongelofelijk Van Donzel is a family business with a 12,000 m² home and interior store in Uden. DataInbox connects its iONE ERP transactions, order status, website knowledge, webchat conversations, delivery updates, sales events, marketing measurement, and operational review without turning one AI agent into an all-access system.
iONE ERP connectedWebchat connectedRead-only order lookupHuman control retained
Van Donzel Customer Experience
1iONE ERP and approved website knowledge
2Governed DataInbox workspaces
3Webchat, email, sales, Meta, and weekly review
The people behind the customer experience
Woongelofelijk Van Donzel · Uden
The business context
Personal service across a long customer journey
Van Donzel has served customers since 1910 and combines a large physical store, interior advice, an extensive assortment, online orientation, ordering, delivery, and after-sales service. A customer question can therefore depend on published advice, a current transaction, delivery progress, or a decision by a Van Donzel employee.
Visit Woongelofelijk Van DonzelThe operational problem
The answer exists, but not in one customer-service tool
Product knowledge lives on the website. The current order and delivery state live in iONE ERP. The conversation lives in the webchat. Sales and marketing need transaction events. Management needs a weekly view of changes and exceptions. Copying all of that into a general chatbot would create another fragmented and over-privileged system.
The DataInbox choice
Keep each source and responsibility separate. Resolve only the context required for the current question, apply a controlled route, use a specialist agent only where interpretation helps, and retain the resulting event for the next permitted business use.
The customer journey in practice
A customer asks: where is my order?
The answer crosses systems, but the customer experiences one conversation. The information boundary remains explicit at every step.
2. The question follows an explicit route
The Webchat Agent distinguishes a greeting, website question, order status, order change, or out-of-scope request. Each route has its own permitted outcome and fallback.
3. Order status uses a minimal lookup
Only an order number and postcode may start the lookup. The agent sees delivery status, delivery date, transaction type, and delivered versus total quantity, not the complete iONE ERP transaction.
4. Product questions use approved website knowledge
The service agent searches Van Donzel's published website content and receives at most three relevant results. Unrelated internal information is not part of the answer context.
5. Change requests remain controlled
An order-status question may be answered from read-only data. A request to change an order follows a separate response path and does not silently acquire permission to alter iONE ERP.
6. The answer returns through the existing service channel
The approved reply is posted back to the same webchat conversation. Conversation and message identifiers make processing idempotent and error paths return a bounded fallback.
The configured DataInbox environment
Eight focused Inboxes form one customer experience
Every Inbox owns a specific message, context, rule set, and outcome. They cooperate without collapsing customer service, transactions, knowledge, marketing, and management into one unrestricted agent.
Source and operational state
iONE ERP
The operational transaction source is normalized into current orders, updates, delivery state, quantities, deposits, invoice state, handling, branches, and line information.
Minimum necessary customer context
Order Lookup
A deliberately small read-only order projection exposes only the fields needed for a safe customer status answer.
Published knowledge only
Website Knowledge
Approved public pages are stored as searchable chunks with source URL, headings, keywords, fetch time, and content identity.
Customer dialogue and policy
Webchat Agent
One conversation-aware entry point routes questions and gives specialist agents only one bounded lookup capability for their task.
Proactive customer updates
Update Agent
Changes in delivery state prepare customer communication and retain delivery feedback, including accepted and delivered email states.
Sales context and reusable events
iONE ERP Sales Events
Validated transaction events produce daily sales views and bounded weekly exports, with explicit claims preventing the same side effect from being processed twice.
Controlled marketing measurement
Meta measurement sink
A separate test destination receives the selected purchase event, value, currency, item count, order reference, event time, and action source for channel verification.
Management overview with visible gaps
Operational weekly view
Delivery changes and sales events come together in a reviewable week view with coverage, postponements, completed deliveries, sales activity, conflicts, and send permission.
AI-enabled and company-controlled
Van Donzel determines which questions and answers are possible
External customers and internal colleagues do not receive the same context, capabilities, or answer rights. That separation is part of the workspace, not a suggestion inside a prompt.
External customer questions
Supported questions
- Greeting and orientation
- Published product and service information
- Order status after order number and postcode
Control boundary
- Order changes follow a separate route
- Out-of-scope requests receive a bounded answer
- The order source remains read-only
Internal operational questions
Supported questions
- Which delivery state changed?
- Which orders were postponed or completed?
- What sales activity is present in the covered period?
Control boundary
- Coverage and source conflicts remain visible
- Missing information is not invented
- A draft is not automatically a sent message
Bounded AI by configuration
Conversation memory is limited to the most recent six or ten relevant messages. A specialist agent may make at most one lookup in an iteration. Order lookup is read-only, exposes a fixed field set, and requires order number plus postcode. Message identifiers prevent duplicate processing.
The isolated next step
Predict a realistic delivery date before writing to the customer
Van Donzel also has a separate synthetic trial for order expectations and communication. It is intentionally isolated from production delivery and cannot send messages automatically.
Order expectation
Evidence dates, supplier-date conflicts, internal signals, and a versioned policy produce an expected date plus explicit reasons.
Communication draft
The calculated expectation is transformed into a baseline and AI-assisted draft for internal review.
Closed action boundary
The trial records sendAllowed and suppression reasons. It has no outbound action and uses synthetic trial data.
Tooling and cost logic
Use iONE ERP and the webchat. Avoid rebuilding customer context around them.
DataInbox does not replace the systems that already do their specialist job. The saving comes from reducing the additional tools and manual work otherwise required to connect, copy, interpret, route, and reconcile the same customer event repeatedly.
This page makes no quantified savings claim. The exact reduction depends on which overlapping tools and manual steps Van Donzel retires after operational approval.
Potential overlap DataInbox reduces
- A separate FAQ bot with its own ungoverned knowledge copy
- A second order-status portal that exposes another customer-data surface
- Repeated point-to-point logic for delivery emails, sales reporting, and marketing events
- A spreadsheet process that reconstructs postponements, delivered orders, and weekly sales
- A large general AI model reinterpreting fixed routes and permissions for every message
What is verifiably present
Configured workflows, observable records, and explicit limits
The inspected Van Donzel environment contains current iONE ERP transaction and order-projection records, routed webchat conversations, indexed website knowledge, delivered email feedback, daily sales views, weekly sales exports, Meta test receipts, and operational week-view records. The order-expectation and communication cases are marked synthetic and keep sending disabled.
Customer answers use bounded sources
Actions and side effects are traceable
Trials stay separated from production
Other detailed examples
Explore another customer case or implementation pattern
Continue with the Markant Theater Maashorst organisation workspace or explore one of the focused implementation patterns.
Build your governed customer experience
Which customer question crosses the most systems in your organisation?
Show us the question, the source systems, the answer your customer expects, and what must remain under human control. We will validate the information in the Sales Workspace before preparing a proposal.