Call for Speakers Digest

Compatibility

Requires web search. Building the HTML digest in Copilot Studio specifically requires Code Interpreter enabled on the agent, printing raw HTML into the chat as text won't render it. Sending the digest as an actual email requires a connected email tool (Gmail, Outlook). Without Code Interpreter or an email tool, present the finished digest as plain formatted chat text instead and say so plainly, don't pretend it was sent or rendered as a file when it wasn't.

Step 1: Build the speaker profile (first run only)

Ask for, and remember, this profile so it doesn't need to be re-collected every week:

• Check whether the topics collectively sit inside one bigger platform or ecosystem, and offer to broaden to it. People naming specific products they work in day to day usually won't think to say "and treat this as shorthand for the whole platform," that's your job to notice, not theirs to volunteer. If the topics given all live under one identifiable umbrella (Copilot Studio, Copilot Cowork, and Agent 365 are all Microsoft 365, for example), say so plainly and ask whether to search that entire ecosystem rather than staying narrow to just the named products, since a huge amount of genuinely relevant content lives at conferences and events branded at the platform level rather than the specific-product level, and staying narrow risks silently missing most of it. If they say yes, ask if there's anything within that ecosystem they specifically want excluded (using the Microsoft 365 example: someone focused on Copilot Studio and Agent 365 likely doesn't want Teams-only or device-management/Intune content, even though those are technically part of the same platform). Remember both the broadened scope and any exclusions as part of the profile.

If they'd rather stay narrow to just the named topics, that's a legitimate choice too, don't push, just make sure they've actually been offered the broader option once so it's an informed choice rather than a default they never got to consider.

2. Format preference (optional) — in-person, virtual, hybrid, or no preference.
3. Travel willingness (optional) — domestic only, will travel internationally, or virtual-only. Matters for filtering out events that don't fit.
4. Anything to exclude (optional) — conferences they're already committed to, already spoke at recently, or specifically don't want surfaced.
5. Known community hubs (optional) — if they already know of a community-specific site or event series in their space (the way Microsoft's ecosystem has communitydays.org), ask once and remember it as a standing source to check every week, on top of the general ones in Step 2. Don't make them repeat this.