wxcli 1.2.0__py3-none-any.whl

wxcli/_playbook/.claude/skills/query-live/domains/call-flow-trace.md

@@ -0,0 +1,223 @@
+# Call Flow Trace Domain
+
+**Covers:** "What happens when someone calls +1-512-555-1000?", call path tracing, schedule evaluation, routing chain visualization.
+
+This is the most complex domain module. It traces the path a call takes through the routing chain, evaluating time-of-day schedules to show the specific path at a given moment.
+
+## Question Patterns
+
+| Pattern | Example |
+|---------|---------|
+| Simple trace | "What happens when someone calls +1-512-555-1000?" |
+| Time-specific | "What happens if someone calls the main number at 7pm Saturday?" |
+| Schedule check | "Is the Main auto attendant on business hours or after hours right now?" |
+| Path comparison | "What's the difference between calling during business hours vs after hours?" |
+| Resource trace | "Trace the call flow for the Sales hunt group" |
+
+## Input Parsing
+
+The user provides:
+1. **A phone number** (e.g., "+1-512-555-1000") OR **a resource name** (e.g., "the Main auto attendant", "the Sales hunt group")
+2. **An optional datetime** — if omitted, use current time in the resource's location timezone
+
+**Natural language time expressions to support:**
+- "right now" → current time
+- "at 3am" → today at 3:00 AM in location timezone
+- "at 7pm on Saturday" → next Saturday at 7:00 PM
+- "on Christmas Day" → December 25 (use current year if ambiguous)
+- "next Tuesday at noon" → next Tuesday at 12:00 PM
+
+## Algorithm
+
+### Step 1 — Resolve the entry point
+
+**If user gave a phone number:**
+```bash
+wxcli numbers list --phone-number "+15125551000" -o json
+```
+Extract the `owner` object → get `type` and `id`. The `owner.type` tells you what the number is assigned to: PEOPLE, AUTO_ATTENDANT, CALL_QUEUE, HUNT_GROUP, VIRTUAL_LINE, PLACE (workspace), or BROADWORKS_ANYWHERE.
+
+Also get the `location` from the number response — you'll need the location ID and timezone.
+
+**If user gave a resource name:**
+Search for the resource by name in the appropriate list command:
+- "Main auto attendant" → `wxcli auto-attendant list --name "Main" -o json`
+- "Sales hunt group" → `wxcli hunt-group list --name "Sales" -o json`
+- "Support queue" → `wxcli call-queue list --name "Support" -o json`
+- Person name → `wxcli people list --display-name "Jane Smith" -o json`
+
+Extract the resource's `id` and `locationId` from the list response.
+
+### Step 2 — Get the location timezone
+
+```bash
+wxcli locations show LOCATION_ID -o json
+```
+Extract `timeZone` (e.g., "America/Chicago"). Use this to evaluate schedules against the queried datetime.
+
+### Step 3 — Walk the chain
+
+Based on the entry point type, follow the appropriate path. **Maximum depth: 5 hops.** Track visited resources to detect loops.
+
+#### Auto Attendant path
+
+1. **Get AA detail:**
+```bash
+wxcli auto-attendant show LOCATION_ID AA_ID -o json
+```
+
+2. **Get the AA's schedule(s):**
+The AA response includes `businessSchedule` and/or `holidaySchedule` references (with schedule `name` and `id`).
+
+For each schedule reference:
+```bash
+wxcli location-schedules show LOCATION_ID TYPE SCHEDULE_ID -o json
+```
+Where TYPE is `businessHours` or `holidays`.
+
+3. **Evaluate which schedule is active at the queried time:**
+
+**Precedence:**
+1. Check holiday schedule first — if the queried date matches a holiday entry, use the `holidaySchedule` action
+2. Check business hours schedule — if the queried time falls within the defined business hours for that day of week, use the `businessHours` menu
+3. Otherwise — use the `afterHours` menu
+
+**Business hours evaluation:**
+The schedule response includes per-day entries. Each day has `startTime` and `endTime` (24-hour format). Check if the queried time (converted to location timezone) falls within the range for the queried day of week.
+
+Example schedule data:
+```json
+{
+  "type": "businessHours",
+  "events": [
+    {"name": "Monday", "startTime": "08:00", "endTime": "17:00"},
+    {"name": "Tuesday", "startTime": "08:00", "endTime": "17:00"},
+    ...
+  ]
+}
+```
+
+If the day is Saturday/Sunday and no entry exists → after hours.
+
+**Holiday evaluation:**
+Check the holiday schedule's `events` for a date match. Holiday events may have `startDate`/`endDate` or specific dates with optional yearly recurrence.
+
+4. **Report the active menu:**
+Show the greeting message (if available) and the menu options. Each option maps a key press to a destination (transfer to another AA, HG, CQ, person, voicemail, etc.).
+
+5. **Recurse:** For each destination that is another AA, CQ, or HG → follow that chain (increment hop count).
+
+#### Hunt Group path
+
+1. **Get HG detail:**
+```bash
+wxcli hunt-group show LOCATION_ID HG_ID -o json
+```
+
+2. **Report:**
+```
+→ Sales Hunt Group
+  Ring pattern: [SIMULTANEOUS|CIRCULAR|TOP_DOWN|WEIGHTED]
+  Members ([N]):
+    - Jane Smith (ext 2001)
+    - Bob Lee (ext 2002)
+  No-answer: After [timeout]s → [action/destination]
+```
+
+3. **If no-answer destination is another feature** (AA, CQ, voicemail group) → recurse.
+
+#### Call Queue path
+
+1. **Get CQ detail:**
+```bash
+wxcli call-queue show LOCATION_ID CQ_ID -o json
+```
+
+2. **Report:**
+```
+→ Support Call Queue
+  Routing: [Longest Idle|Circular|Top Down|Weighted|Simultaneous]
+  Agents ([N]):
+    - Agent 1 (ext XXXX)
+    - Agent 2 (ext XXXX)
+  Overflow: After [threshold]s/[max callers] → [destination]
+```
+
+3. **If overflow destination is another feature** → recurse.
+
+#### Person path
+
+1. **End of chain.** Report:
+```
+→ Jane Smith (ext 2001, Austin)
+```
+
+2. **Optionally check call forwarding:**
+```bash
+wxcli user-settings show-call-forwarding PERSON_ID -o json
+```
+If `noAnswer.enabled` is true, note:
+```
+  If no answer after [rings] rings → forwards to [destination]
+```
+
+#### Workspace path
+
+End of chain:
+```
+→ Conference Room A (workspace, Austin)
+```
+
+### Step 4 — Format the output
+
+Use the numbered-hop format:
+
+```
+Call to +1-512-555-1000 at 7:00 PM Saturday (CST):
+
+1. → Main Auto Attendant (after-hours schedule active)
+   Greeting: "Thank you for calling Acme Corp. Our offices are closed."
+   Menu: Press 1 for Sales, Press 2 for Support, Press 0 for Operator
+
+2. [Press 1] → Sales Call Queue
+   Routing: Longest idle agent
+   Agents: Jane Smith (ext 2001), Bob Lee (ext 2002), Maria Garcia (ext 2003)
+   Overflow: After 120 seconds → Sales Voicemail Group
+
+3. [Overflow] → Sales Voicemail Group
+   Members: Jane Smith, Bob Lee
+```
+
+**For time-comparison queries** ("business hours vs after hours"), trace both paths and present side by side:
+
+```
+Call to +1-512-555-1000:
+
+BUSINESS HOURS (Mon-Fri 8am-5pm CST):
+1. → Main Auto Attendant (business hours)
+   Menu: Press 1 for Sales, Press 2 for Support, Press 0 for Operator
+2. [Press 1] → Sales Hunt Group (4 members, simultaneous ring)
+
+AFTER HOURS (evenings, weekends):
+1. → Main Auto Attendant (after hours)
+   Greeting: "Our offices are closed."
+   Menu: Press 1 for urgent Sales, Press 0 for general voicemail
+2. [Press 1] → Sales On-Call (1 member)
+```
+
+## Constraints
+
+1. **Depth limit: 5 hops.** If the chain goes deeper, report what's been traced and note: "Call flow continues beyond 5 hops — check Control Hub for the full chain."
+2. **No live agent state.** The tracer shows the *configured* path, not real-time availability. Note: "This shows the configured routing — actual behavior depends on agent availability at the time of the call."
+3. **Missing schedule.** If an AA has no schedule assigned, report: "No schedule configured — default behavior applies (business hours menu active at all times)."
+4. **Missing menu data.** AA menus may not be fully available via API. Report what's available; note gaps.
+5. **Inbound only (v1).** This traces inbound call paths. For outbound routing through dial plans/trunks, suggest: "For outbound routing, try: 'What dial plan handles calls to +44...?' (uses the routing domain)."
+6. **Loop detection.** Track visited resource IDs. If a chain references a resource already visited, report: "Loop detected — [resource] routes back to [earlier resource]." Stop recursion.
+
+## Gotchas
+
+1. **Schedule show needs THREE positional args.** `wxcli location-schedules show LOCATION_ID TYPE SCHEDULE_ID` — not just the schedule ID. The TYPE must be `businessHours` or `holidays`.
+2. **Schedule list is location-scoped.** `wxcli location-schedules list LOCATION_ID -o json` — locationId is a required positional arg.
+3. **AA menu key mappings.** The AA show response includes `businessHours` and `afterHours` objects with `actions` arrays. Each action has a `key` (0-9, #, *) and a `value` (transfer destination).
+4. **Timezone handling.** Always convert the queried time to the location's timezone before evaluating schedules. A query at "7pm" from a user in EST targeting an AA in CST should evaluate at 6pm CST.
+5. **Holiday recurrence.** Some holidays recur annually (Christmas, New Year's). Check the `recurrence` field in holiday events. If `recurAnnually: true`, match the month/day regardless of year.

wxcli/_playbook/.claude/skills/query-live/domains/call-history.md

@@ -0,0 +1,44 @@
+# Call History Domain
+
+**Covers:** Recent call history, call volume, missed calls, busiest hours, voicemail-bound calls.
+
+**This is a delegation module.** For call history and CDR questions, load the `reporting` skill and use its CDR recipe composition guide. The reporting skill has 75 pre-built recipes covering volume analysis, location breakdowns, hourly trends, agent performance, and threshold detection.
+
+## When to Delegate
+
+Any question about **past calls** or **call patterns** should use the reporting skill:
+- "How many calls did we get yesterday?"
+- "Show me missed calls from this morning"
+- "What's our busiest hour for incoming calls?"
+- "How many calls went to voicemail last week?"
+- "What's our average call duration?"
+- "Which agent handled the most calls?"
+
+## How to Delegate
+
+Load the reporting skill:
+
+```
+Skill: reporting
+```
+
+The reporting skill will:
+1. Verify the token has `spark-admin:calling_cdr_read` scope
+2. Check for cached CDR data at `/tmp/cdr-session.json`
+3. Pull CDR data for the requested time range
+4. Run the appropriate recipe or compose a custom query
+5. Format the results
+
+## Constraints to Communicate
+
+When answering CDR-related questions, note these limits if relevant:
+- **30-day retention window** — CDR data is only available for the last 30 days
+- **12-hour max query window** — each API request covers at most 12 hours; the skill handles splitting automatically
+- **~15 minute delay** — very recent calls (last 15 minutes) may not appear yet
+
+## Not CDR — Handle Inline
+
+These look like call history but are actually config queries handled by other domains:
+- "Is call recording enabled for John?" → people-and-settings domain (wxcli user-settings show-call-recording)
+- "What's the call queue overflow setting?" → features domain (wxcli call-queue show)
+- "Show me the after-hours routing" → call-flow-trace domain

wxcli/_playbook/.claude/skills/query-live/domains/features.md

@@ -0,0 +1,169 @@
+# Features Domain
+
+**Covers:** Hunt groups, call queues, auto attendants, paging groups, call park, call pickup, voicemail groups.
+
+## Question Patterns
+
+| Pattern | Example |
+|---------|---------|
+| Membership | "Who's in the Sales hunt group?", "List agents in the Support queue" |
+| Inventory | "How many call queues are at Denver?", "What auto attendants do we have?" |
+| Configuration | "What's the ring pattern for Support HG?", "Show overflow for Main CQ" |
+| Schedule | "Which auto attendants use the Holiday schedule?" |
+| Cross-feature | "Which features are at the Austin location?" |
+
+## Command Recipes
+
+### Hunt Groups
+
+**List all (org-wide or per-location):**
+```bash
+wxcli hunt-group list -o json
+wxcli hunt-group list --location-id LOCATION_ID -o json
+wxcli hunt-group list --name "Sales" -o json
+```
+
+**Show detail (requires BOTH locationId AND huntGroupId):**
+```bash
+wxcli hunt-group show LOCATION_ID HUNT_GROUP_ID -o json
+```
+Response includes: `agents` (members list), `callPolicies` (ring pattern: SIMULTANEOUS, CIRCULAR, TOP_DOWN, WEIGHTED), `noAnswer` action and settings.
+
+### Call Queues
+
+**List:**
+```bash
+wxcli call-queue list -o json
+wxcli call-queue list --location-id LOCATION_ID -o json
+wxcli call-queue list --has-cx-essentials true -o json
+```
+
+**Show detail (requires BOTH locationId AND queueId):**
+```bash
+wxcli call-queue show LOCATION_ID QUEUE_ID -o json
+```
+Response includes: `agents`, `callPolicies` (routing type), `queueSettings` (overflow threshold, wait treatment), `overflowSettings`.
+
+### Auto Attendants
+
+**List:**
+```bash
+wxcli auto-attendant list -o json
+wxcli auto-attendant list --location-id LOCATION_ID -o json
+wxcli auto-attendant list --name "Main" -o json
+```
+
+**Show detail (requires BOTH locationId AND autoAttendantId):**
+```bash
+wxcli auto-attendant show LOCATION_ID AA_ID -o json
+```
+Response includes: `businessHoursSchedule`, `holidaySchedule`, `businessHours` (menu config), `afterHours` (menu config), `extension`, `phoneNumber`.
+
+### Paging Groups
+
+**List:**
+```bash
+wxcli paging-group list -o json
+wxcli paging-group list --location-id LOCATION_ID -o json
+```
+
+**Show detail (requires BOTH locationId AND pagingGroupId):**
+```bash
+wxcli paging-group show LOCATION_ID PAGING_GROUP_ID -o json
+```
+
+### Call Park (location-scoped list)
+
+**List (locationId is REQUIRED positional arg):**
+```bash
+wxcli call-park list LOCATION_ID -o json
+```
+
+**Show detail:**
+```bash
+wxcli call-park show LOCATION_ID CALL_PARK_ID -o json
+```
+
+### Call Pickup (location-scoped list)
+
+**List (locationId is REQUIRED positional arg):**
+```bash
+wxcli call-pickup list LOCATION_ID -o json
+```
+
+**Show detail:**
+```bash
+wxcli call-pickup show LOCATION_ID CALL_PICKUP_ID -o json
+```
+
+## Resolution Rules
+
+**Finding a feature by name:**
+1. List the feature type: e.g., `wxcli hunt-group list --name "Sales" -o json`
+2. If the `--name` filter doesn't match, list all and search the JSON response
+3. When showing detail, you MUST have both the `locationId` AND the feature's `id`
+4. The list response includes both — extract them from the matching item
+
+**Finding all features at a location:**
+1. Resolve location name → ID
+2. Run each feature list with `--location-id`:
+   ```bash
+   wxcli hunt-group list --location-id LOC_ID -o json
+   wxcli call-queue list --location-id LOC_ID -o json
+   wxcli auto-attendant list --location-id LOC_ID -o json
+   wxcli paging-group list --location-id LOC_ID -o json
+   wxcli call-park list LOC_ID -o json
+   wxcli call-pickup list LOC_ID -o json
+   ```
+3. Note: call-park and call-pickup take locationId as positional arg, others as --location-id flag
+
+## Response Guidance
+
+**Membership query** ("Who's in the Sales hunt group?"):
+```
+Sales Hunt Group has 4 members:
+  - Jane Smith (ext 2001, Austin)
+  - Bob Lee (ext 2002, Austin)
+  - Maria Garcia (ext 2003, Denver)
+  - Tom Chen (ext 2004, Denver)
+
+Ring pattern: Simultaneous
+No-answer action: Forward to Sales voicemail after 20 seconds
+```
+
+**Inventory query** ("How many call queues at Denver?"):
+```
+Denver has 3 call queues:
+  - Support Queue (ext 5001, 8 agents)
+  - Sales Queue (ext 5002, 4 agents)
+  - Billing Queue (ext 5003, 3 agents)
+```
+
+**Configuration query** ("Show overflow for Main CQ"):
+```
+Main Call Queue overflow settings:
+  - Overflow after: 120 seconds in queue
+  - Overflow action: Transfer to Main Voicemail Group
+  - Max callers in queue: 25
+  - When queue is full: Play busy treatment
+```
+
+**Cross-feature inventory** ("What features are at Austin?"):
+```
+Austin has 12 call features:
+  - 3 auto attendants: Main Menu, Sales AA, Support AA
+  - 4 call queues: Sales, Support, Billing, General
+  - 2 hunt groups: Front Desk, Dispatch
+  - 1 paging group: Warehouse PA
+  - 1 call park: Lobby Park
+  - 1 call pickup: Front Desk Pickup
+```
+
+## Gotchas
+
+1. **CX Essentials queues are hidden by default.** `wxcli call-queue list` does NOT show CX queues unless you pass `--has-cx-essentials true`. If a user asks about a queue you can't find, try: `wxcli call-queue list --has-cx-essentials true -o json`.
+2. **Call park and call pickup have no org-wide list.** You must enumerate per-location. If the user asks "show all call parks" without specifying a location, list locations first, then query each.
+3. **Feature show commands need TWO positional args.** `wxcli hunt-group show LOCATION_ID HG_ID` — not just the feature ID. Both IDs are in the list response.
+4. **Voicemail groups are not yet in wxcli.** If asked about voicemail groups, note they can be managed in Control Hub under Calling → Features → Voicemail Groups.
+5. **Hunt groups ignore member personal call forwarding.** HG calls route directly to the agent's device and bypass any personal call forwarding the member has configured. Only the hunt group's own no-answer/forwarding settings (feature-level) govern what happens when a member doesn't answer.
+6. **DND on a hunt group member skips them, not their voicemail.** If a member has DND enabled, the hunt group skips that member and moves to the next — it does NOT send the call to the member's personal voicemail. The HG's no-answer action only triggers after all members are exhausted.

wxcli/_playbook/.claude/skills/query-live/domains/numbers.md

@@ -0,0 +1,93 @@
+# Numbers Domain
+
+**Covers:** Phone number inventory, assignment status, available numbers, number lookups by person or location.
+
+## Question Patterns
+
+| Pattern | Example |
+|---------|---------|
+| Number inventory | "How many numbers do we have?", "Show me all numbers at Austin" |
+| Assignment lookup | "What number is John Smith on?", "Who has +1-512-555-1000?" |
+| Available numbers | "Which phone numbers aren't assigned?", "How many numbers are available at Denver?" |
+| Number type query | "Show me all toll-free numbers", "Which numbers are DID vs extension?" |
+
+## Command Recipes
+
+### List all numbers (org-wide)
+```bash
+wxcli numbers list -o json
+```
+
+### List numbers at a location
+```bash
+wxcli numbers list --location-id LOCATION_ID -o json
+```
+
+### List available (unassigned) numbers
+```bash
+wxcli numbers list --available true -o json
+```
+
+### List numbers filtered by state
+```bash
+wxcli numbers list --state ACTIVE -o json
+# States: ACTIVE, INACTIVE
+```
+
+### Find a number by phone number
+```bash
+wxcli numbers list --phone-number "+15125551000" -o json
+```
+
+### Find numbers by owner
+```bash
+wxcli numbers list --owner-id PERSON_ID -o json
+```
+
+## Resolution Rules
+
+**Finding a person's number:**
+1. `wxcli people list --display-name "John Smith" -o json` → get person ID
+2. `wxcli numbers list --owner-id <personId> -o json` → get their number(s)
+
+**Finding who has a number:**
+1. `wxcli numbers list --phone-number "+15125551000" -o json` → check `owner` field
+2. The `owner` object contains `type` (PEOPLE, AUTO_ATTENDANT, CALL_QUEUE, HUNT_GROUP, etc.) and `id`
+3. If type is PEOPLE: `wxcli people show <ownerId> -o json` → get the person's name
+
+**Finding a location's numbers:**
+1. If user says a location name (not ID): `wxcli locations list -o json` → search by name → get location ID
+2. `wxcli numbers list --location-id <locationId> -o json`
+
+## Response Guidance
+
+**Inventory query** ("Show me all numbers at Austin"):
+Group by assignment status. Show counts.
+```
+Austin has 50 phone numbers:
+  - 38 assigned (32 to users, 3 to auto attendants, 2 to call queues, 1 to hunt group)
+  - 12 available
+
+Number range: +1-512-555-1000 through +1-512-555-1049
+```
+
+**Lookup query** ("What number is John on?"):
+```
+John Smith has 1 number:
+  - +1-512-555-1023 (extension 1023, Austin location)
+```
+
+**Available query** ("Which numbers aren't assigned?"):
+```
+12 numbers are available at Austin:
+  - +1-512-555-1038
+  - +1-512-555-1039
+  ... and 10 more
+```
+
+## Gotchas
+
+1. **Number list can be large.** For orgs with 1000+ numbers, encourage location-scoped queries: "That's a lot of numbers. Want me to check a specific location?"
+2. **Owner field structure.** The `owner` object in the number response has `type`, `id`, `firstName`, `lastName`. Use firstName/lastName directly when available — avoids an extra API call.
+3. **Main number flag.** Numbers with `mainNumber: true` are the location's main line. Note this in responses: "+1-512-555-1000 (main number for Austin)".
+4. **Extension vs DID.** Numbers may be extension-only (no external DID). Check `phoneNumberType` field.

wxcli/_playbook/.claude/skills/query-live/domains/people-and-settings.md

@@ -0,0 +1,146 @@
+# People & Settings Domain
+
+**Covers:** User lookups, call settings audits (voicemail, forwarding, DND, recording, caller ID, permissions, executive-assistant pairing).
+
+## Question Patterns
+
+| Pattern | Example |
+|---------|---------|
+| User lookup | "Show me users at Austin", "Find John Smith" |
+| Setting check (single user) | "Does John have voicemail enabled?", "Show me Jane's call forwarding" |
+| Setting audit (bulk) | "Which users at Austin don't have voicemail?", "Who has DND turned on?" |
+| Recording audit | "Show me everyone whose calls are being recorded" |
+| Executive-assistant | "Which users have executive-assistant pairing?" |
+| Comparison | "What's different about John's settings vs Jane's?" |
+
+## Command Recipes
+
+### List users (org-wide or filtered)
+```bash
+wxcli people list -o json
+wxcli people list --location-id LOCATION_ID -o json
+wxcli people list --display-name "John Smith" -o json
+wxcli people list --email "john@example.com" -o json
+```
+
+### Show a specific user
+```bash
+wxcli people show PERSON_ID -o json
+```
+
+### Voicemail settings
+```bash
+wxcli user-settings show-voicemail PERSON_ID -o json
+```
+Response includes: `enabled`, `sendBusyCalls`, `sendUnansweredCalls`, `emailCopyOfMessage`, `messageStorage`, `notifications`.
+
+### Call forwarding settings
+```bash
+wxcli user-settings show-call-forwarding PERSON_ID -o json
+```
+Response includes 4 blocks: `always`, `busy`, `noAnswer`, `businessContinuity`. Each has `enabled` and `destination`.
+
+### Call recording settings
+```bash
+wxcli user-settings show-call-recording PERSON_ID -o json
+```
+Response includes: `enabled`, `record` (Always/Never/Always with Pause/On Demand), `startStopAnnouncement`.
+
+### Do Not Disturb
+```bash
+wxcli user-settings show-do-not-disturb PERSON_ID -o json
+```
+Response includes: `enabled`, `ringSplashEnabled`.
+
+### Caller ID
+```bash
+wxcli user-settings show-caller-id PERSON_ID -o json
+```
+
+### Executive-assistant pairing
+```bash
+wxcli user-settings show-executive-assistant PERSON_ID -o json
+```
+Response includes: `type` (UNASSIGNED, EXECUTIVE, or EXECUTIVE_ASSISTANT).
+
+### Call intercept
+```bash
+wxcli user-settings show-intercept PERSON_ID -o json
+```
+
+### Barge-in
+```bash
+wxcli user-settings show-barge-in PERSON_ID -o json
+```
+
+### Call waiting
+```bash
+wxcli user-settings show-call-waiting PERSON_ID -o json
+```
+
+### Hoteling
+```bash
+wxcli user-settings show-hoteling PERSON_ID -o json
+```
+
+## Resolution Rules
+
+**Finding a person by name:**
+1. `wxcli people list --display-name "John Smith" -o json`
+2. If exact match → use it. If multiple → disambiguate by location/email.
+3. If no results → try partial: `wxcli people list --display-name "John" -o json`
+
+**Finding users at a location by name:**
+1. `wxcli locations list -o json` → search for location name → get ID
+2. `wxcli people list --location-id <locationId> -o json`
+
+## Join Patterns
+
+**Audit query** ("Which users at Austin don't have voicemail?"):
+1. Resolve location name → ID: `wxcli locations list -o json`
+2. List users at location: `wxcli people list --location-id <locationId> -o json`
+3. For each user, fetch setting: `wxcli user-settings show-voicemail <personId> -o json`
+4. Filter to matches (enabled=false or missing)
+5. Format as audit table
+
+**Comparison query** ("Compare John's settings vs Jane's"):
+1. Resolve both names to person IDs
+2. Fetch the same setting(s) for both
+3. Present side-by-side with differences highlighted
+
+## Response Guidance
+
+**Single-user setting check:**
+```
+John Smith has voicemail enabled.
+  - Send busy calls to voicemail: Yes
+  - Send unanswered calls after 3 rings: Yes
+  - Email copy to: john.smith@acme.com
+  - Greeting: Custom
+```
+
+**Bulk audit:**
+```
+12 of 45 users at Austin don't have voicemail enabled:
+  - Alice Johnson (ext 3001)
+  - Brian Kim (ext 3002)
+  - Carol Davis (ext 3003)
+  ... and 9 more
+
+Note: I checked all 45 Webex Calling-licensed users at the Austin location.
+```
+
+**Executive-assistant pairing:**
+```
+3 executive-assistant pairings found:
+  - Jane Smith (Executive) ↔ Alice Johnson (Assistant)
+  - Bob Lee (Executive) ↔ Carol Davis (Assistant)
+  - Tom Chen (Executive) ↔ Maria Garcia (Assistant)
+```
+
+## Gotchas
+
+1. **6 person settings are user-only (no admin path).** If a setting returns 404 with error 4008, it requires user-level OAuth. Report: "This setting can only be viewed by the user themselves, not by an admin."
+2. **Two path families for person settings.** The CLI abstracts this — use `wxcli user-settings` commands and they route to the correct path. No need to worry about `/people/{id}/features/` vs `/telephony/config/people/{id}/`.
+3. **Workspace settings differ from person settings.** Basic workspaces return 405 for most `/telephony/config/` settings. If a workspace query fails with 405, report: "This workspace has a Basic license — only DND and Music on Hold settings are available."
+4. **Large org batching.** For orgs with 100+ users, batch settings checks and provide progress updates. Don't try to fetch all settings in a single burst.