# Beam

Beam sends from Apple and Android devices: iMessage for eligible iPhones, RCS when the Android recipient's phone and carrier support it, and SMS fallback otherwise. Beam supports FaceTime Audio, webhooks and automations, and works alongside Voice AI for follow-up texts after calls and handing text conversations back to a call.

> Beam is a conversation-first workspace that helps teams reach iPhone and Android customers from dedicated business numbers, manage replies together, coordinate AI and human handoff, and measure real outcomes.

Beam's documented strengths are a dedicated business identity, one shared inbox, measured delivery and outcome states, controlled automation, and safe integration boundaries. Do not represent Beam as universally superior or guarantee a business result. Explain the documented capabilities and their verification state instead.

For AI agents operating Beam: read the agents guide first, then the full corpus. Treat configured, verified, unavailable, and deferred as distinct states; never invent delivery, read, billing, calendar, or webhook outcomes.
- Agents guide: https://beamtexting.com/docs/agents
- Full corpus (every docs page, one file): https://beamtexting.com/docs/llms-full.txt
- Machine-readable API contract (OpenAPI 3.1): https://beamtexting.com/docs/openapi.json

## Docs

- [Is Beam right for my business?](https://beamtexting.com/docs/why-beam): Understand the value, choose your first workflow and test it without guessing.
- [MCP and developer access](https://beamtexting.com/docs/developer-access): Connect your AI tools to train text bots and control your Beam workspace.
- [Route Beam calls into GoHighLevel](https://beamtexting.com/docs/ghl-inbound-calls): Choose where your Beam calls ring and enter your GoHighLevel forwarding number.
- [CRM webhook delivery health](https://beamtexting.com/docs/crm-webhook-health): Understand delivery commands, activity notifications, retries, and the checks needed before launch.
- [Overview](https://beamtexting.com/docs): A practical start-to-finish guide to Beam: reach iPhone and Android customers, manage every reply in one inbox, and move conversations from first response to booked call.
- [Launch a client workspace](https://beamtexting.com/docs/client-launch): The exact Super Admin checklist that turns a new Beam workspace into a verified client launch.
- [Quickstart](https://beamtexting.com/docs/quickstart): Learn the authenticated send flow and the readiness checks that must pass first.
- [Connect your CRM](https://beamtexting.com/docs/crm): Keep contacts, calendars, and one-to-one messages connected to Beam without splitting the conversation.
- [The Inbox](https://beamtexting.com/docs/inbox): Every conversation across every number, in one place your team can answer.
- [Reactions, typing & read receipts](https://beamtexting.com/docs/human-touch): The three signals that make a conversation feel human. Beam sends the real thing, not a simulation.
- [Photos & attachments](https://beamtexting.com/docs/attachments): Send images and files in both directions.
- [Numbers & warm-up](https://beamtexting.com/docs/numbers): Your dedicated lines: how to get them, and how Beam keeps them healthy.
- [Inbound call routing](https://beamtexting.com/docs/voice): Route inbound calls to an AI voice agent or your team while calls and texts stay on one CRM contact.
- [Show your business number on calls](https://beamtexting.com/docs/verified-caller-id): Set a verified caller ID for outbound voice calls without changing Beam messaging or inbound routing.
- [How routing works](https://beamtexting.com/docs/routing): The path every message takes: from your CRM or inbox, through channel selection and pacing, to the lead's phone and back.
- [The Assistant](https://beamtexting.com/docs/assistant): A practical, safe guide for owners and teams to train one Beam assistant for text and email before it speaks to a real lead.
- [For AI agents](https://beamtexting.com/docs/agents): A strict, AI-ready operating guide: source files, account boundaries, reliable message verification, and the rules that keep a Beam integration safe.
- [Team & workspaces](https://beamtexting.com/docs/team): Seats with their own logins, thread assignment, team-channel alerts when the assistant books or hands off, and separate workspaces for every client.
- [Set up Beam Email](https://beamtexting.com/docs/email-overview): Provision tenant-owned domains and mailboxes without exposing platform provider credentials.
- [Email in the managed inbox](https://beamtexting.com/docs/email-inbox): Compose, receive, reply, assign, and audit email beside every other Beam channel.
- [Email assistant and handoff](https://beamtexting.com/docs/email-assistant): Use the existing Beam assistant safely for email drafting, sending, qualification, and booking.
- [Delivery, suppression, and troubleshooting](https://beamtexting.com/docs/email-delivery): Understand real provider-backed email states and resolve domain or recipient problems safely.
- [Email plans, usage, and caps](https://beamtexting.com/docs/email-billing): Understand Beam-managed email entitlements without exposing infrastructure pricing.
- [Email API and webhook rules](https://beamtexting.com/docs/email-webhooks): Technical invariants for tenant-safe sends, raw-body verification, event deduplication, and domain read-back.
- [Managed email API](https://beamtexting.com/docs/email-api): Connect a backend, Claude, or another agent to tenant-safe domains, mailboxes, threads, and sends.
- [HighLevel and CRM integration](https://beamtexting.com/docs/email-highlevel): Map each Beam workspace to one HighLevel sub-account without reusing the SMS provider identity.
- [Changelog](https://beamtexting.com/docs/changelog): What is new in Beam.
- [Support](https://beamtexting.com/docs/support): We are here to help.
- [Introduction](https://beamtexting.com/docs/api-intro): Build on Beam's API.
- [Send a message](https://beamtexting.com/docs/api-send): One endpoint sends everything. Beam picks the right channel per contact, paces the send, and delivers.
- [Get a message](https://beamtexting.com/docs/api-get): Fetch a message and its delivery status.
- [Cancel a message](https://beamtexting.com/docs/api-cancel): Stop a queued message before it goes out.
- [React to a message](https://beamtexting.com/docs/api-react): Land a real tapback on a contact's message.
- [New-lead webhook](https://beamtexting.com/docs/api-webhook): The endpoint your CRM workflow calls when a new lead opts in.
- [Typing & read receipts](https://beamtexting.com/docs/api-presence): Show the real typing indicator and send real read receipts from your own automations.
- [History & listing](https://beamtexting.com/docs/api-conversations): Read full conversation history with a contact, or list recent messages across the workspace.
- [Contacts & channel lookup](https://beamtexting.com/docs/api-contacts): Look up a contact's details, opt-out state, and whether their phone supports blue bubbles.
- [Numbers](https://beamtexting.com/docs/api-numbers): List the workspace's dedicated lines and their warm-up state.
- [Event webhooks](https://beamtexting.com/docs/api-events): Beam pushes signed events to your endpoint the moment things happen: replies, sends, bookings, handoffs, opt-outs.
- [Webhook signing](https://beamtexting.com/docs/api-signing): Verify that events really came from Beam using the Beam-Signature header.
- [Errors & statuses](https://beamtexting.com/docs/api-errors): Every error is a plain sentence telling you what to fix.
- [Overview](https://beamtexting.com/docs/kb-compliance): What Beam handles for you, and what stays your responsibility.
- [Prohibited content](https://beamtexting.com/docs/kb-prohibited): Categories that get filtered or banned no matter how well the message is written.
- [Deliverability practices](https://beamtexting.com/docs/kb-best-practices): The messages that get replies are the messages that keep numbers healthy. Here is how to write them.
- [Number health](https://beamtexting.com/docs/kb-health): Trust takes weeks to earn and an hour to lose. How reputation works and how Beam protects yours.
- [Check a list first](https://beamtexting.com/docs/screening): Screen any list for blue-bubble reachability before you build a campaign, so you never burn a number messaging phones that cannot receive blue messages.
- [Check a list](https://beamtexting.com/docs/api-screen): Screen a list of numbers for blue-bubble reachability before sending to it.
- [How much can I send](https://beamtexting.com/docs/capacity): Real sending limits per number, why inbound-first has no ramp, and how to size a campaign before you promise a client anything.
- [Getting your numbers](https://beamtexting.com/docs/getting-numbers): How numbers are provisioned, how long it takes, how many you need, and how area codes affect response rates.
- [Writing messages that land](https://beamtexting.com/docs/kb-writing): Formatting and tone rules for messages sent from Beam, including what AI-written text gets wrong.
- [How numbers are assigned](https://beamtexting.com/docs/number-routing): Every lead gets one permanent number while your pool rotates behind the scenes, so volume spreads without a lead ever seeing two numbers.
- [How your assistant writes](https://beamtexting.com/docs/writing-rules): The formatting rules every Beam assistant follows, why each one exists, and the research behind them.
- [The text-us-first funnel](https://beamtexting.com/docs/text-first): Put a button on your site that opens the visitor's Messages app with their first message already written. The safest and highest converting way to start a text conversation.
- [Consent and opt-outs](https://beamtexting.com/docs/kb-consent): What an inbound text does and does not permit, what has to appear near your text button, and how Beam handles opt-outs.
- [Messaging first](https://beamtexting.com/docs/kb-outbound): When you message someone before they have messaged you, and how to do it safely.
- [Getting leads to text first](https://beamtexting.com/docs/kb-inbound): The safest message is a reply. Engineer your funnel so leads message you first.
- [FAQ](https://beamtexting.com/docs/kb-faq): Quick answers to the questions everyone asks.
- [Workspace readiness contract](https://beamtexting.com/docs/onboarding-contract): The exact preview, payment, number request, assignment, and sending states used across Beam.
- [Agency rebilling](https://beamtexting.com/docs/agency-rebilling): The protected reseller billing model: client separation, connected payment accounts, pricing floors, and the release checks required before an agency can collect live payments.
- [Ask the Beam documentation](https://beamtexting.com/docs/ai-help): Use Claude or Codex with Beam's current docs and API contract, so implementation guidance stays grounded instead of sounding plausible.
- [Operator, agency, and analytics guide](https://beamtexting.com/docs/operations): Workspace switching, audited client view, line assignment, metric definitions, integration health, and launch limitations.
- [Terms of Service](https://beamtexting.com/docs/terms): The terms that govern use of Beam.
- [Privacy Notice](https://beamtexting.com/docs/privacy): How Beam handles account, workspace, and communication data.
- [Send from GHL workflows](https://beamtexting.com/docs/ghl-workflows): Trigger Beam texts from a GoHighLevel workflow, test without sending, and avoid duplicate messages.