Support, customer success and founders

An AI support agent that answers each customer from their own records, with a person in the loop.

Customers write on WhatsApp or Telegram. The agent answers as your support persona from that customer’s own records and nothing else, attaches what they send to the right ticket, and sends a reply after your team approves it, or on its own when it is sure.

Every conversation on the customer's record, with its topic, priority and owner, where your team reads and reviews what the agent wrote.

northwind.segmentstream.app
A support inbox: conversations with topic and priority, an open thread with the customer's message, an internal note and a reply, and the customer's record with assignee, priority, topic and first-reply deadline

Swipe the screen sideways to see all of it.

Support, customer success and founders

AI support agent: what it does

Tell your coding agent who should talk to the agent and what it may do. It writes the personas, the sign-up roles, the review rules and the actions in your repository, and deploys them with the rest of your workspace.

What it does
  • Customers sign up with their first message on WhatsApp or Telegram, or by email in your app, with the role you name.
  • The agent answers as your support persona from that customer’s own orders, contracts, invoices and tickets, and nothing else.
  • Documents, photos and voice messages are read and attached to the right record.
  • Each reply goes out at once, after a person approves it, or after review only when the agent is unsure.
  • Your team reads every conversation and reviews replies in its own app.

What it covers

  • Only the customer’s own records

    A customer’s role reads only their own records: their orders, contracts, invoices and tickets. The check runs on the server for every request, whatever the model is asked.

  • A person reviews what matters

    Choose by role who sends each reply: the agent at once, a person always, or a person only when the agent is unsure. Your team approves, edits or rejects before the customer sees it.

  • A persona and skills by role

    Customers meet your support persona; your team meets the company assistant. Procedures such as refunds are skills only the roles you list can load.

  • Tickets on the customer record →

    Conversations sit on the customer’s record with status, owner and priority, beside their orders and contracts.

  • First contact and limits

    New customers hear once that they are talking to an automated assistant. Limits per customer, per hour and per day keep traffic in proportion.

  • Every turn on record

    Every conversation is kept, and every change the agent made names the customer it acted for.

Built from typed blocks

No new product to buy: the blocks below, written by an agent into your workspace's repository and deployed with one command.

Entitiesontology/
  • client
  • ticket
  • order
  • contract
Actionsontology/
  • ticket.open
  • ticket.reply
  • ticket.assign
  • client.ensureMine
Rolesontology/roles.ts
  • clientsigns up on WhatsApp, Telegram or by email
  • support
  • support_lead
Connectionsconnections/
  • whatsapp
  • telegram
  • gmail
Pipelinespipeline/

None required.

Appapp/
  • Inbox
  • Reply review
  • Clients
Agentagent/
  • Support persona for clients
  • Review of replies to clients
  • Company assistant for the team
One deploy

$ segmentstream deploy

Every block ships together from one git repository your company owns. SegmentStream runs it.

What it replaces
  • Intercom Fin
  • Zendesk AI agents
  • Scripted chatbots
  • A shared WhatsApp phone
How to start

Our engineers set up the support agent on your channels, your customer records and your policies, run it with your team reviewing every reply until its answers match theirs, and hand over the code.

Moving from

Build it with your agent

Build your own from the Company agent blueprint.

The Company agent blueprint gives Claude Code, Codex or Cursor the design, the questions to ask you, the rules that must always hold and their tests. Paste this prompt and your agent builds your own version on SegmentStream, shaped to how your company works.

prompt for your coding agent
Read https://github.com/segmentstream/build-your-own/blob/main/AGENTS.md and follow it.
Build our company agent from the company-agent blueprint.
Have us build it

Enterprise, with our engineers

Our engineers set up the support agent on your channels, your customer records and your policies, run it with your team reviewing every reply until its answers match theirs, and hand over the code.

Build it yourself

Self-serve, with your own agent

Tell your coding agent who should talk to the agent and what it may do. It writes the personas, the sign-up roles, the review rules and the actions in your repository, and deploys them with the rest of your workspace.

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

Related solutions

Questions

Can I build my own AI customer support agent?

Yes. Connect your WhatsApp number or Telegram bot, open sign-up for customers with a role scoped to their own records, and write the support persona. The agent answers from those records and works through the actions you allow.

Can a customer see someone else’s data?

No. A customer holds only the role you name for sign-up, and that role reads only their own records. Every request is checked on the server, so no prompt can make the agent read another customer’s data.

Can a person approve replies before customers see them?

Yes. Set review for the client role to always, or to when the agent is unsure. A reply waiting for review reaches the customer only after a person approves or edits it.

How is it different from a helpdesk chatbot?

It works on your own records and actions rather than a help-centre index, with the same roles as your team, and its code lives in your repository. Changing a policy is a change to a file you review.

What does an AI support agent cost?

There is no seat, per-conversation or per-resolution fee. The agent’s work is billed in SSU under Agent, and the models it calls at each provider’s list price, with no markup.

Enterprise pilot

Rather have it built for you? Start a pilot.

Our engineers set up the support agent on your channels, your customer records and your policies, run it with your team reviewing every reply until its answers match theirs, and hand over the code.

  • 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.