|
| 1 | +--- |
| 2 | +title: "Improving uptake" |
| 3 | +description: "Redesigning invites, reminders, and the journey from invite to start." |
| 4 | +date: 2025-12-19 |
| 5 | +--- |
| 6 | + |
| 7 | +The NHS Health Check online service is currently in private beta. As users of the service increased, we began to observe how they interacted with the service and where drop-off occurred across the early stages of the journey. |
| 8 | + |
| 9 | +Early data showed that uptake from the initial invite was lower than expected. At the same time, we had limited visibility of user behaviour prior to accepting the terms and conditions, which made it difficult to understand where and why users were dropping out. |
| 10 | + |
| 11 | +This design iteration focused on improving: |
| 12 | + |
| 13 | +- the effectiveness of invites and reminders |
| 14 | +- the clarity of what the NHS Health Check involves |
| 15 | +- the journey from receiving an invite to starting the service |
| 16 | +- the quality of data available to measure engagement and drop-off |
| 17 | + |
| 18 | +## Problem definition |
| 19 | + |
| 20 | +We identified 3 issues: |
| 21 | + |
| 22 | +1. Low uptake from the initial invite |
| 23 | + |
| 24 | +Fewer people than expected were starting the service after receiving an invite. We hypothesised that this was because the service was hard to find because we could not link directly to the service. |
| 25 | + |
| 26 | +2. Limited journey insight |
| 27 | + |
| 28 | +We were only capturing data once users reached the terms and conditions page (approximately three screens into the journey). We could not see: |
| 29 | + |
| 30 | +- whether users were opening the invite link |
| 31 | +- where drop-off was occurring prior to service start |
| 32 | + |
| 33 | +3. Friction between invite and service start |
| 34 | + |
| 35 | +Due to technical constraints, we were unable to deep link directly to the service start page as we had initially hoped. Users had to navigate from the NHS App home screen to find the service. |
| 36 | + |
| 37 | +## Research and discovery |
| 38 | + |
| 39 | +### Understanding user needs and motivations |
| 40 | + |
| 41 | +To understand why people were not starting the service, we: |
| 42 | + |
| 43 | +- interviewed 6 users who had received an invite but not started the journey |
| 44 | +- ran a survey with 56 panel members |
| 45 | +- explored attitudes to invites, reminders, nudges, and motivations for completing a health check |
| 46 | + |
| 47 | +### Findings |
| 48 | + |
| 49 | +The most common reason for not starting was "life getting in the way", rather than lack of interest. |
| 50 | + |
| 51 | +Reminders were seen as essential to prompt action. |
| 52 | + |
| 53 | +A key motivator was "keeping on top of my health". |
| 54 | + |
| 55 | +Users wanted: |
| 56 | + |
| 57 | +- a clear indication of how long the health check would take |
| 58 | +- a deadline, which helped create a sense of priority (6 weeks to 3 months felt appropriate) |
| 59 | +- reassurance that the check did not need to be completed in one sitting |
| 60 | + |
| 61 | +We also identified opportunities to improve clarity on the early pages of the journey, particularly around expectations and commitment. |
| 62 | + |
| 63 | +## Designing and testing improvements |
| 64 | + |
| 65 | +We worked with the behavioural science team to design several invite and reminder options, informed by the research findings. These explored: |
| 66 | + |
| 67 | +- different framings of the NHS Health Check |
| 68 | +- varying degrees of personalisation |
| 69 | +- reminder timing and tone |
| 70 | + |
| 71 | +We tested these using mock-ups with 8 users, asking them to compare options and explain their preferences. |
| 72 | + |
| 73 | +### Constraints |
| 74 | + |
| 75 | +Invite and reminder messages needed to remain within two SMS fragments to manage costs. This significantly constrained content and required careful prioritisation of language — often described by the team as "playing word Jenga". |
| 76 | + |
| 77 | +### What we took into research |
| 78 | + |
| 79 | +#### Revised invite message options |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +#### Two reminder message variants |
| 84 | + |
| 85 | + |
| 86 | + |
| 87 | +#### Updates to the first pages of the service start journey |
| 88 | + |
| 89 | + |
| 90 | + |
| 91 | +## Learnings |
| 92 | + |
| 93 | +From user research and interviews with GP staff, we learned that: |
| 94 | + |
| 95 | +A sequence of one invite, followed by a reminder after 5 days, and a final reminder 5 days later felt appropriate and aligned with patterns seen in other services. |
| 96 | + |
| 97 | +Wording matters: |
| 98 | + |
| 99 | +- "Your free NHS Health Check is due" felt too broad and unclear |
| 100 | +- "Check your heart health" felt too narrow for some users |
| 101 | +- Users responded most positively to language that explained what the check helps identify, which they saw on the service start page |
| 102 | + |
| 103 | +Referencing "Your GP has asked you" felt more personal and trustworthy. |
| 104 | + |
| 105 | +The tone of the final reminder initially felt too threatening and was softened based on feedback. |
| 106 | + |
| 107 | +## Deep linking and journey tracking |
| 108 | + |
| 109 | +Previously, technical constraints with local GP messaging service providers meant we could not deep link from the invite directly to the service start page. This required us to use valuable message space to explain how to navigate via the NHS App home screen. |
| 110 | + |
| 111 | +At the same time as deploying the updated invites and reminders, we: |
| 112 | + |
| 113 | +- implemented deep linking directly to the service start page |
| 114 | +- introduced improved journey tracking, allowing us to measure invite link opens and drop-off prior to terms and conditions |
| 115 | + |
| 116 | +This allowed us to test our hypothesis about early journey friction and significantly improved our ability to understand uptake. |
| 117 | + |
| 118 | +## Early insights |
| 119 | + |
| 120 | +The updated invite, reminder sequence, journey improvements, deep linking, and enhanced tracking are now live. |
| 121 | + |
| 122 | +Early indicators suggest: |
| 123 | + |
| 124 | +- increased uptake compared to the previous approach |
| 125 | +- improved visibility of user behaviour from invite click through to service start |
| 126 | + |
| 127 | +We are continuing to monitor uptake and engagement as more data becomes available. |
0 commit comments