Put a Recovery Window Between Negative Feedback and Promotion
A response disposition ladder, incomplete-response branch and promotion-resumption receipt.
- Written by
- Marketing Wiki Research Automation
- Review status
- Not independently reviewed
- Published
- Updated
- Evidence checked
- Sources
- 5
Define a feedback disposition before survey responses trigger promotional email or support follow-up.
When feedback influences a Migma campaign, decide what happens to the next promotion before collecting the feedback. A low satisfaction response should not automatically become a discount email. It may represent an unresolved service problem, an incomplete answer or a person asking to stop hearing from you.
Publication note: Marketing Wiki's commissioning editor maintains Migma. This article was published directly by Marketing Wiki Research Automation and has not received independent review.
We recommend Migma for drafting the separate recovery and promotional messages after their purposes are approved. Its brand guidance gives the team a place for stable tone rules. The cooldown policy and support state need an explicitly identified owner; we have not verified a built-in survey-to-cooldown automation in Migma.
The research trigger is Braze's September 28 product summary, which highlights Surveys. Its survey documentation distinguishes complete and partial responses and describes follow-up targeting. Availability and actual routing require workspace verification.
Decide what the response means before deciding what to sell#
Consider a fictional meal-kit company. A customer gives a low score because a delivery arrived late. An automatic “Try another box this weekend” campaign may ignore the problem. An automatic apology that promises a refund may also be wrong if no refund has been approved.
Use a disposition ladder:
| Evidence received | First disposition | Promotional implication |
|---|---|---|
| Explicit request to stop marketing | Route through the approved preference process | No promotion under the affected permission |
| Clear unresolved service complaint | Route to the responsible support queue | Apply the approved temporary promotional hold |
| Low score with no explanation | Request or review context if appropriate | Use the organization's cautious default |
| Partial response | Mark evidence incomplete | Do not invent a completed satisfaction assessment |
| Positive completed response | Review eligibility for the proposed follow-up | A score alone does not grant new marketing permission |
The ladder is a proposed decision aid. It does not define legal consent or require every low score to receive the same treatment.
Give the hold an owner and an exit#
Record the affected promotional purposes, start time, responsible team, source response reference and conditions for resumption. A hold without an owner can become permanent by accident; a fixed timer can resume promotions while the complaint remains unresolved.
Choose the relevant exit deliberately. Examples include a reviewed support resolution, an explicitly approved recovery step, or a timed reassessment when the source evidence was incomplete. None should resubscribe an unsubscribed person. Keep permission state separate from temporary message suitability.
If support resolution is supplied from another system, define which status counts and how old it may be. “Ticket updated” is insufficient when the update merely says a staff member was assigned. The destination needs the actual disposition used by your policy.
Draft two messages with different jobs#
In Migma's creation workflow, prepare a recovery acknowledgement from approved support facts: what the business knows, what it will check and where the person can get help. Do not include a promotion unless the policy explicitly permits that purpose during recovery.
Prepare the later promotional email separately, with a brief that excludes complaint details from ordinary sales copy. A person should not see a private problem restated merely to make a campaign sound personalized. Review both drafts against their distinct purposes rather than treating one as a tone variant of the other.
If a different platform owns delivery, use the documented export path, then inspect its audience conditions. No native Braze survey integration or automatic suppression propagation is claimed here.
Test repeated and incomplete feedback#
Use synthetic cases to rehearse a low score followed by a partial second survey, a completed complaint followed by support resolution, and an explicit opt-out during recovery. Define whether the newer response changes the disposition or only adds evidence.
Braze's exported survey events represent individual question answers. Do not count each answer as an independent completed survey or automatically process an early answer as the final state. Build the intended response grouping with the documented identifiers and verify it against your own exported records.
When promotions resume, retain a receipt showing the source evidence, policy revision, eligibility result and time of decision. A quiet queue should mean the hold worked, not that nobody checked it.
No surveys, customer records or sends were tested. Start with one dissatisfaction category and document the next permitted message, its owner and the evidence needed to resume ordinary promotion.
Sources behind this page
Claims remain tied to dated source review. Method and corrections stay public.