Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the it-l10n-ithemes-security-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-layout-styles domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-uploads domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the it-l10n-ithemes-security-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-history domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/spreckleydev/wp-includes/functions.php on line 6131 Spreckley launches HealthTech device for Locked-In Syndrome in the UK - Case Study | Spreckley
We are experts at telling your story.
Connecting clients with their customers through integrated public relations, content marketing and media relations campaigns.
Spreckley launches HealthTech device for Locked-In Syndrome in the UK
The client
In summer 2018 we launched the EyeControl, a revolutionary AI-powered healthtech communication device. The device is designed for individuals with Locked-In Syndrome, and enables them to once again communicate with their loved ones and carers in a simple, intuitive, and innovative way.
The goals
The client was keen to gain national coverage around the launch of the device and TV and Radio was a key part of this. As part of the launch, we offered interviews with the CEO of the company, Or Retzkin, to key contacts on how technology is revolutionising patient care and the importance of startups in contributing to these innovations. We also positioned Or as an expert on Locked-In Syndrome.
The achievements
TV coverage
We secured an interview for Or on BBC Two’s Victoria Derbyshire show, talking about the device and about Locked-In Syndrome. The feature ran for over 10 minutes and included an interview with Or and a two minute promotional video of the EyeControl device. The clip was also later loaded onto the Victoria Derbyshire show web page.
Press coverage
In total, the campaign received 28 pieces of coverage, including national, consumer and key trade healthcare titles.
Lead generation
The exposure resulted in EyeControl receiving a number of enquiries from patients and/or their family members who were interested in the device.
