Skip to Content
GuidesAdminChannel onboarding queue

Channel onboarding queue

Go to /admin → Channel Onboarding to review pending managed channel requests.

When a tenant selects “Managed” mode during channel setup, their request enters this queue for admin review and provisioning.

Queue view

Each pending request shows:

  • Tenant — organization name and ID
  • Channel — WhatsApp, SMS, Email, RCS, or Push
  • Request date — when the tenant submitted
  • Business info — company name, website, vertical, expected volume
  • Status — pending, in progress, DNS setup, active, or rejected

Approval workflow

Review the request

Click a pending request to see full details: business info, use case, expected volume, and any notes from the tenant.

Provision the channel

For each channel type:

  • WhatsApp — register the number with Meta, configure webhook
  • Email — provision sending domain, generate DNS records (SPF, DKIM, DMARC)
  • SMS — register with the DLT provider, configure sender IDs
  • RCS — submit brand verification to Google
  • Push — generate VAPID keys

Issue DNS records (Email, RCS)

For channels requiring DNS changes, issue the records and mark the request as “DNS setup”. The tenant sees the records in their setup wizard and confirms once added.

Activate

Once verification is complete, activate the channel. The tenant is notified by email and the channel status changes to “active” in their workspace.

Rejection

If a request doesn’t meet requirements:

  • Click Reject with a reason (e.g., “Website less than 3 months old”, “Business verification failed”)
  • The tenant sees the rejection reason and can resubmit after addressing the issue

BYOM channel gating (admin power card)

Bring Your Own Messaging (BYOM) is an admin-gated unlock, separate from this onboarding queue. Use the BYOM Channel Gating power card on the org’s admin page to flip per-channel flags:

  • byom_allowed.whatsapp
  • byom_allowed.sms
  • byom_allowed.email
  • byom_allowed.rcs

The flags persist on organizations.metadata.channels.<ch>.byom_allowed. Until a flag is on, the tenant’s channel setup wizard will only show the Managed path; once flipped, the BYOM option, customer-perception rule, and sender-pin override surfaces unlock for that channel.

BYOM gating and the per-outlet routing UI are orthogonal axes — do not conflate them. The routing UI mounts on senderCount > 1 regardless of BYOM, so a Managed multi-outlet tenant gets it automatically because every outlet receives one Aegis-provided number on activation (additional numbers are billed at the MSG91 rental rate). BYOM only governs whether the operator can register their own credentials and sender-pin overrides.

Channel routing observability

Every outbound send stamps a routed_via value (e.g. brand_unified, per_outlet_primary, dropped) so analytics can attribute deliveries back to the resolved sender. Surface this in delivery analytics with the Routed via breakdown to spot per-outlet routing drift or unexpected fallbacks.

What’s next

Tenant managementPlatform health