Troubleshooting calls
Report a call problem without sharing the whole conversation.
“The call did not work” is hard to investigate. Sending a recording of everything you said can reveal far more than support needs. A short, structured description is a better first step: say which direction failed, what appeared on screen, and approximately when it happened.
Describe the direction, not just the symptom
Write down the two languages and which person could not hear the translation. “I could hear their translated speech, but they could not hear mine” describes a different problem from “Neither side heard translated audio.”
Say whether the problem began with the first exchange or partway through the call. If you do not know what the recipient heard, label it as unknown instead of guessing.
Separate captions from spoken playback
Note whether your original words appeared, whether a translation appeared, and whether translated speech played. These are separate observations. Text appearing on your screen does not prove that the other person heard the audio.
For an incorrect translation, explain the kind of mistake without reproducing private content: for example, “A question was displayed as a statement.” A made-up sentence illustrating the same issue may help, but clearly label it as an example rather than an actual transcript.
Keep a few useful conditions
Include the approximate date and time with your time zone, your iPhone model, and the app version if you can find it. Note whether you used Wi-Fi or cellular data and headphones or the phone’s audio output.
Describe what changed just before the issue, such as switching audio devices or moving between networks. These details do not establish the cause; they help distinguish one test from another.
Keep the first report small
Use a template like this: “At about [time and time zone], using [language A] and [language B], I saw [caption behavior]. I heard [audio behavior]. The recipient reported [behavior, or unknown]. I was using [network and audio setup].”
Use the app’s verified support contact. Leave phone numbers, booking details, access codes, and other people’s private information out of an initial report. If support needs a specific identifier, ask which one and how to send it privately.
Reproduce with harmless content when appropriate
If both people are willing, try a separate short test with a neutral phrase such as “The blue cup is on the table.” Change one condition at a time and report what happened. Do not keep retrying a conversation where an error could cause harm; use another suitable communication method.
Ask before recording or sharing anyone’s speech. If a screenshot is needed, remove unrelated personal information first. Do not assume the app records calls, exports transcripts, or gives support permission to share your report publicly.
Where Origin fits
We build Origin: Translated Calls at Avatar8 LLC. On iPhone, the caller chooses both languages and calls a regular phone number. Origin translates speech in both directions and shows original words and translations on the caller’s screen.
Accuracy and delay vary, and support observations alone do not guarantee a diagnosis or a fix. Check the app for current language and destination availability. Origin does not support emergency calling and does not replace qualified interpretation when professional accuracy is required.