DramWell Docs

Overview

The Telephony section of the Admin Portal provides a control plane for DramWell's Twilio integration. Each customer organization is provisioned as a Twilio sub-account, isolating their phone numbers, messaging history, and billing. This section lets DramWell admins provision numbers, inspect sub-account health, enforce compliance settings, and diagnose delivery issues across all SMS and voice traffic on the platform.

Key Concepts

Sub-Account — A Twilio sub-account created for each DramWell customer organization. Sub-accounts provide billing separation, number ownership, and usage isolation. All API calls for a given org use that org's sub-account credentials.

Phone Number — A Twilio number provisioned into a sub-account and used for SMS sending or voice calls. Numbers are associated with one org and cannot be shared across orgs.

Compliance — Regulatory requirements for messaging and voice. DramWell enforces TCPA opt-in validation, 10DLC campaign registration for A2P SMS, and call recording consent notices.

10DLC — 10-Digit Long Code. The US carrier standard for business SMS. Requires brand registration and campaign registration per use case before high-volume messaging is allowed.

Usage — Per-sub-account metrics on messages sent, calls made, call minutes consumed, and associated costs.

How It Works

Phone Numbers

Go to Telephony > Numbers. The table lists every provisioned number across all sub-accounts with its owning organization, number type (local, toll-free, short code), and current assignment status.

Provisioning a new number:

Click Provision Number.
Select the owning organization.
Search by area code or feature requirement (SMS-capable, voice-capable).
Select a number from the results and confirm.

The number is purchased in the org's Twilio sub-account and linked to DramWell's webhook routing automatically.

Releasing a number: Open the number detail and click Release. This permanently releases the number back to Twilio's pool. Numbers in active use by campaigns will have their sending halted. Confirm the impact before releasing.

Sub-Accounts

Go to Telephony > Sub-Accounts. Each row represents one org's Twilio sub-account with its status, balance, and number count.

Available actions per sub-account:

Action	Description
View	See full sub-account details, credentials, and linked numbers
Suspend	Immediately halt all outbound messaging and calls for this org
Reinstate	Re-enable a suspended sub-account
Top Up	Add credits to a sub-account with a low balance

Sub-account credentials are managed via Supabase Vault — they are never displayed in plaintext in the portal.

Compliance

Go to Telephony > Compliance. This view tracks the compliance status of every org using SMS:

10DLC Brand Status — Pending, Approved, or Rejected for A2P brand registration
10DLC Campaign Status — Registration status per messaging use case
Opt-In Method — Whether the org has configured a compliant opt-in path in their DramGuest/DramPulse settings
TCPA Flags — Any detected violations (e.g., sending to opted-out numbers)

Orgs with a Rejected 10DLC status or active TCPA flags are highlighted in red. Click any org to see the full compliance record and take remediation actions.

Usage

Go to Telephony > Usage. Filter by org, date range, or number to see:

Messages sent and delivered
Messages failed (with failure reason breakdown)
Calls made and total minutes
Estimated cost per org

Export the usage table as CSV for billing reconciliation.

Tips

Check the Compliance view weekly. A 10DLC campaign registration that lapses causes carrier filtering of outbound messages — the org's SMS campaigns will silently fail without this check.
Suspending a sub-account is the correct response to a report of spam or abuse from one of your customers. It is immediate and reversible.
Never store Twilio account SIDs or auth tokens outside Supabase Vault. If a credential is ever exposed, rotate it from the sub-account's Twilio console and update the Vault entry immediately.

Telephony