AI specialists for the work around your product.

Support, sales calls, compliance, finance and hiring. One's bots answer your phone line, work in your team's chat apps and keep each client or function in its own space. You decide what needs your approval.

On the Business plan · Bring your own API keys

One
Quayside
Quayside is fictional. The product in the laptop is real.

Your phone line, answered. Every call written down.

A voice agent follows the call flow you design, in the voice you choose. You test it with chat and audio calls before it gets a number, and after each call it writes the details you ask for into a table your crew works from.

Tested before it's live

Run chat and audio tests on each branch of the flow before you assign a number.

Recording off by default

Calls aren't recorded until your deployment's policy allows it.

A do-not-call list

Numbers on it are refused, whoever asks for the call.

VeraPhone line · +1 (555) 010-4410
Ended · 3:12
Dana · Pellam Couriers+1 (555) 014-7732
  1. Greet
  2. Find the account
  3. Fix or book
  4. Wrap up
  1. VeraQuayside support, this is Vera, the AI assistant. How can I help?
  2. DanaHi, it's Dana at Pellam Couriers. Six of our vans stopped syncing mileage last night.
  3. VeraSorry about that, Dana. I have Pellam's account. Are those vans on app version 2.8?
  4. DanaI think so. And while I have you, we want to add 40 vans.
  5. VeraRestarting the app on each van fixes the sync. Adding vans changes your contract, so I'll book Ines to call you. Does Thursday at ten work?
  6. DanaThursday at ten is fine.
  7. VeraBooked for Thursday at ten. Anything else today?
  8. DanaThat's all, thanks.
Written to Callbacks
Caller
Dana, Pellam Couriers
Solved on the call
Mileage sync: restart the app
Reason
Add 40 vans to the contract
Callback
Thursday 10:00 with Ines

A rule you confirmed hands each new callback to Cass, who prepares the call.

Fictional company, callers and numbers.

Your bots, in your team's chat apps.

Link a bot to a supported chat app and message it there. Add it to a group chat, and everyone with a linked bot is asked first. Only bots whose owners say yes take part.

Asked first

No bot joins a group until its owner replies YES. LEAVE takes it out again.

Signed with a name

Posts read as that person's agent, so everyone knows whose bot said what.

Private stays private

In a group, a bot works without its owner's memory and is told never to share one-to-one chats.

It listens to its people

In a group, bots read messages from people whose own bot has joined.

Quayside
Group chatsDirect messages
# fleet-ops4 people · One line
  1. Tomás

    Pellam wants their 40 new vans live by Monday. Can we do that?

  2. Ines

    Checking with my agent. Can Pellam's new vans go live on Monday?

  3. One lineApp

    Ines's agent: Yes, if the contract change is signed by Friday. Ines calls Dana on Thursday at ten, and the order form is ready for that call.

  4. Tomás

    Perfect. I'll tell Pellam's ops lead.

Fictional team and conversation.

A space for each client, team or function.

Each space has its own crew, Library, memory, connected accounts, credentials, phone numbers and approval rules. A bot works only inside the space it belongs to.

Crew

  • VeraPhone lineMemory · SharedComputer · Team
  • BeaCustomer supportMemory · SharedComputer · Team
  • CassSalesMemory · SharedComputer · Team
  • FayeMarketing & contentMemory · SharedComputer · Team
  • QuillComplianceMemory · SharedComputer · Team
  • JudeRecruitingMemory · IsolatedComputer · Team

Library

  • help.quayside.example
  • Service terms.pdf
  • Rate card.xlsx
  • Fleet customers.csv
  • Security policies.md

Connected

  • Support line · +1 (555) 010-4410
  • fleet-ops group chat
  • Help desk
  • CRM
  • Mail

Rules

  • Ask before sending external email

Bots here can't see what's in Finance or Harlow Freight, and theirs can't see in here.

Your model keys are yours in every space; each space chooses its own models.

Two to six bots, one conversation.

Put the bots a job needs into a group. Each does its part in the same thread and hands the next stage on, so every step is in one place.

GroupRoute planner 3.0 launch
4 of 6
  1. Ines

    Route planner 3.0 ships Thursday. Get us ready.

  2. Faye

    The announcement, the customer email and three social posts are drafted from the release notes.

    route-planner-3-announcement.md
  3. Faye handed off to Bea · Update the help center for 3.0
  4. Bea

    Three help articles are updated, with a saved reply for customers who can't find their old routes.

  5. Bea handed off to Vera · Add 3.0 to the support call flow
  6. Vera

    The support flow now answers 3.0 questions, and its chat test passed 6 of 6. It goes live when you publish it.

  7. Vera handed off to Cass · Tell the open deals
  8. Cass

    A short note to 14 open deals is ready for Thursday at 9:00. Emails wait for your OK, as the space rule asks.

Fictional launch and crew.

The whole operation, on one screen.

Every space has an Architect that keeps it organised. It proposes changes to the crew and waits for you to apply them. Only small edits you ask for apply at once, and those can be undone.

One
Quayside
Quayside is fictional. The Architect in the laptop is real.
How spaces and the Architect work

You decide what needs your approval.

Bots act on their own until you add a check. Ask before external email, before purchases, or before a particular tool or connector. Placing a phone call and publishing a phone agent always ask until you say otherwise.

Tools per bot

Each bot holds only the connections you give it.

Its computer, its permissions

Running commands, changing files, opening apps, installing software, browsing: allow each one per bot, or have the bot ask.

Credentials sealed

Keys are kept encrypted in the secret store. Bots use them without seeing them.

Changes on the record

Crew changes wait for your OK, except small edits you ask for. History keeps every one.

Action confirmations

Next up at QuaysideFictional

  1. CassSend the proposal to Ashby VansMailAsks youYour email rule
  2. VeraCall Ashby Vans backPhone lineAsks youCalls ask by default
  3. JudeBuy a featured job listingJobs boardRunsNo rule applies
  4. QuillTurn off a cloud log settingCloud consoleRunsNo rule applies
  5. FayePublish the 3.0 postWebsiteRunsNo rule applies

Each job, in detail.

The crew's work for each function has a page of its own.

How your business will use it.

Set it up once, then work through the phone line and chat apps you already have.

Give each client or function a space

Start with the part of the business that takes the most time. The Architect proposes its crew, and nothing is set up until you apply it.

Connect the places work comes in

Link bots to your chat apps, connect your tools, and give the phone agent a number when its test calls sound right.

Set your rules, then watch Pulse

Choose what needs your approval. Pulse shows what the crew did and what's waiting for you.

Models and the Business plan

Your company's keys. Your choice of provider.

Connect the providers your company already has agreements with, or an endpoint you run. Each provider bills its usage to you directly.

Fast
Default
Smart

Choose another model for a tier.

Bots can use a tier instead of a model name. Point a tier at another model and every bot on it follows, with nothing rebuilt.

Arranged with our team.

  • Unlimited voice-agent usage, voice and LLM
  • 2 calls at a time
  • 10× Creator workspace resources
  • Semi-private compute
  • Custom features included
  • Priority support
  • 10,000 included credits

Carrier and phone-number charges are separate.

What teams ask us.

Can teammates sign in to the same workspace?

Not in this version. Each account belongs to one person, with its own spaces and crew. Teammates who use One can bring their own bots into your group chats and connect them to yours, with approval.

Which chat apps work?

Slack, WhatsApp, Telegram, Lark, and iMessage or SMS, wherever your deployment has them set up. Group chats work in Slack and in iMessage or SMS; the others are one-to-one.

Can the phone agent call customers?

Yes, once you publish an outbound call type and turn on outbound calling. Each call asks you first until you always allow it, and numbers on your do-not-call list are refused.

Can we keep a client's work apart from ours?

Yes. Give the client a space. Its crew, Library, memory, connected accounts and rules stay in that space, and bots elsewhere can't see them.

Can One connect to our own systems?

Yes. Each space can add MCP servers over HTTPS, OpenAPI tools and, where your deployment offers them, connected apps. A webhook can start a bot's work when something happens in your systems. Where there's nothing to connect to, a bot can build an internal tool and give you a working preview. Connectors

What does Business cost?

Business is arranged with our team, and its price is on the pricing page. Your model providers bill their usage separately, and carrier and number charges are confirmed when calling is set up. Pricing