Requirements Message

Requirements related to messaging/e-mail address handling

• To allow e-mail addresses, which neither correspond to a person nor to a group, to have an associated name, all contacts are tagged with a contact_type enumeration (over human, function and invisible).

(In the following, a "contact" denotes a specific contact in a specific organization.)

• A contact can have any number of e-mail addresses. Some of these are for information purposes and some are for sending messages to.
• A contact has a message sending state: send | do not send
• Receptionists can send text messages to any contact unless the "do not send" flag is set.
• Service agents are responsible for defining distribution lists for all contacts.
• Distribution lists exist in terms of contacts (each with an associated recipient visibility).
• The client allows the receptionist to extend the predefined distribution list for a contact with extra contacts when sending a specific message.
• Informational e-mail addresses can be marked as confidential.
• Messaging e-mail addresses should generally be considered confidential (unless they also exist as non-confidential informational e-mail addresses).
• When a message is sent to a contact, it is sent to all the messaging addresses of that contact.

Assumptions

Warnings

• The same e-mail address can correspond to more than one contact.