Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Specify what the process needs: linking conversations, preparing drafts, receiving notifications or sending messages. These are different capabilities and should not be authorized as one undifferentiated package. Define mailboxes, users, time scope and attachment handling before connecting an account or copying messages into the CRM.
Illustrative example
Illustrative example: sales wants to see an opportunity's latest agreement. A conversation reference and reviewed summary may suffice without importing years of email. If sending is added later, the design should show the recipient, subject and content before a person confirms an action that reaches an external recipient.
Acceptance check
Test a correctly linked message, an unrelated message and a disconnected account. Failure must not be announced as successful sending, and permission changes must affect access. Acceptance requires understandable boundaries and evidence of the actual operation state, not merely the appearance of an email provider's logo in settings.
Key takeaways
- Connect only the email capabilities that the workflow actually needs and can verify reliably.