Early access. The sandbox is open now; production keys open at launch. How going live works

A wellbeing check-in for HR, rota, intranet and learning platforms

For product teams · Updated 29 September 2026

You can add an anonymous three-question wellbeing check-in to your HR, rota or staff app with the Intelligent Wellbeing Engine, using one iframe and three API calls on your server.

The IWE hosts the check-in, stores each answer under a pseudonym and returns organisation-level results for every employer you serve. Your product brings the people, decides where the check-in appears and draws the results screen. Below are four kinds of product, with what the integration looks like in each.

What every integration shares

Each employer customer is one unit in the IWE, and each person is your own opaque user ID, never a name. Your server keeps that roster up to date with POST /respondents:sync, up to 500 people per call. Rounds run fortnightly for each employer, and the first round cannot launch with fewer than five active people on the roster.

When someone opens the check-in, your server asks for an embed token that lasts ten minutes and works for that one person, and your page shows the returned address in an iframe. GET /respondents/{id}/checkin tells you whether a check-in is due, so the entry point only shows when there is something to answer. Your results screen reads GET /aggregates for each employer, with the interval, the provisional label and any withheld rows exactly as the IWE returns them.

HR, HRIS and payroll software

An HR team that keeps its people records in your product gets asked how the workforce is doing. Answering with a separate survey tool means a second copy of the employee list to maintain and one more login for every employee.

The roster already lives in your product. Sync each employee's ID from their HR record when they start, and set them to inactive when they leave, which also stops them counting as an enrolled user. The IWE accepts three optional bands, for age, length of service and working pattern, but no result uses them today. Put the check-in where employees already sign in, such as the self-service home screen or the page where they view payslips or book leave, as a card that appears while a round is open. HR administrators then see their own organisation's results inside your product.

The embed quickstart has the iframe code and the three calls.

Rota, scheduling and frontline apps

Many frontline staff have no work email address and no desk. The rota app on their phone is how work reaches them, so a survey sent by email can miss them.

Your staff list for each employer is the roster. Keep it at one unit per employer. The IWE has no site, shift or team breakdowns, because small groups are how people get identified. On a phone, the check-in works as a full-screen sheet opened from the home screen or after a shift ends. If your app sends the "your check-in is open" notification, GET /respondents/{id}/reminder-eligibility allows one invite and at most one reminder per round, and the reminder only once the round has been open for 48 hours. On a shared tablet, request the embed token after the person signs in, never before, and remove the frame when they close the thank-you screen or sign out. A native app that cannot show a web page can drive the same questions through the API and draw its own screens.

The embed quickstart includes the message handling your frame needs.

Intranets, internal comms and staff apps

An intranet or staff app is where people already go for company news, policies and HR links. A check-in placed there needs no new app and no new password, and the team that runs the channel can promote it alongside everything else it publishes.

Your product already keeps a user directory for each customer, often synced from the customer's sign-in provider, so use your own user ID for each person. The check-in fits a homepage tile, a side panel, or a card in the news feed that opens it. Your own notifications can carry the invite and the one reminder, checked against the reminder-eligibility call before each is sent.

Start from the embed quickstart.

Learning platforms

If your customers run wellbeing courses and resources through your platform, their learning teams will want to show how the workforce is doing over time. A fortnightly check-in in the same platform gives them an organisation-level measure beside the courses. It cannot show that a course caused a change. A rising index next to a course is an association, and the interval shows how much weight it can bear.

The learner list you hold for each customer organisation is the roster. Place the check-in on the learner's home screen or dashboard, outside any course. It gives the person no score, so it does not work as a graded activity or a completion requirement. Results come back for the whole organisation only, so they cannot be split by course, cohort or department, and they cannot be matched to anyone's learning record.

The embed quickstart works against the free sandbox today.

Can we put our own brand on it?

Around the check-in, yes. The page it sits on, your navigation, the words that introduce it, and where the frame goes and how large it is are all yours. Your results screen is your own design, as long as it shows the interval, the provisional label and withheld rows as the IWE returns them.

Inside the hosted check-in, nobody's brand appears today, ours included. There is no logo and no product name. The check-in uses one fixed, accessible colour scheme and the device's system font, and it follows the person's light or dark setting. You cannot change its colours, font or wording, and the support panel with Samaritans, Mind and the workplace EAP cannot be edited or removed.

If the check-in has to look exactly like your product, your server can drive the same questions through the API while your product draws the screens. The rules the hosted page keeps for you, such as the exact question wording, worded answer options and a thank-you screen with no score, then become yours, and certification checks them.

What does it cost?

10p per enrolled user per month, up to 100,000 enrolled users, with a £250 monthly minimum in production that covers the first 2,500. The sandbox is free. Only Tier 1 is sold today. It covers the fortnightly check-in, its results, the OWHS export and the API. Deep dives and signposting to your own services are coming, not sold yet. Each production licensee will have its own database.

An employer measuring its own staff, on its own intranet or anywhere else, uses the IWE free at alltoogether.com. This site is for products that offer the check-in to other organisations. The full rate card is on the pricing page.

Start building: get sandbox keys · the integration guide · what the open export contains · how going live works · questions to hello@wellbeingengine.io