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

Platform status

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 Tenant setup. Locations are assigned from Tenant setup → Numbers.

Email deliverability

Checking…

Record	Result	What we found	Why it matters
Loading…

Security

What the platform enforces today — live from the database

Loading…

Number lookup

Carrier + line type + SMS capability · global cache shared by all clients

Loading…

Tenant accounts

Tenant	Account #	Users	Numbers	Tokens	Active
Loading clients…

Users and devices

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

User	Template	Upload lists	Edit message	Edit schedule	Start / pause	Run lookup	View billing	Mask 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.

Person	Device	Last active	Last IP	Status	Device notifications
Loading…

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.

Carrier webhooks

The two addresses the carrier posts to — set these on the carrier application

Inbound messages

Loading…

Delivery receipts

Loading…

Treat these as passwords. Anyone holding one can post fake incoming messages and fake delivery receipts into this system, so never paste them into a ticket, an email or a chat. Every time they are shown here is recorded.

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.

Flagman's own account

The client account Flagman staff send and receive messages from · superadmin only

Home account

Console users linked to a person in this account get one sign-in for the console and for messaging.

Notification SMS sender

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

Loading…

Campaign safety

When a campaign pauses itself for opt-outs · staff only, never shown to clients

Pause when opt-outs pass (%)

After at least (messages sent)

A campaign pauses when its opt-outs pass this share of the messages it has sent, once it has sent at least this many. When someone presses Resume, counting starts again from that moment.

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

How to set up the Google relay

What to configure 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@.
Authentication	Allowlist this server's public IP, and require SMTP auth as a second factor. Run curl -4 ifconfig.co on the server to read the address Google will see.
Require TLS	On. Google dropped 3DES in 2025, so the sending host must offer TLS 1.2+ with a modern cipher.
App password	Needed only if authenticating as a single user — enable 2-Step Verification, then generate a 16-character app password.
SPF	Include _spf.google.com in the domain's SPF record.
DKIM	Generate and publish the DKIM key from Admin console, then turn on authentication.

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.

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.

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

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	Carrier	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 and devices	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.

Setup

Loading…

Step	State	Detail
Loading…

Account

Account record

Name, PBX domain, billing ID, time zone and pacing template

Client name

PBX domain

Their PBX tenant, for support lookups.

Billing ID

Eight digits, unique across all clients — Flagman Billing sends account-status webhooks against it.

Account number

Support search key. 8-digit numbers starting with 9 are auto-generated at creation and reserved — hand-entered values use any other shape.

Time zone

Campaign schedules are written in this zone. Quiet hours are always the recipient's local time.

Pacing template

The fastest this client may send. A campaign may pick this or a slower one, never faster.

Monthly limit

Segments this account may send per calendar month (Pacific)

Monthly segment cap

A campaign that would pass it cannot start. Default 5,000. Changing it emails the superadmin and is recorded in the audit log.

Used this month

—

Failure auto-pause

A campaign pauses when too many of its last 500 messages fail

Pause when failures pass (%)

Start checking after (sends)

Account default for every campaign without its own limits. Leave a box empty for the built-in value. Each carrier is also checked on its own after a tenth as many sends. Changes are recorded in the audit log; the client is not notified.

Open campaigns

Campaign	Status	In force
Loading…

Numbers

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.

Registration

10DLC campaigns

Registered by Flagman · synced from the registry

10DLC brand	—
Active campaign	—
Throughput class	—

Campaign ID	Label	Brand	Use case	Class / TPM	Status	Numbers
Loading…

A campaign's class and caps can change after registry re-vetting, so details re-sync daily.

Billing

Packages

…

Package	Tokens / month	Left	Numbers
Loading…

Permissions

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

Integrations

Optional · set up on Account settings → Integrations, or mark as not needed

Loading…

Security

Two-factor state for everyone in this account

Every user enrolls in two-factor (authenticator app) while accepting their invite — signing in without it is not possible. SMS codes and recovery codes work as fallbacks.

User	2FA	Method	Status
Loading…

Media library

Hosted by Flagman · used for MMS and RCS

File	Purpose	Size	Dimensions	Status
Loading…

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.

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

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…

Tenants

Throughput today — all tenants

Active campaigns by volume today

Delivery status today

Failures by error code — today

Live tail — all tenants

Applications & callbacks

Locations → clients

Email deliverability

Security

Number lookup

Tenant accounts

Users and devices

Roles

Pending invites

Phones & tablets

RCS agent

Test handsets

Carrier status

Message templates

Send a test

10DLC registrations

All registrations

Carrier accounts

Carrier webhooks

Sandbox destination allowlist

Sub-accounts (Sites) per account

Flagman's own account

Notification SMS sender

Campaign safety

Email / SMTP

How to set up the Google relay

Flagman GO

Console users

Roles & permissions

Sensitive actions

Audit log

Live events — all accounts

Callback pipeline

Campaigns — Sample Clinic

Live tail — Sample Clinic

Compose message

Daily T-Mobile allowance

Carrier queues

Channel mix

Reply keywords

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

Create the account

Setup

Account record

Monthly limit

Failure auto-pause

Numbers location

10DLC campaigns

Packages

What this account may do

Integrations

Security

Media library

Setup

Your sender numbers