Integrations · Patient messaging
Reaching patients, from the record.
SMS under your own sender ID, email from your own domain, and trusted patient information shared straight from the consultation. Every send lands back on the patient record and in one shared inbox - not in somebody's personal mailbox.
Hi Priya - before Thursday's appointment, please complete this short pre-operative assessment.
How it works
Sent, delivered, logged.
A person writes it or a workflow triggers it. Everything after that - delivery, receipts, the record - takes care of itself.
- 01Message written or triggered by a workflowclinician or rule
- 02Patient preferences and quiet hours checkedautomatic
- 03Sent by SMS or from your email domainautomatic
- 04Delivery receipt or open trackedautomatic
- 05Logged on the record and in the inboxautomatic
Replies land in the shared team inbox, where they can be assigned, tagged and answered - not left in a personal mailbox.
Who Jump connects to
Your number, your domain, trusted leaflets.
Three connections that decide what a patient sees when Jump reaches them.
UK patient SMS under your practice sender ID, with per-message delivery receipts and visible credit balance.
Jump Mail sends from your practice's own domain, with per-message open tracking.
Trusted patient information surfaced in the consultation and shared with the patient in a click.
Two things nearby that are not connections to manage: sending clinic letters to a patient's registered NHS GP over the NHS message exchange, and Meta Pixel or Google Tag Manager for conversion tracking on your booking pages.
What you get
One inbox, every conversation.
What the messaging connections do once they are switched on in the App Store.
- 01SMS via FiretextYour practice sender ID, with delivery status on every message.
- 02Email from your domainBuilt-in Jump Mail, with per-message open tracking.
- 03Templates and merge fieldsConsistent wording, personalised per patient, from a shared message library.
- 04Secure expiring linksDocuments, questionnaires, booking tasks and video calls in one link, with expiry you control.
- 05Shared team inboxSaved views, assignment to people or teams, tags, and internal notes with @mentions.
- 06Inbox automationSubmissions and bookings open conversations and set status and priority by rule.
- 07Automated sendsWorkflows send email, SMS and questionnaires on the triggers you define.
- 08Preferences and quiet hoursPer-patient email, SMS and push opt-ins, honoured on every send.
- 09Patient education in contextPatient.info leaflets found and shared without leaving the consultation.
- 10Credit visibilitySMS balance and low-balance alerts on the connection card in the App Store.
- 11Communication feed and logsEvery send, delivery and response logged per patient, plus practice-wide logs.
- 12Connection health you can seeEach connection carries a live status - connected, action needed, failing.
Common questions
Questions, answered.
What practices ask before moving patient messaging onto Jump. If yours is not here, ask us on a demo call.
More integrations
The rest of the stack.
Each connected area works the same way: a clinical workflow that lands on the patient record, not a sync job that lands in a spreadsheet.
See a message land.
Thirty minutes with your own templates: sent from your number and your domain, delivered, logged, and answered in one shared inbox.