Sierra Horizon Makes Long-Running Agents Look Like State Machines

Sierra Horizon shows that a long-running customer agent should be a state machine with signals, playbooks, suppression rules, and terminal outcomes, not a long chat.

1 min1 source

In one minute

  • Sierra Horizon shows that a long-running customer agent should be a state machine with signals, playbooks, suppression rules, and terminal outcomes, not a long chat.
  • The record is connected to 0 topics: .
  • 1 public source carries the evidence boundary.

Source ledger

Publishable sources attached to this record.

1 public source
#SourceRolePublic status
1sierra.aisourceprimary receiptsource_urls

Sierra Horizon is useful as a more mature form of long-running agent. It is not a “chat that lasts for weeks”, but a state machine around the customer journey.

The agent works with signals, playbooks, suppression rules, and a measurable terminal state. It can move a customer toward a mortgage, renewal, or sale through calls, email, messages, and internal systems. The important detail: payment is tied to the outcome.

This kind of agent requires a different operating model. It needs states, prohibitions, events, escalation routes, measurable outcomes, and protection against unnecessary customer touches.

Editorial read: a long-running agent becomes a product only when it has a terminal state and a business outcome, not merely a long message history.