Email and notifications
Use email when a saved action needs a confirmation or someone needs to respond. Describe the recipient, event, content, and conditions under which a message should be sent.
A practical request
Section titled “A practical request”After a request is saved, send the customer an acknowledgment with its reference. Let staff review a suggested reply before sending it. Record whether sending succeeded so a retry does not create duplicate messages.
Configure the email capability and sender options available for the app. Check current limits and usage; do not promise a particular sender address or delivery volume before configuration is complete.
Test the sequence
Section titled “Test the sequence”Use a test recipient you control. Verify that the record is saved before acknowledgment, that the right recipient receives it, and that a failure has a useful recovery path. Repeating the action should not send accidental duplicates.
In-app notifications
Section titled “In-app notifications”If the experience includes a notification list, define how notifications are stored, who can read them, and how read status works. A badge alone does not establish delivery or privacy.