# Beam

> 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 best 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://beam.aisync.link/docs/agents.html
- Full corpus (every docs page, one file): https://beam.aisync.link/docs/llms-full.txt
- Machine-readable API contract (OpenAPI 3.1): https://beam.aisync.link/docs/openapi.json

## Docs

- [Is Beam right for my business?](https://beam.aisync.link/docs/why-beam.html): Understand the value, choose your first workflow and test it without guessing.
- [MCP and developer access](https://beam.aisync.link/docs/developer-access.html): Connect your AI tools to train text bots and control your Beam workspace.
- [Route Beam calls into GoHighLevel](https://beam.aisync.link/docs/ghl-inbound-calls.html): Choose where your Beam calls ring and enter your GoHighLevel forwarding number.
- [CRM webhook delivery health](https://beam.aisync.link/docs/crm-webhook-health.html): Understand delivery commands, activity notifications, retries, and the checks needed before launch.
- [Overview](https://beam.aisync.link/docs/index.html): 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://beam.aisync.link/docs/client-launch.html): The exact Super Admin checklist that turns a new Beam workspace into a verified client launch.
- [Quickstart](https://beam.aisync.link/docs/quickstart.html): Learn the authenticated send flow and the readiness checks that must pass first.
- [Connect your CRM](https://beam.aisync.link/docs/crm.html): Keep contacts, calendars, and one-to-one messages connected to Beam without splitting the conversation.
- [The Inbox](https://beam.aisync.link/docs/inbox.html): Every conversation across every number, in one place your team can answer.
- [Reactions, typing & read receipts](https://beam.aisync.link/docs/human-touch.html): The three signals that make a conversation feel human. Beam sends the real thing, not a simulation.
- [Photos & attachments](https://beam.aisync.link/docs/attachments.html): Send images and files in both directions.
- [Numbers & warm-up](https://beam.aisync.link/docs/numbers.html): Your dedicated lines: how to get them, and how Beam keeps them healthy.
- [Inbound call routing](https://beam.aisync.link/docs/voice.html): 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://beam.aisync.link/docs/verified-caller-id.html): Set a verified caller ID for outbound voice calls without changing Beam messaging or inbound routing.
- [How routing works](https://beam.aisync.link/docs/routing.html): 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://beam.aisync.link/docs/assistant.html): 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://beam.aisync.link/docs/agents.html): 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://beam.aisync.link/docs/team.html): 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://beam.aisync.link/docs/email-overview.html): Provision tenant-owned domains and mailboxes without exposing platform provider credentials.
- [Email in the managed inbox](https://beam.aisync.link/docs/email-inbox.html): Compose, receive, reply, assign, and audit email beside every other Beam channel.
- [Email assistant and handoff](https://beam.aisync.link/docs/email-assistant.html): Use the existing Beam assistant safely for email drafting, sending, qualification, and booking.
- [Delivery, suppression, and troubleshooting](https://beam.aisync.link/docs/email-delivery.html): Understand real provider-backed email states and resolve domain or recipient problems safely.
- [Email plans, usage, and caps](https://beam.aisync.link/docs/email-billing.html): Understand Beam-managed email entitlements without exposing infrastructure pricing.
- [Email API and webhook rules](https://beam.aisync.link/docs/email-webhooks.html): Technical invariants for tenant-safe sends, raw-body verification, event deduplication, and domain read-back.
- [Managed email API](https://beam.aisync.link/docs/email-api.html): Connect a backend, Claude, or another agent to tenant-safe domains, mailboxes, threads, and sends.
- [HighLevel and CRM integration](https://beam.aisync.link/docs/email-highlevel.html): Map each Beam workspace to one HighLevel sub-account without reusing the SMS provider identity.
- [Changelog](https://beam.aisync.link/docs/changelog.html): What is new in Beam.
- [Support](https://beam.aisync.link/docs/support.html): We are here to help.
- [Introduction](https://beam.aisync.link/docs/api-intro.html): Build on Beam's API.
- [Send a message](https://beam.aisync.link/docs/api-send.html): One endpoint sends everything. Beam picks the best channel per contact, paces the send, and delivers.
- [Get a message](https://beam.aisync.link/docs/api-get.html): Fetch a message and its delivery status.
- [Cancel a message](https://beam.aisync.link/docs/api-cancel.html): Stop a queued message before it goes out.
- [React to a message](https://beam.aisync.link/docs/api-react.html): Land a real tapback on a contact's message.
- [New-lead webhook](https://beam.aisync.link/docs/api-webhook.html): The endpoint your CRM workflow calls when a new lead opts in.
- [Typing & read receipts](https://beam.aisync.link/docs/api-presence.html): Show the real typing indicator and send real read receipts from your own automations.
- [History & listing](https://beam.aisync.link/docs/api-conversations.html): Read full conversation history with a contact, or list recent messages across the workspace.
- [Contacts & channel lookup](https://beam.aisync.link/docs/api-contacts.html): Look up a contact's details, opt-out state, and whether their phone supports blue bubbles.
- [Numbers](https://beam.aisync.link/docs/api-numbers.html): List the workspace's dedicated lines and their warm-up state.
- [Event webhooks](https://beam.aisync.link/docs/api-events.html): Beam pushes signed events to your endpoint the moment things happen: replies, sends, bookings, handoffs, opt-outs.
- [Webhook signing](https://beam.aisync.link/docs/api-signing.html): Verify that events really came from Beam using the Beam-Signature header.
- [Errors & statuses](https://beam.aisync.link/docs/api-errors.html): Every error is a plain sentence telling you what to fix.
- [Overview](https://beam.aisync.link/docs/kb-compliance.html): What Beam handles for you, and what stays your responsibility.
- [Prohibited content](https://beam.aisync.link/docs/kb-prohibited.html): Categories that get filtered or banned no matter how well the message is written.
- [Best practices](https://beam.aisync.link/docs/kb-best-practices.html): The messages that get replies are the messages that keep numbers healthy. Here is how to write them.
- [Number health](https://beam.aisync.link/docs/kb-health.html): Trust takes weeks to earn and an hour to lose. How reputation works and how Beam protects yours.
- [Check a list first](https://beam.aisync.link/docs/screening.html): 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://beam.aisync.link/docs/api-screen.html): Screen a list of numbers for blue-bubble reachability before sending to it.
- [How much can I send](https://beam.aisync.link/docs/capacity.html): 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://beam.aisync.link/docs/getting-numbers.html): How numbers are provisioned, how long it takes, how many you need, and how area codes affect response rates.
- [Writing messages that land](https://beam.aisync.link/docs/kb-writing.html): Formatting and tone rules for messages sent from Beam, including what AI-written text gets wrong.
- [How numbers are assigned](https://beam.aisync.link/docs/number-routing.html): 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://beam.aisync.link/docs/writing-rules.html): The formatting rules every Beam assistant follows, why each one exists, and the research behind them.
- [The text-us-first funnel](https://beam.aisync.link/docs/text-first.html): 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://beam.aisync.link/docs/kb-consent.html): 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://beam.aisync.link/docs/kb-outbound.html): When you message someone before they have messaged you, and how to do it safely.
- [Getting leads to text first](https://beam.aisync.link/docs/kb-inbound.html): The safest message is a reply. Engineer your funnel so leads message you first.
- [FAQ](https://beam.aisync.link/docs/kb-faq.html): Quick answers to the questions everyone asks.
- [Workspace readiness contract](https://beam.aisync.link/docs/onboarding-contract.html): The exact preview, payment, number request, assignment, and sending states used across Beam.
- [Agency rebilling](https://beam.aisync.link/docs/agency-rebilling.html): 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://beam.aisync.link/docs/ai-help.html): 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://beam.aisync.link/docs/operations.html): Workspace switching, audited client view, line assignment, metric definitions, integration health, and launch limitations.
- [Terms of Service](https://beam.aisync.link/docs/terms.html): The terms that govern use of Beam.
- [Privacy Notice](https://beam.aisync.link/docs/privacy.html): How Beam handles account, workspace, and communication data.
- [Send from GHL workflows](https://beam.aisync.link/docs/ghl-workflows.html): Trigger Beam texts from a GoHighLevel workflow, test without sending, and avoid duplicate messages.