Push interview transcripts from a Tellet project into your CoLoop workspace with one click. Connect CoLoop once at the organisation level, choose which CoLoop project each Tellet project sends to, and CoLoop keeps a copy of every transcript for coding, tagging, and analysis in their platform.
Do this once per Tellet organisation.
Whoever signs in during the connection step is the person whose CoLoop identity now handles every push. Tellet shows this under the status badge as "Connected by <name>" so any admin can see which account the connection uses.
Pushes from Tellet flow through the CoLoop identity of whoever authorised the connection. If that person leaves your organisation or has their CoLoop access removed, Tellet's pushes stop working until an admin reconnects.
For teams that plan to keep the integration long-term, connect using a shared CoLoop login (for example, [email protected]) rather than an individual's account. This keeps the integration owned by the team, not by a single person, and makes transcripts show up in CoLoop under a neutral identity.
If a different admin needs to take over an existing connection later, they can just click Reconnect to CoLoop on the Integrations page — Tellet transparently switches to their CoLoop identity for future pushes.
Do this once per project you want to send transcripts from.
You can link multiple Tellet projects to the same CoLoop project if you'd like them to share a codebook — for example, if you run several waves of the same study.
To change the link, click Unlink and choose a new destination.
Tellet uploads every finished transcript in the project. Progress appears in the same panel as a live status table:
Only conversations that have finished are sent. Interviews still in progress, abandoned partway, or in test / sandbox mode are skipped.
You can send the same project again at any time. Transcripts already in CoLoop are recognised and updated in place, so there are no duplicates.
Sent:
Not sent:
For each conversation:
Personal data collected in screening questions (name, contact details, etc.) is NOT sent to CoLoop unless it appears inside the interview itself.
CoLoop credentials expire from time to time. When they do, Tellet shows an amber banner on the organisation menu's Integrations page and on any project that has a CoLoop link:
CoLoop has revoked or expired the credentials. Reconnect to resume pushing transcripts.
Click Reconnect to CoLoop and sign in again. Your existing project links are preserved — you only need to reconnect once and every Tellet project keeps its CoLoop destination.
To stop sending transcripts to CoLoop entirely:
Disconnecting:
You can reconnect at any time, but you'll need to link each project to a CoLoop project again.
To protect both platforms, Tellet limits how many transcripts a single organisation can send in one day. If you reach the limit, sending is paused until the following day; anything in the queue when the limit resets picks up automatically.
If you need to send an unusually large batch (for example, migrating a completed study with thousands of interviews), reach out to Tellet support and we can lift the limit for the day.
"Connect to CoLoop" button does nothing. The CoLoop integration may not be switched on for your organisation yet — contact Tellet support.
Redirect after signing in with CoLoop fails. Signing in with CoLoop didn't complete. Contact Tellet support and we'll sort it out with CoLoop.
Every transcript shows as Failed with the same message. The CoLoop project link is pointing at a workspace or project you no longer have access to in CoLoop. Unlink and pick a new destination.
Failed with "expired" in the reason. Your CoLoop sign-in expired. Reconnect from the organisation menu's Integrations page.
A specific transcript is stuck on In flight for more than 10 minutes. The audio file behind it may be missing. Try sending again; if it stays stuck, contact Tellet support with the participant number.