Skip to content

Sample report

RMD Check: Example Voice LLC

This is the one-page check we send when you reply "yes" or request one on this site. Example Voice LLC is fictional; the checks, rules and sources are real. Yours is built from your own public listing, read by a person before it goes out.

Prepared Nov 3, 2026 · Based only on the public RMD listing and the plan on file · Not legal advice

Download as PDFWho prepares your check
VoiceDeskRMD Check · Sample

1. Public record reviewed

Business nameExample Voice LLC (fictional)
RMD number / FRNRMD0000000 / 0000000000
Role in the call pathVoice service provider without a STIR/SHAKEN obligation
STIR/SHAKENNo STIR/SHAKEN implementation, performing robocall mitigation
Last updatedApril 22, 2024
Last recertifiedNone on the public record
Robocall mitigation contactOperations Manager, on a free webmail address
Plan on fileMitigation Plan.pdf (2 pages)

2. What stood out

  • No 2026 recertification on the public record. Every filer had to certify by March 1, 2026 that its filing is true and correct.[1][2] The FCC has said missed recertifications are forcing it to start enforcement, and it is asking whether to suspend unrecertified filings automatically.[5]
  • The plan doesn't describe specific steps. Two pages of general commitments, with no description of how new customers are vetted, how upstream providers are known, or which analytics are used. § 64.6305(d)(2)(ii) asks for all three.[1]
  • The listing hasn't changed since April 2024. If the address, contact or upstream provider changed since then, the update was due within 10 business days; a late update has a $1,000 base forfeiture, continuing until cured.[1][3]
  • The robocall contact is on a webmail address. Not a rule violation, but it reads as unofficial, and the contact must be reachable for 24-hour traceback.[1]
  • The reseller explanation is there. The filing explains that the upstream provider signs calls, which a provider without its own STIR/SHAKEN obligation has to state.[1]

3. Why it matters

A filing that lacks required information can be removed. When it is, other providers must stop accepting your calls directly; the September 2026 order gave them two business days.[1][4] Inaccurate or false information carries a $10,000 base forfeiture.[3]

4. Fix checklist

  1. Rewrite the plan with your actual vetting steps, upstream checks and analytics.
  2. Move the robocall contact to a monitored address on your own domain.
  3. Confirm the address, contact and upstream provider; refile anything that changed.
  4. Check your CORES registration, which the filing pulls from.
  5. Recertify now, and again between Feb 1 and March 1, 2027.

5. If you want it handled

VoiceDesk drafts the revised plan and a field-by-field refile sheet for a fixed $299 (3 business days), or for $690/yr drafts your 2027 recertification and CPNI certificate and monitors your listing and your carriers' listings every night. Founding prices hold until Dec 15, 2026. Your officer reviews and files; we never need your FCC login.

Get the free check for your own filing · Read the recertification guide

Sources

  1. [1]47 CFR § 64.6305, Robocall mitigation and certification (eCFR)
  2. [2]DA 26-72, Public Notice on the annual recertification (Jan. 22, 2026)
  3. [3]47 CFR § 1.80, base forfeiture table (eCFR)
  4. [4]DA 26-872, Enforcement Bureau removal order (Sept. 2, 2026)
  5. [5]FCC 26-49, Further Notice of Proposed Rulemaking (July 23, 2026)