A fictional nine-person VoIP reseller with about 600 business seats, reselling over one wholesale carrier, recertifying for the 2027 filing year and including the CPNI certificate. Generated by the same pipeline a paid order runs through, from the worked example answers shown alongside each section. The provider is invented; no real company's filing is reproduced here.
One element is deliberately left unanswered in the worked example, so you can see what the coverage report does with a gap instead of filling it in for you.
15 elements covered, 1 need more from you
Ridgeline Communications LLC · FRN 0029384756 · filing year 2027 · Voice service provider
| Requirement | Rule | Status |
|---|---|---|
| Where the steps differ by role | Public Notice DA 24-73, citing Sixth Report and Order para 39 | Not applicable |
| Specific steps taken to avoid originating illegal robocall traffic | 47 CFR 64.6305(d)(2)(ii) | Covered |
| Specific steps taken to avoid carrying or processing illegal robocall traffic | 47 CFR 64.6305(e)(2)(ii) | Not applicable |
| Specific steps taken to avoid carrying or processing illegal robocall traffic | 47 CFR 64.6305(f)(2)(ii) | Not applicable |
| How you know your customers | 47 CFR 64.6305(d)(2)(ii); 47 CFR 64.1200(n)(4) | Covered |
| Procedures for knowing your upstream providers | 47 CFR 64.6305(d)(2)(ii) and (f)(2)(ii); Public Notice DA 24-73 | Covered |
| How you know your upstream providers | 47 CFR 64.6305(e)(2)(ii); 47 CFR 64.1200(n)(5) | Not applicable |
| Contract terms that address illegal calls | Public Notice DA 24-73; Sixth Report and Order para 40 | Covered |
| Call analytics used to identify and block illegal traffic | 47 CFR 64.6305(d)(2)(ii), (e)(2)(ii), (f)(2)(ii); FCC RMD FAQ Q12 | Covered |
| Commitment to respond fully to tracebacks within 24 hours | 47 CFR 64.6305(d)(2)(iii), (e)(2)(iii), (f)(2)(iii); 47 CFR 64.1200(n)(1) | Covered |
| The rule you rely on, and why it applies | 47 CFR 64.6305(d)(2)(i), (e)(2)(i), (f)(2)(i); Sixth Report and Order para 45 | Covered |
| Prior enforcement action or investigation | 47 CFR 64.6305(d)(2)(iv), (e)(2)(iv), (f)(2)(iv) | Not applicable |
| The plan describes this company, not the framework in general | Sixth Report and Order para 61 | Covered |
| English, and submitted as a PDF | 47 CFR 64.6305(d)(2); July 2026 RMD filing instructions | Covered |
| Certificate signed by an officer | 47 CFR 64.2009(e) | Covered |
| Officer's statement of personal knowledge | 47 CFR 64.2009(e); Enforcement Advisory DA 26-139 | Covered |
| Statement explaining how the procedures achieve compliance | 47 CFR 64.2009(e); Enforcement Advisory DA 26-139 | Covered |
| Actions taken against data brokers | 47 CFR 64.2009(e); Enforcement Advisory DA 26-139 | Covered |
| Summary of customer complaints about unauthorized releaseNo answer given.If there were none, say so explicitly. If there were any, give the number broken down by category — improper access by employees, improper disclosure to people not authorised to receive the information, improper access to online information. | 47 CFR 64.2009(e); Enforcement Advisory DA 26-139 | Needs more |
| Covers the previous calendar year | 47 CFR 64.2009(e) | Covered |
| Form 499 Filer ID on the certificate | Enforcement Advisory DA 26-139, Attachments 1–2 | Covered |
Elements marked "needs more" still appear in the plan, saying plainly that you have not described them yet. Improving those answers and regenerating is the difference between a filing that answers the rules and one that does not.
Robocall mitigation plan
Prepared 2027-01-15 — this is the document uploaded to the database filing.
Filer: Ridgeline Communications LLC
FCC Registration Number (FRN): 0029384756
Filing year: 2027
Role or roles in the call chain: Voice service provider
STIR/SHAKEN certification the filer will select on the submission form: Option 3: No STIR/SHAKEN Implementation
Prepared 2027-01-15 from the answers Ridgeline Communications LLC supplied. The officer of Ridgeline Communications LLC who signs the filing is responsible for the accuracy of everything in it.
As a voice service provider, Ridgeline Communications LLC takes the following steps to avoid originating illegal robocall traffic.
Every new customer is provisioned with an outbound call cap of 500 calls per day and a concurrent-channel limit set to the number of seats they bought. Our provisioning system alerts the operations team when an account exceeds 70 percent of either limit in a rolling hour, and the account is suspended automatically at 150 percent pending a human review. We review a daily report of accounts whose average call duration falls below 12 seconds, because short-duration high-volume dialling is the pattern we have seen in the two abuse cases we have had. Accounts flagged that way are suspended within one business day unless the customer can show us a legitimate campaign. We do not permit customers to present numbers they have not either ported to us or proven control of through a verification call, and predictive dialling is prohibited by contract on all seats.
Answers requirement P-01
Ridgeline Communications LLC complies with its obligation to know its customers, for both new and renewing customers, as follows.
Before service is turned up, a new customer supplies a business name, a state registration number, a federal employer identification number, a physical business address, and the name and direct telephone number of a person with authority over the account. We verify the registration against the relevant secretary of state's public register and we call the named person on the number supplied before the account can originate any traffic. We ask every applicant, in writing, whether they intend to use the service for outbound campaign dialling; a yes answer routes the application to a manual review that requires their written consent process and their opt-out handling before approval. At renewal, which for us is annually on the contract anniversary, we re-confirm the business registration is still active and re-verify the authorised contact by telephone. We refuse or terminate accounts that will not complete this, and we have done so twice since 2025.
Answers requirement P-02
Ridgeline Communications LLC has the following know-your-upstream-provider procedures in place.
We accept no traffic from other providers. Ridgeline originates only traffic from its own end-user customers, which we state here because the rule asks us to describe any know-your-upstream-provider procedures in place.
Answers requirement P-03
Ridgeline Communications LLC describes the contractual provisions with end users and upstream providers that are designed to mitigate illegal robocalls.
Our standard master service agreement prohibits the origination of calls that violate the Telephone Consumer Protection Act or state telemarketing law, prohibits presenting caller ID the customer does not control, and lets us suspend service immediately on a traceback that identifies the customer. These clauses are in every customer contract we have signed since March 2025, without exception. Our carrier agreement obliges us to respond to tracebacks the carrier forwards to us within one business day.
Answers requirement P-04
Ridgeline Communications LLC describes the call analytics it uses to identify and block illegal traffic, and the vendor behind them.
We do not run our own analytics platform. We rely on the call analytics operated by our wholesale carrier, Northbridge Wholesale Voice LLC, which scores outbound traffic and notifies us when one of our customers' numbers is flagged. On notification we suspend the customer's outbound dialling the same business day and require the customer to explain the campaign before we restore it. We receive a monthly report of flagged numbers from the carrier, which the operations lead reviews.
Answers requirement P-05
Ridgeline Communications LLC commits to respond fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium, and to cooperate with such entities in investigating and stopping any illegal robocallers that use its service.
Ridgeline Communications LLC handles a traceback request as follows. Tracebacks reach the operations lead at the address in this filing and are acknowledged the same day. Our provisioning system holds 13 months of call detail records, so we can identify the originating account from a call detail within an hour. The operations lead is on call for this and a second named manager covers absences.
Answers requirement P-06
As a voice service provider, Ridgeline Communications LLC relies on this rule and explains below why it applies: No control over the network infrastructure needed to implement STIR/SHAKEN — 47 CFR 64.6305(d)(2)(i)
Ridgeline resells hosted voice service over trunks provided by a single wholesale carrier. We operate no softswitch, no SBC and no numbering resources of our own, and we cannot obtain or apply a certificate to calls that our carrier authenticates on its own network. Our carrier signs every call we originate under its own service provider code token, which we have confirmed in writing with them in November 2026. We therefore lack control over the network infrastructure necessary to implement STIR/SHAKEN ourselves.
Answers requirement P-07
Database form answers
| Field | Enter |
|---|---|
| FCC Registration Number (FRN) | 0029384756Pick this business-type FRN from the dropdown. |
| Business Name | Ridgeline Communications LLCRead-only on the form. It is filled from CORES; change it in CORES before starting the filing. |
| Business Address | Read-only on the form. It is filled from CORES; change it in CORES before starting the filing. |
| Type of Provider Filing | Voice Service Provider Filing |
| Foreign Voice Service Provider | No |
| Country for Business Address | United States of AmericaThe form reveals this field only when the answer above is Yes. |
| Principals, Affiliates, Subsidiaries, and Parent Companies | Dana Whitfield (Managing Member, 60% owner); Arun Prakash (Member and Chief Technology Officer, 40% owner). Parent company: none. Affiliates: none. Subsidiaries: none.; NoneAt least one principal must be a named individual. |
| Other FRNs | NoneSeparate multiple values with semicolons. |
| Other DBA Name(s) | Ridgeline Voice |
| Previous Business Names | None |
| Robocall mitigation contact — name | Dana Whitfield |
| Robocall mitigation contact — title | Managing Member |
| Robocall mitigation contact — department | Operations47 CFR 64.6305(d)(4)(v) lists a department. Leave it blank only if the company has none. |
| Robocall mitigation contact — business address | 1400 Harmon Avenue, Suite 210, Columbus, OH 43223The form offers a 'Contact Address Same as Business Address' checkbox. |
| Robocall mitigation contact — telephone | +1 614 555 0142 |
| Robocall mitigation contact — email | compliance@ridgeline.exampleThis address receives Commission correspondence about the filing, including removal orders. |
| Role in the Call Chain — Voice Service Provider Filing | Voice Service Provider without a STIR/SHAKEN obligationWhether the company has a STIR/SHAKEN obligation is the filer's own determination. Check this selection against the other options in the dropdown before submitting. The form also offers a wholesale-originator option and a combined wholesale-and-end-user option. Select one of those instead if the company originates calls as a wholesale provider. |
| Prior action or investigation | NoThe question covers the filing entity and any entity sharing common ownership, management, directors, or control. |
| Operating Company Number (OCN) | NoA filer that does not have an OCN is not required to obtain one. |
| Certification — Voice Service Provider Filing | Option 3: No STIR/SHAKEN Implementation |
| Exemption — the rule that applies and why | No control over the network infrastructure needed to implement STIR/SHAKEN — 47 CFR 64.6305(d)(2)(i) Ridgeline resells hosted voice service over trunks provided by a single wholesale carrier. We operate no softswitch, no SBC and no numbering resources of our own, and we cannot obtain or apply a certificate to calls that our carrier authenticates on its own network. Our carrier signs every call we originate under its own service provider code token, which we have confirmed in writing with them in November 2026. We therefore lack control over the network infrastructure necessary to implement STIR/SHAKEN ourselves.The form asks the filer both to state the rule and to explain in detail why it applies. |
| Confidentiality request | NoCheck this box only if a confidentiality request has already been filed in WC Docket No. 17-97. Certifications and contact information are public and cannot be marked confidential. |
| Robocall mitigation program description (PDF upload) | Attach the robocall mitigation plan from this order.The plan must be uploaded as a PDF, in English or with a certified English translation. |
| Declaration under penalty of perjury | I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct.Tick the box and enter the execution date at the time of filing. |
| Officer e-Signature | An officer of the filing company must sign this, in conformity with 47 CFR 1.16. A consultant or filing agent may not sign for the company. |
Annual CPNI compliance certificate
Filed in EB Docket No. 06-36 by 1 March.
Date prepared: 2027-01-15. The officer enters the filing date when the certificate is signed.
Name of company covered by this certification: Ridgeline Communications LLC
Form 499 Filer ID: 829461
Calendar year covered: 2026
Name of signatory: Dana Whitfield
Title of signatory: Managing Member
I, Dana Whitfield, Managing Member of Ridgeline Communications LLC, sign this certificate as an agent of the carrier and state that I have personal knowledge that the company has established operating procedures that are adequate to ensure compliance with the rules in 47 CFR Part 64, Subpart U, for calendar year 2026.
The statement below accompanies this certificate and explains how those operating procedures work. It was prepared from the answers Ridgeline Communications LLC supplied, and the signing officer is responsible for its accuracy.
Signature: ______________________________ Date: ______________
Answers requirement C-01, C-02, C-06, C-07
Ridgeline Communications LLC describes its operating procedures for calendar year 2026 as follows, in its own words.
Operating procedures: Customer proprietary network information is held in our provisioning system, which records each customer's approval status for marketing use and refuses to export call detail to any marketing list. Access is limited to six named staff by role, and the approval status is checked by the system before any marketing campaign can be built.
Training and the disciplinary process: Every member of staff with access completes CPNI training on hire and annually each January. The training covers what counts as customer proprietary network information, the approval rules, and the authentication rules. Failure to follow the procedures is treated as a disciplinary matter under our employee handbook, up to termination.
Recordkeeping: We keep a record of every marketing campaign that used customer information, including the date, the customer segments included, and the products marketed, for two years, which exceeds the one-year minimum. Disclosures to any third party are logged in the same register.
Supervisory review of outbound marketing: No outbound marketing campaign can be sent until the Managing Member has reviewed and approved it in writing, and the approval record is filed with the campaign record.
Customer authentication safeguards: We do not release call detail on an inbound call. A customer asking for call detail is offered the record at the address of record or through their account portal after password authentication. Password resets require a back-up question that does not use readily available biographical information.
Breach notification: If we discovered unauthorised access to customer proprietary network information, our procedure is to notify law enforcement through the central reporting facility before notifying the customer, and in no event later than seven business days after a reasonable determination of the breach, following the seven-day and subsequent-notification timetable in the rules.
Answers requirement C-03
Ridgeline Communications LLC describes the actions it took against data brokers during calendar year 2026 as follows.
Ridgeline Communications LLC took no action against any data broker during the covered year.
Answers requirement C-04
During calendar year 2026, Ridgeline Communications LLC received no customer complaints concerning the unauthorized release of CPNI.
Answers requirement C-05
These documents are prepared from your answers. CallCert does not file them, cannot sign them, and makes no claim about how the FCC will treat your filing — the declaration on the database filing and the CPNI certificate must each be signed by an officer of your company.
Yours arrives in the same shape, from your answers, within a minute of payment: the plan as a PDF to upload, the text for every database form field, the CPNI certificate if you include it, and this coverage report. $149 once.
Prepare your filing set