State the impact first: which actions are failing, when it began, whether every number or only a subset is affected, and whether a workaround exists. Check for a shared billing or access blocker before describing every failed number as a separate incident.
Provide a small set of request references and a redacted timeline. Keep updates in one support conversation so the scope stays clear. Do not post API keys, customer lists, or recordings to prove urgency. For a suspected security exposure, use [email protected] and describe the exposure without repeating the secret.