Setup

For HighLevel administrators connecting a Evergrove Healthcare sub-account. Takes about 15 minutes.

Evergrove iMessage is a private app. It can only be installed on sub-accounts that Evergrove Healthcare has enabled, and each one must be connected to our Blooio line pool before messages can flow. If you're not sure yours is, contact your Evergrove Healthcare administrator first.

Before you start

You're an admin on the HighLevel sub-account.
LC Premium Triggers & Actions is turned on for the sub-account. HighLevel bills each run of a premium action, currently $0.01.
The sub-account keeps LeadConnector as its default SMS provider. Evergrove iMessage adds a separate iMessage channel next to it. It does not replace SMS.
If the sub-account uses the public Blooio HighLevel app, Evergrove Healthcare disconnects it during cutover so the pool lines are owned by this app only.

1. Install the app

Open the install link Evergrove Healthcare sends you, and sign in to HighLevel if asked.
Choose the sub-account (for example Voyager Recovery Center) and approve the permissions.
You'll land on a page that says "Evergrove iMessage is installed". You can close that tab.
The app creates a contact field named iMessage Line. It shows which pool number each contact is on. It's for information only; changing it does not change routing.

2. Send from Conversations

Open any contact's conversation. Next to SMS and Email you'll see an iMessage channel. Messages sent there go out through the pool. Replies come back into the same conversation, and the message shows Delivered, Read or Failed as Blooio reports it.

3. Build a workflow

In a workflow, click + and search for Evergrove iMessage. There are two actions.

Send iMessage (Pool)

Field	What to enter
Message	The text to send. Custom values like `{{contact.first_name}}` work.
Attachments	Optional. Public `https://` links to images or files, separated by commas.
Pool	Leave blank to use the default pool. Evergrove Healthcare gives you a pool ID if you have more than one.
If not iMessage	Branch (recommended): the action checks the contact first and, if they aren't on iMessage, takes the Not iMessage branch without sending. Fall through to Blooio SMS: send anyway and let Blooio's SMS tier handle it.

Branches: Sent, Not iMessage, Failed.

Values you can use in later steps: sent, from_number (the pool line used), channel_type, protocol, blooio_message_id, error_code.

Check iMessage Availability

No fields. Branches Yes and No, plus an imessage value (true/false). Use it when you want to decide the channel before composing a message.

Recommended pattern

Trigger (e.g. Form Submitted)
 └─ Send iMessage (Pool)
     ├─ Sent          → continue the workflow
     ├─ Not iMessage  → Send SMS (native LeadConnector action)
     └─ Failed        → Internal Notification to staff

For replies, use HighLevel's native Customer Replied trigger.

4. Test it

Run the workflow on a test contact with an iPhone. The message should arrive as a blue iMessage, appear in the conversation, and turn Delivered. The contact's iMessage Line field fills in.
Send again. It should come from the same number.
Reply from the iPhone. The reply appears in the same conversation.
Run it on an Android contact. The workflow should take Not iMessage and send a regular SMS.

Good practice

Message only contacts who have agreed to hear from you, and honor opt-outs right away.
Keep messages short and personal. iMessage lines are protected by sending limits: a new contact can get up to three messages before they reply, and links or media are held until they've replied once.
Never put diagnoses, treatment details or other clinical information in a text. Ask the person to call or use a secure channel.

Something not working? See Support.