Skip to content
Request rates
Menu
Contact on Telegram

DraftThis page is a draft. Values set in grey monospace are placeholders and are not confirmed yet.

Request a test route

Name up to TEST_DESTINATIONS_MAX destinations. We open a bind within TEST_BIND_LEAD_TIME from receipt of your source IPs, after a passed company check, with FREE_TEST_ALLOWANCE free messages. Test on your own numbers, with your own tester.

Request a test route
NAMED_ROUTING_LEADROUTING_LEAD_TITLEContact on Telegram

Test terms

  1. We agree the success criteria with you before the first message: DLR matches the handset, sender ID intact, content intact, latency within an agreed p95. CONFIRM_BEFORE_PUBLISH
  2. Test traffic gets no special handling: it runs exactly like production. CONFIRM_BEFORE_PUBLISH
  3. Run your own TelQ test, or use any independent tester.
  4. Verdict within TEST_VERDICT_DAYS. If the test passes, we move to KYC and contract; if it fails, you owe nothing. CONFIRM_BEFORE_PUBLISH
  5. Test traffic must follow our acceptable use policy.

Tell us what to test.

We open test binds after a short company check. Fields marked * are required.

Company type

A company address speeds up our company check, but any address is accepted. We reply from CONTACT_EMAIL_DOMAIN.

We coordinate the test here, and only from the handles on our verify page.

Traffic type
Connection

LOOKUP_TRIAL_SIZE live lookups for a verified business, set up with your test bind.

For example your sender IDs, timing, or success criteria you already use.

Test traffic must follow our acceptable use policy (opens in a new tab).