How do I publish a project?
For Admins and Owners: ensure all required fields are complete (project status shows Ready), then click Publish and confirm in the dialog. The interview goes live immediately. For Editors: click Request to Publish, select an Admin or Owner to review, and wait for approval. You can send one reminder after 24 hours using the Request Approval Again button. After approval, click Publish to make it live. Publishing requires an active organisation subscription.
How do I share my interview?
Four methods:
Direct Link (copy the interview URL and share via email, WhatsApp, Slack, social media, or any channel)
QR Code (generate and download from the Share tab, minimum 2x2 inches when printed)
Website Embed (copy the iframe code from the Share tab and paste into your website HTML)
Panel Integration (set up automated participant routing via panel providers with completion tracking).
The Test Link (sandbox link) is for internal testing only and should never be shared with real participants.
What is the difference between the sandbox link and the live link?
Sandbox link: for testing only, marked as test data, does not count toward participant limit, unlimited completions, conversations can be deleted in bulk.
Live link: for real participants, counts toward the limit, included in analysis. Use the sandbox link for all internal testing before launch.
Can I customise the interview URL?
Not directly. Use URL shorteners (bit.ly, tinyurl.com, rebrandly.com) for cleaner appearance, embed on your own domain, or use QR codes.
Can I embed Tellet on my website or in a survey?
Yes. An iframe embed code is available in the Share tab. For embedding inside quantitative survey platforms (Dimensions, Decipher, Forsta), use the survey embedding setup with the PostMessage API. The iframe sends STATUS_CHANGE, CONVERSATION_COMPLETE, DIGEST_READY, and END events back to the parent page. Pass participant_id, language, and skipConsent=true as URL parameters for survey embedding. Use the %%variableName%% syntax in questions to inject survey data such as prior scores or product names directly into the interview questions.
Can I unpublish a project?
Yes. Click the three-dot menu on the project card > Unpublish. You will be asked whether to keep or delete completed conversations. Deleting conversations also permanently deletes all associated AI-generated analysis. Unpublishing is blocked if there are any active (in-progress) conversations. The project returns to Ready status and can be republished.
Can I republish a completed project?
Yes. Open the project and click Republish (or use the three-dot menu). Existing responses and analysis data are preserved. New responses are collected and analysed alongside existing data. If the respondent limit was already reached, increase Maximum Participants before republishing.
How do I control which response modes are available per link?
Append the inputMethods URL parameter to the link (e.g. ?inputMethods=text,audio). This overrides the project-level configuration for that specific session. Accepted values: text, audio (or voice as alias), video, image. Comma-separated. Invalid values are silently ignored.
How do I send respondents from my quantitative survey (Qualtrics, Decipher, Confirmit) into a Tellet interview and match their answers?
Two options. Embed the Tellet interview inside the survey as an iframe so respondents never leave the session, using the survey embedding setup described in the Survey Embedding article. Or, after the respondent finishes (or reaches a branch point in) the quantitative survey, redirect qualifying respondents to a separate Tellet interview link or QR code. For the redirect option, append your survey's respondent ID to the Tellet link as participant_id using your platform's piped-text syntax, for example participant_id=${e://Field/ResponseID} in Qualtrics. After both studies finish, export the quant and Tellet data and join them on ResponseID = participant_id to line up each respondent's quantitative answers with their AI transcript and analysis. See Sharing Options for the full redirect setup and a comparison with embedding.