Questions for each source
- Where is the current authoritative information?
- Who manages the source and its access?
- Which information is necessary for the task?
- Should the Dot only read, or also make changes?
AI Dots
Connecting AI Dots to apps and business information
A Dot needs reliable information. BigBase identifies the apps, documents and access required by your task and checks which route is available in your workspace.
Start with the authoritative source
A Dot can prepare a useful overview when it is clear which information matters. A spreadsheet, CRM and separate documents may contain different versions of the same data. Together, we choose the authoritative source.
- Name the information owner.
- Define how current information is recognised.
- Use only the fields and documents required.
- Agree how conflicting versions are handled.
Choose a route that fits the work
We assess existing connections and permitted working methods in your environment. Where a fixed integration better handles a recurring data step, our AI & Automation service can support that step.
The Dot then receives a concrete assignment, such as organising the supplied information into a case overview. This makes it clear which part moves information and which part prepares a result.
Separate reading from changing
Access to information does not automatically mean every change is wanted. An initial setup can produce a draft or overview only.
- Which source may be read?
- Where may the result be saved?
- Which change requires review first?
- Who checks that processing is not duplicated?
These agreements also help with testing: we assess the result and where it appears.
Make failures visible
A missing folder, changed app or revoked permission should lead to a recognisable report. We define who receives that report and which manual workflow the team can use temporarily.
Read access and review for responsibilities and monitoring and improvement for changes after setup.
Agreements for the information flow
- One authoritative source for important data.
- Clear document names and working folders.
- A recognisable result for the employee.
- A fallback when access or information is missing.
Frequently asked questions
Can every business app be connected?
No. We check the options for each app and workspace. An existing connection, permitted browser route or additional automation may be needed. We do not promise an integration before checking the route.
Is an API always required?
It depends on the available route and assignment. An API connection may be useful for fixed data exchange. If operating many different apps is central to the role, we also consider an AI Employee.
Explore AI Dots
Implementing an AI Dot: from assignment to practical trial
Scope, preparation, trial assignments and handover for your first AI Dot.
Read this guideWhich workflows suit an AI Dot?
Examples for case preparation, research, internal work queues and meetings.
Read this guideConnecting AI Dots to apps and business information
Choose sources, avoid duplicate processing and identify the connections you need.
Read this guideAccess and human review for AI Dots
Use focused access, clear approval points and an owner for exceptions.
Read this guideAI Dot pricing: monthly service or one-time implementation
Understand both BigBase prices and how a Dot differs from an AI Employee.
Read this guideManaging and improving AI Dots after setup
Review quality, time savings and changes without quietly widening the task.
Read this guideDiscuss your first AI task
Tell us which work takes time. We help you choose a service and define the scope in a proposal.