Skip to content
NagentNagent
Log inSign upHire your AI team
Atlas/Sierra
Vendor dossier / Customer experience

Sierra

Customer service agent platform with context, actions, guardrails and optimization.

REVIEWED 29 SEPTEMBER 2026CXNO HANDS-ON BENCHMARK

What it is

Official-source notesCustomer experiencescaling

Sierra promotes multichannel agents, Ghostwriter-assisted agent creation and updates, observability and experiments. Horizon extends its published scope to long-running outbound and inbound revenue journeys; the September Ghostwriter announcement describes proactive team participation in Slack and Teams, with broader rollout planned. [V1] [V2]

Documented means the statement is present in the cited material. Capability effectiveness, customer outcomes and security assurances have not been independently audited here.

Promoted use cases

  • Resolve customer issues across channels
  • Pursue long-running sales and retention outcomes
  • Review and improve agents with a team

CX agents operate where answer quality and action correctness directly affect customers. A response that sounds useful can still be wrong, and a conversation marked resolved can reopen. The comparison should combine customer experience, transactional accuracy, human handoff, operational visibility and the exact commercial definition of an outcome.

Pricing and buying model

Published commercial evidence

Outcome-based quote

Vendor confirms outcome-based pricing; no universal per-outcome rate verified.

Check current commercial source ↗

Budget for implementation, model and tool usage, data, human review and ongoing support. Credit units and outcome definitions differ between vendors. A missing numeric rate is marked unverified rather than replaced with an old third-party estimate.

Collaboration and governance

The site describes visibility into changes and tool actions. Verify approval, test evidence and rollback for generated agent updates.

The relevant unit of control is permission to change an order, account or service record. Inspect who can propose, approve, execute, interrupt and audit that action. Shared seats, shared content and a shared live agent session are different capabilities; require a demonstration of the one your process needs.

Evaluate memory correction, permission revocation and release control for updated instructions. An improvement loop should preserve the original evidence, proposed change, test results and named approver. A safety or security badge alone cannot establish those workflow properties.

Review and customer evidence

No independent review sample was verified in this research pass. Vendor-hosted testimonials are selection-biased customer evidence, not an aggregate rating.

Before relying on a testimonial, confirm the exact product, version, package, workload and baseline. Ask a relevant customer about setup effort, failed cases, ongoing manual work and support after launch. This dossier does not convert customer logos or vendor-hosted awards into independent proof.

Focused feature documentation

Focused documentation check · Sep 2026

Horizon growth scope, Ghostwriter teamwork and release governance

Sierra is no longer accurately described as only a service chatbot. Its July 2026 Horizon announcement describes agents pursuing revenue and CX goals across inbound and outbound interactions over days, weeks or months, with a context engine spanning customer interactions. Claims that the system learns from sales and rejection outcomes, and that customers pay for business outcomes rather than tokens, are Sierra’s own descriptions; no universal per-outcome rate was verified. This makes Sierra a closer growth and shared-context comparator, especially in customer-facing journeys.

Sierra’s Agent Studio page describes journeys, tool-call traces, knowledge-gap analysis, regression simulations and voice simulations. Its August release-governance article describes Agent Checks, required simulation gates, a Reviewer role and line-by-line merge approval, split-traffic releases, immutable snapshots and rollback. These are specific vendor-published release controls; a buyer still needs to verify entitlement, configuration and evidence in its tenant. Distinguish approval of a change to an agent from approval of each customer-impacting runtime action.

On 28 September Sierra announced Ghostwriter as a proactive teammate in Slack and Teams that can draw from team discussion and customer interactions, propose experiments and monitor outcomes. Sierra said broader rollout would begin the following week; do not assert universal availability on 29 September. A head-to-head growth pilot should test a long-running renewal or sales journey, a corrected customer fact, a proposed agent update, reviewer rejection, limited rollout and rollback. Record the human who owns each external action and define a billable outcome for retries, escalations and reopened cases.

Primary sources: Official Horizon announcement ↗ · Official Agent Studio capabilities ↗ · Official release governance ↗ · Official Ghostwriter announcement, 28 Sep 2026 ↗

Published documentation and public illustrations; account behaviour was not independently tested.

Visual source

A screenshot was not captured for this entry. Open the official visual source ↗. The absence of an image does not affect the evidence status of the sourced notes.

Fit, limitations and proof requests

Editorial assessment

Sierra is a direct comparator for governed improvement and customer-facing growth journeys. Its outcome definition, rollout status and operating support should be assessed against an equally scoped Nagent service.

Priority question: What counts as a billable outcome when a customer returns, escalates or receives an incorrect resolution?

The evaluation owner should be the customer-experience and support-operations leads. Use durable, accurate resolutions with appropriate human escalation as the business target. Judge the solution in its own stack role: a cloud runtime, a specialist production tool and a managed AI team can be complementary purchases.

Use-case evaluation plan

Knowledge answer with a verifiable source

Provide a current policy, an obsolete policy and an ambiguous customer question. Require the agent to use the right version, identify uncertainty and avoid inventing exceptions. Ask a human reviewer to verify the answer without reading a long hidden history.

Measure: answer accuracy, source freshness and appropriate escalation.

A bounded customer action

Use a test customer, a low-risk transaction and an explicit action limit. Try a request outside that limit and a case with conflicting identity information. Verify the backend state after execution; a conversational confirmation alone is not evidence that the transaction succeeded.

Measure: correct state changes, blocked unauthorized actions and recoverability.

Learning from a failed resolution

Introduce a repeat contact after an apparently successful interaction. Ask the system to identify the failure, propose a policy or knowledge correction and show the evidence. Require a human owner to approve the change before it affects other customers, then replay similar cases.

Measure: reopen rate, correction quality, regression results and human workload.

Detailed comparison

Read the detailed Nagent vs Sierra guide for operating models, shared context, governance, cost, evidence gaps and a staged pilot.

Nagent vs Sierra

Sources and evidence register

Nagent · Multiplayer AI for growth teamsResearch: 21–29 September 2026 · Public-source analysis, no hands-on benchmark · Sources & method