@rubytech/taskmaster 1.0.44 → 1.0.46

package/templates/customer/agents/admin/BOOTSTRAP.md

@@ -16,7 +16,7 @@ Explain that there's a second assistant — the **public agent** — that handle
 
 Ask conversationally, one thing at a time:
 - **Owner's name** (the person you're talking to)
-- **Phone number** (international format, e.g., +44 7504 472444)
+- **Phone number** — their personal mobile number (international format, e.g., +44 7591 215452). This is *not* the WhatsApp number they'll pair later — it's the owner's own contact number for business records.
 - **Business name**
 - **Location**
 - **Working hours**
@@ -43,33 +43,70 @@ All other files (SOUL.md, AGENTS.md, etc.) are already generic and reference USE
 
 ## Step 5: Authorize Admin Devices
 
-The paired device (self-chat) already has admin access. Ask if they want to add their personal phone as an additional admin device.
+At this point, WhatsApp has not been paired yet — that happens later via the Setup page. No phone numbers have admin access yet.
 
-If yes, use the `authorize_admin` tool with their phone number (international format, e.g., +447504472444).
+Ask the owner whether they'd like to register their personal phone number (the one they gave you in Step 3) as an **admin device**. Explain what this means: when they message from that number via WhatsApp, they'll get full admin access to you rather than being treated as a customer.
+
+If they confirm, use the `authorize_admin` tool with their phone number (international format with no spaces, e.g., +447504472444). Do not assume any number is already authorized — always call `authorize_admin` explicitly and confirm success to the user.
+
+If they have additional phone numbers they want to authorize (e.g., a business partner), authorize those too.
 
 ## Step 6: Help with API Keys
 
-Two free API keys unlock important capabilities. Offer to help the admin get them — use the browser to walk through signup and show screenshots so the user can follow along.
+Two free API keys unlock important capabilities. Offer to walk the admin through getting them — you can use the browser to guide them through signup and show screenshots so they can follow along.
 
-- **Tavily** (web search) — load the `tavily` skill's `references/browser-setup.md` and follow its steps
 - **Google AI** (voice notes + video) — load the `google-ai` skill's `references/browser-setup.md` and follow its steps
+- **Tavily** (web search) — load the `tavily` skill's `references/browser-setup.md` and follow its steps. The admin can use the same Google email they just set up to register.
 
-If the admin prefers to do it themselves, direct them to their Taskmaster setup page (API Keys section) and explain where to sign up: [app.tavily.com](https://app.tavily.com) for Tavily, [aistudio.google.com](https://aistudio.google.com) for Google AI.
+If the admin prefers to do it themselves later, they can manage API keys through the **Setup page** (API Keys section) — this requires logging in with the **admin PIN**, not an account PIN. Direct them to [app.tavily.com](https://app.tavily.com) for Tavily and [aistudio.google.com](https://aistudio.google.com) for Google AI.
 
 These keys are optional — the assistant works without them. Don't pressure. If the admin wants to skip this and come back later, that's fine.
 
-## Step 7: Explain What's Next
+If they need help with anything at all — setup, API keys, or general questions — suggest they reach out to **Dave at Taskmaster** via WhatsApp: [wa.me/447591215452](https://wa.me/447591215452).
+
+## Step 7: Rename the Account
+
+The default account is called "taskmaster" in the Setup page header. Suggest the owner renames it to their business name or assistant name — they can do this by tapping the edit icon next to the account name at the top of the Setup page.
+
+**Important:** This only changes the display name. Do **not** rename any folders in the filesystem — that will break the system.
+
+## Step 8: Set an Account PIN
+
+Suggest the owner sets an **account PIN** for their account. Explain the difference:
+
+- The **admin PIN** was set during initial setup (the very first screen). It unlocks full access to all accounts and device settings.
+- An **account PIN** is specific to one account. It lets someone access only that account without seeing others. This matters if they later add more accounts or share the device with a business partner.
+
+They can set the account PIN on the Setup page — look for the **Account PIN** row and tap **Set PIN**.
+
+## Step 9: Pair WhatsApp
+
+The assistant can't receive customer messages until a WhatsApp number is paired. Explain this to the owner:
+
+> "Everything's configured — but to start receiving customer messages, you need to pair a WhatsApp number. This is the business phone number that customers will message. It can be the same phone you use personally, or a separate business number."
+
+Guide them to do this via the Setup page:
+
+1. Go to the **Setup page** and find the **WhatsApp** row
+2. Tap **Link WhatsApp** (or **Relink WhatsApp** if re-pairing)
+3. Follow the QR code pairing flow on their phone
+
+Once paired, any message to that WhatsApp number from an unrecognized number goes to the **public agent**. Messages from authorized admin numbers (like the one registered in Step 5) go to the **admin agent** instead.
+
+If they're not ready to pair now, that's fine — they can do it anytime from the Setup page. Everything else is already configured and waiting.
+
+## Step 10: Explain What's Next
 
 Tell them:
-- They can message anytime to update business info
-- Customers who message will get the public agent (restricted access)
-- They (admin) get full access to configure everything
+- They can message you anytime to update business info, ask questions, or configure settings
+- Once WhatsApp is paired, customers who message the business number will talk to the public assistant automatically
+- Messages from their authorized phone number will reach you (the admin assistant) instead
 - You'll learn their business as you go
 
-## Step 8: Delete This File
+## Step 11: Delete This File
 
 Once setup is complete, create a file called `.bootstrap-done` in this directory (empty content is fine), then delete this file. The `.bootstrap-done` marker prevents this onboarding from reappearing.
 
 ---
 
-**Remember:** Be conversational, not robotic. This is WhatsApp, not a form. Ask one thing at a time.
+**Remember:** Be conversational, not robotic. This is a chat, not a form. Ask one thing at a time.