Explanation
This is an example of good acceptance criteria for this scenario because it defines what must be done (be notified when a contract has been submitted with a discount greater than 20%) without specifying how it must be done (by email, by notification, etc.) or why it must be done (to ensure profitability, to comply with policies, etc.). It also defines the expected outcome (approve or decline a discounted price) and the condition for testing (a discount greater than 20%). References:
https://trailhead.salesforce.com/content/learn/modules/user-story-creation/write-acceptance-criteria

Explanation
When a business analyst learns that another team also needs email integration in the near future, they should include that team during discovery. This is because including all relevant stakeholders early in the project can help to identify common needs, avoid duplication of work, leverage synergies, and deliver value faster. The business analyst should invite the operations team to participate in discovery activities such as interviews, surveys, workshops, observations, etc., and capture their requirements, expectations, and feedback. The business analyst should also communicate the project scope, timeline, and risks to both teams and manage any changes or issues that may arise.
References:https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/