# First-Week Setup Concierge: Guided Onboarding for a New Org or User > **Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes** You say "Help me get set up." Your clone checks what is already switched on, asks five short questions, recommends two or three starter use cases, sets up what it can, walks you through the parts only you can do, runs one end-to-end test, and follows up on Day 3 and Day 7. --- ## 1. Overview and value A new clone can do a lot, and that is the problem. People open it, see dozens of possibilities, connect half a tool, try three things at once and stall at the first permission error. The First-Week Setup Concierge replaces that with one guided path. Your clone: - **checks your basics** and reports them in a table (clone active, connections, skills, knowledge bases, scheduled tasks), - **asks 5 short questions** (role, team, main tools, top 3 time-wasters, what success looks like in 30 days), - **recommends 2–3 starter use cases** from this library using a recommendation matrix, - after your approval, **attaches skills, creates a starter knowledge base and schedules a first task**, - **walks you step by step** through what only you can do (sign-ins, inviting teammates, sharing knowledge, adding the clone to meeting invites), - **runs one end-to-end test** of your first use case, - sends a **"Your setup status"** summary (done / waiting on you / next) and creates **Day 3 and Day 7 reminders**. | Benefit | What it looks like | |---|---| | One clear starting point | One use case first, not ten | | Fewer onboarding blockers | Common snags (clone off, wrong account, missing permissions) are checked up front | | Something working on Day 1 | A scheduled task and a tested first use case | | A habit by Day 7 | Reminders on Day 3 and Day 7 keep you moving | | You stay in control | Nothing changes until you say "yes" to a numbered plan | --- ## 2. Who it's for - **Ops** leads rolling the clone out to a team and wanting a repeatable first week. - **Leadership** who want a quick win and a clear 30-day goal, without learning every feature. - **Customer Success** managers who want account follow-ups, briefings and health updates running early. - **Sales** reps who want meetings and CRM updates handled from the start. It is for **brand-new orgs and users**. If you are already running several use cases, you can still use it as a health check. ## 3. How it works ``` You: "Help me get set up." │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ "Setup Concierge" skill │ │ │ │ 1. CHECK basics → status table │ │ clone active · connections · skills · knowledge bases │ │ · scheduled tasks │ │ 2. ASK 5 short questions │ │ role · team · main tools · top 3 time-wasters · 30-day goal │ │ 3. RECOMMEND 2–3 starter use cases (matrix) → you pick ONE first │ └───────────────────────────────┬───────────────────────────────────┘ │ You reply "yes" to a numbered plan │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ 4. DO: attach skills · create starter knowledge base · │ │ schedule a first task │ │ 5. GUIDE: sign-ins · invite teammates · share knowledge · │ │ clone on meeting invites · follow-up preferences │ │ 6. TEST: one end-to-end run of the first use case │ │ 7. SUMMARY: "Your setup status" (done / waiting on you / next) │ │ + Day 3 and Day 7 reminder tasks │ └───────────────────────────────────────────────────────────────────┘ ``` ### Recommendation matrix The clone picks from this matrix based on your role and your top time-wasters. Slugs are folder names in this library. | If your role or pain point is... | Recommend (title) | Slug | |---|---|---| | "I don't know what to do first each morning" / overloaded inbox | Pressing Items | `pressing-items` | | "I walk into meetings unprepared" | Daily Meeting Briefing | `daily-meeting-briefing` | | "CRM is never up to date after calls" (Sales, CS) | Post-Meeting CRM Autopilot | `post-meeting-crm-autopilot` | | "Same product questions again and again" | Product Knowledge Q&A | `product-knowledge-qa` | | "We need a web page fast" | Website in Minutes | `website-in-minutes` | | "Follow-ups to customers slip" (Sales, CS) | Weekly Personalized Follow-Up Drafts | `weekly-follow-up-drafts` | | "I can't see account risk early" (CS) | Account Health Autopilot | `account-health-autopilot` | | "Meetings produce notes but no actions" (Ops, Leadership) | Transcript to Action | `transcript-to-action` | | "I need a weekly view of the team's meetings" (Leadership) | Meeting Analytics Recap | `meeting-analytics-recap` | | "Support inbox is a mess" (Ops) | Support Inbox Auto-Triage | `support-inbox-auto-triage` | | "I'd like an AI note-taker in my meetings" | AI Meeting Copilot | `ai-meeting-copilot` | | "Work queues in SharePoint get stuck" (Ops) | SharePoint Work Queue Monitor | `sharepoint-work-queue-monitor` | ### Default picks by role | Role | Typical first use case | Typical second | |---|---|---| | Ops | Pressing Items | Product Knowledge Q&A | | Leadership | Daily Meeting Briefing | Pressing Items | | Customer Success | Daily Meeting Briefing | Weekly Personalized Follow-Up Drafts | | Sales | Post-Meeting CRM Autopilot | Daily Meeting Briefing | ### Printable checklist: Day 1 / Day 3 / Day 7 ``` DAY 1 (about 30 minutes) [ ] Clone is switched on and active [ ] Connect Google or Microsoft (use the right work account) [ ] Connect Salesforce or HubSpot (if using a CRM) [ ] Connect Slack or Teams (if you want chat delivery) [ ] Answer the 5 questions; pick ONE starter use case [ ] Approve the plan; skills attached; starter knowledge base created [ ] First scheduled task created (for example daily Pressing Items) [ ] End-to-end test run and checked [ ] Read "Your setup status" summary DAY 3 (about 15 minutes) [ ] Review the first scheduled outputs: useful? too long? wrong account? [ ] Tell the clone what to change (format, time, sources) [ ] Invite teammates (if relevant) [ ] Add the clone to 1-2 meeting invites and admit it from the lobby [ ] Share 3-5 key documents for the knowledge base DAY 7 (about 20 minutes) [ ] Review the week: what saved time? [ ] Check progress against your 30-day goal [ ] Add your SECOND use case (only if the first one is working) [ ] Check credits if you plan heavier skills (coding, video, research) [ ] Set meeting follow-up preferences ``` ## 4. What the clone does (and never does) **It does, after you approve a numbered plan:** - check and report your setup in a table, - ask five short questions and recommend starter use cases, - attach the skills you need, create a starter knowledge base, and schedule a first task, - explain each sign-in step, one at a time, - run one end-to-end test and send the "Your setup status" summary, - create Day 3 and Day 7 reminder tasks. **It never:** - changes anything before you say "yes" to the plan, - asks for or handles your passwords, API keys or tokens (you sign in yourself through the platform's sign-in screens), - sets up more than one use case at first unless you insist, - emails customers or prospects during setup, - starts credit-heavy skills (coding, video, research) without telling you first, - invites teammates or shares files on your behalf without your say-so. ## 5. Setup walkthrough **Step 1: Download the files (2 min).** Get CLONE-INSTRUCTIONS.md from this card. **Step 2: Hand it to your clone (2 min).** Paste or upload it and say: *"Help me get set up."* (Or: "Please set this up for me. Show me a plan before changing anything.") **Step 3: Review the status table (5 min).** The clone reports what is on and what is missing. **Step 4: Answer the 5 questions (5 min).** Short answers are fine. **Step 5: Pick your first use case and approve the plan (3 min).** Say "yes" only when the plan looks right. **Step 6: Do your part (10–20 min).** The clone walks you through each sign-in and setting, one at a time. **Step 7: Watch the test (5–10 min).** The clone runs your first use case once, end to end, and you check it. **Step 8: Read "Your setup status".** Then expect reminders on Day 3 and Day 7. ## 6. Placeholders to decide | Placeholder | What it means | Example | |---|---|---| | `{USER_ROLE}` | Your role | Ops, Leadership, Customer Success, Sales | | `{TEAM}` | Your team and its size | Customer Success, 6 people | | `{MAIN_TOOLS}` | Tools you use every day | Gmail, Google Calendar, HubSpot, Slack | | `{TIME_WASTERS}` | Your top 3 time-wasters | Inbox triage, meeting prep, CRM updates | | `{SUCCESS_30_DAYS}` | What success looks like in 30 days | "Save 5 hours a week; CRM updated within a day of every call" | | `{FIRST_USE_CASE}` | The one use case to start with | Pressing Items | | `{DELIVERY}` | Where reminders and summaries arrive | Email, Slack, Teams, or chat | | `{TIME_ZONE}` | Your time zone for scheduled tasks | Your local zone | | `{FIRST_TASK_TIME}` | When the first scheduled task runs | 7:30 AM Mon–Fri | ## 7. What to expect - **Day 1:** a status table, five questions, a plan, a first scheduled task and a tested use case. About 30 minutes of your time. - **Day 3:** a reminder asks how the first outputs look and nudges you to invite teammates, share documents and add the clone to meetings. - **Day 7:** a reminder reviews the week, checks your 30-day goal and suggests a second use case. Example status table (abbreviated): ``` | Item | Status | Notes | | Clone switched on | ✅ | Active | | Google or Microsoft | ⚠️ | Connected, calendar permission missing | | CRM | ❌ | Not connected yet | | Skills attached | ✅ | 3 skills | | Knowledge bases | ❌ | None yet | | Scheduled tasks | ❌ | None yet | ``` ## 8. Customizing - **Pace.** Ask for a shorter or longer first week, or move the reminders (for example Day 2 and Day 5). - **Team rollout.** Run it once per person, or run it first for yourself and reuse the answers as a team template. - **Delivery.** Receive the summary and reminders by email, Slack or Teams. - **First use case.** Override the recommendation. The matrix is a suggestion. - **Check-in only.** Use it later as a health check: "Run my setup check." ## 9. Known gotchas (onboarding blockers) - **Clone switched off.** If the clone is off, nothing scheduled runs. The status table checks this first. - **No Google or Microsoft connection yet.** Most starter use cases need email and calendar. Connect one first. - **Connection under the wrong account or missing permissions.** If you signed in with a personal account, or skipped a permission box, the clone sees the wrong data or gets "access denied". Delete the connection and re-create it to pick up new permissions. - **Too many use cases at once.** Start with one. Add the second once the first has run for a few days. - **Credits needed for heavier skills.** Coding, video and research skills use credits. Check your balance before you try them. - **Some connections must be finished in integrations settings, not in chat.** If the sign-in does not complete in chat, finish it on the Connections / Integrations page and tell the clone "connected". - **Meeting bots must be admitted from the lobby.** When the clone joins a meeting, a person must let it in. - **Skill names differ slightly by org.** The clone checks your catalog and uses the exact names it finds. - **Read every instruction before saving a skill.** You are responsible for what your clone does. ## 10. FAQ **How long does it take?** About 20–40 minutes on Day 1, then 15–20 minutes on Day 3 and Day 7. **Do I need to know what I want first?** No. The five questions and the matrix help you choose. **Can I set up three use cases on Day 1?** You can, but it is not recommended. Start with one. **Will it ask for my password?** No. You sign in yourself through the platform's sign-in screens. **Can I use it for a whole team?** Yes. Each person connects their own accounts. You can share the answers as a template. **Does it cost credits?** The concierge itself is light. Heavier skills (coding, video, research) use credits, and the clone warns you first. **What if I skip the Day 3 or Day 7 reminder?** Nothing breaks. Ask "What's my setup status?" any time. **Is this the same for Google and Microsoft?** Yes. See the mapping table in REQUIREMENTS.md. ## 11. Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | Scheduled task never ran | Clone switched off, task paused or time zone mismatch | Switch the clone on; ask it to list scheduled tasks and last-run times | | Clone can't see my email or calendar | No Google/Microsoft connection, or wrong account | Connect it; or delete and re-create under the right work account | | "Access denied" or missing data | Missing permissions on the connection | Delete the connection and re-create it, approving all permission boxes | | Sign-in doesn't finish in chat | Some connections need the settings page | Finish it on Connections / Integrations, then say "connected" | | Skill name not found | Names differ slightly by org | Let the clone search your catalog for the closest match | | Heavy skill refuses or stalls | Not enough credits | Check your credit balance; try a lighter use case first | | Clone joined the meeting but nothing recorded | Not admitted from the lobby | Admit the clone when it appears in the lobby | | Too much output, feels overwhelming | Too many use cases at once | Pause all but one; ask the clone to list and pause tasks | | No Day 3 / Day 7 reminder | Reminder tasks not created or clone off | Ask the clone to list scheduled tasks and re-create them | --- **Version:** 1.0.0 · **Last updated:** 2026-10-22 · Part of the Clone Use Case Library.