Product documentation

Last updated: March 24, 2026

Public overview of how Tirro supports structured voice interviews, from study setup through scheduling, live sessions, and reviewing results. This page is written for a general audience and is updated as the product evolves.

What Tirro is for

Tirro helps organizations run consistent, voice-led research interviews at scale. Teams define what they want to learn, invite participants, hold natural conversations guided by an automated interviewer, then review transcripts, recordings, and rolled-up insights across many conversations.

These materials summarize how the experience is organized; they are not a substitute for your own study design, ethics review, or legal advice where those apply.

Who uses Tirro

  • Research and project teams create studies, shape the interview flow, schedule sessions, and analyze outcomes.
  • Participants join with a link you send them. They do not need an account in the main product.
  • Supervisors, when you enable it, can follow a dedicated link to observe an in-progress session, subject to the access rules your organization sets.
  • Platform administrators manage accounts and cross-study operations for your organization.

User guide: research teams (high level)

  1. Set up a study. Create a project, add goals and background materials, and draft the interview guide—the topics and questions you want covered, in order, with notes on how deep or structured answers should be.
  2. Refine how the interviewer runs the session. Align the automated interviewer's script and behavior with your guide so sessions stay on topic and on time.
  3. Schedule participants. Add participant details, choose timing and time zones, and optionally send reminders. You can require joining in a specific window or allow more flexible join times, depending on your study rules.
  4. Share links. Send each participant their personal join link. Provide a supervisor link only to people who should observe that session.
  5. Review after each call. Open the transcript and recording, check how answers map to your questions, and use project-level summaries to see patterns across respondents.

User guide: participants

  • Use the link from your invitation; follow any on-screen setup (for example instructions or language).
  • Join during the window the study defines, unless the host told you otherwise.
  • During the session, speak naturally. You will see cues that the conversation is live and when it has finished.
  • You may be asked for brief feedback or to report if something went wrong—this helps the host improve the study.

Knowledge base: key concepts

Project
One research effort: its materials, question framework, interviews, and aggregated results.
Interview session
A single scheduled conversation with one participant. It moves through states such as scheduled, in progress, completed, or cancelled, depending on what happened.
Interview guide and questions
The ordered flow and wording that shape what the automated interviewer asks and how follow-ups are handled within each section.
Transcript and structured answers
A full conversation record, plus—where the product supports it—answers aligned to individual questions for easier review and reporting.
Insights
Project-level rollups that summarize themes, choices, ratings, or numbers across many interviews, according to how each question was set up.

Frequently asked questions

Do participants need to install anything?

Usually they only need a modern browser and a working microphone. Your invitation should spell out any study-specific requirements.

Can I change a study after interviews have started?

Small updates may be possible depending on your organization's rules and how far sessions have progressed. Plan major guide changes before fieldwork when you can.

Why might a transcript look different after the call?

Final transcripts can be improved after the session ends when additional processing runs. The product may merge or refresh text so record and analysis stay aligned.

Who do I contact for access or billing?

Use the contact channel your organization or account owner provided. This documentation does not replace your contract or support agreement.

Keeping this documentation accurate

Tirro maintains this page as a transparent, high-level reference. We revise it when product capabilities or typical workflows change meaningfully. For feature-specific detail, release notes or in-product help from your account team may apply.

Questions about this documentation or Tirro in general? Contact us.