Email delivery and notifications¶
Set up outgoing mail and choose how staff receive application updates.
Needs: Core / SMTP module
CRM-NG creates messages for ticket replies, campaigns, invoices, approvals and other events. The application action creates the message; the configured mail service delivers it. If a message is missing, check both parts of that process.
Configure outgoing mail¶
Use the bundled SMTP or Gmail API module if it is your chosen mail system. Coordinate it with any existing mail plugin; running the bundled route and a conflicting standalone WP Mail SMTP setup can cause problems.
Enter credentials in the mail settings and send a controlled test to a known recipient. Check that it arrives. Mail health may show the most recent failure, including a warning bar; a later successful send can clear that warning. Read the actual error when troubleshooting.
Choose personal notification preferences¶
The notification hub supports in-app and email updates, including instant, daily digest and none where offered. The reviewed daily digest is scheduled for 8 a.m. according to the application's schedule. Approval messages are handled immediately unless notifications for that route are disabled.
Check preferences when someone is receiving too many updates or missing a message. Those choices affect notifications; assignment of the underlying task or request remains separate.
Send updates to a team chat¶
Supported webhook destinations include Slack, Microsoft Teams, Google Chat and Discord. Configure the intended endpoint, check the allowed host rules and use the test or delivery log where available.
Supported chat notifications omit sensitive HR content. Review the destination and message fields so the people in the channel receive only information suitable for that audience.
Investigate a missing message¶
Check the recipient, notification preference, any relevant opt-out, mail error and scheduled-job status. Then check the destination mailbox. The reviewed staging environment blocks outgoing mail and external HTTP effects, so a blocked staging test does not by itself indicate incorrect production credentials.