Remote interpreting gets talked about as one thing, but agencies dispatch two very different services under that umbrella: video remote interpreting (VRI) and over-the-phone interpreting (OPI). They differ in equipment, in cost, in setup time — and, most importantly, in which encounters they can actually serve. Choosing between them isn't a matter of preference. It's a short decision tree, and the first branch does half the work.
Start with the language
If the encounter involves American Sign Language or any other signed language, the phone is not an option. Not a worse option — not an option. Signed languages are visual languages; there is nothing for an audio line to carry. Every ASL request routes to video or to an on-site interpreter, full stop.
This sounds obvious written down, and yet it's the single most common remote-interpreting dispatch error, usually made by a well-meaning client-side scheduler who selected "phone" because it was the cheaper line item. Good intake catches it before it happens: when the language is signed, phone simply shouldn't be selectable.
For spoken languages, ask what the encounter needs
Once you're in spoken-language territory, both modalities work — the question becomes which one serves the encounter better.
| Factor | VRI | OPI |
|---|---|---|
| Setup | Camera-equipped device, decent bandwidth, a place to position the screen | Any phone, immediately |
| Connect time | Short, but requires the room to be ready | Fastest option available |
| Visual context | Interpreter sees facial expressions, gestures, documents, the room | Voice only |
| Best for | Longer or sensitive conversations, encounters where demeanor matters, anything involving shared documents or forms | Brief calls, high-volume routine contacts, situations with no camera available |
| Typical billing | Per-minute or scheduled block | Per-minute |
The pattern that falls out of that table: OPI wins on speed and ubiquity; VRI wins on fidelity. A pharmacy confirming a pickup time needs a fast connection and thirty seconds of Spanish — that's a phone call. A difficult conversation between a physician and a family, where tone and expression carry as much as the words, deserves video even though both would technically "work."
Where each one earns its keep
Reach for OPI when
- The interaction is short and transactional — confirmations, reminders, basic intake questions.
- Calls arrive unpredictably and in volume, and holding for video setup would create a queue.
- The environment has no reliable camera or bandwidth — field work, older facilities, a caller on a flip phone.
Reach for VRI when
- Any signed language is involved. (Always.)
- The conversation is longer, sensitive, or high-stakes, and non-verbal communication matters.
- Participants are referencing documents, forms, or anything physical the interpreter should see.
- You want closer to an on-site experience without travel time or mileage on the invoice.
OPI wins on speed and ubiquity; VRI wins on fidelity. The mistake is treating them as interchangeable.
The short version
What this means for your operation
The modality decision only helps if your platform treats it as a first-class fact about the job. A request should carry its modality from intake through assignment through billing: video jobs matched to interpreters equipped and willing to work on camera, phone jobs billed at phone rates, and signed-language requests physically unable to end up on an audio line. On platforms where VRI and OPI run alongside on-site scheduling, dispatchers stop making the modality call from memory — the request itself knows what it is, and the rest of the pipeline follows.
Two services, one umbrella, one decision tree. Ask about the language first, the context second, and the logistics last — and put the tree into your intake form so the right answer is the easy one.