Running mode	Rules order	OneUptime level configurations		Project level configurations		Results
		Twilio credentials	Enabled SMS/Call	Twilio credentials + enable “send SMS with Twlio accounts”	Enabled SMS/Call alerts (Billing page)
SAAS	1	*	*	Set	*	Success (without checking daily limits)
	2	Set	Enabled	Unset	Enabled - CHARGE FOR ALERTS	Success (after checking daily limits)
	3	*	*	*	Disabled	Failure
	4	*	Disabled	*	*	Failure
Enterprise	1	*	*	Set	Hidden	Success (without checking daily limits)
	2	Set	Enabled	*		Success (After checking the daily limits)
	3	*	*	*		Failure

- In Enterprise Mode - We never charge for alerts. - In SaaS mode - we only charge for alerts ONLY IF global config is used. - Check limits for global config in both Enterprise and SaaS - Ideally in Enterprise Mode - Enable Alerts in Project Billing Page should be hidden. So, you should NOT check if the alerts are enabled or disabled for the project. Just check if the alerts are enabled / disabled in admin dashboard (if using global config). If using local config (project config) - do not check if the alerts are enabled or disabled. In general, under the SAAS mode, the SMS/Call alerts can fail for one of the following reasons: 1- The custom/global twilio settings are not configured. 2- SMS/Call alerts are disabled in the global configurations, and the custom twilio settings are not set. 3- SMS/Call alerts are disabled for a project (from billing page), and the custom twilio settings are not set. 4- The project's balance is not enough, and the custom twilio settings are not set. 5- The targeted phone number doesn't comply with the policy selected in the billing page (high risk countries not selected), and the custom twilio settings are not set. 6- the alert phone number is not set (in case of on-call team alerts). 7- If the API call fail for any reason (wrong credentials, service down etc...) The same reasons, excepet for 3, 4 and 5 , can cause the failure of alerts under enterprise mode. Return back to the [main README](../README.md)