Find what the customer told sales before they opened the ticket

**Objective:** For Zendesk ticket `{ticket-id}`, find what the customer said to the sales or account team in Chorus within `{window-days}` days (default 30) either side of the ticket being created.

**Step 1: Read the ticket (Zendesk)**

Call `zendesk-get-ticket` with ticket-id set to `{ticket-id}`. If nothing comes back, say the ticket was not found and stop. Keep requester-email, requester-name, organization-name, subject and created-date. Call `zendesk-get-ticket-comment` with the same ticket-id and public true to understand the issue in the customer's own words.

**Step 2: Find the requester in Chorus**

Call `chorus-get-conversation-participants` with email set to the requester-email and max-records 100. Keep each conversation-id. Then call `chorus-get-engagements` with conversation-id set to each one (at most 10) to get date, subject, user-name and meeting-summary. Discard conversations outside the window.

If the requester is in no conversation, fall back to the account: call `chorus-get-engagements` with account-name.contains set to the most distinctive word of the organization-name, date.from and date.to set to the window, max-records 50.

Also call `chorus-get-emails` with initiator-email set to the requester-email, sent-time.from and sent-time.to set to the window.

**Step 3: Report**

1. The ticket in one line: subject, status, created-date.
2. Table of conversations and emails in date order: date, source (call or email), subject, Chorus user, and whether the ticket's issue came up (yes, no, unclear), with a short quote or summary line when yes.
3. Whether the issue was raised in sales conversations before it reached support, and how long before.

**Rules & Guidelines:**

* `zendesk-get-ticket` and `zendesk-get-ticket-comment` are on the zendesk server. `chorus-get-conversation-participants`, `chorus-get-engagements` and `chorus-get-emails` are on the chorus server.
* This prompt is read-only. Do NOT call `zendesk-add-ticket-comment`, `zendesk-update-ticket`, `chorus-add-moment` or any other add, update or export tool.
* Say whether each match came from the requester's own email or from the account-name fallback; the fallback is weaker evidence.

**Validation:**

* If the ticket has no requester-email, use only the account-name fallback and say so.
* Compare email addresses case-insensitively.
* If Chorus returns nothing on either path, report the ticket with no related conversations and stop.