# Amazon Quick Desktop: Your Setup Guide

Paste everything below this line into a new Amazon Quick Desktop conversation. It will walk you through setup interactively.

---

Hi Quick -- I'm new to Amazon Quick Desktop and I want you to help me get set up properly. Walk me through this step by step. Don't rush. Explain what you're doing and WHY it matters at each step. I want to understand the value, not just click buttons.

Here's what I want to accomplish in this session:

## Phase 1: Connect My World (~10 minutes)

Help me connect my key integrations. For each one, explain what it unlocks:

1. **Slack** -- Connect my Slack. Once connected, show me what you can already see (recent channels, DMs, key people I interact with). Explain why this matters: you can search my message history, monitor channels, and understand my work context.

2. **Outlook** -- Connect my email and calendar. Once connected, show me today's calendar and a quick summary of recent emails. Explain why this matters: meeting prep, email search, and calendar awareness.

3. **Local folders** -- Help me add my most important work folder (probably OneDrive or Desktop). Explain what happens when you index it: you can search inside documents, not just filenames.

After each connection, do a quick demo so I can see it working. Don't just say "connected" -- show me something useful immediately.

## Phase 2: Meet Your Knowledge Graph (~10 minutes)

This is the part most people skip and shouldn't. Walk me through:

1. **What is the knowledge graph?** Explain it simply -- it's your personal context about my work: the people I work with, projects I'm on, decisions that have been made, and how everything connects.

2. **Show me what's already there.** After connecting Slack and Outlook, you've probably already started building context. Search for my name, show me what you know about me, and show me a few people I work with. Use the graph_search tool and explain the results.

3. **Why does this matter?** Give me a concrete example: "When you ask me to prep for a meeting with [person], I don't just pull their calendar invite -- I know what projects they're on, what you last discussed, and what decisions are pending." 

4. **The "context spine" concept.** Briefly explain that power users organize their graph with Decisions (things decided), Initiatives (active workstreams), Open Questions (unresolved items), and Constraints (hard limits). I don't need to do this now, but I should know it exists for later.

## Phase 3: Your First Wins (~10 minutes)

Now that I'm connected, walk me through 5 things I can do right now that deliver immediate value:

1. **Meeting prep** -- Pick my next meeting from my calendar. Show me what you'd pull together: attendee context, recent interactions, relevant topics. Explain that I can do this before any call by just asking "prep me for my 2pm meeting."

2. **People lookup** -- Pick someone I interact with frequently. Show me what you know about them from Slack, email, and calendar. Way faster than phonetool + Slack search + email search separately.

3. **Document search** -- Search my indexed folder for something relevant to my current work. Show me the difference between filename search and semantic search ("find docs about cost optimization" vs finding a file named "FinOps-Q3.xlsx").

4. **Email triage** -- Show me my unread emails and offer to summarize the important ones. Explain that I can ask "what emails need my attention?" any morning.

5. **Quick draft** -- Pick something from my recent work context and offer to draft a short response, summary, or follow-up. Show me that you understand my context well enough to write something useful, not generic.

After each win, pause and let me react. Don't bulldoze through all 5.

## Phase 4: What's Next (5 minutes)

Wrap up by telling me:

1. **What I should try this week** -- 3 specific things to do in the next 5 days that will build my muscle memory
2. **What's possible when I'm ready** -- Brief teaser of agents (automated workflows), scheduled monitoring, and deeper graph customization. Don't overwhelm -- just plant the seed.
3. **Where to get help** -- The #amazon-quick-desktop-beta-feedback Slack channel and that I can always just ask you "what can you do?"

## Rules for this session:

- Be conversational, not robotic. I'm learning, not following a checklist.
- After each phase, ask me if I have questions before moving on.
- If something fails (connection issue, missing permission), troubleshoot it with me instead of skipping it.
- Use decision cards when giving me choices.
- Show, don't tell. Every capability you mention, demonstrate immediately.
- Keep it under 30 minutes total. If I'm engaged and want to go deeper, offer to continue. If I'm fading, wrap it up gracefully.