> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sessions

> Read your agent's buyer conversations, the recorded commercial context, and the proposal document when one was sent.

## What a Session is

When a buyer asks your storefront for products or a proposal, your storefront
agent answers on your behalf. A **Session** keeps that conversation, including
requests your agent turned down because nothing matched. Open **Sessions** in
your seller workspace to see one row per conversation, newest first.

Open a Session to see buyer and seller turns in their recorded order. Where the
source recorded it, a turn identifies the person or agent who sent it and how it
arrived. A missing detail stays blank rather than being guessed.

For storefront-agent exchanges, the Session shows:

* **What the buyer asked for.** The recorded brief, advertiser or brand,
  channels, countries, flight dates, budget, and creative formats.
* **What your agent answered.** The opening line, products, outcome
  (**Pitched**, **Counter-pitched**, **Passed**, or **Asked for more
  information**), bundles, and lessons that shaped the answer. A recorded pass
  reason is shown when available.
* **The proposal document.** When a proposal was recorded as a document, open
  it from the response to see the immutable proposal the buyer received. It is
  built from the recorded terms, not regenerated later.

Long briefs are shortened to their first 1,200 characters, and each list shows
up to 12 items. The full record remains with the conversation.

## Open the right Sessions

Sign in to the Seller Account that owns the storefront. If you manage more than
one storefront, open **Sessions** from the one you want to review. Your
assistant can tell you which storefront is open and take you to that
storefront's Sessions Page. What you see depends on your current access to that
seller account.

## Why this response

Under an answer, **Why this response** shows the commercial facts recorded with
it. When recorded, this includes the selling approach, offered price against
the target, floor, and ceiling, and the capacity available at the time. It also
shows applied buyer terms, the seller win rate and recommended approach, and
the recorded rule behind a pitch, counter-pitch, or pass. Capacity is **Unknown**
when the source could not resolve it.

This is a record of the facts used for the answer, not the agent's private
reasoning or a new explanation made later. It is visible only to your seller
team.

## Follow one opportunity

When requests carry the same recorded opportunity for the same buyer and seller,
they appear in one Session. This keeps an initial request and later refinements
together without using the buyer's written brief to join them. Requests without
a recorded opportunity remain separate, and the same opportunity from another
buyer or seller is a different Session.

## Follow the buying stage

Each new request and response shows a recorded stage in the Session and in the
Sessions list. **Exploring** means the structured request included no budget,
format, or flight. **Specific request** means it included some of those facts.
**Ready to buy** means it included all three. A refinement request reads
**Refine**, and **Booked** appears after a recorded media-buy forwarding or
delivery report.

The stage comes from structured request fields, refine mode, and recorded
commercial outcomes. It never guesses from the buyer's written brief. Sessions
recorded before stages were added keep their existing history and do not show a
stage.

## Who can see what

A Session is your record of your own agent's work. Your team can read it. The
buyer cannot read your side of it.

* Buyers never see your private notes, lessons, commercial facts, or anything
  your storefront exchanged with your inventory sources to fulfil an order.
* Where buyer access to Sessions is switched on, a buyer sees only what passed
  between them and your storefront: their request and your agent's answer.
* Another seller can never see your Sessions.

## Leave a private note

Under an answer your agent gave, you can write a **private note**: what you
liked, what you would have done differently, or what the agent should know next
time. For example: "For stationery brands, lead with the lifestyle video
package."

A note is only for you and your team. It is never sent to the buyer and it does
not change what your agent does on its own. Turn it into a lesson if you want
the agent to act on it next time.

## Teach your agent from a note

If your storefront is in the lessons pilot, a saved note shows **Teach this**.
It turns your note into a proposed [lesson](/v3/lessons): short guidance, in
your own words, that your agent follows on future matching briefs after an
administrator approves it.

## Open Sessions from any assistant

Sessions opens the same way in Murph, Claude, and ChatGPT. In Murph, **Teach
this** drafts the lesson for you. In other assistants, Teach this tells the
assistant which note you chose, and you ask it to draft the lesson in your own
words.

## If an answer was wrong

An answer from your agent is a proposal, not a booking. Media buys wait for
your approval unless you chose automatic approval; manual approval is the
default.

* **Correct it for next time.** Leave a note and, if your storefront is in the
  lessons pilot, teach a lesson from it.
* **Stop new business while you sort it out.** Pause your storefront. Buyers
  stop seeing your products and cannot place new buys, while campaigns already
  running keep delivering. Unpause when you are ready.
* **Notice it sooner.** Turn on [Session alerts](/v3/session-alerts) to hear
  when your agent passes on a buyer request, and to get a daily summary of the
  requests it answered. Alerts don't cover every new conversation, so check
  Sessions regularly too.

## Availability

Sessions for storefront conversations are being rolled out to sellers in
stages. If you do not see conversations yet, your storefront has not been
switched on. Teach this and lessons are part of a staff-enabled pilot.

## Related

<CardGroup cols={2}>
  <Card title="Lessons" href="/v3/lessons" icon="graduation-cap">
    Turn your notes into guidance your agent follows
  </Card>

  <Card title="Session timeline (API)" href="/v2/setup/v3/session-timeline" icon="code">
    Read Sessions and save notes from your own tools
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.