Robocall Mitigation Plan
How we keep illegal robocalls off our network: vet every customer, watch every traffic profile, and answer every traceback — fast.
1. Our commitment
TeleComcepts provides voice services over its own session border controller (SBC) infrastructure. Every call our customers originate crosses equipment we control — which means we have both the visibility and the enforcement tools to stop illegal traffic at the source. We do not originate, and will not knowingly carry, illegal robocall traffic, and we cooperate fully with regulators and industry traceback efforts.
2. Customer vetting (Know Your Customer)
Every customer is verified before traffic flows, as detailed in our KYC Policy:
- Business and wholesale customers complete full KYC: business identity and registration, EIN, ownership disclosure, supporting documents, and a description of their telecom use case and expected traffic profile (minutes, CPS, average call duration, DID counts).
- Resellers must additionally provide their FCC FRN or 499 Filer ID, their own RMD filing ID, and a copy of their own robocall mitigation plan — and disclose whether they run KYC on their downstream customers.
- Self-service retail accounts verify identity with email and payment-card verification and are onboarded directly into our most conservative automated risk controls.
- We screen for prior telecom, fraud, and compliance-related legal action and for undisclosed foreign ownership.
3. Risk-based traffic controls
All accounts are assigned a risk tier at onboarding and managed by automated controls enforced at our SBC:
- Ramp caps. New accounts start with conservative daily volume and calls-per-second limits that expand only with sustained clean traffic history.
- Traffic-profile monitoring. We continuously monitor answer-seizure ratio (ASR), average call duration (ACD), call velocity, and destination patterns against the usage profile declared at onboarding. Short-duration, high-velocity patterns characteristic of illegal autodialing trigger automatic review.
- Dialer traffic policy. Conversational routes are reserved for conversational traffic. Autodialer and other short-duration traffic is permitted only on designated routes, with prior disclosure and approval, appropriate rate decks, and tighter monitoring. Undisclosed dialer traffic on conversational routes is grounds for suspension.
- Spend and velocity limits. Prepaid balances and per-account caps bound the damage any compromised or bad-faith account can do.
4. Caller ID authentication (STIR/SHAKEN)
Our caller ID authentication posture and robocall mitigation program are described in our filing on record with the FCC's Robocall Mitigation Database. Customers may only originate calls from numbers they own or are expressly authorized to use, which we verify at provisioning, and we prohibit caller ID spoofing intended to defraud, cause harm, or wrongfully obtain anything of value, per our Acceptable Use Policy.
5. Traceback cooperation
We respond to traceback requests from the FCC, state attorneys general, and the registered Industry Traceback Consortium within 24 hours. Our records allow us to identify the customer responsible for any call originated on our network. Failure of a customer to respond to a traceback or compliance request is itself grounds for suspension under our service terms.
6. Enforcement
- Suspected illegal traffic is blocked or suspended immediately on detection — we suspend first and investigate with the customer second.
- Confirmed illegal robocalling results in termination and, where appropriate, referral to authorities.
- We retain call detail records sufficient to support investigations and traceback requests.
7. Point of contact
Traceback requests, robocall complaints, and compliance inquiries: [email protected] or +1 909 583 8000. Include "TRACEBACK" in the subject line for priority handling.