"Approved" on a WhatsApp survey template usually means what it sounds like: the survey is live, and it'll send. Except for one category, that's not quite true. A survey can be approved and still fail every single send to a US respondent, and the approval screen won't tell you why. The gap is category: Utility and Marketing aren't a label you pick when you build a survey, they're a rule Meta enforces, and getting it wrong doesn't bounce your submission, it quietly breaks delivery weeks later.
The rule, in one sentence
Utility is a message your customer needs to complete or service something they already started: an order, a booking, an appointment, a delivery. It has to name that specific thing and arrive because of it. Marketing is everything else, including a survey that fires right after a real interaction, if the ask itself serves your business more than it serves the respondent. Most surveys read as Marketing to Meta by default, and that's not a flaw in your wording, it's what asking someone for feedback actually is. The exceptions are narrower than most teams expect.
Why delivery is where this gets confusing
"Your order #4471 is out for delivery, arriving by 3pm" is Utility. Your customer needs it, it's operational, and it's tied to one order. "How was your delivery experience? Tap to rate us" is Marketing, even though it fires right after the same delivery and mentions the same order number. Naming the transaction doesn't change what the message is: the first one delivers something the customer needs, the second one asks the business a favor. That distinction, need versus ask, is the whole rule, and it's exactly why a feedback survey is the hardest category to get right. It always LOOKS transactional, since it usually follows a real event, but the ask itself is what decides the category, not the timing.
- Order confirmed, shipped, out for delivery, delayed: Utility. The customer needs to know.
- "Rate your delivery," "how did we do," "leave a review": Marketing, no matter how it's worded or how recently the order arrived.
- A booking confirmation or appointment reminder: Utility. A satisfaction survey sent after the same appointment: usually Marketing, unless it's genuinely part of servicing that specific visit.
The part that actually breaks surveys: silent re-filing
Here's what catches most teams off guard. You can submit a survey AS Utility, correctly, and still have it approved as Marketing. Meta's own review can re-file the category during approval, and unless you specifically pinned the category at submission, the platform won't stop it, and most survey tools won't show you it happened. The survey still says "Approved." It just won't be Utility anymore.
That matters because Marketing-category templates are currently blocked outright from delivering to US numbers. A survey that was working fine, submitted correctly, approved, can start silently failing every send to a US respondent the moment Meta's review re-files it, and the only symptom is response rates that quietly drop to zero. No error banner on the survey itself, just sends that never arrive.
What actually holds up as Utility
The surveys that stay Utility, reliably, are the ones woven directly into servicing one specific transaction, not asking about it afterward. "Your claim is settled, tap to confirm the payout details" holds, because the tap IS the next required step. "Your claim is settled, how did we do?" doesn't, even though it's the same claim and arrives in the same conversation. The second one is a request, and a request is Marketing, whether it's a satisfaction score, a recommend rating, or an open-ended question.
What doesn't, no matter how it's worded
Some surveys get miscategorized on purpose, or by accident, in the direction that hurts them: rewording a feedback ask to sound transactional. It doesn't work, and it isn't worth trying. Review requests, referral asks, win-back check-ins, loyalty pulses, generic "how did we do" surveys: these serve the business, not an obligation to the respondent, and no amount of naming a specific order changes that underneath. Meta's reviewers are specifically looking for exactly this pattern, a promotional ask dressed in transactional language, and dressing it up risks the review flagging the whole account, not just the one survey. If a survey is genuinely a request for feedback, and most are, submit it as Marketing and plan around the US restriction rather than trying to talk your way past it.
How to keep it from happening to you
Two things actually help. First, pin the category at submission when you mean Utility: it tells the provider the category is a commitment, not a suggestion, so a re-filing shows up as a visible rejection instead of a silent swap. Second, don't trust "Approved" on its own, check what category actually got approved, not just that something did. WhatsApp Surveys surfaces Meta's real, final category on every survey, color-coded, with a clear flag the moment a submission comes back different from what was requested, so a re-filing is something you catch in a glance instead of something you find out from a week of empty response counts.
Want to run surveys like these? Request early access to the full survey template library.