What to Do When an AI Transcription Service Ignores Your Support Requests

The short version: Most AI transcription companies run tiny support teams behind a big product, so a silence of five to ten days is normal, not a sign you've done anything wrong. Work through a fixed escalation ladder (email, then public, then payment provider), give each step a deadline, and if you hit day fourteen with nothing, stop waiting and move your account. Waiting politely for a reply from a company that has no incentive to reply quickly is the single most expensive mistake I see people make.

Why your support ticket is sitting in a queue nobody's reading

I want to say something uncomfortable first, because nobody selling you a transcription tool will say it. Most of these companies, even the well known ones, have a support team of two to six people servicing tens of thousands of accounts. Otter.ai has raised over $63 million and has a headcount you could fit in a large meeting room. Sonix, Trint, Descript's transcription arm, most of them run lean on purpose because investors reward growth, not customer service headcount. Your ticket isn't lost. It's in a queue, sorted by plan tier, and if you're on the $8 or $12 a month personal plan, you are at the bottom of that queue by design.

That's not an excuse for them going quiet. It's context, because it changes what you should do. Emailing the same address three more times with "PLEASE RESPOND" in the subject line does nothing, because a human isn't triaging that inbox on emotion, they're triaging it on plan value and keyword flags. Knowing that changes your strategy.

What happened to me with a transcription tool mid-launch

I was running a client's product launch week, seven interviews recorded across two days, all needing turnaround inside 48 hours for a content push. I'd used the same AI transcription tool for about a year without issue, mid-tier plan, roughly $20 a month. On day one of the launch, the tool double-billed me, charged me for an annual upgrade I hadn't asked for, and then locked two of my audio files behind that unpaid "upgrade" it thought I owed.

I emailed support the same day. Nothing. I emailed again on day three, referencing the transaction ID. Nothing. By day seven I'd lost the window to use two of those interviews in the launch content at all, because I wasn't going to sit on unpublished audio waiting for a reply that might never come. I ended up paying a virtual assistant to manually transcribe the two locked interviews from a phone recording backup, which cost me more in a rush fee than the entire year's subscription had. Twelve days after my first email, I got a reply. It said sorry for the delay, and refunded the double charge. Twelve days for a refund on a mistake they made.

The lesson wasn't "that tool is bad." The lesson was that I had no backup workflow and no escalation plan, and both of those are on me, not the software.

The escalation ladder: what to do, and by when

Here's the exact sequence I now use, with real deadlines, because a vague "keep following up" plan is how you end up waiting three weeks.

• Day 0: Submit one ticket, not five. Include your account email, transaction or file ID, exact dates, and one clear sentence stating what you want (refund, file unlocked, feature fixed). Vague tickets get vague queue placement.
• Day 3: If nothing, reply to the same thread (don't start a new one, that resets your position in some systems) and add the words "billing dispute" or "data access issue" to the subject line. These are flagged terms in most support software like Zendesk and Intercom, and they route to a higher priority queue than "question."
• Day 5: Try a second channel entirely. Most transcription companies have a live chat that's routed to sales, not support, but sales reps can often escalate internally faster than a support ticket, because they don't want to lose a paying account. Ask directly: "I have an unresolved support ticket, can you flag it to your team, I'm considering cancelling."
• Day 7: Go public, briefly and factually, on whichever platform the company is most active on, usually X or LinkedIn. Tag the company handle, state the ticket number, no ranting, just the facts. I've watched three-week-old tickets get a reply within two hours of a public post, because community managers monitor mentions even when support doesn't monitor the inbox.
• Day 10: Leave a factual review on Trustpilot or G2 stating the ticket number and the wait time. Buying software makes decisions off reviews, and most tools have someone assigned to respond to negative reviews within 48 hours, faster than their own support inbox.
• Day 14: If you were charged and got nothing for it, contact your bank or card provider and open a dispute. In the UK this is a Section 75 claim if you paid by credit card and the amount is over £100, or a chargeback through your bank for debit cards. In the US it's a standard chargeback through Visa or Mastercard's dispute process. This is the step people skip because it feels dramatic. It isn't. It's the fastest way to get money back from a company that has stopped talking to you.

The step nobody wants to hear: sometimes there's no back door

Here's the part that most guides on this topic won't tell you plainly. Some of these tools have no functioning support at all, not slow support, none. If you're on a free tier or the cheapest paid tier of a smaller AI transcription startup, and you've done all six steps above with no movement by day fourteen, the honest move is to stop treating this as a support problem and start treating it as a vendor risk problem. You cancel, you export whatever files you can still access, and you move on. I know that stings when you've invested time building a workflow around one tool, but the sunk cost of your setup is smaller than the sunk cost of another launch week held hostage by a locked file.

This is also why I tell clients who build any part of their workflow around AI tools for business to always keep a manual fallback for anything time-sensitive. A transcription tool going quiet on you the week before a launch is not a hypothetical, it's a Tuesday.

If you'd rather have someone stress-test your whole AI stack before it fails you at the worst moment, that's exactly the kind of gap an AI consultant gets paid to find before it costs you a client.

What to do while you're waiting

Don't sit still. While a ticket is open, do three things in parallel:

• Export everything you still have access to, immediately, in case access disappears entirely if the dispute escalates or the account gets flagged.
• Line up a stopgap. A cheap human transcription service like Rev.com charges around $1.50 a minute for guaranteed 24-hour turnaround, which is expensive per file but cheap compared to a missed deadline. Or brief a virtual assistant who already knows your formatting preferences, so a rush job doesn't come back needing rework.
• Document the timeline as you go, dates, screenshots, ticket numbers. If you end up needing a chargeback or a public post, having this ready saves you an evening of digging through your inbox trying to reconstruct what happened.

Why the support gap is bigger for AI tools than old software

Traditional software companies built support teams over a decade of growth. A lot of AI transcription tools scaled their user base in eighteen months on the back of one viral feature, and support headcount hasn't caught up. It's worth remembering that the humans behind these tickets are often the same overstretched teams you'll find running customer service jobs from home, on contract pay, handling volume that would strain a much bigger team. That's not a reason to accept twelve days of silence. It's a reason to build your workflow assuming it might happen, rather than being shocked when it does.

If you're outsourcing any of the manual cleanup work that AI transcription still gets wrong, punctuation, speaker labels, formatting for a client deck, it's worth understanding what that kind of support work costs and looks like, which I've broken down in detail on the data entry job description page, because a lot of "transcription cleanup" roles are really data entry roles with a different name.

How to pick a tool less likely to leave you stranded next time

Before you sign up for the next transcription tool, check three things that take about five minutes and save you a lot of grief later.

• Search the tool's name plus "support" on X or Reddit and read the last twenty results. Patterns show up fast.
• Check whether their pricing page even lists a support SLA for your tier. If only the top enterprise tier gets a stated response time, assume everyone below that gets none.
• Test their support before you need it. Send one low-stakes question in your first week and time the reply. That single data point tells you more than any review site will.

Related reading: mobile carrier or wifi doesn't support whatsapp calls.

Related: how much time ai consultant saves ten person business for small businesses.

Related: my ai consultant contract what should be in it page.

Frequently asked questions

How long should I wait before assuming an AI transcription company won't respond?

Give them three days for a first reply on a standard ticket. If you've heard nothing by day seven, move to public channels and treat day fourteen as the point where you stop waiting and start planning your exit.

Can I get my money back if an AI transcription service never responds to support?

Yes, through your card provider. In the UK, a Section 75 claim covers credit card purchases over £100, and debit card chargebacks are handled directly by your bank. In the US, standard Visa or Mastercard chargeback rules apply regardless of what the company's own refund policy says.

Is it worth going public on social media about a support issue?

Yes, if you've already tried a direct ticket at least once. Keep it factual and include your ticket number rather than venting, because community managers respond faster to specific, solvable problems than to general complaints, and a calm public post often moves faster than a second or third email.

Should I switch tools the first time support goes quiet?

Not the first time. One slow response is normal for a lean team. But if you've completed the full escalation ladder and hit day fourteen with nothing resolved, that's a pattern, not a blip, and it's a reasonable point to move your account and your files elsewhere.

Where to check the details

• HMRC's guidance on working for yourself
• Anthropic's own documentation