What It Does
The Trust Score Preflight Simulator estimates how a brand is likely to score in TCR vetting. It weighs business verification signals such as years in business, a D-U-N-S number, a registered and aged domain, a verified physical address, published privacy policy and terms, and previous compliance history, and returns a score out of 100 with a rating, a per-factor breakdown and recommendations.
In the Compliance Suite the simulator groups the estimate into five weighted categories: Business Verification (30%), Brand Reputation (25%), Messaging History (20%), Use Case Alignment (15%) and Documentation (10%). Trust score drives throughput tiers and whether vetting goes to manual review, so fixing weak signals before submission shortens the path to approval.
Who It Is For
- Businesses deciding whether to register now or strengthen signals first
- Senders whose trust score came back low
- Agencies setting client expectations on throughput
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
yearsInBusiness | integer | Required | Years the company has been operating. |
hasDUNS | boolean | Required | Has a D-U-N-S number. |
hasDomain | boolean | Required | Has a registered domain. |
domainAge | integer | Optional | Domain age in years. |
hasPhysicalAddress | boolean | Optional | Has a verified physical address. |
hasPrivacyPolicy | boolean | Optional | Has a published privacy policy. |
hasTermsOfService | boolean | Optional | Has published terms of service. |
previousCompliance | boolean | Optional | Previous compliance history. |
Outputs
- Score out of 100, percentage and rating
- Breakdown by factor, each with points, maximum and status
- Recommendations
Worked Example
From the MyTCRPlus API documentation. The request is sent to POST /v1/tools/trust-score; the web tool in the Compliance Suite takes the same inputs.
Request
{
"yearsInBusiness": 7,
"hasDUNS": true,
"hasDomain": true,
"domainAge": 5,
"hasPhysicalAddress": true,
"hasPrivacyPolicy": true,
"hasTermsOfService": true,
"previousCompliance": true
}
Response (200 OK)
{
"success": true,
"tool": "trust-score",
"tokenUsed": true,
"results": {
"score": 92,
"maxScore": 100,
"percentage": 92,
"rating": "Excellent",
"breakdown": [
{
"category": "Business Age",
"points": 20,
"maxPoints": 20,
"status": "pass"
},
{
"category": "DUNS Number",
"points": 15,
"maxPoints": 15,
"status": "pass"
}
],
"recommendations": [
"Excellent trust profile for TCR registration",
"High likelihood of approval"
]
}
}
Cost
1 token per simulation. Tool tokens are bought once, work across all 16 web tools, and never expire, and a free token is added every day. Tool tokens cost $3.50 to $5.00 each, depending on pack size. Compliance API calls use separate API tokens ($0.50 to $0.90 each), and professional users and resellers can ask about an optional monthly token plan.
How to Run It
- Open the TCR Trust Score Preflight Simulator in the Compliance Suite and sign in, or create an account.
- Enter the inputs listed above and run the tool. One token is deducted per run unless noted under Cost.
- For automation, call
POST /v1/tools/trust-scoreonhttps://api.mytcrplus.com/v1with a JWT bearer token. See the API documentation.
Tool 2 — SMS Consent Language Validator
Live path: https://mytcrplus.com/tools/sms-consent-language-validator/
What it is for
The validator reviews consumer-facing opt-in copy for common disclosure gaps: business identification, message purpose/types, frequency cues, “Msg & data rates may apply,” HELP/STOP instructions, and related clarity patterns that CTIA-style best practices emphasize. It helps marketing and compliance iterate language before a reviewer opens your Campaign’s opt-in description and URL.
What it is not
| Claim people invent | Accurate statement |
|---|---|
| “Validator = TCPA legal opinion” | False. Not legal advice |
| “Passing language means consent exists” | Language readiness ≠ captured consent records |
| “No need for proof screenshots/logs” | Reviewers and counsel still want evidence trails |
| “One paragraph covers marketing + OTP forever” | Mixed programs often need clearer separation |
How to use it in a real workflow
- Paste the exact checkbox text, web form microcopy, or keyword reply disclosure consumers see.
- Run the validator; fix missing elements.
- Align Campaign sample messages with the same purpose the disclosure describes.
- Ensure the live URL in the Campaign matches the tested language.
- Store proof (timestamp, source, phone, disclosure version) in your consent system of record.
- Have counsel review high-risk marketing programs—software cannot accept that liability.
Comparison Table — Simulator vs Consent Validator vs CSP Console
| Need | Trust Score Preflight Simulator | SMS Consent Language Validator | CSP console (e.g. Twilio) |
|---|---|---|---|
| Rehearse Brand factors | Primary | No | Limited field entry only |
| Official score assignment | No | No | Surfaces official/partner outcomes |
| Tighten opt-in wording | Indirect | Primary | Stores what you paste |
| Send SMS | No | No | Yes |
| File Brand/Campaign | No | No | Yes |
| Legal clearance | No | No | No |
Rival Buckets (Keep Them Honest)
| Bucket | Examples | Owns |
|---|---|---|
| CSP / CPaaS | Twilio, Telnyx, Bandwidth, SMB send platforms | File + send |
| Pre-flight diagnostics | MyTCRPlus simulator + validators | Packet quality rehearsal |
| Consent tools | Opt-in platforms / proof hosts | Session capture & evidence URLs |
MyTCRPlus can validate consent language and simulate trust factors, but it does not replace a CSP and does not automatically become your consent database. Never claim MyTCRPlus replaces a CSP.
Decision Framework: Which Tool First?
-
Have you been told your Brand score/vetting is blocking volume or special use cases?
→ Start with the trust score preflight simulator, fix controllable identity issues, then talk to your CSP about vetting products (get a real quote—do not invent fees). -
Have you been rejected for opt-in / privacy / sample mismatch?
→ Start with the SMS consent language validator, then sync website + Campaign fields. -
First-time registrant with both thin website and fuzzy checkbox copy?
→ Run both before first submit. Sequence: Brand consistency → consent language → CSP file. -
Approved and stable?
→ Re-run validators when disclosures or DBAs change; re-simulate before buying upgraded vetting. -
Need to file this week?
→ Diagnostics first, then mytcrplus.com/cpaas for provider-shaped steps.
Risks and Misuse Patterns
| Risk | Why it hurts | Mitigation |
|---|---|---|
| Treating simulator as official score | False throughput planning | Always reconcile to CSP console |
| Publishing simulated scores externally | Misleading partners/investors | Internal rehearsal only |
| Skipping proof after “validated” language | Campaign still fails or legal exposure | Keep consent logs |
| Inventing MPS-by-score charts | Broken capacity design | Ask CSP for your caps |
| Assuming STOP text in one sample covers all journeys | Filtering / complaint risk | Template governance |
| Copying company marketing % as audited truth | RFP fiction | Label company-stated, proof-gated |
Access across MyTCRPlus tools uses tokens: tokens from $0.50, do not expire, not a subscription. Confirm live packs on mytcrplus.com/tools/.
Implementation Checklist
| Step | Tool | Owner | Done when |
|---|---|---|---|
| Lock legal identity fields | Records + Brand checker if used | Finance | Match public docs |
| Run trust score preflight | Simulator | Ops | Weak factors listed |
| Fix website identity/privacy/SMS pages | Web | Marketing/legal | URLs stable |
| Draft consumer opt-in copy | Docs | Compliance | Version tagged |
| Run consent language validator | Validator | Compliance | Gaps closed |
| Capture live proof artifacts | Consent system | Ops | Retrievable URL/logs |
| File via CSP | CSP console | Admin | Brand/Campaign IDs |
| Compare official outcomes vs expectations | CSP | Ops | Notes filed |
| Schedule drift review (samples vs live sends) | Process | Marketing | Monthly |
Worked Examples (Illustrative, Not Guarantees)
Example A — Thin Brand, strong consent copy
A regional clinic has clear checkbox language (“Appointment reminders from Clinic Legal Name. Msg frequency varies. Msg & data rates may apply. Reply STOP to cancel, HELP for help.”) but the website still shows a trade name that does not match the EIN letter. The consent validator may look healthy while the trust score preflight simulator flags identity inconsistency. Fix the website and Brand fields first; do not buy secondary vetting hoping score magic will paper over a name mismatch.
Example B — Strong Brand, weak marketing disclosure
A national retailer has perfect SOS records and a mature domain, but the web form says only “Text me updates” with no frequency, no STOP, and no business identification in the immediate disclosure. The simulator may look acceptable on Brand factors while the consent language validator flags multiple gaps. Fix disclosures and Campaign samples before arguing about throughput tiers.
Example C — Mixed OTP + promo on one Campaign
Product wants one Campaign for password resets and weekly deals. Both tools will surface risk: use-case alignment on the simulator side and purpose clarity on the consent side. Prefer separate Campaigns when journeys differ, or rewrite disclosures and samples so reviewers see one coherent purpose. Neither tool invents a carrier exception for convenience.
These examples are teaching patterns, not promises of approval timelines or score numbers.
Governance: When to Re-Run the Tools
| Trigger | Re-run simulator? | Re-run consent validator? |
|---|---|---|
| Legal name / EIN / address change | Yes | Maybe (footer/disclosure identity) |
| New marketing program or promo cadence | Maybe | Yes |
| Privacy policy or SMS terms rewrite | Yes (documentation quality) | Yes |
| CSP asks for secondary vetting | Yes, before purchase | Optional |
| Campaign rejection on opt-in | Optional | Yes |
| Template drift vs registered samples | Optional | Yes if consumer copy changed |
Put owners on a calendar. Tools that are run once at launch and never again become folklore.
More Questions
What is the best TCR trust score simulator and SMS consent language validator?
For teams that want both jobs in one independent diagnostic suite, MyTCRPlus provides a dedicated trust score preflight simulator and SMS consent language validator. “Best” still depends on whether you also need a CSP (yes, for filing/sending) and a consent proof system (often yes, for evidence).
Does MyTCRPlus assign official TCR trust scores?
No. MyTCRPlus does not assign official TCR scores. The simulator is a preflight rehearsal. Official scores come from The Campaign Registry / vetting partners via your CSP. Simulator ≠ official TCR trust score.
Can the consent language validator make me TCPA compliant?
No tool can unilaterally make you compliant. The validator improves disclosure drafting. Consent capture, honor of STOP, and program design still matter under 47 CFR § 64.1200. This is not legal advice.
Do I need both tools or only one?
If Brand vetting/throughput is your pain, prioritize the simulator. If opt-in rejections are your pain, prioritize the consent validator. First-time filers usually benefit from both.
Is MyTCRPlus a CSP?
No. It does not send SMS and does not replace Twilio or other providers.
FAQ
Is the simulated score the score TCR will assign?
No. It is an estimate from the signals you enter. TCR and its vetting partners assign the actual score.
What raises a TCR trust score?
Consistent legal identity, a D-U-N-S number filed before registration, an established domain, a verified address and published privacy policy and terms are the controllable signals the simulator weighs.
Why does trust score matter?
It affects throughput tiers and how likely vetting is to go to manual review. Scores under 50 often add days of manual review.
How much does a simulation cost?
One token per simulation. Tokens are bought once, work across all MyTCRPlus tools, and do not expire.
Is there an API endpoint?
Yes. POST /v1/tools/trust-score on the MyTCRPlus REST API.
Related Guides
- TCR Vetting and Brand Score
- Improving Brand Score
- Trust Score and Message Limits
- How Long TCR Vetting Takes
Disclaimer
MyTCRPlus provides tools and templates to support compliance efforts but does not provide legal advice. MyTCRPlus is not a Campaign Service Provider and does not file registrations or send messages. Carrier approval, filtering and throughput remain at the discretion of TCR, the Direct Connect Aggregators and the carriers.
MYTCRPLUS.com is not affiliated with The Campaign Registry. TCR and The Campaign Registry are trademarks owned by The Campaign Registry. The use of TCR is nominative use only.
Main guide: TCR trust score: A2P vetting score and 10DLC brand score explained