A treatment companion with a job to do.

A messenger could help patients manage small, repeated tasks during a treatment course. But a chat interface alone would not make the program useful. Each message needed a purpose.

I led the patient support and IT work, connecting the pharmacy offer, conversation design and reporting.

Give each message a next step

The companion used scripted questions, buttons and triggers. Registration explained the rules and collected consent.

The design included configurable reminders, progress confirmations and a way to add a missed record. It also covered reminders for physician visits and purchases. Each message asked the patient to do something specific.

Let patients control participation

Communication preferences and an exit process were part of the design. Patients needed a way to change or end participation as well as join.

We defined how the conversations, pharmacy benefits and reporting would fit together. This gave the team a common specification for a scripted assistant, rather than an open-ended AI conversation.

Give each record a clear meaning

A purchase, a reminder response and a progress update were different events. A patient’s confirmation did not independently prove that they had taken a dose.

We kept those distinctions in the reporting design. The result was a chatbot program with defined actions and records the team could interpret consistently.