Turn a problem raised on a Chorus call into one clean Zendesk ticket

**Objective:** Create one Zendesk ticket for the support problem raised on Chorus conversation `{conversation-id}`. If `{issue}` is given, log that problem; otherwise log the main problem in the meeting-summary.

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

Call `chorus-get-engagements` with conversation-id set to `{conversation-id}`. If nothing comes back, say so and stop. Read date, subject, account-name, user-name and meeting-summary. If `{issue}` is empty and the summary raises several problems, list them and ask which to log.

Call `chorus-get-conversation-participants` with conversation-id set to `{conversation-id}` and pick the customer who raised the problem as the requester (a participant whose company-name or email domain is not the host company's). If several customers attended and it is unclear who raised it, ask.

**Step 2: Check Zendesk for the requester and duplicates**

Call `zendesk-get-user` with email set to the requester's email. Note whether they exist and their organization-name.

Call `zendesk-get-ticket` with requester-email set to the same email and created.from set to 60 days before the call date. If an unresolved ticket (status new, open, pending or hold) already covers the problem, show it and stop. Suggest the add-call-summary-to-ticket prompt instead.

**Step 3: Draft and confirm**

Show the draft: requester-name, requester-email, subject (under 80 characters), priority (normal unless the call describes an outage or data loss), type (problem or question), and the comment. Write the comment to the customer, in neutral terms: what they reported, when (the call date) and any detail from the summary. Do not include internal sales notes, pricing or opportunity details. The first comment is visible to the requester.

Wait for my explicit confirmation. Apply any changes I ask for.

**Step 4: Create and confirm**

Call `zendesk-add-ticket` once, with requester-email, requester-name, subject, comment, priority and type. Then call `zendesk-get-ticket` with the returned id and report the ticket-id, subject, status and requester.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server. `zendesk-get-user`, `zendesk-get-ticket` and `zendesk-add-ticket` are on the zendesk server.
* `zendesk-add-ticket` is the only write, called once, after confirmation.
* Do NOT call `zendesk-add-user`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-user` or any chorus add, update or export tool.

**Validation:**

* If the requester is not yet a Zendesk user, say that creating the ticket will create them as an end user, and include that in the confirmation.
* If `zendesk-add-ticket` fails, report the error and do not retry without asking.
* If the call summary does not describe a support problem, say so and stop.