> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://care.coreware.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# coreILLA - Smart Lists - DoNotDisturb (DND Split)


**DND can now be set to individual channels (FB, SMS, Calls, Emails, GMB, WhatsApp) once they are integrated with the system.**


1. What's changed?

*   Contacts that had **DND switched ON** previously - The system will continue to respect their wishes
    
*   Contacts that did **Not** have DND switched on previously, the system will continue as before 
    

**DND Statuses**

*   **DND ‘On’** \- now means NO automated/ manual outbound messages are permitted to go out (previously, we let people send outbound messages manually and only restricted ‘Automated’ messages)
    
*   **DND ‘Off’** - all automated/manual messages continue to work as usual
    
*   **DND ‘Partial’** - Some Channels are unavailable for Outbound messaging (THIS IS NEW!)

![Step 1 screenshot](https://coreware-screenshots.s3.amazonaws.com/coreILLA_-_Smart_Lists_-_DoNotDisturb_(DND_Split)_1.png)


2. What integrations channels will this affect?

If the integrations _(FB, SMS, Calls, Emails, GMB, WhatsApp)_ exist and are functional, they’ll get enlisted as channels that HL Users can either enable or disable independently or all together at once.

**If the Integrations drop or are disconnected please continue to re-connect.** Once reconnected the previous state in which the contact DND was set to, would be respected - meaning if you DND’d a contact for FB Messenger, it’ll continue to DND that contact in FB Messenger.

![Step 2 screenshot](https://coreware-screenshots.s3.amazonaws.com/coreILLA_-_Smart_Lists_-_DoNotDisturb_(DND_Split)_2.png)


3. How does it work in the case of emails?

The system will **Auto-Enable** **DND** for contact if the criteria below is met:

*   **ISP email permanent failures such as** bounce, generic, suppress-complaint, suppress-unsubscribe, and suppress-bounce. ([Understanding Mailgun Suppressions](https://help.mailgun.com/hc/en-us/articles/360012287493-Understanding-Mailgun-Suppressions-Bounced-Complained-Unsubscribed-And-Whitelisted-))
    
*   **When a recipient unsubscribes** or marks the email as **SPAM** (Mailgun complaint event).



ℹ️ Location/agency users will then have the option to disable the DND from within the contacts record for all the above reasons, except when marked as SPAM.


4. How to remove email DND for a Contact?

When a user is marked as DND for any **bounce and or suppressions events,** please head into Mailgun or your ISP provider and remove the contacts email from the suppression list, then continue to validate the email before enabling the DND in the system.



5. How does it work in the case of SMS?

**There are 2 ways in which the DND will be enabled:**

1.  If the customer replied with **Opt-Out keywords** like **STOP, UNSTOP, UNSUBSCRIBE, or CANCEL** 
    
2.  If we get [30003](https://support.twilio.com/hc/en-us/articles/360008508774-Error-30003-Message-Delivery-Unreachable-destination-handset-when-Sending-SMS), [30004](https://support.twilio.com/hc/en-us/articles/360008705094-Error-30004-Message-Delivery-Message-blocked-when-Sending-SMS), [30005](https://www.twilio.com/docs/api/errors/30005), [30006](https://www.twilio.com/docs/api/errors/30006) any of these error codes from Twilio

![Step 5 screenshot](https://coreware-screenshots.s3.amazonaws.com/coreILLA_-_Smart_Lists_-_DoNotDisturb_(DND_Split)_3.png)


6. How to remove SMS DND for a Contact?

*   **Temporary ->** Can be updated from within the contact record
    
*   **Permanent ->** Cannot</u> be updated from within the contact record, it can only be removed if the contact replies with **START** or the agency shares the contact's **Opt-in info** with support. Once approved, support will remove the contacts DND.



ℹ️ When sharing your opt-in info please include the relationship number(s), contact, and a loom showing the contacts opt-in permission. 