The composer sits pinned under the conversation. SMS and Email are toggles; Call is the third control in the same group and starts an in-app call to that contact. A channel that cannot be used says which of the two possible reasons applies — the account is not set up for it, or this particular person has no number/address on file.
Also called: reply to a customer · send a text from the CRM · composer · message box
- 1Sends post to /api/comms/send, which routes through the org's provider chain rather than straight to GoHighLevel
- 2The composer auto-switches to whichever channel is enabled if the current one is not
- 3Email sends get a subject field; SMS does not
- 4Call hands the contact's number to the in-app softphone without leaving the thread
- 5On mobile the toolbar is pinned above the bottom nav so Send is always visible
Sending depended on one particular CRM connection, so a builder without it could not send at all — and the failure came back as a guess about the customer's email being invalid, which was wrong and sent people looking in the wrong place. A contact with no phone number let a rep type an entire message before failing on send, because the disabled tab never said why. Texting, email and calling now sit side by side under the thread, each stating exactly what is missing before anything is typed.
- Sends hard-wired to one CRM regardless of the account's actual provider
- Silent or misleading send failures
- Having to change screens to call the person you are reading about
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →