Agent Catalog: 20+ Reusable Starting Points

▶ Watch (01:20)

The Agent Catalog holds 20-plus templates, all taken from real customer scenarios. They cover browser automation, e-commerce purchasing, ticket booking, and vertical-specific workflows. Stanford Medicine uses the healthcare template in production today. Partners including Marquee Insight, Site Machine, and Aquan have contributed their own proprietary templates to the platform. Templates work for any experience level. Pick one, adapt it, and skip the blank-page problem.

Connected Agents: Add an Agent as a Tool

▶ Watch (02:22)

A connected agent is an agent added as a tool to another agent. The orchestrator calls it when it needs context it wouldn’t have otherwise. In the mortgage concierge playground demo (07:28), one sub-agent holds Contoso Bank’s eligibility documents via file search; a second connects to Bing for live market rates. Ask about 30-year fixed rates in California and the orchestrator routes to Bing. Ask about Contoso’s credit score requirements and it routes to the file-search agent. Adding more knowledge or actions to a single agent increases hallucination risk. Splitting by expertise keeps each agent’s scope narrow and its responses traceable.

Multi-Agent Workflows: State, Events, and Controlled Handoffs

▶ Watch (09:25)

Connected agents work when the orchestration is simple: one main agent, a few specialized sub-agents, a single conversation thread. For complex processes with private threads, shared context, or multiple handoff paths, multi-agent workflows powered by Semantic Kernel add the missing control. These introduce states (authentication, billing, escalation as checkpoints), transitions between states, and events that trigger agent actions either deterministically or by LLM decision. A VS Code workflow designer visualizes the graph as nodes and transitions. Hierarchical and MapReduce patterns are both supported. The Semantic Kernel SDK was still in progress at time of filming.

End-to-End Demo: Customer Support with Human Escalation

▶ Watch (13:00)

The customer support workflow chains four agents: self-service handles the first response, ticket creation logs the issue to ADO and sends an email, an internal routing agent picks the department, and Windows Support pulls from its troubleshooting guides. When a user says “issue persists,” the ADO ticket creation and email notification demo (15:03) shows ticket 16 appearing in ADO, an email arriving with the issue description and attempted resolution steps, then automatic routing to Windows Support. If that fails, a human escalation node takes over.

Notable Quotes

you might see hallucinations Mona · ▶ 5:52

You can implement this entire workflow without touching a line Mona · ▶ 8:48

it’s entirely modular Mona · ▶ 16:25

Key Takeaways

  • Agent Catalog ships 20-plus ready-made templates built from real customer scenarios across industries.
  • Split overloaded prompts into connected sub-agents to reduce hallucinations and improve traceability.
  • Multi-agent workflows add states and event triggers for deterministic, human-escalation-capable pipelines.