Registration is per brand and happens once. Assigning numbers to a campaign is per group and happens at the aggregator — this page ends where that begins.
VERIFIEDBSTE001
Entity typePRIVATE_PROFIT
Legal nameSpice & Tea Exchange Franchising LLC
EIN84-3921055
VerticalRETAIL
Reference IDteam-103521
Not vetted
Optional, and a spend decision. Buys VETTED_VERIFIED identity, access to special use cases, and higher carrier throughput. Resolves within 48 hours.
AEGISSTANDARD · POLITICAL · ENHANCED · AUTHPLUS · RBM
WMCSTANDARD, US only
CVPOLITICAL, import only
The score-to-throughput mapping is not published, so no predicted throughput is shown here. Actual per-carrier tpm appears in Qualification, after approval.
Three different things are called status. They are three columns here, never one badge.
CampaignTCR statusSharingCarrier decisionsNumbers
STE FranchiseCV8821 · MIXED
ACTIVE
ACCEPTED
AT&T registeredT-Mobile in reviewVerizon no reportUS Cellular registeredClearSky registered
38
STE WestCW1140 · MARKETING
ACTIVE
PENDINGDCA review, 3–5 business days
AT&T no reportT-Mobile no reportVerizon no reportUS Cellular no reportClearSky no report
4
STE SoutheastCV8834 · MIXED
ACTIVE
ACCEPTED
AT&T rejectedT-Mobile registeredVerizon no reportUS Cellular registeredClearSky registered
17
Carriers are encouraged but not required to report a decision. Verizon blank is not a rejection — it is silence, and it needs to read differently from both approval and refusal.
Campaign creation is blocked
The brand is UNVERIFIED. TCR refuses campaign creation until identity resolves, so the button below is not disabled for our convenience — the API would reject it.
TAX_IDThe EIN does not match IRS records for this legal name. Check the name exactly as filed, not the trading name.
WEB_DOMAINThe website does not resolve, or its registrant does not match the brand. A parked domain fails this.
Nothing today can do this
Read straight from TCR for this brand. It lets onboarding tell a customer what they qualify for before anyone promises a date or a volume — and it configures the campaign form: sample count, which opt-in fields are required, and whether links are allowed.
Use caseAT&TT-MobileVerizonUS CellularClearSkyFee
Mixed Marketing3 samples · opt-in, opt-out, help required
4,500tier UPPER_MID
2,400cap 200k/day
—no report
1,200
600
$10/mo
Marketing2 samples · opt-in, opt-out required
4,500tier UPPER_MID
2,400cap 200k/day
—no report
1,200
600
$10/mo
Customer Care2 samples
6,000tier TOP
4,000
—no report
2,000
900
$2/mo
2FA1 sample
—not qualified
—not qualified
—
—
—
$2/mo
Charity2 samples
—needs NON_PROFIT
—needs NON_PROFIT
—
—
—
$2/mo
T-Mobile’s daily cap spans campaigns and CSPs. While we are dual-CSP through the Bandwidth migration, that cap is shared across both — the number here is not ours alone.
Mixed MarketingbrandId and resellerId are known — never asked
How a subscriber opts in, in their own words.
AT&T requires 3 for this use case
CALL_TO_ACTIONNo opt-out language. Carriers reject samples without STOP, and this exact shape is the most common rejection in our own submission history.
Registration skill, inline
~10 rejection events across 8 customers in 12 months. This is what replaces FastTrack.
One-shot fields. Use case, sub use cases, brand and accepted terms can never be changed after create. Everything else is editable. This warning belongs on the submit button, not in a doc nobody reads.
AT&T rejectedTCR ACTIVE
The campaign is alive at TCR and one carrier refused it. Two separate facts, which is exactly why they are two fields.
SAMPLE_MESSAGESample 2 does not identify the brand. AT&T requires the sending business to be named in the message itself.
CALL_TO_ACTIONThe message flow describes in-store signage but does not state what the signage says. The wording has to be quoted, not summarised.
Fix the contentEdit the campaign in place. Description, message flow, samples and links are all editable after create — the one-shot fields are not involved here.
Re-share with the aggregatorSharing is a one-way invite and cannot be rescinded while pending, so a re-share is the only route back to review.
Nudge, with intent APPEAL_REJECTIONA resubmit is also possible but TCR warns it could downgrade the campaign business terms. That needs confirming rather than offering by default.
Bandwidth does not support the TCR nudge. On that side remediation means a re-import, which risks a second vetting charge. The guidance has to branch by aggregator, so the button cannot say the same thing for both.
Registration is per brand; assignment is per group. This page owns the left-hand side of that sentence and the Groups page owns the right — so the two have to agree, and the interesting rows are the ones where they do not.
59Groups on a registered campaign
4On a campaign still in DCA review
1Cleared to send but not in the campaign
548No campaign assigned
GroupCampaignIn campaignUse for sendingReconciliation
Alexandria
STE Franchise · CV8821Verified
✓✓Agrees. Registered, assigned, sending.
Alexandria MN
STE Franchise · CV8821Verified
✗✓Voxie says cleared to send. TCR says the number is not on the campaign. Every blast from here fails silently.
Anchorage
STE West · CW1140Pending
✗—Correct for now — the campaign is still in DCA review, so nothing should be assigned yet.
Charleston
STE Southeast · CV8834AT&T rejected
✗—Blocked upstream. The Groups page shows the symptom; the rejection reason lives on this page.
Why this page and the Groups page need each other
This page is the only place a rejection reason exists. The Groups page can show that a group cannot send, but not why.
The Groups page is the only place the disagreement is visible per location. One campaign covering 59 groups can be perfectly registered and still have one group misassigned.
Number assignment happens at the aggregator, not TCR — which is precisely why the two views can disagree and why neither alone is sufficient.
Changing the EIN resets verificationOne of four fields that knocks the brand out of VERIFIED.
The brand drops from VERIFIED back to UNVERIFIED and has to be re-vetted.
Campaign creation is blocked for the whole team until identity resolves again.
The edit is only permitted at all when there are no external vets and no active campaigns.
This brand has 3 active campaigns, so TCR will refuse the edit outright. Either outcome — a silent de-verification or a hard API failure — is worse as a surprise than as a warning.
companyName · ein · einIssuingCountry · entityType
Walk itThree kinds of status, never collapsed into one badge
Kiosk Mode