Guides
How routing works
The whole system on one picture
One workflow connects GoHighLevel workflows, your AI agent / API and MCP to Beam. Beam checks the recipient and picks the channel. It sends from both Apple and Android devices.
| Send through | Channel | Recipient or action |
|---|---|---|
| Apple devices | iMessage | Eligible iPhones and a capable line |
| Apple devices | FaceTime Audio | Audio calls |
| Android devices | RCS | Android phones with phone and carrier support |
| Your Beam line | SMS fallback | Other recipients where your line can reach them |
| Beam events | Webhooks / automations | Connected workflows |
RCS is used when the Android recipient's phone and carrier support it; otherwise Beam falls back to SMS. SMS fallback is subject to applicable carrier A2P requirements. SMS fallback after a confirmed failed iMessage is a workspace setting. An uncertain delivery is not automatically re-sent.
Voice AI call and text loop: Beam works alongside a Voice AI agent. The agent calls, then Beam follows up by text or iMessage. Text conversations can hand back to a call. Coordinate your workflow and test the handoff before using it with customers.
Your CRM shows pending, delivered and failed states. Queued does not mean delivered.
Outbound: how a channel is chosen
- Capability check. Before choosing the channel, Beam checks the recipient's messaging capability and the selected line's support.
- Line selection. Auto chooses an appropriate assigned line before sending. For a manual message, your team can choose a specific Blue or Green line in the From menu.
- Sticky pinning. The first number a contact hears from is theirs forever. Their entire relationship lives in one thread on their phone.
- Pacing gate. First touches pass through warm-up caps, business hours, and human-spaced timing. Replies in active conversations skip the gate, because answering fast is human.
- Uncertain delivery stays uncertain. Beam does not automatically re-send a blue-bubble message or switch it to SMS after an ambiguous provider update. A teammate makes any intentional follow-up from the inbox.
Inbound: how replies come back
Replies flow into Beam on an instant event feed and a bounded reconciliation sweep. Beam stores a canonical message identity so the same physical message is shown once even if both paths observe it. An inbound reply lands in the inbox, can wake the assistant when that workspace has deliberately enabled it, and stops any approved follow-up sequence.
Where your CRM fits
Beam is the messaging brain; your CRM stays the system of record. Tags (imessage-sent, imessage-replied, bot-booked-call, bot-handoff) fire your existing workflows, including the AI voice call the moment a lead replies. Setup: Connect your account.