The speed of our support team's response time depends on the priority level you select when you submit your ticket, your support plan, and how your plan works with our business hours. Your ticket’s priority level can be changed by the agent to be higher or lower based on how an issue impacts your business.
This table is a quick reference to the support levels you can expect according to the ticket priority, issue status, and support plan you are on.
Note: Twilio Support team works standard business hours in the Americas, APAC, and EMEA regions. For full details, please see Twilio Support Business Hours.
| Support Plan | |||||
| Ticket Priority |
Issue Status |
Developer | Production | Business | Personalized |
| 1 | Business Critical | N/A | Within 3 business hours | Within 1 hour (24x7) | Within 1 hour (24x7) |
| 2 | Degraded Service | N/A | Within 6 business hours | Within 2 business hours | Within 2 business hours |
| 3 | General Issue | N/A | Within 9 business hours | Within 3 business hours | Within 3 business hours |
Notice: Requests for Developer Preview or Beta Products, and those that are handled by specialty non-Support groups within Twilio, are not bound by our standard Support SLAs, and may vary in response times. These groups mainly deal with non-Twilio outside entities such as carriers, and governmental or regulatory bodies, where we are unable to dictate the terms of our communication. Some examples include:
- Phone Number porting and inventory operations
- Billing Tax analysts
- Consumer Trust
- Messaging 10DLC review/registration, and Short Code procurement.
While these delays may be outside of our control, please rest assured that Twilio strives to handle your request quickly and efficiently, and will do our best to keep you updated at regular intervals.
PRIORITY LEVELS
The priority level of a ticket you submit is used to determine what your response time will be.
- PRIORITY 1, BUSINESS CRITICAL: This status only applies to applications that are in production. It represents a complete loss of service or a significant feature that is completely unavailable, and no workaround exists. Does not include development issues or problems in staging environments.
- PRIORITY 2, DEGRADED SERVICE: Includes intermittent issues and reduced quality of service. A workaround may be available. Does not include development issues or problems in staging environments.
- PRIORITY 3, GENERAL ISSUE: Includes product questions, feature requests and development issues.
You can set the business impact of a ticket when submitting via our Help Center web form or in our Console (requires login). However, Twilio reserves the right to reclassify the priority level at any time if we reasonably believe the classification is incorrect. Reclassifications are almost exclusively used in situations where a ticket is submitted as Priority 1, but the situation contradicts the Priority 1 definition - usually a non-production setup issue, or how-to question. Twilio team members may also increase the priority level if the situation is deemed to be more urgent than originally reported. If you do not choose a priority level when you create a ticket, the ticket will default to Priority 3.