These problems live in Meta, not in Kylo. Kylo cannot fix them, and it shows them only as failed sends.

Business verification stuck or rejected

Symptom. Your messaging tier does not grow, or Meta limits what the account can do. Cause. Meta requires business verification for higher messaging tiers and some permissions. A rejection usually means the documents do not match the business details. Meta also ties the template limit to verification: 250 templates per account when the portfolio is unverified and up to 6,000 when it is verified. What to do. Complete verification in Meta Business Settings. Kylo links you to Meta during Facebook login but does not run verification. See Meta: quality rating and Messaging limits.

Payment declined or missing

Symptom. Template sends fail and the receipt carries a payment-related Meta error. Cause. Per Meta’s error table, a payment account is not attached, the credit line is over its limit or not active, or the account was deleted. Without a valid payment method, template sends do not go out. A Meta Verified for Business payment can also be declined when the card expired or is unsupported, which is a Meta billing issue independent of Kylo’s Stripe billing. See Meta: WhatsApp payment help. What to do. Fix the payment method in Meta Business Settings, Billing. Then pause and resume the campaign, and leads retry after the one hour failure cooldown. See Send errors.
Meta billing and Kylo billing are separate. Your Kylo plan pays for agent credits. Meta charges for WhatsApp messages on its own bill.

Send errors

The full list of Meta error codes.