Ask a question in the same chat app on phone, tablet or computer, and get the answer from several connected systems at once, with nothing to install. Scheduling, membership and contract data or bookkeeping figures such as tax, revenue and liquidity are right there. Nothing gets written on its own, every change waits for your confirmation.
The Agentic Part
An agent reads every request against the live database, never a copy, and follows the sign-in of the person asking: it only ever shows what that person could already reach. It never writes directly: a chat request becomes a proposal in a form, checked under your application’s own rules and executed only after your confirmation. It checks authorization individually for every tool, so a visitor automatically sees a different tool set than a staff member.
Main Features
- Fixed, checked tools over your existing API
- Tool descriptions tuned to how your team asks
- Fuzzy matching for imprecise names
- Reads without confirmation, changes only with confirmation
- Chat access built into the existing application
- Two sign-in methods, per connecting app
- Standardised connector description for chat sign-in
- Reliable sign-in behind a shared access point
- Documented fix for a known directory-service sign-in issue
- AI proposes, a chat form confirms and executes
- Same live data source across app, chat and automation
- Fuzzy name matching for imprecise entries
- Ready-to-use topic areas: scheduling, members and contracts, tax figures, vouchers, revenue by contact, liquidity, invoicing, and work time and billing.
- In-chat form with your application's fields and rules
- Fixed rule: AI proposes only, never writes directly
- All changes routed through the checked form
- OAuth 2.1 sign-in with auth description for the chat app
- Separate access key for desktop apps without OAuth
- Directory setup so consumer chat apps accept the sign-in
- Tool visibility set by who is asking: visitor or staff
- Authorization checked individually for every tool
- Preview and confirmation before any change-making tool runs
- Automated test for visitor-only tool visibility
- Two sign-in modes: personal for staff, automatic for systems
- Own presence per location, under its own web address
- Automated test for correct sign-in and rejected wrong entries
- Desktop chat app installer that merges with existing settings
Use Cases
- Answering a question that touched a different system used to mean opening a separate application. Now the same chat app on phone, tablet or computer answers a question from several connected systems at once.
- A staff member asks about a contract change in chat. The agent turns it into a proposal in the form, and it is only written after confirmation.
- A visitor and a staff member ask the same question in the same chat. Each only sees the tools their own sign-in gives them access to.
- A new location joins the estate. It gets its own presence and its own address from the same shared base.
What we build for you
- Each additional system gets its own checked connection before it joins.
- Custom tools for your data structure
- Wording in your office's own terminology
- Registration and verified custom domain
- Issuing the access keys
- Chat app connection setup
- Staging test before go-live
- The form's fields and checks are set to match your records.
- Your identity provider
- Proof of domain ownership
- Role-based access to tools
- Which tools and data are public versus internal
- Records from your own business systems
- Scope and description of the covered tools
- Domain names mapped to each location
- Sign-in area for staff
