A retention automation request for proposal should ask vendors to prove a customer journey, not just list features. Test email and WhatsApp together: consent, customer events, message eligibility, replies, reporting and implementation ownership. Score demonstrated workflows against your requirements, then agree on acceptance tests before committing to a platform contract.

Last reviewed: October 7, 2026.

This checklist is for Indian marketing and retention teams evaluating platforms for businesses with 10K+ contacts and 50–500 employees. Use it when separate campaign tools create manual handoffs, conflicting customer records or unclear responsibility for failed journeys.

CampaignHQ is a Meta Tech Provider offering Email + WhatsApp customer engagement, with AWS supporting its infrastructure. Evaluate it against the same requirements as every other vendor. Ask for a demonstration of the configuration you need; a feature on a product page is not proof that it covers your exact workflow.

Why a Retention Automation RFP Needs a Journey Lens

An RFP, or request for proposal, turns your operating requirements into questions vendors must answer. “Do you support segmentation?” invites a yes. “Can a customer leave the win-back audience immediately after buying?” asks for behavior your team can test.

Choose the journeys that matter for your next launch, not every journey you might eventually build. For each, record the trigger, eligible audience, exclusions, channel sequence, exit condition, owner and success measure. Keep later requirements separate so a long wish list does not obscure a launch blocker.

RFP Section 1: Company Context and Desired Outcomes

Give vendors your active contact count, channel volumes, current tools, priority journeys, integration constraints and internal owners. Explain whether you need a campaign sender or coordinated lifecycle automation. Share sample event definitions, not real customer records, during initial evaluation.

Set an observable outcome: less manual campaign preparation, fewer duplicate reminders or faster reply handoffs. If you want higher repeat purchases or renewals, define the baseline and how you will measure change. Do not accept a guaranteed uplift in place of a measurement plan.

Require vendors to list assumptions, exclusions and work your team must perform. A connector that needs custom development belongs in the implementation scope, not under an unqualified “supported.”

RFP Section 2: Official WhatsApp Platform Requirements

Ask which official WhatsApp integration the vendor uses and verify its exact Meta designation. Establish who handles account onboarding, phone numbers, template submissions, quality alerts and support escalations. A designation alone does not establish the service you will receive.

Meta’s WhatsApp Business Platform documentation describes the platform and its account resources. Require a written map of the accounts, numbers, templates and data your business controls, the access granted to the vendor, and what remains accessible if you leave.

Ask for demonstrations of template rejection, failed delivery, replies and opt-outs, not only a successful send. Request clear responsibility for diagnosis: what the vendor resolves, what depends on Meta and what requires action from your team.

Meta’s guidance on WhatsApp opt-ins requires permission before messaging. It allows general permission rather than a WhatsApp-specific opt-in when applicable law is satisfied. For your RFP, ask how the platform records the permission’s source, purpose and withdrawal, and how those records control message eligibility. Do not assume an imported phone number proves consent.

RFP Section 3: Email + WhatsApp Journey Orchestration

Two channels in one subscription do not necessarily share customer state. Ask a vendor to demonstrate one person moving through email and WhatsApp without manual exports or duplicate reminders.

Use this hypothetical acceptance test: a customer abandons a cart, receives an eligible reminder and then purchases before the next scheduled step. The remaining reminders should stop. Repeat the test with missing consent and a support escalation. These are requirements to prove, not claims that every platform supports them automatically.

Check delays, branches, re-entry and exit rules. Ask whether a failed message can trigger an appropriate fallback without bypassing the other channel’s consent or suppression rules.

Use our guide to customer retention automation platforms in India for the category decision. Keep this RFP focused on proving your shortlist’s capabilities rather than adding more vendors.

RFP Section 4: Customer Data, Segmentation, and Event Readiness

Ask how the platform identifies a customer, merges duplicates and keeps consent attached to the right record. List the profile fields and events each launch journey needs. For every data connection, name the source system, update frequency and responsible team.

Test late events, duplicate events and missing identifiers. A purchase arriving after a reminder has been queued should have a documented outcome. Ask whether operators can see rejected records and recover them without importing the entire audience again.

For customer segmentation across WhatsApp and email, test a segment’s entry and exit conditions. Require a preview of included contacts and exclusion reasons. Agree on one definition of “active” or “dormant” rather than allowing each campaign to invent its own.

RFP Section 5: Consent, Suppression, and Customer Protection

Ask how an opt-out affects campaigns already queued and journeys already running. Separate channel preferences from global exclusions so the team knows what each control stops. This is an operating recommendation, not a substitute for legal advice on your consent requirements.

Amazon SES explains bounces, complaints and delivery notifications in its email deliverability guidance. Ask who monitors those signals, who maintains suppression lists and who can pause sending. Cloud infrastructure does not guarantee inbox placement.

Request a clear rule for conflicting exclusions: an opt-out, recent purchase, open support issue or frequency cap. The marketer should be able to see why a person was excluded. Test promotional pressure across both scheduled campaigns and automated journeys, not each in isolation.

RFP Section 6: Campaign Operations, QA, and Approvals

Walk through a campaign from brief to launch. Can the right people edit, review and approve it? Can a reviewer identify changes to the audience, copy, links and schedule?

Use the WhatsApp campaign QA checklist to test missing variables, broken links, template status, exclusions and duplicate sends. Ask which checks are automated and which remain the operator’s responsibility.

Follow a customer reply through the system. Who receives it, what context do they see, and can they stop the next marketing step? Test assignment and escalation before agreeing that the inbox is ready for your team.

RFP Section 7: Reporting That Leads to the Next Action

Keep delivered messages, clicks, completed orders and attributed revenue separate. Ask how the platform defines each measure, joins events to customers and handles missing data. A dashboard total is not proof that the campaign caused the result.

Our guide to WhatsApp campaign reporting for retention teams helps frame the questions. Require an export you can reconcile with a known test order or completed booking. Then check whether the report helps your team choose a follow-up audience or investigate a failed journey.

Document access to contact, consent, event and campaign history, including retention periods and export limits. Your reporting should remain usable if you change platforms.

RFP Section 8: Integrations, Security, and Infrastructure

For each required ecommerce, CRM, helpdesk or payment connection, specify what data moves, in which direction and how quickly. Identify who handles authentication failures, retries and changed field definitions. Separate native connectors from custom work and roadmap promises.

Ask security reviewers which requirements are mandatory and which are preferred. Request evidence for hosting location, access controls, encryption, audit logs, backups, incident response, deletion and subprocessors. Do not treat a cloud provider’s certifications as the software vendor’s certifications.

For availability or recovery commitments, request the contract terms, exclusions and escalation route. For sensitive data, agree on what must not enter message bodies or customer profiles before using production data in a pilot.

RFP Section 9: Migration, Implementation, and Ownership

Request a plan covering data mapping, consent reconciliation, account and sender setup, journey rebuilds, testing, training and launch support. Every task needs a named owner from the vendor, your team or a third party.

Use the retention platform migration checklist once you have a shortlist. It covers the cutover job; the RFP should establish whether each vendor can deliver that plan and what is excluded.

Define acceptance through working journeys and reconciled data, not account creation. Ask which campaigns remain live during the switch, what can be rolled back and how reporting history will be preserved.

If sending and journey operations involve different providers, assign diagnosis and escalation responsibility explicitly. Our CampaignHQ, MoEngage and WebEngage delivery-ownership comparison shows the questions to ask. Integration architecture alone does not prove better delivery or support.

How to Score Vendor Responses

Agree on mandatory requirements before scoring. A high total should not cancel a failed consent control, required integration or security condition.

For each requirement, record the vendor’s answer, supporting evidence, responsible owner, implementation dependency and acceptance test. Classify the answer as available now, configurable, custom work, partner-dependent, planned or unavailable. Do not score a roadmap feature as delivered.

Compare the full operating commitment: implementation effort, internal staffing, additional providers, support and migration risk, as well as the quote. Choose weights that reflect your priority journeys instead of copying an arbitrary universal scorecard.

Run a Proof of Concept Around One Real Journey

Choose a controlled journey with representative test profiles and no unsolicited customer messages. Agree on expected segment membership, channel eligibility, message sequence and reporting before the vendor configures it.

Include failure cases: a duplicate event, a missing permission, a purchase before the next reminder and an opt-out during a delay. Record expected versus actual results and who will resolve each failure. End the pilot when the agreed acceptance tests pass, not merely when the demo looks finished.

Common RFP Mistakes Indian Retention Teams Should Avoid

• Letting the demo define the requirements: send the same test brief to every shortlisted vendor.
• Accepting an unqualified yes: ask for evidence, dependencies and the plan on which the capability is available.
• Leaving exceptions for launch week: test a failed journey as carefully as a successful one.

Frequently Asked Questions

1. What should we send vendors with the RFP?

Send priority journeys, current tools, channel volumes, sample event definitions, mandatory requirements and acceptance tests. Use anonymized or synthetic examples until data-sharing terms are agreed.

2. Does a Meta designation settle our WhatsApp evaluation?

No. Verify the exact designation, then test onboarding, template handling, customer replies and escalation responsibilities. An official integration does not remove your business’s consent obligations or guarantee delivery.

3. Must email and WhatsApp come from one vendor?

No. Separate vendors can be appropriate if customer data, exclusions and operating responsibilities remain clear. Compare the coordination work with a shared platform using the same journey and failure tests.

4. How long should the proof of concept run?

Base the duration on event availability, integration readiness and the agreed acceptance tests. Document unresolved dependencies before signing; a longer trial does not compensate for an untestable requirement.

5. Where does CampaignHQ fit in the shortlist?

Consider CampaignHQ when your team needs Email + WhatsApp engagement, event-triggered journeys and customer conversations in one workspace. Bring your must-have integrations and controls to the demo so the team can confirm fit and implementation scope.

Written by CampaignHQ Team