One view of a customer from support tickets and sales calls

**Objective:** Brief me on `{organization-name}` from both sides, support (Zendesk) and sales conversations (Chorus), looking back `{lookback-days}` days (default 90).

**Step 1: Confirm the organization in Zendesk**

Call `zendesk-get-organization` with name set to `{organization-name}`. If nothing comes back, call it again with domain-names.contains set to the most distinctive word of the name. If several organizations match, list them with organization-id and domain-names and stop. Keep the exact Zendesk name and its domain-names.

**Step 2: Support side (Zendesk)**

Call `zendesk-get-ticket` with organization-name set to the exact Zendesk name, created.from set to today minus `{lookback-days}` days (YYYY-MM-DD) and max-records 200. Treat status new, open, pending and hold as unresolved. Note the unresolved tickets by priority, the oldest unresolved ticket, and the recurring subjects.

**Step 3: Match the account in Chorus**

Chorus account names are typed by reps and rarely match Zendesk exactly. Call `chorus-get-engagements` with account-name set to the exact Zendesk name, date.from set to the same start date and max-records 100. If nothing comes back, call it again with account-name.contains set to the most distinctive word of the name. If the results cover more than one distinct account-name, list them and ask which one is meant before continuing.

Then call `chorus-get-emails` with account-name.contains set to the same text and sent-time.from set to the same start date, max-records 50.

**Step 4: Report**

1. One-line status: unresolved ticket count, urgent/high count, last sales conversation date.
2. Support: table of unresolved tickets (ticket-id, subject, priority, status, created-date, assignee-name).
3. Sales: table of conversations (date, subject, user-name, opportunity-name) with one line from each meeting-summary.
4. Overlap: any issue that appears both in a ticket subject and in a meeting-summary or email subject, with the ticket-id and conversation-id side by side.
5. Risks and next steps, at most three.

**Rules & Guidelines:**

* `zendesk-get-organization` and `zendesk-get-ticket` are on the zendesk server. `chorus-get-engagements` and `chorus-get-emails` are on the chorus server.
* This prompt is read-only. Do NOT call `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-organization`, `chorus-add-moment`, `chorus-create-playlist` or any other add, update or export tool.
* Do not quote email bodies at length; summarize them.

**Validation:**

* If Zendesk has the organization but Chorus has no matching account, report the support side and say no sales conversations were found under that name.
* If Chorus has conversations but Zendesk has no tickets in the period, say so plainly rather than implying the account is healthy.
* If neither side returns anything, say the account was not found and stop.