ACS WhatsApp WABA Tier 0 — Need BSP Escalation Without Paid Azure Support Plan

No publicly documented free ACS-specific escalation path exists for a WABA tier reassessment; this account-specific investigation must be submitted through Azure Support using a paid or otherwise entitled technical support plan.

Available escalation paths

1. Check for an existing support entitlement
   • Azure portal → Help + Support → Support Plans → Link support benefits.
   • If your organization has an Azure support contract, enter its Access ID and Contract ID.
   • Ensure the submitting account has Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope. ^1^
2. If an entitlement is available, open the case from the affected ACS resource
   • Open the ACS resource.
   • Select Support + Troubleshooting under Help.
   • Describe the issue, then select Create a support request.
   • Choose Technical, the affected subscription, and Azure Communication Services with the closest Advanced Messaging/WhatsApp problem type.
   • Request: “BSP escalation for ACS-managed WABA messaging eligibility and Authentication-template capability review.”
   Azure documents free support for subscription management, billing, quota adjustments, and account transfers, but requires a support plan for technical support. The available documentation does not classify a Meta WABA tier reassessment as an Azure quota adjustment, so the free quota-request route cannot be treated as a supported path for this case. ^1^
3. If CloudVendo qualifies for Microsoft for Startups
   • The Microsoft for Startups investor offer includes a complimentary support plan.
   • For participants onboarded after May 29, 2026: Azure portal → startup overview → Overview → Your Microsoft team → request technical guidance.
   • Earlier participants can use Get Paired in the Microsoft for Startups portal. Eligibility depends on the specific startup offer. ^2^

If none of those entitlements applies, the documented route is to purchase an Azure technical support plan. A general Service and subscription limits (quotas) → Other Requests ticket might accept the submission without a paid plan, but no ACS WhatsApp source confirms that it routes WABA eligibility reassessments to the correct team. It should therefore be considered only an unverified intake attempt, not the supported escalation process.

Information to include in the case

Provide non-sensitive context in the initial description:

• ACS resource name and subscription
• Azure region
• Channel registration ID
• Current WABA state: TIER_0, 250-message limit
• Business-verification date
• Confirmation that the display name is approved
• Authentication-template creation symptom and exact error text
• Meta support case reference and Meta’s instruction to contact the BSP
• Requested outcome: WABA messaging-eligibility reassessment and Authentication-template eligibility review

Do not publish the WABA ID, Business Portfolio ID, phone number, or Meta correspondence in Q&A, and do not place confidential information in the general support description. Supply those details through an approved secure attachment or after the assigned engineer requests them; Microsoft’s support guidance explicitly warns against including confidential information in the description. ^1^

Authentication templates

ACS does not create WhatsApp templates itself. Custom templates must be created in Meta WhatsApp Manager, submitted for Meta approval, and can then be viewed under ACS resource → Templates. ^3^

Microsoft’s FAQ confirms that:

• Business verification supports scaling marketing, utility, and authentication conversations.
• WhatsApp requires business-initiated conversations to use approved templates.
• Verification is not documented as guaranteeing an automatic messaging-tier increase or Authentication-template eligibility. ^4^

Because Meta has already confirmed that the account is active and unrestricted, disconnecting and reconnecting the active WABA is not the documented remedy; ACS prescribes reconnection for Revoked or Disconnected accounts. ^5^

Finally, ACS WhatsApp is retiring after September 30, 2028. Existing integrations remain supported during the transition, but no new features will be added, so include BSP migration in the platform roadmap. ^6^

References

1. Create an Azure support request
2. Technical Guidance & Support Overview
3. Send WhatsApp template messages
4. WhatsApp business account FAQ
5. Register WhatsApp Business Account
6. Retirement and breaking changes guide for Azure Communication Services