An Azure communication platform for deploying applications across devices and platforms.
Manage the existing request from the Azure portal rather than opening another ACS technical case immediately:
- Go to Help + support > All support requests, open the case, and select New message.
- Add a short routing clarification: Azure Communication Services > Telephony and SMS > Regulatory Documents > US local number/10DLC campaign registration. Include the exact portal error, UTC timestamp, ACS resource/region, subscription billing country, brand status, campaign type, and a screenshot. This should resolve the subject-versus-description mismatch noted in the comments.
- Check that the case is not marked Waiting for customer and that the contact email/phone are correct. Also check junk mail for the case thread.
- If your support plan and business impact allow it, use Change severity. If an engineer is already assigned, request the severity change through New message.
Two weeks without acknowledgement is well beyond normal initial-response targets. If the case still receives no response after the update, create a separate support request specifically for help managing an existing support request, and reference the original case number. Azure's support guidance explicitly permits that path.
Avoid creating multiple duplicate ACS technical cases, because that can split the history and routing. Also remove the case number and any subscription/resource identifiers from this public Q&A post; share them only inside the private support case.