.png)
Before you resell a messaging or voice service, evaluate how the supplier will support the work your agency actually sells. Compare the service scope, compliance responsibilities, operating process, support, reporting, commercial terms and exit options. Ask for evidence for important claims, document who owns each task, and test a representative workflow only after the audience and permissions are clear.
1. Define the work you plan to resell
Start with the customer problem, not a feature list. Write down the channels you intend to offer, the kinds of communication involved, who supplies and maintains the recipient data, who approves content, and what your agency will own after launch. Separate a promotional campaign from a service update or authentication message; the purpose can change the applicable process and provider requirements.
Ask the supplier to describe what is included, what is handled by another provider, and what your agency must arrange. Record assumptions about onboarding, account access, campaign preparation, reporting, support hours and escalation. A verbal statement is not a substitute for a written scope.
2. Map compliance and accountability
For Indian commercial communications, make the responsibility map specific to the channel and use case. Ask who checks the sender's role, required registrations or templates, recipient consent and preferences, message content, and complaint or escalation process. The exact steps depend on the communication and current access-provider requirements, so confirm them with the parties responsible for the campaign.
TRAI explains that unsolicited commercial communication can include unwanted messages or voice calls that do not follow the recipient's consent or registered preference. Its telemarketer guidance describes distinct delivery, aggregation and voice-calling functions. Use these as prompts for a responsibility discussion, not as a complete legal checklist: TRAI's UCC guidance and TRAI's advice to telemarketers.
Put the answers in a simple handoff table: task, responsible party, required input, approval owner, evidence retained and escalation contact. If no one accepts a critical step, pause the reseller plan until ownership is resolved.
3. Verify service fit with a realistic workflow
Describe one representative job from brief to report. Ask the supplier to walk through the relevant setup, review points, test process, launch approval, available reporting and exception handling. Request a demonstration or written documentation for any capability that matters to your offer. Do not rely on a broad claim such as “supports integrations” without confirming the specific system, scope and support arrangement you need.
Check practical fit: how campaign files are transferred, who can see customer data, how changes are approved, what happens when the audience or message is rejected, and how a pause or correction is requested. For an agency, white-label terms, customer ownership and permitted use of the supplier's name should be explicit rather than assumed.
4. Assess support, reporting and escalation
Ask who responds during preparation, launch and post-campaign review. Confirm the support channel, expected response process, escalation route and information the team needs to investigate a problem. Review a sample report and identify which statuses are measured, when the data is available, how long it is retained and what it cannot tell you.
Agree on a review routine that distinguishes attempted activity from outcomes you can actually observe. If a link, response flow or conversion event is not instrumented, do not promise that the supplier can report it.
5. Read the commercial and exit terms
Compare the full written terms, including onboarding charges, minimum commitments, billing units, taxes, validity, refund or credit rules, rate changes, support scope, service restrictions and termination. Ask how unused balances, open customer requests, campaign records and account access are handled if the relationship ends. Check whether your customer contract and supplier contract allocate responsibilities consistently.
Build a simple margin model from the supplier's actual quotation and your own costs. Treat every price, delivery commitment, coverage statement and service-level promise as unverified until it appears in current written terms that you can pass on accurately.
A practical comparison checklist
Scope: channels, use cases, setup and exclusions are written down.
Compliance: each registration, audience check, approval and complaint task has an owner.
Service fit: the supplier demonstrates the workflow you plan to sell.
Data and access: transfer, permissions, retention and incident contacts are clear.
Operations: launch checks, pause requests, corrections and escalation are defined.
Reporting: sample outputs and their limits are understood.
Commercials: current quotation, billing rules, support and termination terms are documented.
Reseller model: branding, customer ownership, training and permitted claims are explicit.
Illustrative example
Imagine a small agency adding SMS campaign execution to its service menu. Before accepting a client, the agency maps who confirms the intended message purpose and audience, who handles sender and template readiness, who approves the final copy, who launches the test and campaign, and who explains the report. This is a hypothetical workflow, not a customer result or a description of any supplier's guaranteed process.
Questions to ask before you decide
Should an agency choose the cheapest supplier?
Price is one input. Compare the written scope, responsibilities, support, operational fit and exit terms against the service you intend to provide.
How can I check a supplier's capability?
Ask for current documentation or a demonstration of the exact workflow you need, then confirm the scope and limits in writing.
What should a reseller confirm about compliance?
Ask each party to identify its tasks for the specific channel and use case, including audience eligibility, required setup, approvals and complaint handling. Confirm current requirements with the responsible provider and official guidance.
SMSNiti lists bulk messaging services and reseller information on its Bulk SMS service page. Review the current scope and request written answers to your own onboarding, channel and support questions before deciding whether a supplier fits.
Build a fair supplier scorecard
A scorecard makes a supplier conversation easier to compare. Decide the criteria before the demonstrations, and write what evidence would count for each one. For example, “support is available” is too broad to score consistently. A more useful test is whether the supplier can show the support channel, hours, escalation owner and process for an urgent correction. Keep the scoring simple: meets the need, partly meets it, does not meet it, or not yet confirmed. Add a note and evidence link beside every score so a confident presentation does not become a substitute for proof.
Weight criteria according to your service model. An agency that prepares and monitors campaigns may care greatly about operational support and approval workflows. A reseller that only introduces a customer may focus more on account ownership, handoff and commercial terms. Do not let a high score on a minor feature cancel out a missing answer about a critical responsibility. Identify “must have” requirements separately from preferences, and treat an unknown answer as unknown rather than assuming it is acceptable.
Check the operating model, not just the feature list
Ask the supplier to walk through a normal campaign and one exception. A normal example could begin with a client brief, continue through audience preparation and copy approval, and end with a report and a review. An exception might be an incorrect audience file, a late copy change, an unexpected rejection or a request to pause. At each step, ask who acts, what information they need, how approval is recorded and how the next person knows the work is ready. This reveals handoffs that a feature checklist can miss.
Agree how changes are controlled. A campaign can become different from the version that was approved when a date, offer, destination link, recipient segment or message changes. Decide which changes require a new approval and a new test. Confirm who can make changes in the account, whether those changes are visible to the client, and how the final approved version can be identified. These are operating questions for your supplier arrangement; the exact platform capabilities must be demonstrated rather than presumed.
Ask precise questions about data and access
Map the data your agency expects to handle: contact details, campaign content, sender details, response records and reports. For each type, document where it enters the workflow, who can view or export it, what purpose it serves, how long it is retained under the agreed terms, and what happens when the relationship ends. Ask whether a customer can be separated from other accounts and how access is removed when a team member changes role. Use the supplier’s current written policies and your own obligations to decide which arrangements are suitable.
Check the mechanics as well as the policy. Is a file sent through a controlled account, or emailed between several people? Does the client need a separate login? Who resets access? If an account is shared during onboarding, how will it be replaced with named access? These questions can be recorded without requesting more personal data than the campaign requires. Keep test files synthetic or properly authorized, and do not send a real contact list to a supplier merely to see whether the upload works.
Compare the written commercial offer
Use a like-for-like example when comparing quotations. State the channel, use case, expected activity, setup needs, support expectations and reporting requested; then ask each supplier to identify assumptions and exclusions. Separate one-time onboarding, recurring commitments, usage charges, taxes, optional work and any third-party costs. Check the unit used for billing and how partial units, failed attempts, unused balances or changes in rates are treated. Do not infer a final customer price from a headline rate without including your delivery and account-management costs.
For a reseller model, verify whether the quotation permits the way you plan to sell. Ask about client onboarding, resale rights, branding, customer support boundaries, renewal and termination. If the supplier can change terms, find out how notice is given and what options you have for existing customers. Ask who owns the customer relationship and the operational records if either party exits. Have the final commercial language reviewed by the person in your organisation who approves supplier contracts.
Use a small, controlled evaluation
If a supplier appears suitable, define a limited evaluation before offering the service broadly. Use an authorized internal test or a properly approved low-risk use case. Set the objective, named participants, data limits, timeline, success criteria, stop conditions and person who can approve the next step. Avoid real customer data unless it is necessary, authorized and covered by the agreed safeguards. Record what was tested and what was not. A test is evidence about the specific workflow and conditions used; it is not proof that every future campaign will behave the same way.
At the review, compare expected steps with what actually happened. Were the responsibilities clear? Did the team know where to raise a question? Did the report contain the fields needed for the customer conversation? Were there delays or manual handoffs that need to be priced into the agency’s service? Write down limitations alongside strengths. If an important capability could not be demonstrated, keep it marked “not confirmed” and do not promise it to a client until it is verified.
A one-page decision record
Before deciding, capture the use cases you will support, the evidence reviewed, critical gaps, agreed owners, commercial assumptions, data and access questions, support route, and next action. State why the supplier fits the agency’s current scope and what the agency will decline to sell until more information is available. Add a review date so the arrangement is revisited when your service changes, the supplier changes its terms or your customer requirements change. A short written record protects the quality of the decision better than relying on notes scattered across calls and messages.
For an agency comparing two providers, the decision may be “Supplier A is suitable for a narrow SMS workflow after the open support question is resolved,” rather than a broad claim that one platform is best. A carefully limited conclusion is more useful: it tells the sales and delivery teams what they can offer now, what they must verify, and which promises are out of scope. Confirm the conclusion with the people responsible for compliance, commercial approval and campaign delivery before making it part of a client proposal.
