Extensions
Live

Scheduling a Chat Message

Draft a chat message now and schedule it to send at a future date and time, useful for planned check-ins, recurring reminders, or messages timed for when you'll be away. Works across 1:1 conversations, Community Chats, Message Blasts, and Organization-level chat, with no limit on how many messages can be scheduled. Scheduled messages can be edited or canceled anytime before they send, and clients see no indication that the message was scheduled in advance.

Built by Core Engineering

The problem it solves

Providers who want to send timely check-ins, reminders, or program-related messages on a predictable cadence would otherwise need to remember to send each one manually at the right moment. This solves that by letting the message be written once and delivered automatically at the chosen time, without relying on the provider to be online when it needs to go out.

What's included

  • Future-dated send scheduling for any chat message
  • Support across 1:1 chats, Community Chats, Message Blasts, and Organization chat
  • Unlimited number of scheduled messages
  • Dedicated Scheduled tab for reviewing, editing, or canceling a pending send
  • No client-facing indication that a message was scheduled in advance

How it works

While composing a message, a provider clicks the dropdown arrow next to Send and selects Schedule Send, then chooses a delivery date and time from suggested options or a custom selection. The message stays pending until that time, viewable and editable from the Scheduled tab within Chat, where a provider can also cancel the send entirely before it goes out. At the scheduled time, the message sends automatically and appears to the client exactly as any other chat message would.

Scheduling a Chat Message lets a provider draft a message and set it to send automatically at a chosen future date and time, rather than sending it immediately. It's built for planning ahead, whether that's a recurring check-in, a weekly reminder tied to a program, or a message meant to go out while the provider is away. The feature works the same way across 1:1 conversations, Community Chats, Message Blasts, and Organization-level chat, and there's no cap on how many messages can be scheduled at once. From the client's side, a scheduled message looks identical to one sent in real time, with no indication it was pre-planned.

Building on Healthie?

Talk to our team about API access, white-label, and enterprise architecture — or dive into the docs.