₹0.15/SMS on Business planFree DLT registration helpInternational SMS worldwide
Talk to sales+91 95851 60363 Get started
Partner programme · Operators and aggregators

Become a messaging route partner of SMS Gateway Providers

AvanceZone has run SMS Gateway Providers from Coimbatore since 2000. We are adding telecom operators, A2P aggregators and international carriers to our platform as we expand SMS, WhatsApp and other channels. If you offer reliable routes at competitive prices under a strict SLA, send us your proposal.

Reply within one weekNo exclusivityIndia and international
Who we are

AvanceZone, in short

AvanceZone Technology has offered bulk SMS since 2000 and serves more than 5,000 businesses through its messaging brand, SMS Gateway Providers. We run an API-first platform for SMS, OTP, WhatsApp, RCS and voice, for customers in India and abroad.

Our platform carries several operators and aggregators at once and routes each message by delivery rate, speed and cost. Every new partner adds capacity and redundancy, which matters most for the OTP and alert traffic our customers depend on.

Who we want to work with

Telecom operators

Direct A2P connectivity for Indian circles or international networks.

A2P SMS aggregators

DLT-registered telemarketers with stable routes to Jio, Airtel, Vi and BSNL.

International carriers

Wholesale SMS on direct or declared routes, priced per country and network.

WhatsApp, RCS and voice

Business Solution Providers and channel partners for WhatsApp, RCS, voice and OBD.

Requirements

What we need from a route partner

Six things decide whether a route joins our platform. Open any card for the full details.

HTTP API first

Send, delivery report and balance endpoints over HTTPS, with keys and IP whitelisting.

SMPP when volume grows

SMPP v3.4 with several binds and an agreed TPS, once daily volumes need it.

24×7 support

A NOC that answers day and night, with an escalation matrix and named contacts.

One panel for India and international

Reports, rates, sender IDs and delivery reports for both, in one place.

Documented API

Up-to-date API documentation uploaded with your proposal, plus test credentials.

Clean, compliant routes

TRAI DLT scrubbing in India, declared routes abroad, no grey routes, real DLRs.

Partner SLA

A strict SLA, in plain numbers

Our customers send OTPs and alerts that cannot wait. These are the minimum service levels we ask every partner to commit to.

Draft terms. Final figures are agreed in the partner agreement.

Partner SLA summary
What we measureMinimum we expect
API and SMPP availability99.9% per calendar month
HTTP API responseUnder 1 second for 99% of requests
OTP and transactional delivery95% delivered within 10 seconds
Delivery reportsReal operator DLRs, 95% within 60 seconds
ThroughputYour committed TPS, at least 100 TPS to start
Support24×7×365 NOC, 15-minute response to outages
Change notice30 days for India rates and API changes, 7 days for international rates
Service credits5% to 20% of the monthly bill when availability drops
Pricing

How to quote

Quote per SMS: INR for India, and INR or USD for international. Give rates by monthly volume slab, and list any setup, DLT scrubbing, sender ID or monthly fees.

Delivery-based

You bill only for messages with a delivered report. We prefer this for OTP and transactional traffic.

Submission-based

You bill for every accepted message. Include your typical delivery ratio, so we can compare cost per delivered message.

Volume slabs

Up to 1 lakh, 1 to 10 lakh, 10 lakh to 1 crore, and above 1 crore SMS a month. Better slabs earn more traffic.

Process

How the evaluation works

Submit your proposal

Fill in the form and upload your company profile, API document, SLA and rate card.

Review within one week

Our technical and commercial team checks routes, pricing and SLA fit, and replies within 7 days.

Test traffic

Shortlisted partners connect over HTTP and carry test traffic for up to two weeks while we measure delivery, speed and reports.

Agreement and go-live

We sign the partner agreement and SLA, then add your route to our platform alongside our other routes.

FAQ

Partner FAQs

Who can submit a partner proposal?

Telecom operators, A2P SMS aggregators registered on DLT as telemarketers, international wholesale SMS carriers, and WhatsApp Business Solution Providers or RCS and voice providers. You need a stable route, a documented HTTP API and 24×7 support.

Do we need SMPP from day one?

No. The HTTP(S) API is our primary connection. We ask for SMPP v3.4 once the daily traffic on your route grows enough to need it, with at least 30 days' notice. Tell us in the form whether you support SMPP now or when you can.

Should we quote delivery-based or submission-based pricing?

Either, or both. Say clearly which basis each rate uses. We compare proposals on the cost per delivered message, so submission-based rates should come with your typical delivery ratio.

What documents should we upload?

Your company profile and API documentation are required. Your standard SLA, a rate card and licences or DLT registration help us decide faster. PDF, Word, Excel, CSV or ZIP files are accepted, up to 10 MB each.

How long does the evaluation take?

We reply within one week of a complete submission. If you are shortlisted, we run test traffic for up to two weeks before we sign a partner agreement.

Do you ask for exclusivity?

No. Our platform runs several operators and aggregators side by side and routes each message by delivery rate, speed, report accuracy and price. Routes that perform better carry more traffic.

Will our pricing and documents stay confidential?

Yes. Rates and documents are seen only by our evaluation team. They are not shared with other partners or customers, and are stored outside our public website.

What happens if a partner misses the SLA?

Service credits apply as set out in the SLA, and traffic may move to other routes. Fake delivery reports or undisclosed grey routing end the partnership.

Who can we talk to before submitting?

Email info@avancezone.com or call or WhatsApp +91 95851 60363, Monday to Saturday, 9am to 7pm IST. Mention that you are a prospective route partner.

Ready to partner with us?

Have your company profile and API document ready. The form takes about ten minutes.

Email us instead
Requirement 1 of 6

HTTP API first

HTTP(S) is the main way we connect. Every message goes out through an API call, and delivery reports come back on a callback URL.

  • An HTTPS endpoint on TLS 1.2 or newer, with API key or token authentication and IP whitelisting.
  • Single and bulk send, with a unique message ID in every response.
  • DLT fields for India: principal entity ID, template ID and header, plus Unicode and long (concatenated) messages.
  • A delivery report callback with message ID, final status, operator error code, submit time and done time.
  • A balance or credit check, and clear error codes for rejected requests.
  • Your rate limits and TPS stated in the documentation.

Good to have: status lookup by message ID, a reports API, and webhooks for incoming (two-way) messages.

Requirement 2 of 6

SMPP when volume grows

We start every route on HTTP. When the traffic on your route grows enough to need SMPP, we will ask you to open a connection. Tell us now whether you support it and how soon you can enable it.

  • SMPP v3.4 (v5.0 welcome), as a transceiver or separate transmitter and receiver binds.
  • At least two binds to start and more on request, with the TPS for each bind stated.
  • Delivery receipts through deliver_sm in the standard format, with operator error codes.
  • UCS-2 and concatenated messages (UDH or SAR), and DLT parameters as TLVs for India.
  • Enquire_link handling, automatic reconnection, and IP whitelisting or a VPN.

We give at least 30 days' notice before moving a route to SMPP.

Requirement 3 of 6

24×7 support

OTP and alert traffic does not stop at night, so support cannot either.

  • A 24×7×365 NOC reachable by phone and email, plus a shared chat channel (WhatsApp, Slack or Teams).
  • A named account manager and a three-level escalation matrix with names, numbers and email addresses.
  • Response times as in our SLA: 15 minutes for a route outage (P1), 30 minutes for degraded delivery (P2) and one business day for general questions (P3).
  • Alerts from you when an operator, circle or country route has problems.
  • A root cause report within two business days of any P1 incident.
Requirement 4 of 6

One panel for India and international

Our operations team works in your panel every day, so Indian and international traffic should be in one place.

  • One login for Indian and international traffic, with reports by country, operator and circle.
  • Live delivery reports, and message logs you can search by number, message ID and date.
  • Your rate card in the panel, per country and route, with a history of changes.
  • DLT header and template management for India, and sender ID registration status for other countries.
  • Downloadable daily and monthly reports: submissions, deliveries, failure reasons and billing.
  • Sub-users with roles, and two-factor login.
Requirement 5 of 6

Documented API

Our platform is API-driven. Clear documentation cuts integration from weeks to days.

  • Upload your API document with the proposal: PDF, Word, or an OpenAPI or Postman file in a ZIP.
  • Cover authentication, endpoints, request and response samples, the delivery report format, error codes, rate limits, Unicode and long messages, and DLT parameters.
  • An online copy that you keep current, with a changelog.
  • Test credentials or a sandbox that we can send test traffic to.
  • At least 30 days' notice before any breaking change.
Requirement 6 of 6

Clean, compliant routes

We only use routes we can stand behind with operators, regulators and our customers.

  • India: legitimate A2P routes only, under TRAI TCCCPR 2018, with DLT scrubbing of entity, header and template, and whitelisted URLs.
  • International: declare whether each route is direct, through an aggregator, or OTT or converted. No undisclosed grey routes or SIM boxes.
  • Sender IDs and message content reach the handset unchanged.
  • Real operator delivery reports only. Fake or early "delivered" reports end the partnership.
  • Data protection in line with India's DPDP Act 2023: our customers' numbers and message content are used only to deliver our traffic.
  • Valid licences or registrations for the services you offer, such as a DoT licence or DLT telemarketer registration.
Partner SLA

Service level agreement for route partners

These are the minimum terms we expect from route partners. Final figures are agreed in the partner agreement, and we consider equivalent terms. Draft version 1, October 2026.

1. Availability

  • HTTP API and SMPP available at least 99.9% of each calendar month, measured by our monitoring.
  • Planned maintenance is excluded only with 48 hours' notice, between 00:00 and 05:00 IST, and for no more than 4 hours a month.

2. API performance

  • HTTP submit acknowledged in under 1 second for 99% of requests.
  • Clear, documented error codes for every rejection.

3. Delivery speed

  • OTP and transactional: 95% delivered to the handset within 10 seconds of submission, for reachable handsets.
  • Promotional: 95% within 5 minutes, inside permitted hours.
  • International: 90% within 30 seconds, or the figure agreed per country.

4. Delivery reports

  • Real operator delivery reports only. No fake or early "delivered" status.
  • 95% of final reports within 60 seconds, and every report within 72 hours.
  • Each report carries the message ID, status, operator error code and timestamps.

5. Throughput and quality

  • The TPS you commit in your proposal, and at least 100 TPS on HTTP at the start.
  • SMPP capacity agreed when we scale, with 30 days' notice from us.
  • A delivery ratio per operator in line with the test-phase benchmark.
  • No changes to sender ID or content, and no undisclosed hops, grey routes or SIM boxes.

6. Support and incidents

  • 24×7×365 NOC by phone, email and a shared chat channel.
  • P1, route down or more than 20% failures: response in 15 minutes, workaround in 1 hour, fix in 4 hours.
  • P2, slow delivery or delayed reports: response in 30 minutes, fix in 8 hours.
  • P3, billing or general questions: answer within one business day.
  • Root cause report within two business days of a P1 incident.

7. Changes

  • India rate changes: 30 days' written notice. International rate changes: 7 days' notice with a new rate card.
  • API changes: 30 days' notice, keeping backward compatibility.
  • Any change of upstream operator or hop is notified before it goes live.

8. Billing

  • Delivery-based or submission-based, exactly as quoted in your proposal.
  • Monthly invoice with message-level records (CDR) or MIS for reconciliation. Disputes raised within 15 days of the invoice.
  • On delivery-based routes, there is no charge for failed, expired or rejected messages.

9. Service credits

  • Monthly availability below 99.9%: 5% credit on that month's bill.
  • Below 99.5%: 10% credit.
  • Below 99.0%: 20% credit, and we may move traffic to other routes.
  • Fake delivery reports or undisclosed grey routing: immediate termination, with no payment for the affected traffic.

10. Security and data

  • TLS 1.2 or newer, API keys and IP whitelisting.
  • Our customers' numbers and message content are used only to deliver our traffic, never shared or resold.
  • Security incidents affecting our traffic are reported to us within 24 hours.
  • Compliance with TRAI regulations and India's DPDP Act 2023, and the data laws of each destination country.

11. Term

  • A test phase of up to two weeks with limited live traffic, then a partner agreement.
  • Either side may exit with 30 days' notice, or immediately for a material breach.
About us

AvanceZone and SMS Gateway Providers

AvanceZone Technology is a software and messaging company in Coimbatore, Tamil Nadu. It has offered bulk SMS since 2000, and runs SMS Gateway Providers as its messaging brand.

Since 2000in bulk messaging
5,000+businesses served
1B+messages a year
MSMEregistered

Company figures reported by AvanceZone Technology.

SMS Gateway Providers

Bulk, OTP, transactional and promotional SMS, WhatsApp Business API, RCS, voice SMS, two-way SMS and a white-label reseller panel, for businesses in India and in international markets including the UAE, Saudi Arabia, Kuwait, Sri Lanka, Nepal, Singapore, Malaysia, the UK, the USA and Nigeria. AvanceZone is also a Meta Tech Provider for WhatsApp.

An API-first, multi-operator platform

Our platform runs several routes side by side. It picks a route for each message by operator, country, delivery rate, speed and cost, and fails over automatically when a route slows down. Each new partner adds capacity and redundancy for our customers.

Why we are adding partners now

We are expanding our SMS gateway, WhatsApp and other messaging services, and want more operators and aggregators on the platform, especially for high-volume OTP, transactional and international traffic.

Partner proposal

Submit your proposal

  1. 1. Company
  2. 2. Routes
  3. 3. Pricing
  4. 4. Technical & SLA
  5. 5. Documents
Company details

Tell us who you are and who we should talk to.

For example a DoT licence, NLD/ILD, or your DLT telemarketer ID.

Step 1 of 5
 Chat on WhatsApp