Beam
Open Beam
Guides

Operator, agency, and analytics guide

Current documentation

Workspace switching, audited client view, line assignment, metric definitions, integration health, and launch limitations.

Workspace roles

Platform team sign-in

A current platform administrator adds each platform teammate in Settings → Platform admin team. Each person then opens the platform sign-in link and requests their own six-digit email code. Platform access is individual, auditable, and can be deactivated without changing anyone else's session. Do not share a platform key.

Audited client view

Select Open client workspace from the Clients or Platform view. Beam verifies the client belongs to the agency, issues a hashed 30-minute session, and records the actor, source workspace, target, reason, and expiry. A persistent banner identifies client view and provides an immediate exit.

Client view includes the full inbox, analytics, and configuration status. Persistent login keys, API keys, signing secrets, lead-webhook secrets, and account-changing controls remain hidden. Exiting ends the session and records the end event. Expired or ended credentials fail closed.

Line assignment and readiness

  1. A confirmed payment record creates one idempotent provisioning request. It never buys or assigns a line.
  2. A platform operator selects an available inventory line and assigns it to the requested workspace.
  3. The assignment is recorded with actor and request context. A paid self-serve workspace becomes active only when an active assignment exists.
  4. Removing the assignment deactivates the line, clears contact pins, records the removal reason, and locks sends immediately.

Area codes are sourcing preferences, not guarantees. Pacing always counts new outbound-first conversations, never messages.

Analytics definitions

MetricExact meaning
Outbound-firstA contact whose first successfully sent message is outbound, with no earlier inbound message, inside the selected window.
Inbound-firstA contact whose first recorded inbound message occurs before any successful outbound message.
Messages sentOutbound rows recorded as sent or delivered. Attempts also include queued and failed rows.
RepliesThe first inbound response after an outbound-first conversation. Response time uses recorded send and inbound event times.
FailuresRecorded failed or no-ready-line attempts, grouped into plain-language reasons.
Opt-outsCurrent contact state. Period change is unavailable until a canonical opt-out timestamp exists.
BookedA distinct real calendar appointment ID. Duplicate events and tag-only states do not count.

The analytics trend charts plot daily recorded sent, delivered, failed, and inbound activity for the selected window. Funnel stages are operational signals, not a claim that every booking was caused by one particular message. Recipient read status is shown only when a channel supplies a real read event. Beam does not infer an open rate for texts. Rescheduled, cancelled, no-show, and completed outcomes remain unavailable until real calendar outcome updates are synchronized.

API and event-webhook health

Configured means a key or HTTPS endpoint exists. It does not mean healthy. API usage health, event-webhook delivery health, and calendar outcome sync remain labelled unavailable until their attempts and read-backs are persisted.

Billing, revenue, and profit truth

Super Admin shows the stored billing status, sending state, plan, cancellation-at-period-end flag, recovery deadline, and current period end when the accepted Billing contract is integrated. Catalog MRR is calculated from the recorded direct-client plan and recorded number add-ons. It is contracted recurring value, not proof of cash collected.

Number add-on MRR is shown separately. Revenue from bundled lines is not split out because the catalog does not assign independent revenue to each bundled line. Profit remains Unavailable until real per-line costs and invoice adjustments are stored. Beam does not manufacture a margin from inventory counts.

Launch truth