← All Trainings

Copilot Agents Hack-a-Thon — Facilitator Guide

Full-day facilitator script for running a Copilot Agents hackathon, including demos, hands-on exercises, build phase coaching, and team presentations.

⚠️ Disclaimer
All prompts, scenarios, examples, and referenced entities are fictional and provided only for training and demonstration purposes. Do not use this material for decision-making, reporting, or external distribution.
📝 How to Use This Guide
Read this guide end-to-end before the event.
Bring a printed copy on the day and keep it next to your laptop during the build phase.
Priority sections: Section 4 (Run of Show) and Section 5 (Build Phase Coaching).
📝 Session Details
Duration: Full Day (9:00 AM – 4:30 PM)
Format: Educational session · Hands-on exercises · Team hackathon · Demos
Level: 200-Level Intermediate
Classification: Facilitator Version — For Facilitator Use Only, Not for Distribution to Participants
🎯
Section 1

Event Overview

Overview What Success Looks Like ▼

This document is your complete guide for facilitating the Copilot Agents Hack-a-Thon at the customer site. It is designed for a first-time facilitator delivering this engagement.

  • Every attendee has hands-on experience building a Microsoft 365 Copilot agent
  • Every team demos a working proof-of-concept by 4:00 PM
  • The customer leaves with 2–3 specific agent scenarios ready to pilot
  • You have a clear next-step proposal for the customer within 48 hours
Details Attendee Profile ▼
Attribute Details
Expected roles IT leaders, business analysts, franchise operations, marketing, HR
Technical level Mixed — some very technical (IT/dev), most business users
Expected headcount 10–20 attendees (optimal for hackathon format)
License requirement Every attendee MUST have a Microsoft 365 Copilot license
Event format 200-level intermediate, guided, hands-on, full day on-site in Boston
✅
Section 2

Pre-Event Checklist

Checklist 2 Weeks Before ▼
Task Owner
Confirm all attendees have Microsoft 365 Copilot licenses Facilitator + Customer IT
Confirm Copilot Studio access is enabled for attendees (included with M365 Copilot license — no separate trial needed) Customer IT Team
Send attendee pre-read: What are AI Agents in M365? (Microsoft Learn) Facilitator
Confirm room: full-day, team pod seating for 4–5 per table the customer
Confirm AV: projector/screen, HDMI or USB-C adapters the customer
Request strong WiFi credentials (full M365 access, not guest) Customer IT Team
Plan backup connectivity: personal hotspot as failover Facilitator
Print participant workbooks (1 per attendee) Facilitator
Prepare sample SharePoint site with the customer docs for Exercise 2 Facilitator
Pre-load Agent Builder and Copilot Studio in browser tabs and test login Facilitator
Confirm catering: breakfast, lunch, afternoon snacks the customer
Checklist 1 Week Before ▼
Task Owner
Send calendar invite: address, parking, WiFi info, agenda Facilitator
Test full exercise flow on your own laptop end-to-end Facilitator
Prepare 2–3 sample starter agents for teams who get stuck Facilitator
Test Copilot Studio loads correctly with attendee tenant (not your own) Facilitator
Prepare post-event follow-up email (template in Section 8) Facilitator
Checklist Day Before ▼
Task Owner
Confirm room setup time — plan to arrive 45 minutes before attendees Facilitator
Charge devices; pack USB-C hub, power brick, presentation clicker Facilitator
Pre-download: slide deck, workbooks, facilitator guide (offline backup) Facilitator
Print WiFi credentials sheet (one per table) Facilitator
Test laptop connectivity to room AV system Facilitator
Pack printed workbooks, whiteboard markers, sticky notes Facilitator
🔧
Section 3

Day-of Logistics

Setup Room Setup (Arrive by 8:00 AM) ▼
  • Tables in pods of 4–5 chairs each — team-based seating, not classroom rows
  • Facilitator station at front: laptop + projector + whiteboard access
  • Each table: printed workbooks, sticky notes, markers, WiFi credentials card
  • Power strips under or near each table if possible
Setup AV Setup ▼
  • Connect laptop to projector — test HDMI and USB-C dongle
  • Pre-advance slides to Slide 2 (Agenda) as welcome screen while people arrive
  • Backup plan: if projector fails, share deck link so attendees view on laptops
Setup Technical Setup — Your Laptop ▼
  • Browser tabs pre-loaded: microsoft365.com, copilotstudio.microsoft.com, Agent Builder
  • Slide deck open in Presenter Mode (notes visible only on your screen)
  • This facilitator guide open in a second window
  • Backup: deck saved to OneDrive AND downloaded locally
⚠️ WiFi Warning
Critical: Verify you can access microsoft365.com and copilotstudio.microsoft.com on the room WiFi BEFORE attendees arrive.
If guest WiFi blocks Microsoft 365, escalate to Customer IT Team immediately — this is a day-of blocker.
Switch to personal hotspot without hesitation if needed. Test it in advance.
⏲
Section 4

Run of Show — Minute by Minute

Schedule Full-Day Timeline ▼
Time Dur. Activity Facilitator Actions & Talking Points
9:00–9:30 AM 30 min Welcome (Slides 1–3) Intro: name, CSA role, Microsoft. Cover agenda — emphasize 2 hrs building time. Share 3 outcomes. Quick intros: name + role + one word describing what they hope to build. “Safe space. No wrong answers. We learn by building.”
9:30–10:30 AM 60 min “AI Agents in Microsoft 365” (Slides 4–8) Slide 4: A chatbot answers questions, an agent takes action. Slide 5: Most teams use Declarative column. Slide 6: Tie value to the customer. Slide 7: Raise hand for scenario keeping you up at night. Slide 8: M365 security boundary.
10:30–10:45 AM 15 min Break Circulate. Ask informally: “What scenario are you leaning toward?” Note teams needing extra hackathon support.
10:45–11:45 AM 60 min Hands-On Exercises (Slides 9–12) Ex 1 (15 min): Pre-built agent in Teams. Ex 2 (30 min): Declarative agent in Agent Builder — live-demo UI for 3 min first. Ex 3 (20 min): Orient in Copilot Studio. Walk the room constantly. Ask: “What are you trying to build?”
11:45 AM–12:30 PM 45 min Lunch Plant hackathon seeds. Ask each table: which scenario resonates? Ensure teams are naturally forming before lunch ends. Quietly introduce anyone without a team.
12:30–1:00 PM 30 min Hackathon Kickoff (Slides 13–16) High energy: Hackathon starts now. Rules: every team demos, live only, 5 min. Teams claim a scenario. Show Design Canvas — 10 min to fill out BEFORE building. Circulate and review each canvas. RED FLAG: team still arguing about scenario at 12:55 PM — assign one.
1:00–3:00 PM 120 min Build Phase — Create Your Agent Check in at 1:10, 1:30, 2:00, 2:30. Ask: “What is your agent doing right now?” At 2:30 PM: STOP building, prepare demo. See Section 5 for coaching prompts.
3:00–3:15 PM 15 min Break Remind teams: Demo in 15 minutes. Practice 30-second intro. Help any team in crisis with their demo flow.
3:15–4:00 PM 45 min Team Demos (Slides 17–19) Use visible 5-min timer. Most confident team volunteers first. After each: “One thing you liked?” Keep Q&A under 90 sec. Group vote for favorite after all demos. Recognize winner.
4:00–4:30 PM 30 min Wrap-Up (Slides 20–21) Recap top 2–3 scenarios. Present specific next-step recommendation. Get a named owner for follow-up. Capture whiteboard photos. Exchange contact info.
🎬
Section 4B

Demos & Hands-On Exercises

Use these demos during the morning presentation session. Each demo showcases a different Copilot capability and builds toward the hackathon build phase.

Demo Researcher M365 Copilot Premium ▼
Prompt
Build a white paper to help “early majority” companies create a plan to scale adoption of generative AI in the workplace via Microsoft 365 Copilot. This white paper should be written in a way that’s easily digestible and practical for IT as well as business leaders. It should identify and address their fears and concerns, talk through ROI and ways to rationalize investments, tactical programmatic approaches, and give very specific examples that can act as the art of the possible. Use technical press, recent academic research, analysts’ reports, and thought leadership written by industry leaders and management consulting firms.
📝 Facilitator Instructions
Run this in Copilot Researcher. Highlight how it pulls from multiple web sources, structures a full document, and cites sources automatically.
Demo Analyst M365 Copilot Premium ▼
📝 Facilitator Instructions
Upload a sample Excel file with sales/order data. Run this prompt in Copilot Analyst and walk through the structured output with the audience.
Prompt
You are Copilot Analyst. Using the attached Excel file (sheet “Orders”), produce an executive-ready analysis of sales performance and fulfillment health. Deliver the following, in this order: Data quality check: confirm row count, list any missing/invalid values, and call out any suspicious outliers (price, units, discount, margin). Performance summary (overall): total revenue, total gross margin, gross margin %, average order value, on-time shipping rate, average CSAT. Segment insights: break down revenue and margin % by Region, SalesChannel, and CustomerSegment. Identify the top 2 and bottom 2 groups for margin %. Trend analysis: summarize weekly revenue and margin trends across the date range. Call out any weeks with unusual spikes/dips and what’s driving them (region/product/channel). Anomaly detection: find the 5 most suspicious orders (e.g., unusually low price, unusually high units, margin compression, extreme discount, late shipment vs SLA). For each, explain why it’s flagged and quantify the impact (revenue/margin). Operational linkage: analyze how ShipDays vs SLA_Days relates to CSAT and margin (e.g., do late shipments correlate with lower CSAT or margin?). Provide evidence (grouped stats). Recommendations: give 6 concrete actions (pricing controls, discount guardrails, fulfillment improvements, channel mix, product focus). For each action, include expected impact (directional), who owns it (Sales Ops / Finance / Fulfillment), and how to measure success.
Demo Prompt Coach Chat Basic ▼
📝 Facilitator Instructions
Access via Agents → Prompt Coach in Copilot Chat. Walk through multiple prompts to show iterative refinement.
Prompt 1
Show me three good examples of prompts.
Prompt 2
Help me generate a prompt to be used in Copilot.
Follow-Up
I want to get a summary of what’s new regarding how AI is being actively leveraged by organizations in my industry.
Refinement
Change the timeframe to the last 2 months. Add a requirement to cite all sources. Show me two alternative versions of this prompt.
Prompt Analysis
Analyze my prompt and provide feedback on how I could improve it. “Generate 3–4 creative campaign slogans.”
Demo Idea Coach Chat Basic ▼
📝 Facilitator Instructions
Show Idea Coach side-by-side with regular Chat to highlight the guided brainstorming flow.
In Chat (Comparison)
Can you draft an email to my manager about a new idea I’d like to pitch?
In Idea Coach – Start
Help me brainstorm about a specific topic.
Follow-Up 1
I’d like to brainstorm ideas on how we can encourage employees to use Copilot agents to streamline business workflows.
Follow-Up 2
Let’s focus on training and onboarding users.
Follow-Up 3
I’d prefer live instructor-led, webinar-style sessions. Can you design a detailed agenda for a 1-hour webinar?
Demo Build an Agent in Agent Builder M365 Copilot Premium ▼
📝 Facilitator Instructions
This is a live build demo. Go to microsoft365.com → New agent. Build the agent step by step while narrating. After the initial description, a preview of the agent will appear in the right-hand test pane.
Step 1 – Describe
Create an agent to monitor public notices for consumer-based product recalls and summarize “What do I need to know today?” for store ops and merchandising teams.
Step 2 – Name It
Please name it “Total Recall”
Step 3 – Refine Instructions
The agent should report on and surface recent consumer-based product recalls within the last 30 days. Please provide details on the recall reasons and recommended actions consumers should take. And please focus on recalls affecting the NE US area. Primarily use reputable websites like FDA, USDA, and CPSC but also information provided by affected retailers as well. Do NOT infer anything beyond published notices.

Note: FDA = Food and Drug Administration, USDA = United States Department of Agriculture, CPSC = Consumer Product Safety Commission

Step 4 – Test It
What do I need to know today?
Step 5 – Refine
Make sure the Agent cites all sources.
💬
Section 5

Build Phase Coaching Guide

Schedule Check-in Schedule ▼
Time Check-in Goal
1:10 PM Quick round — every team has a finalized canvas (not still planning)
1:30 PM Deeper check-in: “What is your agent doing right now?” (not “How are you doing?”)
2:00 PM “Are you on track for a demo at 3:15?” Nudge any team to narrow scope if needed
2:30 PM “Stop building. Start preparing your demo.” Enforce this firmly.
Coaching Coaching Prompts ▼

When a team is stuck

  • “If I were the user, what would I type to start a conversation with your agent?”
  • “What is ONE thing your agent absolutely must do? Just build that first.”
  • “What is the simplest version of this that still demonstrates value?”

When a team is overcomplicating

  • “What if your agent only did one specific action? Would that still be useful?”
  • “A narrow scenario done well is worth more than an ambitious one half-built.”

When a team finishes early

  • “Can you add a second knowledge source to improve accuracy?”
  • “What questions is your agent getting wrong? Fix that with better instructions.”
  • “Can you improve the demo flow so value is obvious in the first 30 seconds?”
Troubleshooting Common Technical Issues ▼
Issue Likely Cause Resolution
Agent Builder not loading License not provisioned or wrong tenant Check microsoft365.com/admin; try Edge browser
Knowledge source not returning results Still indexing (2–5 min) Wait and retry; have a fallback document ready
Copilot Studio loading slowly Browser cache or VPN Clear cache, disable VPN, try incognito mode
Agent giving wrong answers Instructions too vague Help refine system prompt to be more specific
Cannot log into Copilot Studio Wrong tenant or no license Confirm tenant URL; check license in M365 Admin
WiFi dropping Guest network blocking M365 Switch to personal hotspot immediately
Team completely stuck Scope too broad, no clear user Name ONE user with ONE problem. Build for that person only.
⚠️ Most Common Hackathon Failure Mode
The most common reason teams fail to demo is trying to build too much.
A working agent that does ONE thing well beats a broken agent that tries everything.
If a team has more than 3 topics in Copilot Studio at 2:00 PM, intervene.
🤖
Section 6

the customer Agent Scenarios

Use this section as your reference when coaching teams during the hackathon. Each scenario includes a build guide with specific starting instructions.

Easy Scenario 1 — Franchise Daily Ops Agent ▼
Attribute Details
Difficulty Easy
Agent Type Declarative Agent (Agent Builder)
User Persona Regional franchise manager overseeing 8–15 stores
Knowledge Sources SharePoint with daily ops reports, brand standards, compliance checklists
Key Actions Answer KPI questions, surface compliance gaps, list open items by store
Expected Outcome Save franchise managers 3–4 hrs/week; improve response to underperforming stores
📝 Build Guide
System prompt: “You are a business operations assistant for your organization. Use the provided documents to answer questions about daily store performance. Be concise and direct.” Add a SharePoint knowledge source. Test with: “Which stores had the lowest scores yesterday?” and “What are the top compliance issues this week?”
Medium Scenario 2 — Guest Recovery Agent ▼
Attribute Details
Difficulty Medium
Agent Type Custom Agent (Copilot Studio)
User Persona Guest Relations specialist or store manager
Knowledge Sources Guest recovery policy, brand-specific response guidelines, escalation matrix
Key Actions Classify complaint type, suggest recovery action, flag escalations, draft response
Expected Outcome Reduce complaint-to-resolution time from 48 hours to 4 hours across all brands
📝 Build Guide
Create Copilot Studio agent with topics for each complaint category (food quality, service, wait time, order error). Each topic suggests a recovery action from policy and offers to draft a response. Advanced: connect to guest feedback API.
Easy Scenario 3 — New Hire Onboarding Agent ▼
Attribute Details
Difficulty Easy
Agent Type Declarative Agent (Agent Builder)
User Persona New hourly employee or new corporate hire at any company brand
Knowledge Sources Employee handbook (SharePoint), benefits guide, first-week task checklist
Key Actions Answer policy questions, surface required forms, first-week step-by-step guidance
Expected Outcome Reduce HR onboarding support tickets by 40%; improve new hire retention
📝 Build Guide
System prompt: “You help new the customer employees navigate their first 30 days. Answer only using the provided documents. Always be encouraging and clear.” Test with: “What do I need to do on my first day?” and “How do I enroll in benefits?”
Medium Scenario 4 — Inventory Reorder Alert Agent ▼
Attribute Details
Difficulty Medium
Agent Type Custom Agent (Copilot Studio)
User Persona Store manager or supply chain coordinator
Knowledge Sources Vendor contact list, par-level thresholds document, order form templates
Key Actions Recommend reorder quantities based on par levels, draft reorder email to vendor
Expected Outcome Reduce out-of-stock incidents by 25%; save 2 hrs per store per week
📝 Build Guide
Start declarative: upload vendor contact list and par-level doc. Instructions: recommend reorder when item is mentioned as low. Advanced: connect to inventory management API via Copilot Studio action.
Easy Scenario 5 — Campaign Content Agent ▼
Attribute Details
Difficulty Easy
Agent Type Declarative Agent (Agent Builder)
User Persona Brand marketing coordinator for Arby’s, Sonic, Dunkin’, etc.
Knowledge Sources Brand guidelines per brand, campaign examples, tone-of-voice documents
Key Actions Generate social captions, promo email subject lines, in-store copy per brand voice
Expected Outcome Reduce content creation time from 3 hours to 30 minutes per campaign
📝 Build Guide
Instructions: “When the user specifies a brand, follow that brand’s tone-of-voice guidelines exactly. Always present 3 options for the user to choose from.” Create one knowledge source per brand or one document with brand sections.
Hard Scenario 6 — Food Safety Audit Agent ▼
Attribute Details
Difficulty Hard
Agent Type Custom Agent (Copilot Studio)
User Persona Food safety manager or compliance officer
Knowledge Sources FDA food safety guidelines, audit checklists, corrective action templates, incident logs
Key Actions Walk through audit prep checklist, surface open corrective actions, generate summary report
Expected Outcome Reduce audit prep time from 8 hours to 2 hours; reduce findings through proactive documentation
📝 Build Guide
Requires Copilot Studio for multi-step workflow. Create an agent that guides through a checklist where each item is a topic. Generate a summary report at the end. Ambitious for 2.5 hours — recommend for technically strong teams only.
⚠️ Facilitator Note
Only assign this to teams with at least one technically strong person. It requires Copilot Studio actions and multi-topic flow design.
🔧
Section 7

FAQ & Troubleshooting

FAQ What if an attendee does not have a Microsoft 365 Copilot license? ▼

They can participate in Copilot Studio exercises (which has a trial) and team up with a licensed colleague for Agent Builder. Pair them intentionally at team formation so they are never blocked.

FAQ What if Copilot Studio is slow or unresponsive? ▼

Usually a browser issue. Try: (1) clear browser cache, (2) use incognito/private mode, (3) switch from Chrome to Edge, (4) disable VPN. Edge is the most reliable browser for M365 tools.

FAQ What if a team finishes building before 3:00 PM? ▼

Use coaching prompts: add a second knowledge source, improve instruction quality, practice and tighten the demo flow, or begin drafting a production deployment plan.

FAQ What if a team is completely stuck? ▼

Scope is too broad. Walk them through this: “Name one person. Name one thing that person asks repeatedly. Build an agent that answers only that one thing.” This always unlocks them.

FAQ What if attendees are skeptical about AI? ▼

Do not argue. Say: “Your skepticism is healthy — we are going to let the demo speak for itself. Try building one thing, and then tell me what you think.” Skeptics who build something often become the loudest advocates.

FAQ What if the WiFi fails completely? ▼

Switch to personal hotspot immediately. If all connectivity fails: pause the build phase, run group paper-based scenario planning using the canvas, and reschedule the actual build as a virtual session within 2 weeks.

FAQ What if no one wants to go first in demos? ▼

Prep a volunteer in advance — briefly ask one confident attendee over lunch if they will present first. A strong opening demo sets the tone and encourages everyone else.

FAQ What if a team’s agent does not work during the demo? ▼

Normalize it: “This is exactly what happens in real pilots, and it is why we demo early.” Ask them to walk through what the agent is supposed to do and what they would fix. Intent and design are as valuable as a working demo in this context.

📧
Section 8

Post-Event Follow-Up

Action Items Within 24 Hours ▼
  • Capture notes: top 2–3 scenarios built, team contacts, specific pain points raised
  • Take photos of the whiteboard and any team canvases left behind
  • Note any technical blockers for future event prep improvements
Template Within 48 Hours — Follow-Up Email Template ▼
Subject: Your Copilot Agents Hack-a-Thon — Recap & Next Steps

Hi [Name],

Thank you for an energizing day at the Copilot Agents Hack-a-Thon. What your teams built in 2.5 hours was genuinely impressive, and I left with a clear sense of how AI agents can create real value at the customer.

Key highlights from the day:
• [Insert 2–3 bullet points: scenarios built, standout demos, key themes]

Based on today’s demos, my recommended next step is:
• [e.g., “AI Agents Pilot — Workforce Productivity, starting with the Franchise Daily Ops Agent”]

I’d like to schedule a 30-minute call this week. Are you available [day] or [day]?

Facilitator  |  [facilitator email]  |  Senior Cloud Solution Architect, Microsoft
Logging Engagement Logging ▼
Field Value
Customer the customer
Engagement type AI Agents Hack-a-Thon (200-level)
Outcomes to capture Number of POC agents built, scenarios identified, next step proposed
CRM / MSX update Update opportunity with next step engagement and follow-up date
Manager update Send brief email to [customer sponsor]: top 3 outcomes + recommended next engagement
⚠️ Most Important Reminder
Follow up within 48 hours. Hackathon momentum is powerful but fragile.
Worst outcome: great demos, no follow-up, and the customer moves on without a next step.
Have a specific pilot recommendation ready BEFORE you leave the room at 4:30 PM.
🏆
Reference

Judging Criteria

Scoring Hackathon Scoring Rubric ▼

All teams present. Use this rubric to evaluate each team’s demo. The winner is recognized at the end of presentations.

Criteria Weight What We’re Looking For
Business Value 30% Clear ROI, tied to a real business challenge with quantifiable impact
Creativity 20% Novel problem choice, fresh approach, or unexpected application of agents
Technical Execution 30% Agent works in demo, right type chosen, knowledge sources properly connected
Demo Quality 20% Clear story, compelling pitch, confident delivery within 5 minutes
Total 100%
📝 Facilitator Instructions
Print or display this rubric before demos begin so teams know what they’re being evaluated on. Consider having 2–3 judges from the customer’s leadership team to add weight and visibility to the outcomes.
🤖
Reference

Agent Builder Solutions

Ready-to-use agent configurations for Agent Builder (declarative agents). Each agent includes instructions, knowledge sources, and starter prompts you can copy directly.

M365 Copilot Premium — Agent Builder supports custom instructions, SharePoint/OneDrive knowledge sources, and starter prompts. It does not support external connectors, automated triggers, or proactive notifications — those require Copilot Studio.

Agent 1 Writing Tasks Agent ▼

Purpose: Performs repeated writing tasks using preconfigured prompts.

Instructions
You are a Writing Assistant for [Team/Department] at [Company Name]. You help team members quickly complete common writing tasks using consistent, on-brand language. When a user picks a writing task, deliver polished output that matches [Company Name]'s voice and style. Common task types include: weekly recap emails, project status updates, meeting recaps, leadership summaries. Always ask for any missing context before writing. If the user wants a different tone or format, adjust accordingly.

Knowledge Sources: Brand voice guide, style guidelines, writing sample documents in SharePoint.

Starter Prompts:

  • Write a weekly recap email
  • Draft a project status update
  • Write a leadership summary for [topic]
Agent 2 Memo Drafter ▼

Purpose: Drafts memos using a standard template.

Instructions
You are the Memo Drafter for [Company Name]. Your job is to help team members create professional memos quickly using the standard [Company Name] memo template. When a user wants to write a memo, collect recipient(s), subject, key message, any action items or deadlines, and the sender's name. Then produce a complete, formatted memo matching the standard template in the knowledge base. Keep language clear, professional, and direct. Offer to revise tone or length if asked.

Knowledge Sources: SharePoint library with the official memo template(s) and 2–3 example memos.

Agent 3 Project Companion ▼

Purpose: Answers questions based on project documentation stored in SharePoint.

Instructions
You are the Project Companion for [Team Name] at [Company Name]. Your role is to answer questions about ongoing projects by referencing project documentation stored in SharePoint. When a user asks a question, search the project documents and provide a concise, accurate answer — always noting which document the answer comes from. Help with project status, milestones, task ownership, and key decisions. If the answer isn't in the documents, say so clearly rather than guessing.

Knowledge Sources: SharePoint library or OneDrive folder where project docs are stored.

Agent 4 Consumer Research Plans Agent ▼

Purpose: Creates research plans, surveys, and interview guides.

Instructions
You are a Consumer Research Assistant for [Company Name], trained in our standard research methodologies. Your role is to help teams create consumer research plans, draft survey questions, and build interview guides. Always ground your recommendations in the research training documents in your knowledge base — use those as the standard for structure, question formats, and best practices. For a research plan, always include research objectives, methodology, target audience and respondent criteria, timeline, and success metrics. For surveys, use proven question formats from our training materials.

Knowledge Sources: Consumer research training documents and methodology guides in SharePoint.

Agent 5 Support Buddy ▼

Purpose: Summarizes possible solutions for support technicians.

Instructions
You are Support Buddy, an AI assistant for [Company Name] support technicians. When a technician describes a problem, search the knowledge article repository and respond with: (1) the most likely causes ranked by probability, (2) step-by-step resolution steps for the top cause, and (3) references to the relevant knowledge articles. Ask clarifying questions if the problem description is vague. If no articles match, suggest an escalation path. Use clear, technical language appropriate for IT support professionals.

Knowledge Sources: Knowledge article repository in SharePoint. A live ServiceNow connector requires Copilot Studio.

Agent 6 New Hire Marketing Buddy ▼

Purpose: Provides helpful answers for new Marketing hires.

Instructions
You are the Marketing Onboarding Buddy for [Company Name]. Your mission is to help new Marketing team members get up to speed quickly by answering their questions and pointing them to the right resources. You have access to onboarding guides, team processes, brand guidelines, tool documentation, and org information. Always be welcoming and encouraging. When referring to a resource, name the document and its location so the new hire can find it easily. Common topics: team structure, system access, brand guidelines, campaign processes, ways of working, and key contacts.

Knowledge Sources: Marketing team SharePoint site — onboarding materials, brand guidelines, tools/process guides.

Agent 7 Email Copy Writer ▼

Purpose: Writes first-draft email copy.

Instructions
You are an email copy expert for [Company Name]. Your job is to write compelling, on-brand first-draft email copy for marketing campaigns, customer communications, and internal updates. Before writing, ask for: the email's purpose, target audience, key message or offer, and the desired call to action. Then deliver: (1) a subject line with 2–3 alternatives, (2) preview text, (3) body copy, and (4) a clear CTA. Write mobile-first — short paragraphs, scannable structure. Match the appropriate brand voice.
Agent 8 Brand Content Drafter ▼

Purpose: Drafts digital content for brand channels.

Instructions
You are a Brand Content Specialist for [Company Name], focused on creating digital content. Your role is to draft and refine content for brand websites, blogs, and digital channels. When a user requests content, ask about: the specific brand, the content type (blog post, webpage copy, social caption, etc.), target audience, key topics or messages, and any SEO keywords to include. Generate content that matches the brand's voice, is structured with clear headings, and is written for both search and readability. Reference brand guidelines in the knowledge base to maintain consistency.
Agent 9 BU Knowledge Sharing Agent ▼

Purpose: Guides users on document storage and retrieval.

Instructions
You are the Knowledge Navigator for the [BU Name] team at [Company Name]. You know our SharePoint structure, naming conventions, metadata tagging standards, and storage guidelines for all training decks and working documents. When someone needs to store a new file, recommend the right folder, the correct file name format, and the metadata tags to apply. When someone is looking for a document, help search by topic or function. You also know which presentations have been recorded and can point users to replay links. Always explain the "why" behind naming and storage conventions so the team understands the system.
Agent 10 Memo + Creative Ideas Agent ▼

Purpose: Drafts memos AND brainstorms creative marketing ideas.

Instructions
You are a Creative Communications Specialist for [Company Name] with two modes. MEMO MODE: When asked to draft a memo, collect recipient(s), subject, key points, any action items or deadlines, and sender. Produce a clean, professional memo ready to send. CREATIVE MODE: When asked for creative ideas, help brainstorm headlines, product claim concepts, campaign taglines, or other marketing creative. Generate 5–8 diverse ideas spanning different angles (emotional, functional, humorous, bold), then refine based on feedback. If it is unclear which mode the user wants, ask.
Agent 11 Research Assistant / Repository Summary ▼

Purpose: Answers research questions AND summarizes the document repository.

Instructions
You are the Research Assistant and Knowledge Hub for [Team/Department] at [Company Name]. You have two functions. RESEARCH: Help users build research outlines, summarize reports, synthesize findings from multiple documents, and answer questions grounded in the document repository. Always cite the source document for each finding. REPOSITORY GUIDE: Help users understand what knowledge is available in the SharePoint library — identify key documents by topic, provide high-level summaries of specific files, and surface relevant resources the user may not know about. If a question cannot be answered from the knowledge base, say so clearly and suggest where else to look.
Agent 12 Paid Search Ad Copywriter ▼

Purpose: Writes paid search ad copy.

Instructions
You are a Paid Search Copywriter for [Company Name]. Your specialty is writing high-performing Google and Bing search ad copy. When a user provides keywords, a product or offer, and campaign context, generate (1) 5 headline options (max 30 characters each), (2) 3 description lines (max 90 characters each), and (3) a suggested display URL path. Apply search copywriting best practices: include the target keyword naturally, highlight the key differentiator or offer, create urgency where appropriate, and include a clear CTA. Provide multiple variants to enable A/B testing. If the user shares historical CTR or performance data, use it to optimize the copy direction.

Note: Automated collection of live keyword and CTR data from ad platforms requires Copilot Studio with connectors.

Reference Agents That Require Copilot Studio ▼

The following agent ideas cannot be built with Agent Builder alone. All require Actions — automated triggers, writing to external systems, sending proactive notifications, or live data connectors — which are features exclusive to Copilot Studio.

Agent Name Why Copilot Studio Is Required
Industry Research Assistant with Alerts Requires proactive alerts and triggers when new information appears
Process Workflow Agent Requires process orchestration with time-based reminders and workflow automation
Meeting Recap Agent Requires launching meeting recordings and sending transcripts — M365 write actions needed
Procurement Workflow Agent Requires automated follow-up pings on a recurring schedule
Knowledge Base Notifier Requires notifying team members when a new document is added
Newsletter Creation Agent Requires pulling live campaign performance data from internal systems
Customer Website Evaluation Agent Requires browsing and evaluating external websites in real time
SEO Agent Requires live web data connectors and external site analysis
📝 Facilitator Instructions
Use this section as a reference when teams propose agents that need external connectors or automation. Redirect them to Agent Builder solutions that can be built during the hackathon, and note the Copilot Studio agents as future roadmap items.