A code guide covering twelve carrier rejection codes, each with a plain label and a concrete instruction. Codes are extracted from the verbatim carrier text, the flagged field names are translated into wizard language, and every filing is appended to an attempt history so you can see how many times each half was tried and whether the last change helped.
Also called: 30896 · opt-in couldn't be verified · why was my campaign rejected · carrier error codes
- 1The campaign status read pulls the carrier's structured verdict: description, error code and flagged fields.
- 2Field names are mapped to wizard language (MESSAGE_FLOW becomes 'how you collect opt-in').
- 3Codes are extracted and looked up in the guide.
- 4The attempt is appended to a capped history with its kind, status, reason and codes.
- 5The panel shows the verdict, the code, the flagged field and what to change.
Recorded at the top of the attempts module (Keith 08-14): 'Every filing costs money and takes days, so the useful question is never just "did it fail" — it is "how many times, on which part, and did the last change help". The dashboard used to answer none of that: one latest failure string, and a fixed line of advice about EIN and IRS paperwork that was printed for every rejection regardless of cause.' The structured parse exists because the description alone names neither the code nor the field — recorded against a real campaign rejection (Keith 08-16, code 30896 / MESSAGE_FLOW). And the advice function deliberately returns nothing for unknown codes, because 'saying nothing beats the old behaviour of confidently offering EIN advice for a Call-to-Action failure.'
- Rejections showed one opaque string with generic, often wrong advice.
- There was no record of how many filings had been attempted or what changed between them.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →