.png)
When a campaign message is wrong or outdated, pause first, then identify what went to whom, verify the correct facts, approve the correction through the same review path, send it, and record what happened. Decide who can pause, and write the process down, before the first send, because during an incident there is no time to design one.
Every campaign that sends at scale will eventually send something wrong: a date that moved, a number with a typo, a link that does not open. What separates a minor correction from a damaging episode is speed and discipline. This guide sets out a calm campaign message correction process for SMS and voice, from the pause to the written record. It belongs to our wider guide to political campaign marketing in India, and it relies on the version control described in the approval workflow guide.
By Rupali Dahiwal. Last reviewed: 25 October 2026. This is operational guidance, not legal advice. It uses no partisan examples and does not repeat false claims.
Why a correction process must exist before you need it
Under pressure, teams improvise. They send a quick follow-up with new unchecked wording, or argue about who may stop the send, or wait for a meeting while the queue keeps running. A written process removes these choices. It also makes the correction itself believable, because it is clear, accurate and approved.
The Election Commission's press note of 20 March 2026 refers to action against reported misinformation, disinformation and fake news during elections. Whatever the exact rules for your election, a campaign that can pause and correct quickly is better placed to deal with an error in good faith.
Step 1: Pause
The pause owner stops anything still queued or scheduled, on every channel that carries the item. Speed matters more than certainty at this stage. A pause can be lifted, but a send cannot be undone.
Know in advance how to pause in your provider's panel, and who to call if the panel does not respond.
Ask your provider, before the campaign, how quickly a scheduled or running campaign can be paused, and what happens to messages or calls already submitted.
Pause related items too, such as a voice call that repeats the same wrong detail.
Confirm the pause took effect by checking the status, not just by clicking the button.
Step 2: Establish what happened
Use your logs, not memory. Record:
Which version was sent, with its number.
To which list, and how many recipients, according to the report.
When the sending started and when it was paused.
What is wrong, in one sentence.
How the error got through, such as a skipped step or a late edit.
If you cannot say which version went out, your version control has a gap. Note it for the review, and for now treat the worst case as true.
Step 3: Verify the correct facts
Do not guess the right detail. The fact checker confirms it against a named source, such as the organiser's confirmed record. If the correct fact is not yet known, the correction may need to say that the earlier message should be disregarded and that details will follow, rather than offering a new unconfirmed detail.
Step 4: Decide the scope of the correction
Ask three questions:
Who needs to know? Everyone who received the wrong item, and only them where you can separate them.
Through which channel? Usually the same channel as the original, so it reaches the same people. Check whether a second channel is needed and whether it is approved.
How serious is the error? A typo in a helpline digit needs a quick correction. A wrong venue for an event that day is urgent.
Step 5: Draft the correction
Keep it short and plain. A reliable structure is: who is sending, what the earlier message said that was wrong, what is correct and where to get help. For example, with placeholders: "Correction from [sender name]: our earlier message gave [wrong detail]. The correct detail is [right detail]. Helpline: [number]."
Do not repeat a false claim more than you must. State the correct fact clearly.
Do not blame anyone.
Do not add new content. A correction that adds unrelated messages invites new errors.
Do not use urgent or alarming language unless the situation is urgent.
Step 6: Approve the correction through the normal path
A correction is a message, and it follows the same review as any other: fact check, language review, compliance check and release approval. Speed up the process by pre-agreeing who can approve corrections, not by skipping steps. If the original needed election-specific approval, check whether the correction does too. For the elections covered by its press note of 20 March 2026, the Election Commission required pre-certification of political advertisements on electronic media, including bulk SMS and voice messages, so ask the committee or a qualified adviser how a correction is treated in your election. See MCMC pre-certification.
For SMS, a correction usually needs a registered template, and an approved template cannot be edited. Keep a pre-approved correction template with fields for the wrong and right details, so you are not waiting for a new approval when you need it most. See bulk SMS setup for election campaigns.
Step 7: Send and confirm
Send to the affected list only, after a quick test.
Check the report to confirm the correction was delivered.
Make sure the helpline or reply route can handle the extra queries.
Confirm that nothing wrong remains queued on any channel.
Step 8: Record and review
Write a short incident record: what happened, when it was found, who paused, what was verified, what was sent, to whom and when, and what changes will prevent a repeat. Keep it with the approvals and reports. Hold a review within a few days. Look for the process gap, not a person to blame. If the cause was a late edit, tighten the rule on changes. If it was a list problem, fix the list process.
Who does what in a correction
Pause owner: stops the send and confirms it.
Channel operator: pulls the logs and the version number.
Fact checker: confirms the right detail.
Content owner: drafts the correction.
Compliance contact: checks approvals.
Release approver: authorises the correction.
Helpline lead: prepares staff for the questions that follow.
A hypothetical example
This is an illustration, not a real case. A reminder goes to the first batch with the wrong start time. A recipient replies to the helpline. The helpline lead alerts the pause owner, who stops the remaining batches within minutes. The operator confirms from the log that version 2 went to the first batch, that the start time in that version was wrong and that later batches were not yet sent. The fact checker confirms the correct time with the organiser. The content owner uses the pre-approved correction template, the release approver authorises it, and it goes to the first-batch list only. The report confirms delivery. The incident record notes that the error entered through a last-minute edit made outside the approval path, and the team tightens the rule that no edit is made after sign-off.
Prepare a correction kit before the campaign
The fastest correction is one that was mostly prepared in advance. Build a small kit and keep it where the pause owner and the release approver can reach it at any hour:
The names and phone numbers of the pause owner, the release approver, the fact checker, the helpline lead and the provider’s urgent contact.
Step-by-step instructions, with screenshots if helpful, for pausing a campaign in your provider’s panel.
A pre-approved correction template for each channel and language, with fields for the wrong and right details.
A one-page incident record form.
A short script for the helpline team, so every caller hears the same facts.
A list of the channels and lists each message type normally goes to, so you can see the scope of an error at once.
Rehearse the kit once during testing. A ten-minute drill, in which the pause owner stops a test send and the team walks through a mock correction, will reveal missing numbers and unclear steps while nothing is at stake. Update the kit when roles change, and make sure anyone who might act as a backup has read it.
Common mistakes
Sending a quick follow-up without review. It can add a second error.
Waiting for a meeting before pausing. Pause first, discuss later.
Not knowing what was sent. Version numbers and logs fix this.
Correcting to everyone. Target the people who received the error where you can.
Hiding the incident. Record it and learn from it.
Repeating the false claim. State the correct fact.
Frequently asked questions
What should I do first if a campaign message is wrong?
Pause anything still queued or scheduled, on every channel that carries the item, and confirm the pause took effect.
Can I send a correction without full approval?
Use the same review path as any message, but speed it up by pre-agreeing who approves corrections and by keeping pre-approved correction templates. Do not skip the fact check.
Do I need a registered template for an SMS correction?
For commercial SMS in India, messages go out through registered templates, and an approved template cannot be edited. Prepare a correction template in advance.
Who should be able to pause a campaign?
One or two named people on the campaign side, reachable throughout the send, plus a contact at your provider.
How do I stop this happening again?
Review the incident, find the process gap and fix it, such as locking versions, stopping late edits or improving list checks.
Sources checked
Election Commission of India, Press Note No. ECI/PN/038/2026 dated 20 March 2026. Checked 24 October 2026.
TRAI, Advice to Senders / Telemarketers, last updated 23 October 2026 as shown on the page. Checked 24 October 2026.
Before your campaign starts, ask SMSNiti about bulk SMS how a scheduled campaign can be paused and who to contact in an urgent situation, and get the answer in writing.
