One provider described a client they could not move online no matter what. The organisation was, in their words, very old school. Employees there did not want to use apps. They picked up the phone, called the EAP, asked their questions, and booked that way. The provider was not trying to force them to change. What worried them was the reporting. They still owed that employer a full picture of usage and outcomes, and if those phone bookings lived only in someone's memory and a calendar entry, the report would always have a hole in it.
Here is the direct answer. Complete EAP client reporting does not depend on every employee using your app. It depends on every appointment, however it was booked, being captured in one place with the right information attached. A phone-in employee and an app-booking employee can produce identical, fully reportable records, as long as your ops team logs the phone booking into the same system that holds the digital ones. The channel an employee prefers and the completeness of your reporting are two separate problems, and providers tangle them together.
It is worth saying plainly: a branded app does not mean abandoning the phone. Some people will always prefer to call, and for some workforces that proportion is high. Pushing them online against their preference is a good way to lower utilisation, not raise it. The goal is a service that meets people on whichever channel they choose.
So the app is not there to replace the phone for these employees. It is there to be the place all of their data lands, regardless of how they first made contact. That reframing is what makes the old-school client a solved problem rather than a permanent exception in your reports.
The phone call itself is not the issue. The issue is what happens to the information around it. When an employee calls and books, a lot can go uncaptured: which employer they belong to, whether the matter is work-related or personal, the outcome measure at intake, the attendance record. If that detail is not recorded in a structured way, it cannot appear in the client report, and the employer's view of their own EAP usage is incomplete.
For corporate clients who are increasingly demanding about data, an incomplete picture is a commercial problem. It makes utilisation look lower than it is, weakens your renewal position, and invites the question of why your reporting has gaps. The fix is to make sure the phone channel feeds the same data store as everything else.
The practical move is simple. When an employee phones in, your ops team books them the same way they would handle any other appointment, in the platform, attached to the right employer, with the relevant classification fields completed. The booking did not start in the app, but it lives in the same place as the ones that did.
From a reporting standpoint, that appointment is now indistinguishable from a self-booked one. It carries the employer association, the custom fields, the attendance status, the outcome data. When you run client reporting, it is included automatically. The phone-in employee never has to touch a screen, and the employer's report is whole.
There is an additional step worth taking, even with people who called. After the phone booking, your team can send that employee an invitation: a text or email with a download link and a one-time password. They are under no obligation to use it. But many will, because now they have a specific reason, their appointment is already there waiting.
This is how an old-school client base shifts over time without being pushed. You meet them on the phone, capture everything centrally so reporting is complete from day one, and offer the app as a convenience attached to a booking they have already made. Some adopt it, some never do, and your reporting holds either way. It also means that as more employees opt in, your self-service booking volume climbs gradually, which lightens the load on your ops team.
The outcome you are aiming for is a single reporting view that does not care how a booking originated. App, web portal, phone, or an employee your team added by hand all resolve into the same dataset. You filter by employer, by date range, by service, by the custom classifications your client cares about, and you export or share it without assembling anything by hand.
That is what turns reporting from a monthly scramble into a routine task. The data is complete because every channel feeds it, and it is structured because it was captured at the point of booking, not reconstructed afterward.
Wellifiy is built so that the booking channel and the reporting are decoupled. Employees can self-book in your branded app or web portal, and your ops team can add or book anyone who phones in, all into the same platform, all attached to the right employer and the same custom fields. Whether an appointment was self-booked or logged from a phone call, it appears in your exports, your API feed, and the employer reporting view the same way.
For a provider with a mix of digital-native and phone-first clients, that means one clean reporting picture instead of a digital report plus a manual patch for the clients who would not come online. The old-school customer stops being the reason your data has holes.
Do not let the employees who phone in become an asterisk in your reporting. Capture every booking centrally with the right fields attached, offer the app as a convenience rather than a requirement, and let your reporting draw from one complete dataset. The clients who refuse to change can still be fully, accurately reported on. That is a stronger commercial position than carrying gaps you hope nobody asks about.
Wellifiy partners with EAP providers to run and scale a modern employee assistance program from a single platform, including a fully white-labelled employee app published under the provider's own name on the Apple App Store and Google Play. Self-service and team-logged bookings flow into the same dataset, so client reporting stays complete across every channel, including the employees who still phone in. Founded by Clinical Psychologist Dr Noam Dishon (PhD Clinical Psychology).
