# Put each participant’s full context in front of their counsellor.

A health coaching company’s counsellors work with participants across app messages, calls and sessions, and stitching one person’s full history together before each conversation is manual. The system is drawn to carry that context on one screen per participant, with the next nudge already drafted for the counsellor to approve.

Domain: Health coaching
Label: Designed

## Architecture

- **Aggregate**: Every channel a participant used lands in one updating timeline: messages, calls and sessions.
- **Profile**: A short set of profiles per participant stays current as new information arrives.
- **Summarize**: A weekly summary is drafted from the timeline and the profiles.
- **Flag**: A participant showing a missed session, a skipped step or a change in tone is flagged for the counsellor.
- **Draft**: The next nudge is drafted from the summary and the flag, ready for the counsellor to read.
- **Approve**: The counsellor reads the screen and decides the next nudge; nothing reaches the participant unapproved.

Boundary (a person decides): The system aggregates, profiles and drafts the next nudge. The counsellor decides what reaches the participant, every time.

## Scope

Mapped how a counsellor covers a caseload today, across every channel a participant uses, and designed the system to carry it.

Not built for the company, and not running. The demo on this page is ours, on synthetic participants.

## Anonymized

The company, its participants and every message and log are left out. Every participant in the demo is synthetic.

## The situation

Each participant’s record is scattered across the channels they used that week: an app message here, a phone call there, a session note somewhere else. Before a counsellor can decide what to say next, they first have to reassemble what already happened.

The next outreach to a participant runs on a fixed cycle, so how well it lands depends on how much of that scattered history the counsellor pieced together in time. That reassembly is the same manual work whether the caseload is ten participants or a thousand.

## What the design settles

This system is designed, not running, so what follows is what the design decides, not a result.

- Which channels feed the one timeline, and how often each profile updates.
- What counts as a flag worth a counsellor’s attention, and what’s routine.
- What the weekly summary contains before a counsellor reads it.
- What the counsellor sees first for an at-risk participant, and why.

## Demo

[Open the demo](https://octyn.co/casestudies/participant-context/demo)

## Related

- [Operations systems](https://octyn.co/systems/operations)
- [Move a cross-border order from quote to delivery without the email chain.](https://octyn.co/casestudies/trade-order-desk/demo)
- [The Consult](https://octyn.co/consult)

Canonical: https://octyn.co/casestudies/participant-context