docs: clarify account provisioning requirement for first-time CLI auth

docs/install/CALL-E-installation-guide.md

@@ -40,6 +40,10 @@ env CALLE_SOURCE=skills_sh CALLE_INTEGRATION=skills_sh_skill CALLE_INTEGRATION_V
 
 ## Step 3 Authenticate
 
+<!-- sync-with: docs/install/install-guide.md#first-time-users-create-the-account -->
+First time? Choose **Continue with Google** on the sign-in page.
+See [First-time users](./install-guide.md#first-time-users-create-the-account).
+
 Run the login command and let the user complete browser authorization:
 
 ```bash

docs/install/cli.md

@@ -28,6 +28,10 @@ The command opens the brokered login URL, polls until authorization completes,
 exchanges the authorized session, and stores the token in a private local cache.
 The token is never printed to stdout.
 
+<!-- sync-with: install-guide.md#first-time-users-create-the-account -->
+First time? Choose **Continue with Google** on the sign-in page.
+See [First-time users](./install-guide.md#first-time-users-create-the-account).
+
 For agent integrations that need to show the authorization link before
 continuing:
 

docs/install/install-guide.md

@@ -186,6 +186,13 @@ The Codex, Claude Code, Cursor plugin, OpenClaw, and skills.sh skills use the
 repository-local CLI when available, then a global `calle`, then the
 npm fallback.
 
+### First-Time Users: Create The Account
+
+On the sign-in page, choose **Continue with Google** to create a CALL-E
+account or sign in to an existing one.
+
+If login fails, see [Troubleshooting](./troubleshooting.md).
+
 ## Safety
 
 CALL-E can place real outbound phone calls. Integrations must plan first,