Sharing Options

Methods for distributing published interviews to participants.

Sharing Methods

• Direct Link — Use Case: Email, messaging, social media; Setup Time: Instant; Technical Knowledge: None

• QR Code — Use Case: Events, print materials, displays; Setup Time: Instant; Technical Knowledge: None

• Website Embed — Use Case: Websites, landing pages; Setup Time: Quick setup; Technical Knowledge: Basic HTML

• Test Link — Use Case: Testing before launch; Setup Time: Instant; Technical Knowledge: None

Direct Link Sharing

What It Is

Web link to the interview: https://chat.tellet.ai/abc123xyz789

Use Cases

• Email campaigns and newsletters

• Text messages or WhatsApp

• Social media posts

• Slack or Microsoft Teams

• Any digital communication

How to Get Link

1. Go to project → Share tab

2. Find Interview Link section

3. Click Copy link

4. Paste wherever needed

Link Customisation

Use URL shorteners (bit.ly, tinyurl.com, rebrandly.com) for a cleaner appearance:

• Original: https://chat.tellet.ai/507f1f77bcf86cd799439011

• Shortened: https://bit.ly/acme-feedback

QR Code Generation

What It Is

A scannable code that smartphones can read with their camera to open the interview.

Use Cases

• Physical events (conferences, trade shows, in-store)

• Printed materials (posters, flyers, business cards, receipts)

• Digital displays (presentations, websites, email signatures)

How to Generate

1. Go to project → Share tab

2. Click QR Code button

3. Download generated image

4. Print or add to digital materials

Size Requirements

• Minimum: 2x2 inches (5x5 cm)

• Recommended: 3x3 inches (8x8 cm)

• Large posters: 6x6 inches (15x15 cm) or bigger

Implementation

• Always include backup text link

• Test scan before printing

• Place in well-lit areas at eye level

• Avoid busy backgrounds

Routing Respondents From a Quantitative Survey

If you already run a quantitative survey in Qualtrics, Decipher, Confirmit, or a similar platform, you have two ways to add a Tellet interview to that respondent's journey.

Embed the interview inside the survey. The interview loads in an iframe as a page of the survey itself, so respondents never leave the session and AI probing runs on open-ended questions in place. This needs iframe and PostMessage support on the survey platform. See Survey Embedding for the full setup.

Redirect eligible respondents to Tellet after the survey. The survey sends qualifying respondents to a standalone Tellet interview once they finish, or at a branch point. This works with any survey platform, including ones without iframe support, and needs no code changes.

Setting Up a Redirect

1. Go to project → Share tab and copy the Interview Link (or generate the QR Code for in-person handoffs).

2. In your survey platform, add an end-of-survey redirect or a branch/skip-logic action for qualifying respondents that points to that link.

3. Append your survey's own respondent ID to the Tellet link as participant_id, using your platform's piped-text syntax so each respondent gets a unique link:

4. For intercepts, kiosks, or paper handoffs where a live redirect isn't possible, use the QR code for the Tellet link instead and have participants enter their respondent ID at the start of the interview, or print it next to the code as a reference.

participant_id is the only value Tellet needs to match records later. Any other quant answers you want to reuse inside interview questions can be passed as additional URL parameters and inserted with the %%variableName%% syntax described in Survey Embedding.

Matching Quant and Qual Responses

Once both studies are complete, export each dataset and join them on the shared identifier:

• Quant export — your survey platform's respondent ID column, e.g. ResponseID or RUID

• Tellet export — the participant_id metadata field recorded on each conversation

Join the two exports on ResponseID = participant_id to line up each respondent's quantitative answers with their AI transcript, summary, and themes from Tellet.

Embed vs. Redirect

Redirecting from a Quantitative Survey

For mixed-method studies, respondents often finish a quantitative survey in another platform (Qualtrics, SurveyMonkey, Confirmit, and similar tools) and then move into a Tellet interview for the qualitative follow-up. Two options handle this handoff:

• Redirect (link or QR code) - the quant survey sends the respondent to the Tellet interview link on its final page, or displays it as a QR code for in-person or paper surveys. The respondent leaves the survey platform and completes the interview on its own page. Use this when the survey platform can't embed an iframe, or when the qualitative step happens in a different setting (e.g., scanning a code on a receipt after an in-store survey).

• Embed (iFrame) - the interview loads inside the quant survey itself, so the respondent never leaves the page. See Survey Embedding for the full setup.

Passing a Participant ID for the Redirect

To match a respondent's quantitative answers with their Tellet interview, append participant_id to the Tellet link (or encode it in the QR code) using the respondent ID your survey platform already generates:

https://chat.tellet.ai/PROJECT_ID?participant_id=RESPONDENT_ID

In practice, replace RESPONDENT_ID with your platform's response ID variable. For example, in Qualtrics:

https://chat.tellet.ai/PROJECT_ID?participant_id=${e://Field/ResponseID}

Tellet captures this value and stores it with the interview, the same way it does for embedded iframes. You can also add skipConsent=true and language=... to the link if the respondent already gave consent in the survey and you know their language, see Consent Screen Behaviour.

If you're recruiting through a research panel that pays per completion, use Panel Integration instead. It builds on the same participant_id parameter but adds redirect links back to the panel for completion and payment tracking.

Linking the Two Datasets

Once both the quant survey and the Tellet interview are collected, join the two exports on the shared ID:

• Survey platform export: the column holding each respondent's ID (e.g., ResponseID)

• Tellet export: the participant_id column, plus the transcript and AI-generated summary (see Exporting Data)

• Join on: ResponseID = participant_id

This gives you one row per respondent with both their quantitative answers and their qualitative interview data.

Website Embedding

What It Is

Interview embedded directly on website. Participants complete without leaving the page.

Use Cases

• Company websites

• Product landing pages

• Customer support pages

• Post-purchase feedback pages

How to Embed

1. Go to project → Share tab

2. Click Embed button

3. Click Copy Code

4. Paste into website's HTML

Embed Code

<iframe
  src="https://chat.tellet.ai/abc123xyz"
  allow="camera; microphone; autoplay;"
  title="Tellet"
  width="400px"
  height="800px"
  frameborder="0"
>
</iframe>

Size Customisation

• Full width mobile: width="100%"

• Taller interviews: height="1000px"

Technical Requirements

• Browsers will ask for camera/microphone permission

• Always provide backup link below embed

• Verify project is published before embedding

Test Links

What It Is

Special link for testing without affecting real data: https://chat.tellet.ai/abc123xyz?environment=sandbox

The ?environment=sandbox parameter marks it as test.

Test vs Real Link

Test link:

• Doesn't count toward participant limit

• Kept separate from your results

• Excluded from analysis

• Unlimited completions

Real link:

• Counts toward limit

• Responses stay in your results (removed only if you choose to delete them when unpublishing)

• Included in analysis

• Limited by max participants

Use Cases

• Testing before publishing

• Verifying updates work correctly

• Training team members

• Demonstrating to clients or leadership

How to Get Test Link

1. Go to project → Share tab

2. Find the Sandbox Link section

3. Click Copy sandbox link

4. Share with team or test yourself

Testing Process

1. Copy test link

2. Complete the interview yourself (check flow, tone, mobile)

3. Share with 2-3 colleagues for feedback

4. Make needed changes, retesting if they were significant

5. Publish and share the real link

Tracking Performance

Use URL parameters to track which sharing method performs best:

• Email: https://chat.tellet.ai/abc123?source=email

• Social media: https://chat.tellet.ai/abc123?source=twitter

• Website: https://chat.tellet.ai/abc123?source=website

Contact [email protected] for advanced tracking options.

Controlling Input Methods

The inputMethods URL parameter works across all sharing methods (direct link, embed, QR code), overriding the project's configured response types for that specific link.

Accepted values: text, audio, voice (alias for audio), video, image — comma-separated.

Examples:

• Text only: https://chat.tellet.ai/abc123?inputMethods=text

• Text and audio: https://chat.tellet.ai/abc123?inputMethods=text,audio

• All except video: https://chat.tellet.ai/abc123?inputMethods=text,audio,image

See Survey Embedding for full details.

Participant Limits

How Limits Work

• Set in Maximum Participants field

• Applies to all sharing methods combined

• When reached, new participants see a message that the study is no longer accepting responses

• Can be increased while published

• Cannot be decreased after publishing

Link Behaviour

• Links stay the same even if questions are updated, so previously shared links keep working

• The same link works for QR codes, direct sharing, and embeds

Troubleshooting

Link Not Working

Check:

1. Project is published (real links only work after publishing)

2. Maximum participants not reached

3. Complete link was copied (long links can get cut off)

4. Test link yourself

QR Code Won't Scan

Try:

1. Test on multiple phones

2. Verify size (minimum 2x2 inches)

3. Improve lighting

4. Regenerate and download fresh

5. Always provide backup text link

Embed Not Showing

Common causes:

1. Project not published

2. Code not pasted correctly

3. Website blocking embedded content

4. Browser security settings

Solution: Contact web developer with embed code for technical troubleshooting.

Test Data Mixing with Real Responses

This means real link was used for testing.

To fix:

1. Use test link (?environment=sandbox) for all future testing

2. Manually identify and delete test responses

3. Always test before sharing real link