Skip Navigation
Incident email responses not sending
Answer ID 7877   |   Last Review Date 12/22/2022

Why do incident responses fail to send an e-mail while forward works correctly?


Customers using Message Templates
November 2012 and newer releases


Incident responses are not being emailed to customers when "Send On Save" is selected.   The Audit log is missing "Response Sent" or showing "Failure -  Message delivery to some recipients failed".  Incidents being forwarded by email are working correctly.


There are several reasons why Incident Responses might not be emailed to the contact.  One possibility is that Message Templates might be enabled while the Contact Email Message Templates are not configured to send.

Configure Contact Message Templates to send:

  1. Navigate to Configuration > Site Configuration > Message Templates
  2. Click the Interface
  3. On the ribbon, click Contact Emails and expand the Incident drop-down menu
  4. The check boxes must be selected for the corresponding Message Template to send
  5. On the ribbon, click Deploy All and Save & Close


Additional reasons may include incorrect outgoing mailbox configurations or smtp delivery failures. Delivery failures will typically be bounced by receiving mail servers, so it is generally recommended to enable the EGW_SAVE_EMAIL_HEADERS configuration in order to capture delivery information regarding failed addresses. Your site can be configured to allow returned messages into the system which gives you the opportunity to review the message and and attempt to find root cause of the failure. Alternatively, you can configure your mailboxes to send rejected messages to a different email address without having them create or update existing incidents. Please see the below link regarding applicable mailbox configurations:


Answer ID 1638: Allowing bounced incident responses into Oracle B2C Service for review


Depending on the source of the failure, additional information may be found in the transactions table (trans_type 15 (Failure) & transactions.description). These fields have full analytics usage. Please see the link to our documentation regarding possible values for attribute and description fields within the transactions table.