Quickstart

Run your first in-product AI interview. Verified new accounts receive a small starting balance; interviews need a positive one.

1. Sign in

Signing up at usertold.ai creates your first Project and a draft First user interview Study: what the participant tried to accomplish, what was difficult, and what they expected instead.

Creating a Project, saving or editing a draft Study, and configuring its Invitation do not incur interview charges. You can prepare and review the setup before running an interview. Recorded interviews are billed under the current pricing; UserTold does not supply or recruit participants.

2. Put the interview on your site

The Project home and the Studies page open on the first-interview card, whose steps are Install · Verify · Publish. Copy prompt for your agent hands your coding agent a Project-scoped instruction: fetch the snippet with projects.get_widget_setup, add it to the shared layout, verify a public page with projects.verify_widget_installation, fix what the report flags, propose changes first, and leave publishing to you.

By hand has the same snippet under Copy snippet:

<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; it is the same code for every Study in the Project. Verify page then checks a deployed page's HTML, not the running widget.

3. Publish

Publish puts the Invitation on your verified site; it invites nobody and charges nothing. Only an interview that completes processing with recorded duration and transcript creates a charge. An unfinished Study step holds Publish. Tailor the interview with your agent first reveals an optional prompt: your agent revises the Study for your goal and shows you the draft. See MCP setup, CLI setup, and the Study Design Guide.

4. Review participant disclosure

Keep your identity, purpose, voluntariness, and required privacy information in the host product or invitation. UserTold requires no separate privacy-policy URL or setup step. The widget supplies its recording notice, privacy link, and Allow recording and start action. See Participant Consent.

5. Understand placement

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 limits, the starter is eligible everywhere. See Widget Integration for matching and conflicts.

6. Test one complete Interview

Visit the embedded product as a participant and confirm:

1. The widget opens First user interview.
2. The Interview completes.
3. Interviews shows the source recording, transcript, timeline, capture limitations, and processing state.
4. Source-linked Evidence appears after processing, or the result says none was found.

Use Study Runtime to diagnose failures.

7. Review the result

Inspect the Interview source before its analysis. Evidence preserves a source-linked moment; a Finding synthesizes one or more Evidence cards. Check a draft Finding's sources, then choose Review, which changes UserTold only; Send to Linear and the GitHub handoff are separate.

Choose a recipe or add product context.

Continue

• Core Concepts
• Glossary
• Widget Integration
• API Integration Guide