Quickstart

Run your first in-product AI interview from the dashboard. Managed AI uses prepaid balance at $0.25 per recorded minute with no per-interview minimum; new accounts include a small starting allowance.

If you want an agent to perform setup, use the focused MCP setup or CLI setup instead.

1. Create a project

Sign in to the dashboard, then create a project for the product or product area you want to research.

You can add an OpenAI API key in Project Settings. Keys are encrypted at rest and project-scoped. BYOK costs $0.15/min; OpenAI bills inference directly. Neither mode has a per-interview minimum.

2. Create a study

Open Studies. Choose to observe use, test a feature, or have an open conversation. Add goals and a short sequence:

  • talk for conversation and follow-up questions
  • speak for scripted instructions and transitions
  • observe for silent capture while the participant completes a task

Start small and test the interview yourself. The Study Design Guide covers the design decisions and a complete example.

3. Add participant disclosure

Before inviting users, show your identity, purpose, voluntariness, and privacy link in the host product. The widget adds its recording notice and Allow access action. See Participant Consent.

Use an Intake only for qualification questions.

4. Embed the widget

Open any Study's Launch setup and copy the Project embed into your product. It is the same code for every Study in the Project:

<script
  async
  src="https://usertold.ai/v1/widget.js"
  data-project-key="ut_pub_YOUR_KEY"
></script>

Install this Project script once across the site. Visibility selects one active Study for the current pathname and widget language; that Study's Invitation defines the launcher. One Project can contain many active Studies.

Without Visibility limits, a Study is eligible on all pages and all supported widget languages. Configure matching and resolve conflicts in Widget Integration.

The loader waits for the host page to finish loading before fetching the widget. When a visitor opens it, they begin the study directly or complete its linked Intake first, without leaving your product.

5. Test one complete interview

Visit the embedded product as a participant and confirm:

  1. The widget opens the intended study, or its linked Intake when qualification is enabled.
  2. For an Intake-backed study, a qualifying response enters the intended study.
  3. The interview reaches its final segment and completes.
  4. The interview appears in Interviews with its recording, transcript, or processing state.
  5. Evidence appears after processing, or the result clearly says that no evidence was found.

If the widget or interview does not behave as expected, use Widget Integration and Study Runtime to diagnose that path.

6. Review the result

Open the interview and inspect the source recording, transcript, timestamps, and page context. Related evidence is grouped into draft Work in the backlog, not automatic delivery instructions.

Before pushing work to Linear or GitHub:

  1. Verify the linked source context.
  2. Confirm the grouping and current product area.
  3. Move the Work to ready only when it represents a problem worth shipping.

When a linked Linear issue completes, UserTold can resolve the current evidence and continue watching future interviews for possible recurrence.

Continue