A library branch manager needs a single thank-you email draft to a donor. Should the manager create a custom agent?
Select an answer to reveal the explanation.
Short Explanation
One thank-you note doesn't need its own permanent help desk. Fire up chat or draft in Outlook and save agent-building for the stuff that keeps repeating.
Full Explanation
Creating a custom agent is unnecessary for a single thank-you email to a donor. A library branch manager can draft with Copilot chat or ordinary Outlook Copilot drafting; building a published agent would be overkill for a one-off message. Judging when not to create an agent is as important as knowing when to create one—AB-730 fundamentals include right-sizing the experience to the task.
Every individual email requiring its own published agent fails by forcing agent sprawl for disposable correspondence. Agents required because Outlook cannot draft any email without an agent fails because in-app Copilot drafting does not depend on a custom agent for ordinary mail. Copilot forbidden from drafting any library communications fails as an absolute ban not implied by the scenario; the issue is proportionality, not prohibition.
Exam caveat: If donor communications later become a high-volume, tightly branded program with standing style rules and knowledge (gift levels, stewardship language), an agent may become appropriate—but that is a different need than one thank-you note.
Operational check: Draft the donor thank-you in Outlook or Copilot chat, apply the library's existing acknowledgement template if one exists, have the manager review tone and gift details, and only revisit agents if the stewardship workflow becomes recurring and standardized.