Identity and Business Verification (KYC)

Know Your Customer (KYC) is the identity and business information Ringer collects and keeps current for every account that carries traffic. A telecom carrier must know who originates the calls and messages on its network: that obligation comes from regulators, from the carriers Ringer interconnects with, and from the industry programs that govern caller-ID authentication and robocall mitigation. Your verification record is the evidence behind those obligations.

Your verification status lives at Settings → KYC (/settings/kyc). The page is read-only. It shows what is on file, whether the record is complete, and which fields are still outstanding.

What the Page Shows

The header carries a single status line:

• KYC / COMPLETE — every required field is on file.
• KYC / ACTION REQUIRED — at least one required field is missing.

When something is missing and a record already exists, a Missing fields panel lists each outstanding item by name. If no record exists yet, the page says No KYC on file yet instead of listing fields.

Below that, an Update your KYC card links to the secure form used to submit or change details, and the record itself is shown in three cards.

If the data shown is a stored copy rather than a live read, the page prints "Showing last-synced data" with a timestamp above the cards.

The Business Section

The Identity & Business card describes the legal entity behind the account:

• DBA Name
• Entity Type
• Business Description
• State of Incorporation
• Year Incorporated
• Type of Business
• FEIN (federal tax identification number)
• Tax Exempt

Use the legal entity that is party to your service agreement, not a brand or trading name. The same details are checked again during 10DLC brand registration, where business details that do not match public records are a common rejection cause — so getting them right here saves work later.

The Telecom Section

The FCC, STIR/SHAKEN & Robocall Mitigation card covers your standing as a service provider:

• FCC Registered
• FCC Registration Name
• FCC Registration Number
• FCC 499 Filer ID
• Robocall Mitigation Plan ID

These fields document that your business is registered with the FCC and that you have a robocall mitigation plan on file. They are the telecom-specific half of verification and have no equivalent in a generic business KYC form.

Contact Roles

The Contact Roles card records four named contacts, each with a name, email address and phone number:

• Main Contact
• Legal Compliance
• Regulatory
• Billing / AP

These are routing destinations for real events: a regulatory notice goes to the regulatory contact, a billing question to Billing / AP. Keep them pointed at roles that are still staffed, not at individuals who have moved on.

What Is Required

Twelve fields determine whether your record reads complete. Anything else on the page is useful context but does not hold up verification.

Required field	Section
Entity Type	Identity & Business
FEIN	Identity & Business
State of Incorporation	Identity & Business
Year Incorporated	Identity & Business
Type of Business	Identity & Business
Business Description	Identity & Business
FCC Registered	FCC / Robocall Mitigation
Robocall Mitigation Plan	FCC / Robocall Mitigation
Main Contact Email	Contact Roles
Legal Compliance Email	Contact Roles
Regulatory Contact Email	Contact Roles
Billing/AP Contact Email	Contact Roles

Any of these left blank appears in the Missing fields panel by the same name.

How to Submit or Correct Details

The portal does not edit your KYC record. There is no save button and no submit form on /settings/kyc; the page only reads what is on file.

Submission happens through Ringer's secure KYC form. On the Update your KYC card, use Open KYC form — the button carries your company reference, so the form arrives pre-associated with your account. If your account has no form link available, the card shows an email address instead; write to help@ringer.tel and Ringer will send you one.

Ringer requires every customer to re-verify annually, so expect to revisit the form even when nothing about your business has changed.

After you submit, return to /settings/kyc and reload. The page reads the record fresh, subject to a short client-side cache, so a completed field drops off the Missing fields list once the submission has been processed — give it a minute and reload again if it has not. If a field you supplied is still listed well after that, treat it as an open question for support rather than resubmitting repeatedly.

What Verification Gates

Verification status is a compliance record, not a runtime switch. WARP does not turn off portal pages or API endpoints based on it: an incomplete record does not stop calls, block messages, or reject API requests on its own.

What it does affect sits outside the platform. Ringer manages account activation and service enablement against your verification record, and several adjacent processes depend on the same facts — 10DLC brand registration is vetted against your legal business details, and caller-ID authentication depends on your standing as a registered provider. An incomplete record will surface there even though nothing in the portal is switched off.

Who Can See and Submit It

Anyone signed in to your account can open /settings/kyc. No permission scope gates the page, so it is visible regardless of role. Multi-factor authentication must be satisfied for the session before the record loads — this is account compliance data, not session metadata.

Only one account is ever shown: the active customer for your session. There is no cross-account view.

Submission is a separate question from viewing. The secure form asks for legal, tax and regulatory facts, so route it to whoever in your organization can attest to them — typically the legal or compliance contact you named on the record.

Checking Status Programmatically

GET /v1/me/kyc returns the same record the page renders. It is a session-only endpoint: it is reached from a signed-in portal session, not with an API key, so use it for in-portal tooling rather than for a server-to-server integration.

The response carries:

• kyc_complete — true when every required field is present.
• kyc_missing_fields — an array of { property_name, label } for each outstanding field. Empty when the record is complete.
• kyc_data and business_info — the record itself, in the shape the three cards render. kyc_data is null when nothing is on file.
• source — live when read fresh from the system of record, snapshot when serving the last stored copy, none when no record exists.
• fetched_at — when the data was read (for a snapshot, when it was last stored).

A source of snapshot means the record was served from the last stored copy rather than read live, so the values may lag a recent submission. A source of none with kyc_complete: false means no record exists yet and every required field is reported missing — which is accurate, not an error.

Troubleshooting

• Status says action required, but you submitted everything. Reload the page and check the source line. If it says "Showing last-synced data", you are looking at a stored copy that predates your submission.
• A field is listed as missing that you believe you provided. Compare the label in the Missing fields panel with what you entered on the form; partial answers (for example, an FCC registration number without the registration flag set) still count as missing. If it still disagrees, contact support with the field name.
• No KYC on file yet, but your account is live. Verification and service activation are tracked separately. Complete the form; nothing in the portal is blocked in the meantime.
• The Open KYC form button is not shown. Your account has no form link associated with it yet. Email help@ringer.tel.