Real-time transcription sounds harmless until you use it on a professional call.
Then the questions start. Does the agency allow it? Does the client allow it? Does the tool store the transcript? Does it count as recording? Does healthcare privacy law apply? Who can access the text?
The safe answer is not a blanket yes or no. Real-time transcription can be allowed for interpreters when the workflow fits policy, privacy, and the call setting. You need approval for the actual tool and the actual use case.
Allowed depends on the tool, the policy, the data, and the call.
Start with the rule that controls your call
Interpreters work under layers of rules.
TIP
Ask for permission in writing when you can. A verbal “sure” is weak if the tool stores sensitive text.
Your agency may have a technology policy. The client may have stricter rules. A hospital may require HIPAA-approved systems. A court may prohibit unapproved electronic tools. A benefits agency may have its own confidentiality standards.
Use the strictest rule that applies to the session.
If your agency says no outside tools, stop there. If your agency allows tools only from an approved list, use that list. If the client says the call cannot be transcribed, do not transcribe it, even if the tool itself has strong privacy controls.
Permission belongs to the workflow, not the category.
Ask what the tool does with audio and text
“Transcription” can mean different things.
Some tools record audio. Some stream audio and delete it. Some store transcripts. Some create summaries. Some train models on user content. Some invite a bot into a meeting. Some share notes with a team.
Those differences decide whether the tool fits interpreter work.
Before using real-time transcription, ask:
- Does the tool record audio?
- Does it store transcript text?
- Does it save summaries or notes?
- Does it train models on call content?
- Does it require a meeting bot?
- Can anyone else access the session content?
- Does it have compliance support for my setting?
Interpreter was designed for live OPI support, not meeting archives. It does not store audio or transcripts. It gives interpreters live transcription, two-way translation, speaker labels, quick lookup, and floating notes while the session is active.
That design helps with privacy review. It does not replace agency approval.
Medical calls need extra care
Healthcare calls can include protected health information. HHS guidance for business associates and minimum necessary use points to a basic principle: handle only the information needed for the task and make sure vendors fit the covered entity’s requirements.
For an interpreter, that means a transcription tool needs the right privacy posture and the right approval path. A free consumer tool, a general meeting recorder, or a personal notes app may not fit.
Use your agency’s HIPAA process. Confirm whether a business associate agreement or client-approved vendor status applies. If your agency cannot answer, do not improvise with patient information.
Our HIPAA for interpreters guide explains the daily-work version of this problem.
Legal and court calls need their own approval
Legal calls create a different set of concerns. The issue may involve privilege, court rules, confidentiality orders, or agency contracts.
Do not assume a tool allowed on medical calls is allowed for legal calls. Do not assume a tool allowed for prep is allowed during a live hearing, deposition, jail call, or attorney-client call.
Ask the court, agency, attorney, or contract administrator before you bring live transcription into the session. If you receive approval, keep the workflow narrow. Use the transcript for live support. Avoid saving content unless the approved process requires it.
For legal workflow support, Interpreter tools for legal calls and legal interpreting topics can help you think through the fit.
Recording law is a separate question
Transcription and recording are related, but they are not the same workflow.
State recording laws may restrict recording, and professional settings can have stricter contract or court rules than general phone-recording law.
Because the details vary, interpreters should avoid giving themselves legal permission based on a quick internet answer. If a tool records audio, treats transcripts as retained records, or gives third parties access to call content, ask for policy approval before use.
If the tool streams audio only during the session and does not store content, the privacy review may be easier. It still belongs in policy, not guesswork.
A practical approval script
Send a short question before you use a tool on live calls:
“I would like to use a real-time transcription support tool during OPI calls. It does not store audio or transcripts, and I would use it only to support accuracy during the live session. Is this approved for medical, legal, and general calls? Are there call types where I should not use it?”
If you use Interpreter, you can link your reviewer to the privacy page, medical page, and security documents in the site footer.
The safe answer
Real-time transcription can be allowed for interpreters when the tool, setting, and policy line up.
Use approved tools. Prefer no-recording and no-storage workflows for sensitive calls. Confirm agency and client rules before the first session. Treat healthcare and legal calls with extra care.
Ask the specific version: “Can I use this tool, on this call type, under this policy?”
Get that answer before the phone rings.
Sources: HHS business associate guidance, HHS minimum necessary guidance, Reporters Committee recording guide, and NCIHC Standards.
Related reading: