It knows when to stay quiet
A pause, a glance away, or a change in attention is context, not an automatic interruption. Its role decides whether the moment matters.
For product trials, onboarding, and quickstarts
Sit with everyone
who tries your product
Give Presence your docs and a role. It notices when someone gets stuck, helps at the right moment, and leaves behind what happened.
The job
The call your best prospects get.
For everyone
The useful part of a founder-led trial is not the demo. It is noticing the moment someone stops making progress, helping without taking over, and learning what the product made difficult.
It stays present while it works
Presence can search your docs or use a tool without disappearing from the conversation. The person can keep talking and interrupt it.
The useful outcome survives the call
When the Session ends, a durable summary can record where they got stuck, what Presence helped with, and what it left behind.
After the Session
The conversation ends.
The learning does not
Choose the summary your product needs. Presence retains it as a Session artifact, alongside any authorized transcript or recording manifest. Read the durable result through GET /v1/sessions/{session_id}/outputs.
Give the Presence a strict summary tool to post this body directly to an endpoint you choose. Retain the same outcome as an artifact, and it also remains available through /outputs. The schema belongs to the published Presence, so a support trial, a quickstart, and a research interview do not have to produce the same report.
SESSION-SUMMARY · EXAMPLE BODYAuthored for this product trial
{
"where_they_got_stuck": [
{
"area": "Clerk quickstart",
"signal": "Paused after a 500 error"
}
],
"what_it_helped_with": [
{
"issue": "Dashboard route was excluded",
"resolution": "Updated the middleware matcher"
}
],
"what_it_left_behind": [
{
"kind": "artifact",
"title": "Working middleware rule"
}
]
}One real run
He stopped.
It checked in
A developer testing Clerk auth hit a 500 and hesitated. Presence had been told only to check in when he seemed stuck. It later inspected one shared-window frame and identified the excluded route.
The check-in was unprompted. The screen read was not. The transcript includes complete timing, classifier output, and the disclosed edit.
Privacy boundary
It sees enough to help.
Not everything forever
The participant grants camera access like a video call. Continuous video does not reach the reasoning model. When the task calls for a look, Presence receives a frame; it is not retained in later conversation history.
Recording and durable media remain off unless the Session has the required authority and participant consent.
Read security and privacyTwo ways to start