How it works

Four steps, starting with an email.

There is no automated signup and no instant activation. Every request is read by a person, and the requirements we send back depend on the service, the markets, and the use case you describe. This page explains what to expect at each stage.

The four onboarding steps

  1. Send Your Request

    Contact Numeratel by email and briefly explain the service, locations, expected usage, and any technical requirements.

  2. Receive the Requirements

    Our team will reply with the information and documentation needed to review your request.

  3. Complete the Review

    Provide the requested business, identity, technical, or use-case information. Additional verification may be required depending on the service.

  4. Service Configuration

    If approved, Numeratel will confirm availability, commercial terms, configuration details, and the next steps.

Submitting a request does not guarantee approval, availability, or activation.

Step one, in detail

What to put in your first message.

You do not need a formal specification. A few clear paragraphs covering these points lets us give you a useful answer on the first reply instead of asking a series of follow-up questions.

Use the request form instead

Who you are

Your organization, what it does, and the website or platform involved. If you are applying as an individual, say so — it changes what we ask for, not whether we reply.

Which service you need

VoIP connectivity, virtual numbers, SIP integration, or something that does not fit those descriptions. A rough idea is fine at this stage.

Which markets are involved

The countries or regions you need to call, receive calls in, or hold numbers in. This is usually the single most useful detail you can give us.

Expected usage

Approximate volume, concurrency, and whether it is steady or seasonal. An estimate is enough; we are looking for the order of magnitude.

How the service will be used

Customer support, sales, internal calling, notifications with recipient consent, platform functionality, and so on. Being specific here speeds the review considerably.

Technical details, if you have them

Platform or PBX, authentication preference, codecs, and whether you have static addresses available. Leave this blank if you are not sure — we can work it out together.

Steps two and three

What the review usually involves.

Requirements vary by service and market. The categories below cover what is most commonly requested — you will receive a specific list, not a generic checklist.

Business information

  • Registered name and company number
  • Registered and operating address
  • Website or platform
  • Contact for technical and billing matters

Identity verification

  • Identification for the responsible person
  • Proof of address, where applicable
  • Confirmation of authority to contract
  • Additional checks for certain markets

Technical and use-case detail

  • Platform, addresses, and authentication
  • Traffic profile and capacity
  • Description of intended use
  • Consent and compliance arrangements, where relevant

Why we ask

Numbers and voice routes are regulated in most markets, and carriers expect the provider assigning them to know who is using them. Verification protects the people receiving your calls, keeps our routes in good standing, and means we can defend your traffic if it is ever questioned.

Information collected during the review is handled in line with our Privacy Policy. We ask for what the service and market require, not more.

Step four

If your request is approved.

  • We confirm what is available for your markets and services, and anything that could not be supported.
  • Commercial terms are provided in writing, based on service type, destination, volume, capacity, and configuration.
  • Configuration details are agreed with your technical contact, including authentication, addresses, and routing behaviour.
  • Service is provisioned and tested before it is treated as live.
  • You receive the contacts to use for support, billing, and compliance matters.

Numeratel may decline a request based on availability, risk, compliance requirements, intended use, or network considerations, and is not obliged to give a detailed reason. Service remains subject to the Acceptable Use Policy and Terms of Service for as long as it is active.

Start with step one.

Send the details and we will come back with the requirements that apply to your request.