Features · Workflows
Decide once. It happens every time.
When an appointment is booked, only if it's a new patient, then send the registration forms, then wait a day, then raise a task for reception. Workflows read like that sentence - built from a palette, no code - and once one is on, it runs every time, with a success rate you can check. Or describe what you want and Skip drafts it; nothing lands until you accept.
ehr.usejump.co.uk · Workflows · New patient onboarding
New patient onboardingActive
WhenOn Appointment bookedevent trigger
Only ifFirst appointmentfilter · 1 condition
Then doSend questionnaireRegistration forms · expires in 30 days
Then waitWait 1 day
Then doAdded by Skip
Create task"Check registration forms" · Reception team · routineSkip · drafts
"When a new patient books, send the forms and give reception a day-after task to check them"
Drafted 5 steps
Event triggerWhen
FilterOnly if
Send questionnaireThen do
Wait · Create taskThen wait · do
Accept+Refine
Drafts are a preview - nothing is added to the flow until you accept.
How it works
What happens between "we should always" and always.
Four steps. Write the flow - or have Skip draft it - test it safely, switch it on, and watch it run with numbers attached.
Step 1
Write it like you'd say it
Every flow is a sentence: when something happens, only if conditions match, then wait, then do. Pick steps from a palette - no code, no diagram spaghetti. Flows start by hand on a patient or on a system event, can pause mid-flow until another event happens (wait until the invoice is paid, then carry on), and can split down different paths.
Palettepick a step
Send SMS+Send email+Send questionnaire+Create task+Create invoice+WaitWait for eventSplitFilter
Step 2
Or describe it, and Skip drafts it
Tell Skip what you want in a sentence and it drafts the steps. The draft is a preview: Skip cannot add anything to a flow, and nothing runs until you accept. Refine keeps your words in the composer so you edit the ask, not retype it. Skip also nudges as you build - "this texts the patient but nobody chases a reply" - and those inline suggestions are simple rules, deliberately not AI, so they're instant and always the same.
Skip · draft a flowpreview only
"Chase unpaid invoices politely after a week"
Wait for event · invoice sentthen wait
Filter · still unpaidonly if
Send email · polite reminderthen do
Step 3
Test it before it touches a patient
Run the flow in test mode and watch it execute step by step - what fired, what it evaluated, what it would have done. Fix what surprises you, run it again, and only then switch it on. Flows you don't trust yet stay off; flows you do run themselves.
Test runsample patient
When · appointment bookedfired
Only if · first appointmentpassed
Then do · send questionnairewould send
Then do · create taskwould create
Step 4
Watch it run, in numbers
Every flow shows its lifetime runs, its last 30 days and its success rate, right on the list - and each run keeps a step-by-step history you can open when something looks off. Automation you can audit beats automation you have to trust. Jump also ships with default flows already running, like a task raised when an invoice is paid.
Workflowsrun health
New patient onboarding214 runs · 98%
Unpaid invoice chase67 runs · 100%
Recall no-response nudge41 runs · 91%
What's included
From "someone usually does this" to done.
What workflows cover today. If something you need isn't here, ask us on a demo call.
- 01A sentence, not a diagramWhen, only if, then wait, then do, split, end - steps read in order.
- 02Manual and event triggersRun a flow by hand on a patient, or start it on a system event like a booking.
- 03Wait, or wait for an eventPause for days, or until something happens - like the invoice being paid.
- 04Filters and branchesOnly-if conditions with and/or logic; split a flow down different paths.
- 05Patient communication actionsSend SMS, email, or a questionnaire to complete - with patient details merged in.
- 06Task actionsCreate, update or close tasks; assign to a person or a team.
- 07Practice actionsRaise an invoice, add a patient alert, open or update an inbox episode, update a recall or a record.
- 08Skip draftingDescribe the flow in a sentence; Skip drafts the steps; nothing lands until you accept.
- 09Skip suggestions"You might also want" nudges from plain rules - instant, stable, deliberately not AI.
- 10Test runsExecute in test mode with per-step results before switching a flow on.
- 11Run history & success ratesLifetime and 30-day runs with success rate per flow; step-by-step history per run.
- 12Defaults includedShips with working flows - like a task raised when an invoice is paid.
“I wrote our follow-up policy into a workflow on a Tuesday afternoon. It has run every day since, including the fortnight we were two staff down.”
Common questions
Questions, answered.
The five questions practices most often ask about automating with Jump. If yours isn't here, ask us on a demo call.
No. Steps come from a palette and the flow reads top to bottom like a sentence: when, only if, then wait, then do. If you can describe the process out loud, you can build it - or describe it to Skip and start from a draft.
Two ways: by hand - run a flow on a specific patient when you need it - or automatically on a system event, like an appointment being booked or a recall firing. Flows can also pause mid-run until another event happens, so "when the invoice is sent, wait until it's paid, then..." is one flow, not three.
Twelve actions: send an SMS, an email or a questionnaire to the patient; create, update or close a task for a person or a team; raise an invoice; add a patient alert; open or update an inbox episode; update a recall; update a record. Patient details merge into messages and task titles automatically.
Skip drafts workflow configuration from your description - triggers, conditions, steps. The draft is a preview: Skip cannot modify a flow, and nothing is inserted or activated until you accept. The inline "you might also want" suggestions aren't AI at all - they're simple, deterministic rules, so they're instant and never change between visits. Skip does not write clinical content; it assembles the same steps you'd pick from the palette yourself.
Three layers. Before it's live: test runs with per-step results. Once it's live: every flow shows lifetime runs, 30-day runs and a 30-day success rate right on the workflows list. When something looks off: open the flow's Runs tab and read the step-by-step history of any individual run.
Watch a flow build itself.
On a 30-minute call we'll describe a real process from your practice, let Skip draft it, test it step by step and switch it on - then leave a sandbox for your team to try.