Skip to main content

Outreach

The recall list is built before you ask for it.

Brigid builds the worklist from the criteria your clinic sets. Your staff review it, author the message and release it through the clinic’s connected email. Nothing reaches a patient without a person deciding it should.

Staff recall queue

Synthetic example · provider approval required

Staff-authored message: Hi Mary — please contact the clinic if you would like to book a check-up.

Staff reviewed and sent this message

One visit, start to finish

Follow it through the day.

Monday · Worklist ready

Recall lists, prepared

Brigid builds the recall worklist from the criteria your clinic defines — who, when and why are yours. It arrives ready for review, not sent.

Reviewed · Released by Aoife

Every message, in your words

Staff author and release each message through the clinic’s connected Gmail or Outlook. The patient hears from the practice, not from a system.

DNA · Queued for staff

No-show follow-up that waits for you

A missed appointment raises a follow-up for the team. It sits in the queue until someone releases it.

11:40 · Slot freed

Waitlist backfill

When a slot opens, the waitlist is offered it and staff confirm the rebooking. The diary fills without the phone ringing.

Step 3 of 5 · Awaiting approval

Campaigns that pause at every send

Build a sequence, set the approvals. A campaign runs exactly as far as the last person who signed it off.

By design

What is switched off

Autonomous sending, voice calls and channel escalation are disabled. Reporting on delivery is shown only where the connected provider returns reliable status.

Integrates with

GmailOutlook
See all integrations

Catch the patients who go quiet.

See a recall worklist reviewed and released with synthetic data. Every message on it was released by a person.

Request early access