Data lives in silos.
ERP + ChatGPT / Find and understand information.
Personal agents
deployed
Reduction in
workforce hours
Lower cost
compared with other AI tools
An answer from
what the business knows.
A customer’s order arrives short. BotX reads the ERP records and the policy shared by Finance, then prepares a response. People step in for missing facts or a new decision.
Get a client proposal
ready to send.
BotX works from the brief, current records and authorised shared knowledge. It asks a person when evidence or a decision is missing.
“Prepare the client proposal using the approved price and delivery plan.”
Your BotX starts the work in TandemX.
Built for work
between people.
Compare the standard workflows below.
| What comes built in | TandemX BotX for you. Shared work for your team. | ChatGPT Standard Slack / Teams assistant | ERP agent Business Central Sales Order Agent |
|---|---|---|---|
| Shared requests between personal assistants | |||
| Colleague replies continue your original task | |||
| New deployment cost* | $ | $ | $$$+ |
| Also covered by all three | |||
| Works with available business information | |||
| Works between human check-ins | |||
Included Not documented in the compared standard workflow. Custom integrations may add it.
*Illustrative cost bands for a new deployment. Existing ERP licences change the comparison; actual costs vary.
Your team’s tools.
Part of the work.
connections
integrated
Availability and actions depend on provider setup and permissions. Some connections need administrator setup.
Start with a sample business.
Then bring your own work.
Explore how BotX handles orders, planning and follow-through with ready-made sample records. Or connect your own Google or Outlook account for supported tasks: find what needs attention, prepare a response and review proposed actions before they run.
Your data.
Protected and controlled.
Connect the systems you choose. Control who can use them and which actions need your approval.
Read our privacy policy ↗Encrypted in transit and at rest.
Protection while your data moves and while it is stored.
Access to your connections is restricted.
Give access to the people who need it. Revoke it when they no longer do.
Connected-account data is excluded from training.
Optional sample-demo sharing is a separate choice. See the privacy policy for AI processing and provider handling.
Review before sharing.
Share the details a colleague needs. Your private conversation stays separate.
Before you try it
with your team.
What is BotX?
BotX is a personal business assistant for an employee. The intended flow starts with available connected records, brings in authorised knowledge from colleagues’ BotX assistants and involves people for missing facts or decisions.
Does BotX need colleagues to type every answer?
No. Facts already available in a permitted ERP record, document or shared knowledge should be used directly. The source-first example shows this with sample records. A person is needed for an unrecorded fact, conflicting evidence, a fresh commitment or an approval outside delegated authority.
How do I give it the starting information?
Describe the outcome and provide or connect the relevant sources. BotX works within the access available for that task. You should not need to copy facts out of a connected system or ask a colleague to retype information that is already available.
Does everyone need to share private conversations?
No. An employee’s BotX contributes only information authorised for the request. Being in the same company does not grant access to another employee’s private sources or conversations.
What do I get back?
An answer or draft grounded in the available sources, with its conditions and any gaps visible. In the sample short-shipment example, the order, dispatch record and published Finance policy support the proposed response. Maya reviews it before it goes to the customer.
Is this a shared knowledge graph?
Connected knowledge helps find relevant facts and relationships. The outcome is useful work carried through from evidence to response, with current sources, permissions and necessary approvals preserved.
Can it use all our software?
Connection options cover mail, files, calendars, projects, CRM and ERP. Available reads and actions depend on the provider, setup and your permissions. The examples are illustrative; we confirm the supported end-to-end work with your team.
What can I try today?
Try TandemX on a ready-made business, then see what it can do with your own work. Start with clearly labelled sample records, or connect your Google or Outlook account for supported tasks. BotX can help identify what needs attention; the current Google connection also supports proposed email, calendar and Drive actions that you review before confirming. Sample scenarios do not change your ERP or prove that every company workflow is connected.
How do we start?
Choose a repeatable request and the sources needed to answer it. Check that BotX uses available records without repeated questions, shares only permitted knowledge and involves a person where an actual gap or decision remains.
Which task should we try with your team?
Tell us how your team handles it today. We’ll discuss the people, information and decisions involved, and what TandemX can support.