Onboarding feedback

We want the path from opening Sess to your first typed result to be short and obvious. These pages run no analytics, cookies or tracking scripts, so we only learn what you choose to tell us.

The path we measure

Time to first typed result is the time from opening the product page to reading the first typed result in quickstart step 3. The milestones along the way:

1. Product page opened.
2. Quickstart opened.
3. Trial Session created (201 from POST /v1/trial/sessions).
4. Answered as the person on the human page.
5. First typed result read ("status": "responded").
6. Receipt verified (step 4).
7. Three rounds completed and Events read with an API key (quickstart step 5). Draft — lands with P1 increment 2
8. Signed webhook received and verified with an API key (quickstart step 6). Draft — lands with P1 increment 2
9. Account created and an API key issued. Draft — lands with P1 increment 2

Feedback template

Copy this, fill in what applies, and send it to us. Times can be approximate.

Sess onboarding notes
Date (UTC):
Product page opened at:
Quickstart opened at:
Trial created at:
Answered as the person at:
First typed result read at:
Receipt verified at:
Three rounds completed at (API key only):

Where I hesitated or was confused (page and section):
Errors I saw (status, code and request_id only):
Help I needed, and from whom:
What would have stopped me from using Sess:
Anything else:

Never include an owner key, an API key, a trial management credential, a human link or the content of a Session. Session IDs (ses_…) and request_id values are fine.

Guided onboarding sessions

Sometimes the Sess team watches a developer who has never used Sess follow these pages, with their permission. The facilitator records the same template, plus:

• The developer starts from the product page and uses only the public pages; the facilitator gives no hints unless asked.
• Every request for help is noted with the time, the page and what was unclear.
• The clock stops at the first typed result; later milestones are timed separately.
• Nothing is recorded from the developer's screen beyond the template fields: no credentials, links or Session content.