The assistant on every screen
Piper opens beside any page and knows the page and the selection, so “why is this one stuck?” needs no explaining. One box takes every request — answer, investigate or build.
Not a chatbot in a corner. Agents people talk to wherever they work — answering from your data, citing it, and able to act.
On Botminds every agent holds a conversation: beside every screen, on the home page, inside apps, by email, in Microsoft Teams and through an API — with Viber and Telegram bringing customer messages in. Built for a project on knowledge bases of millions of documents, it is the same agent at every door: the same knowledge, tools and record.
In the appWhere people already are
Conversational AI is software people talk to in their own words — by chat, email or voice — that understands the request, keeps track of the conversation and replies in natural language. Enterprise conversational AI adds what a business needs: answers drawn from the organisation’s own data, held to what each person may see, with sources shown and actions a person approves.
The difference that matters to an enterprise is not how fluent the replies are — it is where the answers come from, who they reach, and whether the system can act on what it was told.
On Botminds the conversation sits where the work is — beside the screen, on the home page, inside the app built for the job.
Piper opens beside any page and knows the page and the selection, so “why is this one stuck?” needs no explaining. One box takes every request — answer, investigate or build.
Each person keeps their own agents, a click from the home page, with the same composer and features as the assistant.
The chat, and beside it the collections, pages and apps the agent works with — shared with everyone the agent is shared with.
Any page of an app carries a chat card bound to one agent: suggested questions, streamed answers, sources beside the chat, earlier conversations.
Share a conversation with colleagues to watch it or to continue it together, signed in with their own accounts.
You choose which tools wait for a person. When the agent reaches one, the request appears in the conversation: approve, reject or edit.
The chat runtime holds no conversation in memory: conversations, summaries and files are stored durably, so replicas scale out as people arrive and any replica takes the next turn. Customer messages queue durably and workers scale with them — on Azure, AWS, Google Cloud or on-premises.
scale out with the conversations · answers stream back as they are written
bursts absorbed · workers scale with the queue · every message kept until worked
conversations, summaries and files — any replica takes the next turn
Behind a reply that takes a few seconds, the same steps run every time, at every door.
Typed, dictated, or with files attached.
Who is asking, the page they are on, the conversation so far.
The agent’s sources, within what this person may read.
Granted tools; the ones you chose wait for a person.
In the person’s language, with its sources — kept with the conversation.
How the context is assembled: context engineering. How the search decides where to look: agentic RAG. How actions are granted and approved: the agent harness.
The risk with enterprise conversational AI is a confident answer drawn from a document the asker should never see, or from nothing at all. Both are closed off by design — across knowledge bases of millions of documents.
How many supplier invoices are still unmatched this quarter, and which is the largest?
42 invoices are unmatched for Q3. The largest is Bayside Freight’s INV-88213 for $48,920 — its purchase order was closed early. Sources: Invoices table · PO-5521
Draft a note to Bayside asking for a corrected invoice.
Here is the draft. Sending it uses the email tool, which waits for your approval — approve, reject or edit it.
People rarely ask in a vacuum: they have the spreadsheet, the photo, the contract. They drop it into the chat and ask about it — or dictate the question.
Which of these invoices don’t match the pallet in the photo
Kept to its conversation — for its owner and everyone it is shared with.
A dropped file is searched inside its own conversation, for its owner and everyone it is shared with.
The same reading and indexing as a library document, so the agent finds page 97 and quotes it with its page.
Dictation runs on the browser’s own speech recognition, and a one-time notice tells people who processes the audio.
Agent Reach takes the agent to people who will never open another app: a mailbox of its own and a presence in Microsoft Teams, answering there as itself — not as a person, and not from a person’s inbox.
Same engine as the API— so pausing the agent, spend quotas and the run record apply to every email and every Teams message.
An admin promotes an agent to email, Teams or both; one Teams app serves every agent in the organisation.
An operator pauses a promoted agent in one move; its mail waits, unread, for the resume.
Every email and Teams turn is kept on the run record like a chat in the app, under the same spend quotas.
Customers write on the messaging apps they already use. Connect Viber and Telegram as channels and every message, with its photos and files, becomes a record the right agents and people work on.
A Viber or Telegram account is connected to a collection, like any source.
Messages and their media land in the collection as records.
Switch on cases and a new message opens one, with its own reference.
The sender gets a confirmation with that reference.
The collection’s agents, workflows and people take it from there.
Any tool that talks to a chat-completions endpoint can talk to a Botminds agent: point it at the platform, name the agent as the model, and use a key. The agent keeps its own instructions, tools and knowledge.
POST /api/runtime/v1/chat/completions
Authorization: Bearer bm_live_…
{
"model": "agent:supplier-desk",
"stream": true,
"messages": [
{ "role": "user",
"content": "Which invoices are unmatched?" }
]
}The agent replies in the language it is spoken to in. On app screens, the words that come from your own data are translated on the reader’s own device where the browser supports it, and otherwise by the browser’s own translator. Botminds runs no translation server.
The agent replies in the language of the person’s newest message.
0 characters sent by Botminds to a translation server. A browser’s own translate button uses that browser’s service.
Most enterprise chatbot projects stall on the same questions: whose data the bot can see, what it can do, where people reach it, and whether it holds up at scale.
| Chatbot builder | General AI assistant | Botminds conversational AI | |
|---|---|---|---|
| Answers from | Scripted replies and an FAQ | Whatever the user pastes or connects | The libraries, documents and records the agent was given — millions of documents |
| Who sees what | Everyone sees the same | Depends on each connector | Each person’s read rules, inside the search |
| Can act | Hand-built integrations | Some, with plug-ins | Granted tools, with approvals in the thread on the tools you choose |
| Sources | None | Sometimes | The sources the answer used, to the page |
| Where people reach it | A website widget | Its own app | Every screen, home page, apps, email, Microsoft Teams, Viber and Telegram intake, API |
| Scale | Per bot | Per seat | Stateless replicas that scale out; durable queues; any cloud or region |
| Record | Chat logs | Chat history | Every turn, tool call and approval kept with the run |
More from the platform: the full architecture, and how security works at Botminds.
Conversational AI is software you talk to in your own words and that replies in natural language, keeping track of the conversation. In an enterprise it should also answer from the company’s own data, respect who may see what, and show where each answer came from.
A traditional chatbot follows a script: it recognises phrases someone wrote in advance and returns prepared replies. Conversational AI understands free text and composes its replies. On Botminds the conversation also sits on a full agent, so it can search, cite and act.
Conversational AI is about the dialogue: understanding and replying. Agentic AI is about doing: planning steps, using tools and finishing tasks. Botminds combines them — every conversation runs on an agent with granted tools and the approvals you choose. See the agent harness.
Yes. The chat runtime holds no conversation in memory, so replicas scale out on Kubernetes as conversations grow and any replica takes the next turn. Customer messages queue durably and workers scale with the queue, on Azure, AWS, Google Cloud or on-premises.
Yes. In the app, the agent searches the sources it was given, within what the person asking may read under each collection’s read rules, and shows its sources. Agents reached by email, in Teams or over an API key search what they were given, so you choose what each holds. See agentic RAG.
Yes. With Agent Reach, one app installed once by a Microsoft 365 admin lets people mention an agent in a channel or pick it in a one-to-one chat. Messages from other organisations are refused.
Yes. An admin gives an agent a mailbox of its own — an address created for it, never a person’s. It answers colleagues inside your domain, one thread as one conversation, and answers each message once.
Viber and Telegram connect as channels: customer messages and media become records, open a case with its own reference and receive a confirmation, and the collection’s agents and people work them. Conversations with agents also run in the platform, by email and in Microsoft Teams.
Yes. Every agent is reachable through OpenAI-compatible chat-completions and responses endpoints, with streaming, idempotency keys on the responses endpoint, and project API keys or OAuth client credentials.
The agent replies in the language of the person’s message. On app screens, text that comes from your data is translated on the reader’s own device where the browser supports it, and otherwise by the browser’s own translator. Botminds runs no translation server.
Bring the questions your team asks every day. We’ll show you an agent answering them from your data — in the app, by email and in Teams.