Sierra building agent access layer

Sierra is trying to own the control layer between consumer agents and enterprise systems, not just the agent that talks to customers. Its support bots already read help content, look up account data, and take actions like refunds and cancellations inside billing and CRM systems. Personal agents turn that same action layer into a new choke point, where retailers need rules for which outside agents can enter, what data they can see, and which actions they can execute.1 2 3 4

• Sierra started in inbound support, where AI could replace phone trees and low level BPO work at about $1 to $1.50 per resolution, versus roughly $10 to $15 for humans. That gave it the integrations, guardrails, and action taking workflows needed to move into cancellations, refunds, and account changes.2 3
• The expansion into sales and outreach follows the same pattern. Instead of waiting for a customer question, the agent calls a lead, follows up on an insurance claim, chases a payment, or nudges onboarding over days or weeks, then writes the outcome back into Salesforce or another system of record.1 2 4
• This is why the company looks different from classic help desk software. Intercom bundled an agent into an existing inbox and ticketing stack, while Sierra and Decagon have pushed further toward agent first workflows that can sit on top of CRM, billing, and support systems and eventually make those systems feel like back end databases.2 3 4

The next step is a market where every business needs both a customer facing agent and an agent access policy. If Sierra keeps supplying both, it can expand from support budget into sales, operations, and commerce infrastructure, and become the layer that decides how autonomous software is allowed to do business with a company.1 4