Back office, overnight
Reaching into a system we have never heard of
Your own API, as a tool the assistant can use
Every business has one system nobody else has — an inventory database, a warehouse API, a legacy booking tool. The assistant being unable to see it is usually the reason automation stops at the interesting part.
- Describe your endpoint once; it becomes a tool
- Same approval gates as any built-in capability
- Outbound calls pass a guard — HTTPS only, no internal addresses
- Credentials encrypted, and never shown to the model
We reply in under an hourOr message us on WhatsApp
Today
An assistant that can answer everything except the question customers actually ask, because the answer lives elsewhere.
With this running
Your own system answering through the same conversation, with the same approvals and the same audit trail.
Step by step
What actually happens
- Your team
Describes the endpoint — method, URL, fields, credentials — once, in settings.
- Customer
“Do you have the blue one in stock in Lahore?”
- Assistant
Calls your inventory endpoint like any other tool and answers from the response.
- Your team
Sees the call, its arguments and its result on the run's timeline, like everything else.
01 / 02
It is a tool, not an exception
A connector goes through the same machinery as a built-in capability: the per-assistant permission map, the approval gate, the audit trail, the spend ceiling. There is no separate path with weaker rules — which is what makes it safe to add one without re-reasoning about the whole system.
02 / 02
The guard on the way out
Outbound calls are forced through a guard: HTTPS only, private and internal addresses blocked after the hostname is resolved, and redirects refused. A connector cannot be pointed at something inside your own network, deliberately — that is the failure mode that turns a helpful integration into a way in.
- HTTPS enforced, plaintext refused
- Resolved addresses checked, so a public name cannot map inward
- Redirects not followed
- Credentials encrypted at rest and never in the model's context
How this is put together
The same building blocks every assistant is made of. Nothing here is bespoke to this scenario.
What starts it
A customer message — Any run — a connector is just another tool
Where it runs
What it can do
- Looked up a contact by number
- Looked up the contact
- Replied
- Added a note
What it uses
Every action above is a real capability, and every run keeps a record of which ones it used. How the engine holds this together →
More like this
Other things it does
The weekly digest that writes itself
What moved, what did not, and what to look at
Dashboards answer questions you already knew to ask. What a manager actually wants is the two numbers that moved unexpectedly, and finding those means reading all of them.
Learn moreKnowing exactly what it told your customer
Every action, every result, in plain language
The question anyone asks about an assistant is always the same, and it is always asked urgently: what did it actually tell my customer, and what did it change.
Learn moreTomorrow, prepared overnight
Split across helpers while the building is empty
Preparing a clinic day is three unrelated jobs that all have to be done and none of which need each other. Done in sequence it takes an hour; done at once it takes as long as the slowest one.
Learn moreWhere this runs
The channels this scenario works on, and the industry module it belongs to.
Would this work for how you actually operate?
Tell us the scenario you have in mind. If it needs a building block we do not have, we would rather say so than sell you a demo.
We reply in under an hourOr message us on WhatsApp