SAM FROM OPS / GETTING STARTED

Start with one feature.
Give Sam the story.

You don’t need to map your whole system. Pick one AI feature you know well, describe the job and agree what good looks like.

Prepare your feature

Sam is currently in pilot.

This guide helps you prepare and check your first integration. It doesn’t create a Sam account or connect your application. You’ll need pilot access to Sam before sending reports; self-service sign-up isn’t available yet. In the pilot today, each feature’s key records a short description. Checks proposed from it are coming.

A small starting point.

Choose one feature, a test environment and an owner. Have a way to run a successful call and a failed call. Start with observation; grant more authority only when you are ready.

01 / DESCRIBE THE JOB

What should this
feature do?

Write the purpose, not a prompt. Keep customer content, credentials and real conversations out of the description.

YOUR STARTING CONVERSATION WITH SAM

A brief you can take with you.

Fill in the form to create a plain-language starting point. Once proposed checks arrive, Sam will turn it into checks for you to confirm. Today, use it to write the description on your feature’s key.

Feature brief

02 / MAKE THE FIRST CONNECTION

Work through it,
one step at a time.

Use these as your own completion checks. Ticking a box doesn’t configure Sam. Progress lasts only while this page stays open.

0 of 5 steps complete

Agree the checks.Give Sam your feature description when you create its key. Until proposed checks arrive, write down the expectations you would confirm. Add the two reports.Send a start and finish around each AI call, asynchronously, with a shared call identity. Keep raw content out of both payloads. See the integration pattern. Verify success and failure.Run a successful call, a failed call and a reporting failure. Confirm that reports match, missing data is visible and telemetry does not block your application. Review a finding with the owner.In a test environment, introduce a known change such as a duplicate run. Check the observation, expectation, explanation and who receives the finding. Verify the fix before expanding.Resolve the test change and confirm Sam sees recovery in the data. Review messaging and action permissions before connecting more features.

The checklist and brief builder need JavaScript for progress and generation. You can still use the steps above and write down your feature’s name, purpose, expectations, owner and environment.

KNOW WHAT GOOD LOOKS LIKE

Your first win:
a finding you understand.

You can see what changed, why Sam noticed, who owns it and how to tell whether the fix worked.

Try the walkthrough

Start with one feature.Give Sam the story.

A small starting point.

What should thisfeature do?

A brief you can take with you.

Work through it,one step at a time.

Your first win:a finding you understand.

Start with one feature.
Give Sam the story.

What should this
feature do?

Work through it,
one step at a time.

Your first win:
a finding you understand.