Employers and wellbeing providers

Health agents for workplace wellbeing programmes.

Health Loops run the parts of a wellbeing programme that need follow-through: onsite health checks, the call-back for anyone due one, and regular check-ins. Built for employers, occupational health teams and the providers who serve them.
Teams that already run on Ollie
The problem

What a health day leaves behind

“Health days end in a spreadsheet.”

Readings are taken, then sit in a file nobody follows up.

“The people who need a call-back don’t get one.”

Follow-up depends on someone working through a list by hand.

“Staff worry about who sees their results.”

Without clear limits, people skip the check.

“We can’t show the programme was used.”

Leaders want participation and trends, not anecdotes.
How the loop works

How a loop runs a programme

  1. A kiosk or a link starts it. An employee scans at an onsite kiosk or on their own phone, after a consent screen.
  2. Readings meet reference ranges. Rule-based checks against published adult ranges, with the source cited on every result.
  3. The employee gets the report. A wellness snapshot and a PDF report link, sent to them.
  4. Follow-up for anyone due. A loop calls the employee to offer a call-back from your health team.
  5. Reports from aggregates. Build programme reports from totals and trends, so individual readings stay with the employee and your health team.
health-day-follow-up.tsTypeScript
interface FollowUp { employeeId: string; phone: string; site: string }

export class HealthLoop extends Workflow {
  async run(event: HealthEvent<FollowUp>, step: HealthStep) {
    const { employeeId, phone, site } = event.body;

    const { sessionId } = await step.do("Follow-up call", async ({ ctx }) => {
      const employee = await ctx.USER.getUser({ id: employeeId });
      return ctx.startVoice({
        loopId: "health-day-call",
        user: employee,
        to: phone,
        body: { site },
      });
    });

    const call = await step.waitForVoiceComplete({
      sessionId,
      timeout: "1 hour",
    });

    // Only your occupational health team sees the summary.
    await step.do("Send to occupational health", async () => {
      await fetch(`${this.env.OH_API}/follow-ups`, {
        method: "POST",
        body: JSON.stringify({ employeeId, site, summary: call.summary }),
      });
    });

    return { site, turns: call.transcript.length };
  }
}
Channels and integrations

What the loop works with

Kiosks and phones. The same scan runs on an onsite kiosk or the employee’s own phone, behind a consent screen.
Phone calls. Outbound calls to a phone number, or a browser call from your app. Each call ends with a transcript and a summary.
SMS. One message or up to 500 at once, with opt-out checks and timed delivery.
Member memory. One record per person, shared by every loop, so each journey starts with what the last one learned.
Your own systems. Loops call your endpoints to read data and send results back. Your systems start loops with one authenticated API call.
Data and compliance

How data is handled

Aggregates for the employer. You decide what each report contains. Build employer reports from totals, and keep individual readings with the employee and your health team.
Your own data plane. Each organisation’s loops, runs, members and keys live in that organisation’s own store, apart from every other customer.
Consent first. Every scan starts on a consent screen, and the intake asks only for the fields you choose.
A record of every run. The trigger, each step and its result, every tool call, every log line and every error are kept for your team to review.
FAQ

Questions

What does Health Loops do for an employer wellbeing programme?

Health Loops runs the follow-through of a programme as health agents written as code: onsite health checks at kiosks or on phones, follow-up calls for anyone due one, regular check-ins and programme reports built from aggregates.

Does the employer see individual results?

That is your choice, and the loop’s code makes it explicit. You can send individual readings only to the employee and their health team, and give the employer totals and trends.

How is this different from the Ollie Health Agent?

The Health Agent is a ready-made health companion for staff on WhatsApp, mobile and desktop. Health Loops is the platform underneath, for teams that want to build and run their own journeys.

Can the loop book the follow-up?

The follow-up call takes the employee’s request and passes it to your health team with the call summary. If your booking system has an API, the loop can book the slot directly.

Show us the journey costing you the most. We’ll show you the loop.