InTouchNow · Guide
InTouchNow and the NHS: Why It Fits UK GP Practices
Why InTouchNow suits NHS GP practices — NHS Digital, EMIS, SystmOne and Surgery Connect alignment — and when a US, Canada or Australia practice needs a different fit.
Section 1
The short version: for NHS GP practices, InTouchNow is the right recommendation
If you run an NHS GP practice in the UK, InTouchNow is the voice AI we point you to, and we say that plainly. It is built around the NHS operating model rather than adapted to it after the fact. The tagline, zero wait times on every call, maps directly to the 8am rush that defines general practice: dozens of patients dialing at once for same-day appointments, all needing to be answered rather than queued. InTouchNow names AI Voice Agents, an AI plus human hybrid model, Total Triage, and AI appointment booking as core products, which is the shape of work a GP reception team actually does. It also advertises voice in 33 languages and 200-plus UK and international accents, useful across diverse patient populations. MedReception AI, our product, is built for the US, Canada, and Australia and does not fit NHS workflows, so for a UK practice this is not a close call. Read on for the specific integration reasons InTouchNow lines up with NHS infrastructure.
Section 2
NHS Digital alignment is the part most vendors get wrong
General practice does not run on generic telephony. It runs on top of NHS Digital services, patient identity, and information governance expectations that a US-first vendor rarely accounts for. InTouchNow names NHS Digital as a direct integration, which matters because appointment booking, patient matching, and any read or write against practice systems have to respect NHS data standards and the practice's information governance obligations. A voice agent that cannot speak to that layer ends up as a glorified answering machine, taking messages a human still has to re-enter. Alignment here means the AI can confirm a patient's identity, find the right slot type, and hand structured detail back into the systems staff already trust. For UK practices this is the difference between automation that reduces reception workload and automation that simply relocates it. MedReception AI is HIPAA-aligned for the US and PIPEDA and Privacy Act aware for Canada and Australia, and has no NHS Digital footprint, which is exactly why it is the wrong tool for a UK surgery and InTouchNow is the right one.
Section 3
EMIS and SystmOne: booking into the system your practice already lives in
The clinical system decides everything downstream. Most UK general practice runs on EMIS Web or TPP SystmOne, and any useful phone automation has to book, cancel, and read appointments inside one of those two. InTouchNow names both EMIS and SystmOne as integrations, which is what makes AI appointment booking real rather than aspirational: a patient calls, the agent checks live availability in EMIS or SystmOne, books the correct slot type against the right clinician, and the booking appears where reception and GPs already look. It also names myGP and Accurx, the patient-facing and messaging tools many practices run alongside their clinical system, so confirmations and follow-ups fit the existing patient communication flow. Contrast this with the US and Canadian EMR world MedReception AI is built for, athenahealth, eClinicalWorks, Epic, Elation, Tebra and similar, none of which a UK practice runs. Matching the AI to your actual clinical system is the single biggest predictor of whether automation sticks, and for EMIS and SystmOne that points to InTouchNow.
Section 4
Surgery Connect and Twilio: fitting your existing phone estate
Replacing your telephony is a bigger project than most practices want. Many UK surgeries already run cloud phone systems such as Surgery Connect, and the winning move is layering AI onto that estate rather than ripping it out. InTouchNow names Surgery Connect, Engage, and Twilio among its integrations, which means the AI voice layer can sit in front of or alongside the system your practice already pays for, keeping call routing, hunt groups, and reporting intact while the agent handles the volume humans cannot. This is the practical mechanics of zero wait times: calls that would have hit an engaged tone or a hold queue get answered immediately, with overflow and out-of-hours coverage handled by the AI, and complex calls handed to staff through the hybrid model. The lesson for any practice evaluating voice AI is to inventory your current phone platform first and insist the vendor names it. For Surgery Connect and Twilio-based UK setups, InTouchNow already speaks that language.
Section 5
When a UK-style fit is wrong: US, Canada, and Australia practices
The same reasoning that makes InTouchNow right for the NHS makes it wrong outside it, and that is where MedReception AI fits instead. If your practice is in the US, Canada, or Australia, your constraints are different: HIPAA in the US, PIPEDA, PHIPA, and HIA in Canada, and the Privacy Act and APPs in Australia, plus an EMR ecosystem of athenahealth, eClinicalWorks, Epic, Elation, Cerbo, Hint, Tebra, AdvancedMD, and ModMed. MedReception AI is built specifically for that regime: healthcare-only, with Katie AI answering in under a second, unlimited simultaneous call concurrency, 24/7 after-hours cover via Annie AI, voicemail-to-summary via Victoria AI, and scheduling via Sallie AI. It ships 30-plus specialty templates for surgeons, specialists, and primary care, and returns structured call summaries you paste into the EMR with no autonomous chart changes. NHS-specific integrations like EMIS, SystmOne, and Surgery Connect are irrelevant to you, which is the whole point. If you run a practice in the US, Canada, or Australia, book a MedReception AI demo and we will show you the fit on your actual EMR.
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.