Sierra: keep the evidence beside your AI changes

Begin with a request you understand

A customer asks to change a delivery date. Before asking AI to handle it, describe the answer they need: whether the change is possible, what it costs and who can help if it fails. Keep a few made-up examples of both a straightforward request and an awkward one. They give you something concrete to review.

Sierra announced a redesigned Agent Studio on November 2. Agent Studio is its workspace for building AI helpers that talk to customers and carry out tasks. The update brings more of that work into conversations with Ghostwriter, Sierra's existing building assistant.

Read the announcement: Sierra: Agent Studio redesign around Ghostwriter.

Keep the question and the change together

Sierra says teams can investigate customer conversations, change how a helper handles a request and test the change in one conversation. The supporting examples, edits and test results stay together.

Each piece of work has its own session. Proposed edits remain there until reviewed and combined with the shared version. Teams can share a session or copy it to continue from a colleague's work. This redesign brings existing tools together; Ghostwriter itself was introduced earlier this year.

For a business owner, that suggests a useful question for a demonstration: can the person reviewing a change see the customer problem and the evidence for the proposed answer without hunting through separate messages?

Review the answer before customers see it

Sierra's existing release controls include required reviewers, simulated conversations and gradual releases to a portion of customer traffic. The November update brings comparisons and testing into the redesigned workspace. These are ways to check changes, not a guarantee that every answer will be right.

For the delivery-date example, ask the builder to show what happens when a date is unavailable, a record cannot be found or the customer changes their mind. Check that the helper gives an understandable explanation and a way to reach a person. A smooth demonstration of one successful request leaves these questions unanswered.

Check the account details

The announcement does not provide a public price or a plan-by-plan availability list. Existing Sierra customers should confirm access with their account contact. New buyers should ask about subscription and setup costs, connections to existing records, and who will maintain the helper.

Ask to see your particular request handled in a practice version, using information approved for that purpose. Include the person who knows how the work is done today.

A useful exercise for your next build

You can prepare this review without buying new software.

1. Choose one repeated customer request and define a finished, acceptable result.
2. Write three examples: an ordinary request, missing information and a request the helper must pass to a person.
3. For one proposed change, keep the original answer, revised answer and reason together.
4. Ask someone else to check the examples before approving the change.

Make your judgment easier to use

Our perspective is that easier editing makes clear review more valuable. Your knowledge of the customer request helps a builder choose useful tests. Learning to describe an acceptable answer, and knowing when a person should step in, are practical skills to bring to training or a shared build.