Skip to content
KODA VOICE Talk to sales

Solutions · Contact operations

A licensed voice carrier for customer-contact teams: inbound and conversational outbound

Koda Voice is a licensed U.S. voice carrier for contact operations: inbound and conversational outbound calls for customer-contact teams over a standard SIP trunk. Calls originated on Koda's network are signed under Koda's own STIR/SHAKEN Service Provider Code, customers are vetted at onboarding, and calling-hour awareness, accurate caller ID and number-reputation monitoring are part of the service.

What Koda provides

What does Koda provide a customer-contact team?

Three services over standard SIP, so they work with the contact platform or phone system you already run.

  • Outbound

    Voice termination

    Conversational outbound calls to the United States and Canada, signed under Koda's own STIR/SHAKEN identity and monitored per customer and per route.

    Voice termination →

  • Inbound

    Phone numbers

    Local numbers across U.S. markets, porting of the numbers your customers already know, caller-ID name (CNAM) and inbound routing to your SIP endpoint.

    Phone numbers →

  • Connection

    SIP trunking

    One trunk for inbound and outbound. IP allow-list or SIP digest authentication, TLS and SRTP where supported, and a Koda engineer on the line during setup.

    SIP trunking →

Traffic profile

What traffic fits Koda's network?

Koda carries live, person-to-person business calls. What does not fit is stated as plainly as what does.

Fits Koda's network Does not fit
Live sales conversations placed by a person Prerecorded or artificial-voice calls without required consent
Customer follow-ups and account reviews Caller ID showing a number you are not authorized to use
Appointment confirmations made by a person Calls to people who have asked not to be called
Support callbacks and service recovery Telephone solicitations outside the federal calling-hour window
Inbound customer-service and sales lines Short-duration, high-attempt patterns that draw complaints

The full list of prohibited uses is in Koda's acceptable-use policy. If your use case sits near the line, say so.

The carrier layer

Why do connection and compliance both come from the carrier layer?

A contact platform decides when to place a call. The carrier decides who signs it, which number it comes from and what traffic shares the route.

  • Who signs the call

    Attestation is set by the signing provider, not the contact platform. Calls originated on Koda's network are signed under Koda's own Service Provider Code (583H), not a reseller's certificate.

  • Where the numbers live

    Number reputation is built by analytics engines used by terminating carriers (TNS, for example, describes its Call Guardian engine as building reputation profiles for telephone numbers from cross-carrier call events) and attaches to the number, not the platform. Koda provisions the numbers, knows which customer uses each one and watches the traffic behind them.

  • What shares the route

    Koda vets every customer at onboarding and monitors answer-seizure ratio, call duration and failure codes per customer and per route, so the only traffic that shares a route with yours is traffic Koda has vetted for conversational use.

How Koda signs calls is on the STIR/SHAKEN page. The vetting program, including cooperation with the Industry Traceback Group (ITG), the Federal Communications Commission (FCC)-designated traceback consortium, is in the robocall-mitigation summary.

Attestation

How does attestation affect whether calls get answered?

Attestation is the signing carrier's statement about how well it knows the caller and the calling number. The SHAKEN standard, ATIS-1000074, defines three levels, and Koda applies them as written: A when the customer is verified and authorized to use the number, B when the customer is verified but number authorization cannot be confirmed, C otherwise. Numbers provisioned or ported through Koda are the simplest way to satisfy the number condition. Attestation is one input to the terminating carrier's analytics; it does not by itself decide whether a call is labeled or answered. The attestation-levels guide has worked examples.

Inbound

How does inbound work for a contact team?

Inbound for a contact team runs on the same Koda trunk as outbound. Koda provisions local numbers across U.S. markets, ports the numbers your customers already know, registers caller-ID name (CNAM) against them and routes each number to the SIP endpoint you name.

  1. Submit a signed Letter of Authorization and a recent bill for the numbers to port; the timeline depends on the losing carrier, and Koda submits, tracks and schedules the cutover.
  2. Choose new local numbers by market where you need them.
  3. Point each number at your platform's SIP endpoint, then place inbound test calls with a Koda engineer.

Details are on the phone numbers page.

Traffic quality

Why does Koda monitor answer-seizure ratio and call duration per customer?

Koda monitors answer-seizure ratio, average call duration and failure codes per customer and per route because those signals separate live conversations from short-duration, high-attempt patterns, and the call behavior they describe is what a calling number's reputation profile is built from (see number-reputation monitoring below). Watching them per customer means drift is attributed to the customer that caused it and addressed with that customer, and the only traffic that shares a route with yours is traffic Koda has vetted for conversational use. Koda tells you what it sees rather than silently throttling. The program is summarized in the robocall-mitigation summary.

Compliance-forward

How does Koda help with calling hours, consent and number reputation?

Compliance-forward means Koda treats these four things as part of the service: it asks about them at onboarding and monitors for them in traffic. Under the acceptable-use policy, the customer remains responsible for lawful calling.

Consent first

Consent first means your platform establishes and records consent before a number is called. Koda asks at onboarding how your platform records consent and honors do-not-call requests, and its acceptable-use policy makes those duties a condition of service.

Calling-hour awareness

Under federal rule 47 CFR § 64.1200(c)(1), telephone solicitations may not be made to a residential subscriber before 8 a.m. or after 9 p.m. local time at the called party's location. Koda asks how your platform enforces that window, and calling outside it is a traffic-quality signal Koda's monitoring reviews.

Accurate caller ID

Accurate caller ID means the displayed number is one you are authorized to use and one that answers when a customer calls back. Koda provisions and ports numbers to your business and registers caller-ID name (CNAM) against them.

Number-reputation monitoring

Number reputation is a profile that carrier-side analytics engines build for a calling number; TNS, for example, describes its Call Guardian engine as building reputation profiles from cross-carrier call events and crowd-sourced data that carriers use to label and block calls. A "Spam Likely" label is the visible result. Koda watches the behavior behind the profile per customer and per route and flags drift to you. See why calls get flagged as spam.

Onboarding

What do onboarding, capacity and pricing look like for a contact team?

Onboarding is an engineering and compliance conversation, not a self-serve signup.

  1. 01

    Describe the business and the traffic

    Legal name, address and a responsible officer; the platform that places the calls; where they go; expected volume; how consent is recorded. That is the Know-Your-Customer review.

  2. 02

    Interconnect

    IP allow-list or SIP digest credentials, TLS and SRTP where supported, and the SIP settings your contact platform needs, engineer to engineer.

  3. 03

    Test calls

    Inbound and outbound test calls with an engineer on the line, checking signing, caller-ID name and routing before production traffic.

  4. 04

    Go live with monitoring

    Traffic is watched per customer and per route from the first call. Numbers and capacity grow with your record.

The rate deck and order form state which billing model applies to your trunk, per concurrent call path or per minute with its billing increment, together with the rates and the concurrent-call capacity per trunk, sized from the peak concurrent conversations you describe and grown with your record. The website does not publish rates. What a carrier asks for and why is in carrier KYC: what to expect; the trunk checklist is on the network page; the billing-increments guide shows why the increment matters for short calls.

FAQ

Frequently asked questions

What should a customer-contact team look for in a voice carrier?

A voice carrier for a customer-contact team should hold its own credentials rather than resell another carrier's: its own FCC registration, Form 499 filing, Operating Company Number and STIR/SHAKEN certificate. It should state what traffic it accepts, vet its customers and publish an acceptable-use policy. Koda Voice publishes all of these in its Trust Center.

Will Koda sign every call with full (A) attestation?

Attestation level follows the STIR/SHAKEN framework as ATIS-1000074 defines it: A when the customer is verified and authorized to use the number, B when the customer is verified but number authorization cannot be confirmed, C otherwise. Koda signs under its own Service Provider Code, 583H, and applies the level the framework supports.

Can a contact team bring its existing inbound numbers to Koda?

Inbound numbers can be ported to Koda, so the numbers your customers know keep working, with the reputation you have built on them. Koda also provisions local numbers across U.S. markets, registers caller-ID name (CNAM) against them and routes each one to your SIP endpoint.

What does Koda's Know-Your-Customer review ask a contact team for?

Koda's Know-Your-Customer review asks for the business behind the calls: legal name, address and a responsible officer; the platform that places the calls; where they terminate; expected monthly volume; and how consent and do-not-call requests are handled. The review is a conversation, not a self-serve signup.

Is Koda priced per channel or per minute for a contact team?

Koda's billing model is stated in the rate deck and order form you receive after the first conversation: per concurrent call path or per minute with its billing increment, charges for the numbers you hold, and concurrent-call capacity per trunk sized from your peak conversations. The website does not publish rates; the billing-increments guide explains the arithmetic.

Talk to Koda about your contact traffic.

Tell us what platform places the calls, where they go and your peak concurrent conversations. We'll come back with an interconnection plan and a rate deck.

Talk to sales See the Trust Center