Help

How do replies get into my CRM?

Over webhooks, or natively for GoHighLevel. The moment a lead replies, Blue Reacher posts the message to a URL you own with four fields: from, content, channel, and external_id. In GoHighLevel, replies sync straight into Conversations with nothing to build. Either way, the reply lands on the CRM record while the lead is still holding the phone.

Each field has one job. "from" is the lead's number, the key you match against a CRM record. "content" is the raw text they wrote, which is what a routing rule reads. "channel" returns imessage, rcs, or sms, so your workflow knows what the thread can carry before it sends an attachment. "external_id" is the stable message ID that keeps a thread threaded and stops the same reply being processed twice. Full payloads are on the webhooks and API page.

Delivery events ride the same pipe, keyed to the same external_id you got back at send time. Your CRM learns that a message was sent, delivered, or read, that it did not complete on the rail it was tried on, or that the contact opted out, without anyone opening the platform. Operators gate sequence steps on delivery, trigger nudges on read-with-no-reply, and stamp every state change on the record.

Push beats polling for a reason that shows up in revenue: a webhook fires the instant the event happens, so the workflow triggers and the rep gets pinged while the lead is still engaged, instead of on the next polling cycle. On a channel where most messages are read within minutes, that difference decides whether the rep gets a conversation or a voicemail.

For GoHighLevel teams none of this needs building: replies, opt-outs, and delivery states sync into GHL natively. Other tools with prebuilt paths are on the integrations index.

Updated August 9, 2026