Store Policy Q&A Assistant
Description
What this agent manifest does
Ask a store-policy question; get the answer straight from the ops handbook, with the policy reference — or an honest "not covered.".
Build an agent that answers store associates' policy questions from the operations handbook. It uses SharePoint to retrieve the relevant policy and answers in plain language with a reference to the exact section, so an associate gets a fast, trustworthy answer on returns, opening and closing steps, safety procedures, or promo rules — without paging through the whole handbook.
This is a single-tool retrieve → grounded answer pattern using a numbered-rules structure. Numbered rules suit a policy assistant because grounding has to be strict and auditable: answer only from the handbook, cite the section, and never improvise a policy. The defining design decision is making "this isn't covered in the handbook" a first-class, expected answer — on policy questions a confident guess is actively harmful, so the agent points the associate to a manager rather than inventing a rule. It also stays out of HR and legal advice, deferring those to the right people. Edge cases cover not-found questions and conflicting policy versions (surface both, don't pick).
This pattern applies anywhere frontline staff need fast, grounded policy answers. Common scenarios for this pattern:
- Returns and exchange rules
- Opening and closing procedures
- Safety and incident steps
- Promotion and discount rules
- Day-to-day "what's our policy on…" questions
The tools it uses
This manifest uses: SharePoint
Use this agent manifest to understand
How to build multi-turn agents using numbered rules prompt structure for grounded answer + doc reference output.
License
This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .
Disclaimer
IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .