Company agent · agent/

A company agent in every team chat, working as the person who asks.

One agent per workspace that knows your company’s records and rules. It works for your team in Slack, Teams, WhatsApp, Telegram and email and for your customers on WhatsApp, Telegram and your website, acts with the permissions of whoever it talks to, lets a person review what matters, and runs routine work on a schedule through workflows.

The company agent as its agent/ folder declares it: the models it uses, the deployment it runs and every step a message takes, from the channel to the reply.

segmentstream.com
The console's agent page: live on Telegram, its chat model and the model for preview deployments, the deployment it runs and its Agent SDK version, then how a message is handled, from the channel it arrives on, with voice transcribed to text and images described for the chat model, to who may talk
Slack, Teams, WhatsApp, Telegram and email

Ask in a chat. Get an answer with your own permissions.

  • It knows who is asking

    Ada connects once. Every answer after that is read with her roles, and every change is recorded as hers.

  • It asks before it acts

    Moving a deal or adding a task runs the same actions the app runs, with the same rules inside them. Before a change that matters, it shows the change and waits for her to confirm.

  • It stops where the role stops

    Revenue needs the accountant role, which Ada does not hold, so the agent says so instead of answering. No prompt can talk it past a permission.

In every team chat and inbox

The company agent works in the channels your team already uses: Slack, Microsoft Teams, WhatsApp, Telegram and email. Every workspace agent also has its own email inbox, so customers and suppliers can write to it directly.

For customers too

Open sign-up on WhatsApp, Telegram or by email, and customers talk to the same agent with a role you name, scoped to their own records.

On your website

Visitors of your website chat with the agent without an account, as guests with only the permissions you give them, a bot check and a daily cap on model spend.

A persona for each audience

Customers meet your sales or support persona; your team meets the company assistant. Skills for one procedure load only for the roles you list.

Replies reviewed when it matters

Choose by role who sends each reply: the agent at once, a person always, or a person only when the agent is unsure.

Inside your apps

Members talk to the agent inside your own apps, signed in as themselves, with nothing to pair.

Acts as the person asking

Each person connects once. From then on the agent acts as that member, with the roles they hold at that moment, and the history of every change names them.

Asks before it acts

Before it changes anything that matters, the agent shows what it will do and waits: confirm, edit or cancel. When something is unclear, it asks.

Reads what your team sends

It reads documents, scans, spreadsheets and voice messages, works with files in a private sandbox, and attaches what it produces to the right record.

Works on its own, on a schedule

Workflows start the agent on a schedule or when something happens: check yesterday’s bank transactions, find the leads nobody followed up, sort the inbox. It reports back in the team’s chat.

Fits into group conversations

In a group, it answers when someone addresses it or asks for something it does, and keeps the rest as context. It can post updates to other chats and remembers past conversations.

A model per role

Pick a model per role, for example a stronger one for finance. Every major model is available, with no API key to manage.

Stops when access stops

Deactivate a member, or let them disconnect in the app, and the agent stops acting for them at once.

In code

agent/
<!-- agent/agent/instructions.md -->You are Acme's operations agent.- Answer from the company's records, and say which record you used.- Before you change a deal, an invoice or a contract, show the change  and wait for the person to confirm it.- If a document is attached, read it and file it on the right record.// agent/segmentstream.json{  "sandbox": true,  "confirmations": { "mode": "deferred" },  "groups": { "mode": "smart" }}
Agent SDK reference →

Use it, build on it, or have it built

Use it

Add the agent to your team’s chat, connect once, and ask.

Build it with your agent

Your coding agent writes the agent’s instructions and channels in agent/ and deploys; the agent starts answering.

Have our engineers build it

Our engineers set up the agent, its channels and its first workflows with you during a pilot.

Replaces Chatbots with a shared service account, One agent per SaaS tool and Bot tokens in code.

Works with

Solutions built with it

Read more

Enterprise pilot

Start a pilot.

Want company agent set up for you? Our forward-deployed engineers build it with you in your workspace, as code you own.

  • One solution, on your data, in your own workspace
  • First version live in two weeks
  • Parity proven before anything is switched off
  • Fixed scope and price, credited to your contract if you continue

Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.

How the pilot works

Goes to our founder’s inbox. No sales queue, no newsletter.

Build your company’s own software. Let agents run it.

$ segmentstream workspace create acme --region eu --subdomain acme

▸ Created workspace acme · database, warehouse and a private git repository

$ segmentstream workspace WORKSPACE-ID clone acme && cd acme

▸ your coding agent builds what your team asked for and runs the checks

$ git add -A && git commit -m "First version"

$ segmentstream deploy

▸ app, company agent, API and MCP tools live for your invited members

Start a pilot

Our engineers build the first version on your data in two weeks, at a fixed price.

Or build it yourself with your coding agent:

curl -fsSL https://segmentstream.com/install.sh | sh

We’ll email you product updates, tips and onboarding help. Unsubscribe anytime.