Skip to content

Add Meta payment/currency error-code mapping to observe-whatsapp playbooks#6

Draft
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-code/whatsapp-payment-error-mapping
Draft

Add Meta payment/currency error-code mapping to observe-whatsapp playbooks#6
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-code/whatsapp-payment-error-mapping

Conversation

@posthog

@posthog posthog Bot commented Jun 28, 2026

Copy link
Copy Markdown

Summary

The observe-whatsapp skill's message-debugging-reference.md and triage-reference.md both tell the agent to "surface error codes and map to remediation" / "translate error codes into user-facing guidance", but shipped no mapping for the Meta payment/currency error codes that the message logs actually surface. So when users hit the "Payment method needed in Meta" error testing WhatsApp templates and then dug through failed message logs, the playbooks couldn't explain the very error on screen.

This adds a Meta error-code reference to both files, with explicit guidance for code 131042 ("Business eligibility payment issue"):

  • It's a Meta account billing problem (no payment method, or currency mismatch) — not a code/template bug, and not fixable from Kapso.
  • Templates / business-initiated sends are blocked, but 24-hour-window replies still work — mirroring the existing payment "Special case" in health-reference.md.
  • Remediation points the user to Meta Business Suite > Billing & payments.

Why

Across two replay sessions users repeatedly hit the payment-method error sending template tests (saludo, saude) and got confused inspecting Meta logs, abandoning work mid-session — the agent had no way to translate the error. The real inline product fix lives in the Kapso web app; this closes the documented gap in the skills repo so the agent can at least explain it.


Created with PostHog Code from an inbox report.

…books

message-debugging-reference.md and triage-reference.md both instruct the agent
to map/translate Meta error codes to remediation, but shipped no mapping for the
payment/currency codes the logs actually surface. Add a Meta error-code reference
to both, with explicit guidance for code 131042 ("Payment method needed in Meta"):
it is a Meta account billing problem (missing payment method or currency mismatch),
templates are blocked while 24-hour-window replies still work, and it is fixed in
Meta Business Suite, not Kapso.

Generated-By: PostHog Code
Task-Id: 835af75f-8ce2-45ac-9b5b-ad00b8206058
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants