See which problems from a Chorus call have no Zendesk ticket

**Objective:** For Chorus conversation `{conversation-id}`, list every support problem the customer raised and whether Zendesk already has a ticket for it.

**Step 1: Read the conversation (Chorus)**

Call `chorus-get-engagements` with conversation-id set to `{conversation-id}`. If nothing comes back, say so and stop. Keep date, subject, account-name and meeting-summary. From the meeting-summary, list each distinct problem, bug, outage, billing dispute or request for help the customer raised. Ignore commercial topics such as pricing and renewals unless they describe a fault.

**Step 2: Identify the customer participants (Chorus)**

Call `chorus-get-conversation-participants` with conversation-id set to `{conversation-id}`. Treat as customers the participants whose company-name differs from the host company or whose email domain differs from the Chorus user-email on the conversation. Keep their name and email.

**Step 3: Look for tickets (Zendesk)**

For each customer email, call `zendesk-get-ticket` with requester-email set to it and created.from set to 60 days before the conversation date. If none of the customers has a ticket, call `zendesk-get-ticket` with organization-name set to the account-name. Organization names may differ between the systems; if that returns nothing, call `zendesk-get-user` with email set to one customer email to read its organization-name, and retry with that.

Match each problem from Step 1 to a ticket by subject and content. Call `zendesk-get-ticket-comment` with a ticket-id only when the subject alone is not enough to decide.

**Step 4: Report**

Table: problem raised, who raised it, matching ticket-id (or none), ticket status, ticket priority. Then list the problems with no ticket and suggest using the log-call-issue-as-ticket prompt for them.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server. `zendesk-get-ticket`, `zendesk-get-ticket-comment` and `zendesk-get-user` are on the zendesk server.
* This prompt is read-only. Do NOT call `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-add-user` or any other add, update or export tool.

**Validation:**

* If the meeting-summary is empty, say the call has no summary to check and stop.
* If no problems were raised, say so and stop without searching Zendesk.
* If a customer email is not a Zendesk user at all, say so; it usually means they have never contacted support.