Tenants

Console / Tenants

KP (Karen Petrosyan)kp@flagmantelecom.com

Signed in · session expires in 6h 12m

Today · all tenants

Total tenants

—

Active campaigns

across 6 tenants

Sent today

—

Delivered

—

of DLR-final

Failed today

—

Tokens consumed

—

sends + lookups

Low balance

tenants under threshold

Signed in now

—

Month to date

Sent this month

—

Delivered this month

—

Failed this month

—

Throughput today — all tenants

msgs/min

Active campaigns by volume today

Delivery status today

Delivered —

Failed —

Queued —

Failures by error code — today

Pacific day · all tenants

Live tail — all tenants

newest first

Tenant accounts

Tenant	Users	Numbers	Tokens	Active
Loading clients…

Users & permissions

Templates: Admin / Editor / Viewer, flags adjustable per user

User	Template	Upload lists	Edit message	Edit schedule	Start / pause	Run lookup	View billing	Full numbers
Loading…

Roles

What each role can open and do · users hold one role

Role	Users	Numbers	Can

Pending invites

Accounts that exist but haven't been activated

Name	Email	Role	Sent	Expires

Invite links are single-use and expire after 72 hours. Resending issues a new link and invalidates the old one. Nobody — including Flagman staff — can set a client's password.

RCS agent

Flagman's own agent — pre-launch, test handsets only

Test handsets

Bandwidth registers up to 10 while pre-launch

Number	Who	Handset

Number

Who has it

Carrier status

each carrier approves on its own schedule

Carrier	Status	Updated

Message templates

the RBM content block from Bandwidth's design tool

Template	Kind	Notes	Updated

Send a test

RBM only — no SMS fallback while the carriers are pending

Template

To	Message	Status	Sent	Delivered	Read	Tokens

10DLC registrations

The Campaign Registry — Flagman's own CSP account

Campaigns—

All registrations

Every campaign on the CSP account — search by id, brand or description

Show

Show deleted brands

Campaign	Brand	Use case	Status	Renews / expires	Numbers	AT&T/min	T-Mo/day	Shared
Loading…

Carrier accounts

Credentials, application ID and rate limits are per account

Account ID	Label	Application ID	Rate limit	Messaging	Numbers	Status
Loading…

Each account has its own rate limit ceiling, counted in segments per minute — the carrier counts segments, not requests. Secrets are encrypted on the server and never shown again after saving.

Sub-accounts (Sites) per account

Fetched from the carrier · choose which client settings may use

Carrier account

Site ID	Name	Locations	Allowed	Default
Pick an account and fetch its sub-accounts.

Only allowed sub-accounts appear in client settings. The first one you allow becomes the default for new clients.

Applications & callbacks

Every messaging application this portal serves callbacks for

BW account	Purpose	Application ID	Callback URL	10DLC	Status
Loading…

Callbacks are acknowledged with HTTP 2xx, deduplicated (at-least-once delivery is expected from the carrier), and retried by the carrier for 24 hours. Queue health lives on Live events.

Locations → clients

Every assigned Location and its tenant

BW account	Site	Location (SIP Peer)	Name	SMS	Assigned tenant	Numbers
Loading…

A Location with SMS disabled can't send — enable it in the carrier dashboard, then refresh it from that client's settings. Locations are assigned from Client settings → Numbers.

Notification SMS sender

System alerts to client mobiles — Flagman's own number, never billed to packages

Loading…

Email / SMTP

Used for all portal email — alerts, invites, password resets VERIFIED

Provider preset

SMTP host

Port

587 · STARTTLS (recommended)

Encryption

Username

Password

From name

From address

Reply-to

Where client replies land

Rate limit

emails / min

On failure

Bounce handling

Verify TLS certificate — turn off only for an internal relay with a self-signed cert

Last testtoday 13:41

Sent 24h418

Bounced3

Queue0 pending

Send a test email to

Google Workspace relay checklist

Configured in Admin console → Apps → Gmail → Routing → SMTP relay service

Allowed senders	Set to Only addresses in my domains so the portal can send as no-reply@ and support@.	SET
Authentication	Allowlist this server's IP 38.191.45.20, and require SMTP auth as a second factor.	SET
Require TLS	On. Google dropped 3DES in 2025, so the sending host must offer TLS 1.2+ with a modern cipher.	SET
App password	Needed if authenticating as a user — enable 2-Step Verification, then generate a 16-character app password.	USER AUTH ONLY
SPF	Include _spf.google.com in the domain's SPF record.	PASS
DKIM	Generate and publish the DKIM key from Admin console, then turn on authentication.	PASS

Relay limits: 10,000 recipients per user per 24h and 100 recipients per SMTP transaction — the sender batches accordingly. Alerts are one-recipient messages, so the transaction limit only matters for staff broadcasts.

Email deliverability

DNS records for the sending domain · checked hourly

Record	Host	Status	Why it matters
SPF	flagmantelecom.com	PASS	Authorises this server to send as your domain
DKIM	portal._domainkey	PASS	Signs messages so they aren't altered in transit
DMARC	_dmarc	p=none	Move to quarantine once SPF and DKIM are stable
Reverse DNS	38.191.45.20	PASS	Mail servers reject senders without matching rDNS

Email templates

Sent by the notification system

Template	Subject	Sent 30d
Balance threshold reached	Your SMS package is running low	64
Package exhausted	Sending paused — package used up	11
Campaign finished	Your campaign has finished	203
Campaign paused — failure spike	Campaign paused: delivery failures	7
User invite	You've been invited to Flagman SMS	18
Password reset	Reset your password	9
2FA reset notice	Your two-factor authentication was reset	2

Error type	Action	Backoff	Attempts	Why
rate-limit-exceeded	RETRY	5s ×2 + jitter	8	Also lowers that carrier's queue rate for the window
unauthorized	REFRESH AUTH	immediate	2	OAuth token expired — refresh once, then alert
forbidden	ALERT STAFF	—	0	Missing role or feature on the BW account. Never retried
request-validation	FAIL	—	0	Payload is wrong — retrying sends the same bad payload
unsupported-content-type	FAIL	—	0	Client bug
internal-server-error	RETRY	10s ×2	5	Provider side — retry before failing the recipient

Console users

User	Role	2FA	Tenant scope	Last active	Status
Loading…

Roles & permissions

Sensitive actions

Always emailed to the superadmin, regardless of notification preferences

When	Action	Who	Tenant	Detail	Notified
Loading…

Topups also count against each agent's daily aggregate limit, so a per-action ceiling can't be defeated by repetition.

Audit log

When	Staff user	Action	Target	IP
Loading…

Every action taken while impersonating is logged against both the staff user and the impersonated tenant user.

Pacing templates

Carrier throughput classes and the per-tenant rates built on them

Not built yet.
Templates already drive real sending — the runner reads them for every carrier queue — but the screen for editing them is still to come. Nothing is shown here rather than showing numbers that are not yours.

Live events — all accounts

Callback pipeline

Bandwidth → this portal

Inbound queue: 0 pending · 0 failed · retries with backoff for 24h
Last callback received: 4s ago · Catch-up sweep: last run 14:00, 0 stuck messages re-queried
HMAC verification: ON · Heartbeat monitor: PLANNED

Campaigns — Sample Clinic

Campaign	Sender	Status	Progress	Est. finish
March service upgrade notice	+1 818 555 0100	SENDING		Today 15:05 PT
Recall reminders — hygiene	+1 818 555 0177	SCHEDULED		Aug 4 ~14:40 PT

Live tail — Sample Clinic

this tenant only

Carrier queues

each drains independently · pausing one does not stop the others

Carrier	Progress	Sent	Queued	Fail %	Rate	State

Message detail

Phone	Sent at	DLR at	Seg	Status

Reconciliation snapshot

what the portal recorded vs what the package was charged

	Portal	Billed	Δ

Groups

Group	Contacts	Sendable	Type	Updated
Loading…

Contacts

	Name	Mobile	Email	Groups	Line type	Last contacted
Loading…

— · 0 selected

SMS templates

Name	Category	Preview	Seg	Tokens	Used

Variables pull from the contact record — {{first_name}}, {{company}}, or any custom field. Use | for a fallback: {{first_name|there}}.

These limits come from the mobile carriers and from your registered 10DLC campaign — Flagman applies them automatically so your messages keep getting delivered. They are shown here for reference and can't be changed from the portal. If a limit is causing you problems, contact Flagman support and we'll look at whether your registration can be upgraded.

Your 10DLC registration

Managed by Flagman

Loading…

Sending limits by carrier

Applied automatically · each carrier drains its own queue

Carrier	How the limit works	Your limit	What you'll see
Loading…

We look up each number's carrier before sending, then send to each carrier in its own queue. If one carrier slows down or starts blocking, the others keep going.

Rules that apply to every message

Why messages fail

The codes you'll see in your reports

Code	Meaning	What to do

Account

Sample Clinic ACTIVE

Loading…

Operational state

Today's allowances

Daily T-Mobile allowance per brand · resets at 12:00 AM PST

Packages

Balances and reset dates

Package	Left	Remaining	Resets	Status
Loading…

Sender numbers

Package assignment and 10DLC binding

Number	Label	Package	Campaign	Opt-outs
Loading…

Recent activity

Events only — no message content

Loading…

Conversations

Content requires the client's consent

🔒

Message content is hidden

You can see counts and delivery state from here. Reading conversations, sending on the client's behalf, or changing their settings requires an impersonation session the client approves.

Request access as

The session inherits that user's permissions, not yours.

The client sees who is asking, why, and for how long — and must approve.

What staff can do without impersonation

Area	Without a session	Needs impersonation
Billing & tokens	VIEW + TOPUP	—
Sender numbers, packages	VIEW + EDIT	—
10DLC registration	VIEW + SUBMIT	—
Users & permissions	VIEW + MANAGE	—
Campaign status & delivery stats	VIEW	Editing or starting a campaign
Conversations, message bodies	HIDDEN	YES
Address book contact details	HIDDEN	YES
Sending on the client's behalf	NO	YES

These are your personal notification settings for this account. Other users set their own. SMS alerts go to your verified mobile from a Flagman system number and are never billed to your package.

Balance alerts

You choose when to be warned · one alert per threshold per cycle

Alert me when a package drops to…

Thresholds are shared account-wide (they decide when the alert fires); whether YOU get the alert is your personal choice below. Each fires once per billing cycle and re-arms at reset.

Notifications

Pick what you want and how · SMS comes from a Flagman number, never billed to you

Event	Email	SMS
Loading…

These are your personal settings — each user in your account sets their own. Account admins can also subscribe other users.

What this account may do

Flagman's ceiling — nobody in the account can exceed it, including their own admin

Why — recorded in the audit log

Numbers location

Site (sub-account) + Location (SIP Peer) this client's numbers live in

Location	Name	Application	Sub-account	Assigned

Carrier account

Sites and locations are fetched for this account

Sub-account (Site)

Allowed list managed in Console → Settings

Location (SIP Peer) = this client

Fetched live from the carrier — type to search

Location SMS—

Location MMS—

Messaging app—

Last sync—

Numbers inherit SMS/MMS from the Location, but each number is checked individually — only SMS-enabled, in-service numbers appear in campaign sender lists.

Number	Label	Status	SMS	MMS	A2P state	Package	Sender list
Loading numbers…

Numbers with no package assigned cannot send — assign them under Billing & tokens.

Media library

Hosted by Flagman · used for MMS and RCS

File	Purpose	Size	Dimensions	Status
crown-banner.jpg	RCS banner	184 KB	1440 × 448	VALID
crown-logo.png	RCS logo	36 KB	224 × 224	VALID
appt-confirmed.jpg	RCS card	212 KB	1200 × 800	VALID
promo-old.png	RCS banner	96 KB	800 × 600	REJECTED banner must be exactly 1440 × 448

Files are checked on upload — format, byte size and pixel dimensions — and served from Flagman's CDN over HTTPS, so the URLs we hand to the carrier never break.

Send defaults

Maps to the send_sms request body

from — default sender

Must be a number on this domain unless the token has global scope.

MMS media support

MMS is billed differently — confirm token cost with Flagman.

Numbers are sent in E.164 (+1XXXXXXXXXX) to match the endpoint's expected format. The portal records segmentCount from each response as the authoritative billed segment count.

Campaign defaults

Pre-filled on every new campaign · still editable per campaign

Default sender number

Default daily window

Timezone handling

Failure auto-pause

% of last 500 sends

Low balance threshold

Notify when tokens drop below this

Line-type lookup

Append Reply STOP to opt out if the message text doesn't already include opt-out language

Carrier policy

Which throughput class this tenant sends under STAFF

Assigned template

Their 10DLC registration

Set by the approved campaign — a template above this tier can't be selected

Carrier / group	Tier	Rate	Fail threshold

Every tenant starts on Low volume. Raise it only after their 10DLC registration supports it — a higher template on a low-volume brand is throttled by the carriers and looks like a broken campaign.

Carrier limit overrides

Clamps for this tenant only · can only slow down, never speed up STAFF

Carrier / group	Template rate	Override /min	Daily cap (seg)	Effective

Reason — required, recorded in the audit log

Overrides are clamp-only: the sender takes the minimum of template, override, and the 10DLC grant, so a value above the template has no effect. Every set, change, or removal emails the superadmin.

Sending policy

Staff-only — clients cannot change these STAFF

Enforce quiet hours — in the recipient's local time, derived from area code

Earliest send

Latest send

Some states require 20:00 — check before widening

Tenant time zone

Schedules are expressed in this zone

Monthly cap

segments

Raised by Flagman on request

Max list size

Larger uploads need staff approval

Message retention

Older messages are deleted permanently

Used this month3,180 / 5,000 seg

Held for quiet hours42

Billing statusACTIVE

Oldest message2025-11-04

⏰

Recipients outside the window are held, not dropped — the queue releases them when their local morning arrives, so a campaign started late finishes the next day rather than failing.

10DLC campaigns

Registry fields are read-only · the rest we keep here

Add campaign ID

Label (optional)

We look the ID up with the registry and pull its brand, use case, throughput class and status. Numbers are then matched to the campaign they're registered under.

Campaign ID	Label	Brand	Use case	Class / TPM	Status	Our record	Numbers
C-A4F2	Appointment & billing	Sample Clinic LLC	Account Notification	A · 4,500	ACTIVE	COMPLETE	2
C-B7K1	Promotions	Sample Clinic LLC	Marketing	B · 2,400	PENDING VETTING	3 FIELDS MISSING	0

Last synced today 14:02 · a campaign's class and caps can change after TCR re-vetting, so we re-check daily.

Compliance

Managed by Flagman — shown for reference

10DLC brand	Sample Clinic LLC · verified
Campaign ID	C-A4F2 · use case: Account Notification
Throughput class	Class A · 4,500 TPM (AT&T, shared by all sends under this campaign) · Daily T-Mobile allowance 2,000 (brand-level)
Quiet hours	8:00 AM – 9:00 PM recipient local · stricter state limits applied automatically (e.g. FL, OK end 8:00 PM) · ENFORCED, NOT EDITABLE
Opt-out scope	Account-wide — STOP on any of your numbers blocks all your campaigns

User	2FA	Method	Status
Loading…

Your sender numbers

Managed by Flagman support — contact us to add or change numbers

Number	Label	Package	10DLC campaign	Brand	Description	Default	Opt-outs

SMS packages

1 SMS segment = 10 tokens · MMS = 30 · TN lookup = 1

A campaign draws from the package that owns its sender number. Numbers with no package assigned cannot send. At zero tokens sending stops — there is no overage, so set your alert thresholds to give yourself warning.

Package messages (62)

From	To	Text len	Media len	Segments	Points used	Points left	Package	Type	Source	Timestamp
Loading…

—

Usage ledger

Date	Package	Entry	Source	Δ	Left

Suppression list — tenant scope

STOP on any of your numbers blocks all your campaigns · re-subscribe only via inbound START

🛑

Opt-outs apply across every channel. A STOP received over SMS also blocks RCS and MMS to that number, and vice versa. The list records which channel the opt-out arrived on, but enforcement is channel-agnostic.

Number	Source	Received on TN	Keyword	Date
Loading…

Auto-replies

Sent from the number that received the keyword · never billed to your package

Reply to STOP

Keep the promise accurate: any message they send back re-subscribes them automatically.

Reply to HELP

Sent when someone texts HELP or INFO to any of your numbers.

Default opt-out message

The campaign composer appends this with one toggle

Shown in the composer preview and counted in the segment math. Keep it short — it rides on every message.

Opt-out history

Append-only — every opt-out and re-subscribe, forever

When	Number	Event	How	Who / keyword
Loading…

MacBook Pro · Chrome	this device · Glendale
iPhone · Safari	last used Jul 28

Tenants

Throughput today — all tenants

Active campaigns by volume today

Delivery status today

Failures by error code — today

Live tail — all tenants

Tenant accounts

Users & permissions

Roles

Pending invites

RCS agent

Test handsets

Carrier status

Message templates

Send a test

10DLC registrations

All registrations

Carrier accounts

Sandbox destination allowlist

Sub-accounts (Sites) per account

Applications & callbacks

Locations → clients

Notification SMS sender

Email / SMTP

Google Workspace relay checklist

Email deliverability

Email templates

Security

Number lookup

Provider error handling

Flagman platform APIs

Console users

Roles & permissions

Sensitive actions

Audit log

Pacing templates

Live events — all accounts

Callback pipeline

Campaigns — Sample Clinic

Live tail — Sample Clinic

Compose message

Daily T-Mobile allowance

Carrier queues

Channel mix

Replies & button taps

Message detail

Reconciliation snapshot

Groups

Contacts

SMS templates

RCS templates

Your 10DLC registration

Sending limits by carrier

Rules that apply to every message

Why messages fail

Account

Today's allowances

Packages

Sender numbers

Recent activity

Conversations

What staff can do without impersonation

Balance alerts

Notifications

What this account may do

Numbers location

Flagman API connection

Webhooks

Media library

Send defaults

Campaign defaults

Carrier policy

Carrier limit overrides

Sending policy

10DLC campaigns

Compliance

Security

Data purge (HIPAA)

Your sender numbers

SMS packages