The 2 p.m. Call to Riyadh: An Ohio Hospital's International Patient Office, in Arabic

At 2:10 on a Wednesday afternoon, a coordinator in a large Ohio hospital's international patient office dials a mobile number in Riyadh. It is ten past nine in the evening there. The man who answers is the eldest son of a retired engineer in his late sixties who is due to fly to Ohio in three weeks for a specialist evaluation. The son speaks good English. His mother, who will travel with her husband and handle most of the day-to-day decisions, does not, and tonight she is the one with the questions.

This is the call international offices find hardest to staff well: outbound, in the family's evening, in Arabic, to relatives who are not the patient. Here is how it works with a live interpreter on the line, and where the interpreter's job stops. The family and the hospital are composites; no real institution is described.

Seven hours ahead, with a Friday-Saturday weekend

The clock sets the rhythm. Riyadh is seven hours ahead of Ohio while the US is on daylight saving time and eight hours ahead in the American winter, and the Saudi weekend falls on Friday and Saturday. That leaves a narrow, predictable window: Sunday to Thursday, early afternoon in Ohio, which is evening at home for the family.

Inside that window, the office usually relies on whoever speaks Arabic. If that is one coordinator, every Arabic call waits for her calendar. If it is the son, he becomes the interpreter, and his mother hears a summary of a summary. When he is at work and she rings the office herself, she reaches an English voicemail and gives up. A family that feels lost before the trip arrives anxious and asks the same questions again at the front desk.

Four conversations before the plane lands

Pre-arrival work for an international patient is mostly logistics, and every piece of it is a conversation the family wants to have in Arabic.

1. Who may hear what. Before anything clinical is discussed, the office confirms that the patient has authorized this family member to receive information, and explains the form if he has not.
2. Records. Prior imaging, reports and a current medication list, and how to send them securely. Families often ask whether Arabic-language reports are acceptable; that is a question for your office's records policy, and the interpreter carries the answer, not the policy.
3. Dates. The appointment sequence, how many days to plan for, and which visits must happen before others. Flights get booked around these, so each change means another call.
4. Practicalities. Mobility help at arrival, a companion's role, dietary needs, and sometimes a request about who will be present during an exam. Your office knows what it can offer; the family needs to hear it clearly.

Here is that pre-arrival call as a flow, with the authorization check placed first, where it belongs.

flowchart TD
  A[Coordinator calls the family in Riyadh from Ohio] --> B[Interpreter joins, family chooses Arabic]
  B --> C[Coordinator confirms identity in English, family hears Arabic]
  C --> D{Patient authorization on file for this relative?}
  D -->|No| E[Coordinator explains the authorization form in Arabic and sends it]
  D -->|Yes| F[Records checklist read in English, heard in Arabic]
  F --> G[Family confirms travel dates and arrival airport in Arabic]
  G --> H[First appointments booked, dates repeated back in Arabic]
  E --> I[Callback scheduled for the family evening, Riyadh time]
  H --> I

The update call after the first visit

Two weeks later the family is in Ohio. The specialist has seen the patient, and tomorrow brings tests that start at 7:30 a.m. with fasting from midnight. The coordinator calls the patient's wife at the hotel, with the patient's authorization already on file. Roughly how it sounds:

• The interpreter voice opens in Arabic with "مرحبا" and tells her the coordinator from the hospital is on the line and will be interpreted both ways.
• The coordinator explains the morning: where to park, which entrance, the 7:30 check-in, nothing to eat after midnight. She hears each sentence in Arabic a few seconds after it is spoken.
• She asks, in Arabic, whether her husband can take his morning blood-pressure tablet with water. The coordinator hears the question in English and answers from the written instructions the doctor's team provided, word for word, rather than improvising.
• She asks whether the results will be explained to them in Arabic. The coordinator says that conversation with the physician will be scheduled with a qualified medical interpreter present, and gives her the day.
• The coordinator asks her to repeat the plan. She does, in Arabic, and the coordinator hears it in English and knows it landed.

To hear the flow for yourself, open the live interpreter in your browser, choose Arabic, and have an Arabic-speaking colleague play the patient's wife while you read tomorrow's instructions in English.

Where a qualified human interpreter, and your counsel, still belong

An always-on interpreter is for the many logistics calls that otherwise wait. It is not a replacement for the moments your policies reserve for a qualified medical interpreter.

• Consent and serious news stay with a human interpreter. Informed consent for procedures, explaining a significant diagnosis, and anything your policy reserves for a qualified medical interpreter should keep going to one.
• Privacy comes first, contractually. Every CallSphere plan is HIPAA compliant, and CallSphere signs a Business Associate Agreement with every healthcare customer, whatever the plan, before any patient information is handled. The HIPAA-compliant AI voice agent page explains what that covers.
• Pre-arrival calls are logistics, not care. Giving clinical advice to a patient who is still in Saudi Arabia raises licensing questions your own counsel should answer. The interpreter does not change them.
• The interpreter carries words, not judgment. It does not soften, summarize or decide what matters. Your staff do.

Setting up an Arabic-ready international office line

Start with the calls you already make and the hours you already keep.

• Put the language choice first on the number international families are given, so a caller who hears it in the first seconds stays on the line.
• Script your outbound checklists in English. Records, dates, practicalities. The interpreter carries them into Arabic and the answers back, so you never maintain a second script.
• Book callbacks in the family's evening and say the time in both time zones.
• Let the AI receptionist take the overflow. When the coordinator is in a meeting, CallSphere's AI receptionist can answer in Arabic, take the message and book the callback, instead of an English voicemail.
• Check your obligations once. Your own licensing, privacy and records rules govern international patients. Confirm them before you scale the program.

The healthcare overview shows how hospitals and practices use the rest of the platform, and current plans are on the pricing page.

Frequently asked questions

Can we use the interpreter for clinical conversations with patients still abroad?

The interpreter does not change what your clinicians may do. It only carries the conversation. Whether anyone on your team can advise a patient physically in another country depends on licensing and your own policies, so keep pre-arrival calls to logistics unless counsel says otherwise.

Is the interpreter covered under HIPAA?

Yes. Every CallSphere plan is HIPAA compliant, and CallSphere signs a Business Associate Agreement with every healthcare customer before any patient information is handled, on any plan. Be wary of any vendor claiming a "HIPAA certification"; no such government certification exists.

Saudi families speak their own dialect. Will that work?

Usually, yes. Arabic is one of the languages on the interpreter's in-call menu, and most callers adjust toward a more widely understood Arabic when speaking with an office abroad. Dialects vary, so test a few real calls with your own families before you depend on it, and keep your human interpreter service as a fallback.

Who should we call when the patient is unavailable?

Only the people the patient has authorized. Confirm that at the start of each call, as the flow above does, and record who is cleared to receive which information. The interpreter carries the question and the answer; your authorization process decides who hears what.

Does the family need to install anything?

No. It is an ordinary phone call. The family answers their mobile in Riyadh or the hotel phone in Ohio, chooses Arabic, and hears every sentence in Arabic a few seconds after your coordinator says it in English. No app, no video link, no account.

The quickest test is a real script. Try the live interpreter with Arabic selected, read your pre-arrival checklist aloud, and listen to whether a family member would understand what to send and when to fly.