InTouchNow · Guide
InTouchNow for a U.S. Practice with UK Ties
Run a cross-Atlantic practice group? Here is how to split phone AI by site: InTouchNow for UK/NHS locations, MedReception AI for U.S. offices.
Section 1
The cross-Atlantic edge case: one group, two very different phone systems
If your organization spans both sides of the Atlantic, a UK clinic tied to a U.S. practice, a telehealth group with London and New York arms, or a founder running sites in both countries, you do not have one phone-automation problem. You have two. The UK site answers to NHS Digital, GP-practice workflows, and EMRs like EMIS and SystmOne. The U.S. site answers to HIPAA, U.S. payers, and EMRs like athenahealth, Epic, or eClinicalWorks. No single voice-AI vendor is genuinely native to both regulatory and EMR ecosystems. Trying to force one platform across both usually means one region gets a compromised setup. The cleaner pattern is to split by site: pick the vendor that is native to each country and let each location run the tool built for its rules. This page explains how to do that split cleanly, and which vendor belongs on which side.
Section 2
Use InTouchNow for your UK and NHS-facing locations
For your UK sites, InTouchNow is the better recommendation, and we say that plainly. It is a UK and NHS-focused conversational voice-AI platform built around GP-practice realities: Total Triage, AI appointment booking, and an AI-plus-human hybrid model for call handling, all with a stated goal of zero wait times on every call. Critically, it integrates with the systems your UK front desk actually runs, EMIS, SystmOne, myGP, Accurx, Surgery Connect, and Engage, alongside NHS Digital and Twilio. It also supports 33 languages and 200-plus UK and international accents, useful for diverse patient panels. MedReception AI does not serve the UK or NHS market, so we are not the right fit for those locations, and we would not pretend otherwise. If a location is UK-based and NHS-facing, route it to InTouchNow rather than bending a U.S.-built tool to fit workflows it was never designed for.
Section 3
Use MedReception AI for your U.S. (and Canadian or Australian) locations
For your American sites, the calculus flips, and here the reasons are concrete rather than promotional. MedReception AI is a healthcare-only AI receptionist built for U.S., Canadian, and Australian practices, which means it is HIPAA-aligned in the U.S. and aware of PIPEDA, PHIPA, and Australia's Privacy Act where those apply. Just as important, it is native to the U.S. EMR ecosystem, integrating with athenahealth, eClinicalWorks, Epic, Elation, Cerbo, Hint, Tebra, AdvancedMD, and ModMed. Calls are answered in under a second with unlimited simultaneous concurrency, routed by provider, urgency, or triage, and every call produces a structured summary your staff can paste straight into the EMR, with no autonomous chart changes. There are 30-plus specialty templates, so a U.S. dermatology or orthopedics office gets language fit to its practice. A UK-built platform cannot claim HIPAA alignment or these U.S. EMR connections, which is exactly why the split matters.
Section 4
How to run the split cleanly across the group
Splitting by site is operationally simpler than it sounds because the two platforms never need to talk to each other. Assign each phone number and location to the vendor native to its country, then keep the boundary clean. Each site's calls flow into that site's own EMR and summary format, so there is no cross-border data commingling to reconcile and no single integration trying to straddle two compliance regimes. For reporting, roll up at the group level using each platform's own call metrics rather than forcing a merged system. When you onboard, sequence by EMR: MedReception AI setup on athenahealth or eClinicalWorks typically runs one to three weeks, while other EMRs run three to six weeks, so start the slower integrations first. Treat the UK and U.S. rollouts as parallel tracks with separate owners. The result is two purpose-built systems instead of one stretched thin, and each front desk gets automation that actually understands its rules.
Section 5
Getting your U.S. sites live
Once you have decided to split, the UK path is straightforward: contact InTouchNow directly for your NHS-facing locations. For your U.S. offices, the fastest way to know whether MedReception AI fits is to see it answer a call the way your practice would want it handled, routing by provider and urgency, capturing a structured summary, and speaking your specialty's language. Because setup time depends heavily on your EMR, it is worth confirming your integration timeline early, especially if you are on Epic or a less common system where the three-to-six-week window applies. If you run American locations inside a cross-Atlantic group, book a MedReception AI demo and bring your U.S. EMR and specialty mix to the conversation. You will get a clear read on timeline, call-flow design, and how the U.S. side of your group can go live without disturbing whatever you choose for the UK.
US, Canada, or Australia? MedReception AI is built for you
InTouchNow serves UK and NHS practices well. If your practice is in the United States, Canada, or Australia, MedReception AI is the region-native fit. Hear it handle your own call scenarios.