Sierra

What is Sierra?

Sierra is a platform for conversational AI agents that take actions on behalf of a brand. Where many chatbots answer a question and hand off, a Sierra agent connects to your order system, returns flow, or account records and finishes the task the customer asked for. A shopper who wants to return an item can have the agent process that return in the conversation, and a customer who needs to change an order can have the agent update it.

Sierra makes the product. The company was founded in 2023 by Bret Taylor and Clay Bavor, and it focuses on agents built around a brand's own systems and voice. Each agent is defined once and runs across channels, so the same logic answers on chat and on the phone.

The audience is brands with a high volume of customer requests that involve a task, not a lookup. Retail, subscription, and consumer services fit the model, because those queues fill with returns, order changes, cancellations, and account updates that an action-taking agent can own.

Key features

Sierra centers on a set of capabilities that let an agent complete work rather than stop at an answer:

• ▸Action-taking agents: agents connect to your backend systems and finish tasks such as processing returns, updating orders, and changing subscriptions inside the conversation.
• ▸Voice and chat: one agent definition runs across phone and chat, so customers get the same behavior wherever they reach out.
• ▸Guardrails: policy controls keep an agent inside the topics, tone, and rules you set, so it stays on brand and defers where you want a human.
• ▸Enterprise controls: security review, access management, and compliance features fit brands with governance requirements.
• ▸Backend integrations: agents reach order systems, CRMs, and internal tools to read and write the data a task needs.
• ▸Outcome tracking: reporting shows what agents resolve, so you can measure completed tasks against goals.

The action piece is what sets Sierra apart. Because an agent writes to your systems and does not read from a help center alone, it closes the loop on a request. That capability depends on integration: the agent can complete a return only when it connects to the system that handles returns, so setup involves wiring the agent to your backend.

How well does it work?

Sierra performs well on task-heavy queues where the goal is to finish a request, not answer a question. For brands that connect the agent to their order and returns systems, it can own the common actions end to end, which cuts the load on human teams and gives customers a resolution in one conversation. Voice and chat coverage from a single definition keeps behavior consistent across channels.

The limits track the model. An action-taking agent is only as capable as its integrations, so a task the agent cannot reach in your backend becomes a task it cannot complete. Standing up those connections takes engineering effort, and complex or account-specific requests still route to a person. Brands that invest in clean integrations and clear guardrails see the strongest results.

A practical way to raise what a Sierra agent resolves is to map the top tasks in your queue first, then connect the agent to the systems those tasks touch. Coverage of your highest-volume actions drives the return.

Sierra pricing

Sierra uses custom, outcome-based pricing. There is no public rate card. Instead of charging per seat or per message, Sierra ties cost to outcomes, so you pay when an agent resolves a case or completes a task. The specific rate is scoped during an engagement with the Sierra team.

Because pricing is custom, the tiers below describe how the engagement is structured rather than fixed prices:

The model favors brands with high volumes of repeatable tasks, since each resolved case ties cost to value. Because there is no list price, budget for a sales conversation and ask how outcomes are counted, what a resolution means for your use case, and how integration work is scoped, so you can compare the total against seat-based tools.

Who should use Sierra?

Sierra fits brands that want agents to complete tasks and have the systems for an agent to act on. It suits these groups in particular:

• ▸Retail and ecommerce brands with heavy returns, order change, and cancellation volume that an agent can own end to end.
• ▸Subscription and consumer service companies where account updates and plan changes fill the support queue.
• ▸Brands that field customers on both phone and chat and want one agent covering each channel.
• ▸Enterprises with security and compliance needs that require guardrails and access controls around any AI agent.

Sierra is a weaker match for small teams with low volume, or for support work that is informational and needs no action, where a lighter answer-focused tool would cover the job with less integration effort.

Alternatives and how it compares

Sierra competes with a field of AI support agents. The right comparison depends on your stack and how much action-taking you need.

• ▸Intercom Fin: an AI support agent that resolves conversations across chat, email, and social and prices per resolution, with a tight bond to the Intercom inbox.
• ▸Ada: an automation-first support platform that resolves conversations across channels and suits larger support operations.
• ▸Decagon: a customer support agent platform aimed at enterprises that want AI to handle high-volume queues.

Sierra's edge is its focus on agents that take actions across voice and chat, backed by guardrails and enterprise controls. If your queue is full of tasks that need a write to your systems, Sierra is built for that job. If most of your volume is answering questions from documented content, an answer-focused agent may cover the work with less integration effort, so weigh the task mix alongside the price.

Limitations and getting started

Be honest about the trade-offs before you commit. Sierra's value rides on integrations, so an agent can complete only the tasks it can reach in your backend, and standing up those connections takes engineering effort. The custom pricing means no public rate to compare, and the product aims at larger brands, so small teams may find it heavy for their volume.

Getting started follows a clear path:

1. 1Map the top tasks in your queue, such as returns, order changes, and cancellations, and note which systems each one touches.
2. 2Scope the engagement with Sierra, including how outcomes are counted and what a resolution means for your use case.
3. 3Connect the agent to the backend systems the priority tasks need, so it can read and write the data to finish them.
4. 4Set guardrails for tone, topics, and the cases you want a human to own, then launch on a subset before a full rollout.
5. 5Review resolved tasks and handoffs each week, then widen coverage as the agent earns trust.

A staged rollout keeps risk low: start with one high-volume task and one channel, confirm the agent completes it as intended, then add tasks and channels as your numbers hold up. Because pricing tracks outcomes, the early weeks tie spend to the cases the agent resolves.