Bulk SMS, WhatsApp, RCS, voice and email for businesses across India [email protected] Baner, Pune

How to Conduct a Post-Campaign Review of SMS and Voice Communication

By SMSNiti Team · · 8 min read

A post-campaign review of SMS and voice communication compares what you set out to do with what the records show: objectives against delivery, process exceptions, corrections, costs, response handling and channel limits. It ends with a short list of changes with named owners. It does not try to prove that messages changed anyone's vote.

Many teams finish a campaign and move on, so the same mistakes return next time. A structured post-campaign review of SMS and voice communication turns experience into specific changes. This guide gives a review agenda, the evidence to bring, the questions to ask and how to record decisions. It belongs to our wider guide to political campaign marketing in India. It follows the records gathered in campaign communication close-out, and uses the metrics described in measuring delivery without overclaiming.

By Rupali Dahiwal. Last reviewed: 25 October 2026. This is operational guidance, not legal advice. The review is about process and delivery, not about political persuasion or outcomes.

What the review is, and what it is not

The review is a retrospective on how the communication operation ran. It looks at plans, approvals, sends, reports, issues and costs, and asks what to keep, change or stop. It is not an assessment of the campaign's political success, and it should not claim that delivery figures show persuasion. Keep that line firm, because a review that overclaims will mislead the next campaign.

Before the meeting: prepare the evidence

A review is only as good as the records behind it. Bring:

  • The original brief and calendar, so you can compare plan with reality.

  • The send log and the provider's reports, with the status definitions.

  • The approval records and version history.

  • The issue register and any incident records.

  • The invoices and the expenditure tracking sheet.

  • Notes from the helpline or reply handlers about what people asked.

If these are not ready, finish close-out first. A review built on memory tends to favour the most recent and most dramatic event.

Who should attend

Keep the group small and cross-functional: the content owner, the fact checker or language reviewer, the compliance contact, the channel operator, the finance lead and the person who handled replies. If an agency or provider took part, invite a representative for the part of the review that concerns them, and keep the internal discussion separate.

The review agenda

1. Objectives against what happened

List the objectives from the brief, one line each. Beside each, write what the records show. Mark each as met, partly met or not met, and say what evidence supports that. Where the objective was something the records cannot show, such as changing opinion, say so and drop it from the scorecard.

2. Delivery and response

Review the provider's reports by channel. Separate submitted, delivered or answered, failed and responded, using the provider's definitions. Note failure patterns and what the list or setup explains. Do not compare channels as though the audiences and messages were identical, because they rarely are. For SMS and voice differences in general, see SMS vs voice calls for election campaigns.

3. Process: where did the plan slip?

Walk through the calendar phases. Where did a gate slip, and why? Common causes are late template approval, language review that started too late, an unresolved classification question and a missing owner. Record the cause and the effect on the schedule.

4. Approvals and versions

Check whether every send matched an approved version. Were there any changes after sign-off? Was any election-specific approval needed, and was it in place on time? Our guide to the approval workflow explains the controls. Note any gap and how it was closed.

5. Issues and corrections

Go through the issue register. For each item: what happened, how it was found, how fast it was paused or corrected and what would have prevented it. Look for patterns. Three small issues with the same cause are one process problem.

6. Replies, helpline and complaints

What did people ask or complain about? Did the helpline have the answers? Were opt-out requests handled promptly? These notes often show what the messages left unclear.

7. Cost

Compare the actual cost with the plan. Where did it differ, and why? Include staff time for review, testing and corrections, not only provider charges. See what determines the budget for the cost drivers to examine.

8. Suppliers

Review the provider's and any agency's performance against the brief: support response, report quality, pause speed and the accuracy of what they told you. Note what to ask for in writing next time.

9. Decisions

For each finding, choose one of: keep, change, stop or investigate. Assign an owner and a date for each change.

Questions that produce useful answers

  • Which single change would have prevented our biggest problem?

  • What did we do that we would repeat exactly?

  • Which approval or check caught a real error, and which one never caught anything?

  • Where did we waste time?

  • What did recipients tell us the message left out?

  • Which decision did we make on a guess that we could have made on evidence?

How to turn findings into changes

A finding is only useful if it becomes a change that someone owns. For each finding, write one sentence that states the change in plain terms, such as “start template submission 20 days earlier” or “lock venue names before translation”. Then name the owner, set a date and say how you will know it was done. Limit the list to the few changes that matter most. A list of twenty items is rarely completed, while a list of five usually is.

Put the changes into the next campaign’s brief and calendar straight away, not into a report that nobody opens. If a change affects a supplier, such as faster support on peak days or clearer report definitions, put it in writing to the supplier and file their reply. When the next campaign begins, start its kick-off by reading the last review record aloud. It takes five minutes and reminds everyone what the team agreed to do differently.

Reviewing a campaign that was small or short

Not every campaign justifies a long meeting. For a small or short operation, use the same agenda in a shorter form: thirty minutes, the same evidence and a half-page record. Skip nothing in the structure, since the value comes from asking the same questions each time. Shorter reviews also make it easier to compare campaigns over time, because the record has the same shape.

Keep the review honest

  • Use the records, not recollection.

  • Do not rank people. Rank problems.

  • Do not compare to benchmarks from elsewhere. Compare to your own plan and earlier sends.

  • Say when the data cannot answer the question.

  • Write down disagreements. A recorded disagreement is more useful than a false consensus.

A review record template

  1. Campaign, period and channels reviewed.

  2. Attendees and date.

  3. Objectives with evidence and status.

  4. Delivery and response summary, with definitions.

  5. Process slips with causes.

  6. Approval and version findings.

  7. Issues and corrections, with patterns.

  8. Replies and complaints themes.

  9. Cost against plan.

  10. Supplier notes.

  11. Decisions: keep, change, stop, investigate, with owners and dates.

A hypothetical review outcome

This is an illustration, not real data. A team reviewing a district campaign finds that its SMS notices were delivered as planned, but the voice reminder was sent later than the calendar said because the recording needed a second round of pronunciation review. The issue register shows two small corrections, both caused by a venue name that changed after approval. Helpline notes show that several callers asked the same question that the message did not answer. The team decides to start voice production earlier, to lock the venue name before translation and to add the common question to the next notice. Each change has an owner and a date, and the review record is filed with the close-out set.

Common mistakes

  • Skipping the review. The same errors return.

  • Reviewing from memory. The records tell a different story.

  • Claiming persuasion. Delivery logs do not show it.

  • Blaming individuals. It stops people reporting problems.

  • No owners for changes. Nothing happens.

  • Leaving the record out of the permanent file. The next team cannot find it.

Frequently asked questions

What is a post-campaign review?

A structured meeting and record that compares plan with outcome for the communication operation, and produces specific changes with owners.

When should it be held?

Within a few days to a few weeks of the last release, once close-out records are ready and while memories are fresh.

Can a review show whether a campaign message worked politically?

No. Delivery, answer and key-press records cannot show opinion or voting behaviour. Review the operation, not the persuasion.

Who should run it?

The close-out owner or the campaign communication lead, with a note-taker.

How long should the review record be?

One to three pages is enough if each finding has evidence and each decision has an owner.

Sources checked

  • Election Commission of India, Press Note No. ECI/PN/038/2026 dated 20 March 2026. Checked 24 October 2026.

  • SMSNiti bulk SMS service and bulk voice call service pages, for the report fields referred to. Checked 25 October 2026.

To make the next review easier, ask SMSNiti about bulk SMS which reports and logs you can download, and in what format, before your next campaign starts.