Know what is available.
Manage sources and inspect samples of imported data. Make it clear which information you publish for use by AI.
Business context for AI
Make business data, definitions and working practices available together to your AI assistant. With ThinkBox, you manage what is available, how data connects and who can use it.
ThinkBox provides the data and context.
Your connected AI assistant creates the answer.
A product by DevBox
Can I deliver everything I promised Delta on Friday? Check the customer agreements, order schedule and my email.
Delta needs 20 units for the opening. CRM
The schedule has 20 units on Friday and 60 on Tuesday. ERP
Your email promises all 80 on Friday. Outlook
The schedule covers the opening, but not your full promise. Agree on a split delivery: 20 on Friday and 60 on Tuesday.
The context behind the answer
A customer is called a debtor elsewhere. Status A means ‘active’. And ‘resolved’ has exceptions. Record that knowledge centrally so your AI assistant can consult it for future questions.
Manage sources and inspect samples of imported data. Make it clear which information you publish for use by AI.
Give fields recognisable names. Describe terms, codes and business practices so the explanation is available alongside the data.
Record how customers, service requests and other data relate to each other. Explore suggested relationships and review which connections are valid.
Configure publication, roles and personal access. Make deliberate choices about shared and user-specific data.
Business knowledge that lasts
Manage working practices with a topic, applicable sources and validity dates. Prepare a change as a draft while the published explanation remains available.
“Use the invoice date for monthly revenue. State whether cancelled invoices have been included.”
Available as guidance for the assistant. Your organisation owns the content and checks how AI applies it.
AI in practice
A customer meeting, a delivery promise or an open quotation. With configured sources and recorded relationships, your connected AI assistant can combine information from several systems.
01 / Prepare for a customer meeting
Three pieces of information about the same customer:
ThinkBox context: the customer record, orders and email addresses belong to the same organisation.
Measure in your pilotPreparation time, missed talking points and incorrect customer matches.
I am meeting Noordlicht tomorrow. What opportunity do you see when you combine our CRM data, orders and my email?
The expansion opportunity in the CRM is becoming more concrete: order volume has grown by 30% and the customer has emailed to ask about delivery to two addresses.
Discuss a proposal for both locations, including volumes and delivery arrangements, at tomorrow’s meeting. The order growth and the email give you a concrete reason to follow up the CRM opportunity.
02 / Check a delivery promise
The order does not tell you what you promised:
ThinkBox context: the customer agreement, order and delivery promise concern the same delivery.
Measure in your pilotIdentified discrepancies and time spent checking the delivery promise.
Can we honour what I promised Delta? Compare the customer agreements, order schedule and my email.
Not in full. Your email promises all 80 units on Friday, while the ERP schedules only 20 for that day. Those 20 do meet the minimum needed for the opening, as recorded in the CRM.
The schedule covers the opening, but differs from your promise. Discuss 20 units on Friday and 60 on Tuesday with Delta before the customer expects all 80.
03 / Follow up a sales opportunity
Extra context sheds light on a budget objection:
ThinkBox context: the quotation, orderable items and correspondence belong to the same sales opportunity.
Measure in your pilotUsefulness of the preparation and corrections needed by the account manager.
How can I make my follow-up on Rivierzicht’s open quotation more relevant? Combine the CRM opportunity, ERP quotation and latest email.
The CRM records a budget objection at €18,000. The email says one team starts later, and the ERP shows that the two parts can be ordered separately.
Suggest ordering €9,000 now and €9,000 next quarter. This matches the start dates of the two teams. Ask whether phasing the order would help address the budget objection.
Fictional illustrations of a conversation in a connected AI application. Required source connections, relationships, user-specific email data and the AI connection are configured and checked for each use case. The assistant creates the answer; you assess the result and carry out any follow-up actions.
Start with a recurring task. Agree in advance what makes an answer useful.
Service
“Which previous issues and service agreements are relevant to this customer?”
Management
“How many requests have been resolved according to our agreed definition?”
Onboarding
“What does ‘waiting for customer’ mean, and which working practices apply here?”
How it works
Each component has its own role. Together they connect available information to its use by AI.
Where you work and record information.
Retrieves the agreed data and delivers it to ThinkBox.
About SyncBoxStores data and manages meaning, relationships and access.
Where context comes togetherRetrieves permitted information, analyses it and formulates an answer.
Through a suitable connectionWe configure source connections, refresh schedules and the AI connection for your situation. Standard AI access is read-only. An authorised administrator can temporarily enable help with configuration; this does not change customer records or source systems.
Behind the scenes
Record how a CRM customer appears in orders and emails. Add explanations of codes and business practices, and decide which data is available.
The connected AI assistant uses that context to bring together information relevant to a question.
Useful context for your AI assistantThe assistant combines information and formulates the answer.
Set up with your AI assistant
Let your assistant help make sources understandable. It can define readable field names and code meanings, record synonyms, and create and activate relationships.
An authorised administrator temporarily enables these capabilities for their own connection. You can then have multiple definitions and relationships recorded from a single conversation.
Discuss the setup of your sourcesFrom 5 minutes to 4 hours · stop earlier at any time
Choose your own sign-in or one personal key. Existing permissions and the scope of accessible data still apply.
Have the assistant examine source information and data samples. It can develop suggestions and save changes directly in ThinkBox.
ThinkBox validates changes; you remain responsible for their meaning. There is no separate approval step. Once the window ends, new admin actions are refused.
The admin window does not renew automatically. These functions cannot change customer records, technical import keys or access settings.
Deliberate choices
Good use of AI starts with clear agreements. About the information you make available, who can use it and who maintains the setup.
More about data and accessPrepare sources and practices as drafts. Decide what to activate and which guidance is available. Deactivation stops publication but does not delete stored data.
Choose shared or user-specific data and configure ThinkBox’s own permissions. Users assigned to the same data group can see the same data. Administrative roles may have broader access.
Assign owners for meanings, relationships and business practices. Review answers and adjust the context where needed.
Deactivate users or revoke personal AI keys. Updated permissions apply to subsequent requests; information already received in an AI chat is not recalled.
A focused first step
Choose a recurring task, a subject owner and a small group of users. A pilot shows what works and what still needs attention.
Record the question and the current way of working. Agree in advance what counts as a good result and which decisions people will continue to make.
Check source data and refresh schedules. Define terms, relationships and access, then connect the chosen AI assistant.
Measure time including review, accuracy and missing information. Weigh the results against setup, maintenance and AI usage.
Expand when both the results and ongoing management are workable.
Discuss your first use caseThinkBox manages the data and context that a connected AI assistant can use. The assistant interprets your question and formulates the answer. ThinkBox does not include its own chat interface in this product setup.
Data is supplied through SyncBox. We determine suitable source connections and an AI connection for each use case. A source or assistant is ready for use once its connection, access and data exchange have been configured and checked.
That depends on the source and the data delivery configured through SyncBox. ‘Last received’ shows when ThinkBox received a delivery; it does not prove that the entire source has been fully updated. We agree what freshness and completeness your use case requires.
ThinkBox uses its own roles, permissions and publication settings. Data can be configured as shared or user-specific. Administrative roles may have broader access. Permissions from a source system are not automatically copied one-to-one.
ThinkBox stores the supplied data for use by the connected AI assistant. Hosting, data location, retention and deletion are part of the setup agreements. Processing by the chosen AI provider also needs to be considered.
Quality depends on the source data, the context recorded and how the AI assistant uses it. ThinkBox supports better-grounded answers. A person still reviews results where needed. Recorded business practices guide the assistant and are not automatically enforced as rules.
Yes. An authorised administrator can enable temporary administration for their own sign-in or one of their AI keys. The assistant can change source information, field meanings, alternative identifiers and relationships, including activating relationships. The sources involved must already be active. ThinkBox validates and saves changes without a separate approval workflow.
Choose 5, 15 or 30 minutes, or 1, 2 or 4 hours. Then start a new chat and reload the connection if needed. The assistant cannot enable or extend this period itself. Read how temporary administration works.
Standard AI access is read-only. A question through ThinkBox does not change a customer record, ticket or order, or send an email. Temporary AI administration can change configuration and meaning inside ThinkBox; it does not broaden access to customer data.
After you select two sources, ThinkBox can suggest relationships based on a limited portion of the data. You can see matches and possible duplicates. An administrator reviews the connection: a suggestion does not prove that all records belong together and does not repair incorrect source values.
The current admin interface uses English. Names, descriptions and business practices can be entered in your organisation’s language. The chosen AI application determines which languages it supports for questions and answers.
Start with one recurring question, a clear owner and a result you can verify. Together, we identify the necessary sources, configuration, AI connection and how to evaluate the pilot. We discuss costs and service based on that scope.
Let’s make it concrete
Tell us what information you are looking for and where it is today. Together, we can explore a suitable first use case for ThinkBox.