Combine Salesforce deals and Zendesk support in one brief

**Objective:** Produce a brief on the Salesforce account {account-name}, covering its commercial position in Salesforce and its support history in Zendesk over the last {lookback-days} days (default 90), for a renewal or account review meeting.

**Step 1: Find the account in Salesforce**

Call `salesforce-get-account` with `name` set to {account-name}. If nothing comes back, call it again with `name.contains`. If more than one account matches, list them (`name`, `account-id`, `billing-city`, `owner`) and stop so the user can pick one.

With the `account-id`:

* call `salesforce-get-opportunity` with `account-id` and `closed` set to false for open pipeline;
* call `salesforce-get-contract` with `account-id` for contract `status`, `start-date` and `end-date`;
* call `salesforce-get-contact` with `account-id` for contacts and their `email` addresses;
* call `salesforce-get-task` with `account-id` and `closed` set to false for open follow-ups.

**Step 2: Match the account in Zendesk**

**How to match a Salesforce account to a Zendesk organization (use this order, stop at the first hit):**

1. Call `zendesk-get-organization` with `external-id` set to the Salesforce `account-id`.
2. If nothing comes back, call `zendesk-get-organization` with `name` set to the Salesforce account `name` exactly.
3. If still nothing, take the domain from the account's `website` (strip `http://`, `https://`, `www.` and any path) and call `zendesk-get-organization` with `domain-names.contains` set to it.
4. If more than one organization matches at any step, list them and treat the account as ambiguous rather than guessing.
5. If none match, report the account as "No Zendesk organization found" and continue with the next account.

Once matched, use the Zendesk organization's own `name` (not the Salesforce account name) as `organization-name` on `zendesk-get-ticket`, since the two systems can spell the company differently.

**Step 3: Pull support history from Zendesk**

* Call `zendesk-get-ticket` with `organization-name` and `created.from` set to {lookback-days} days ago (default 90).
* For each Salesforce contact with an `email`, call `zendesk-get-ticket` with `requester-email` and the same `created.from` to catch tickets not filed under the organization. Merge by `ticket-id` so no ticket is counted twice.
* For each ticket, call `zendesk-get-satisfaction-rating` with `ticket-id` (at most 25 tickets).

**Step 4: Report**

* **Account:** name, owner, annual revenue, industry, rating.
* **Commercial:** open opportunities (name, stage, amount, close date), active and upcoming contract end dates, open Salesforce tasks.
* **Support:** tickets in the window by status and priority, unsolved tickets listed with subject, priority and age, CSAT good/bad counts with any bad-rating comments quoted.
* **Contacts raising tickets:** which Salesforce contacts filed tickets and how many each.
* **Talking points:** three short bullets the account team should raise, based only on the data above.

**Rules & Guidelines:**

* Salesforce tools start with "salesforce-" and come from the Salesforce MCP server. Zendesk tools start with "zendesk-" and come from the Zendesk MCP server. Both servers must be connected.
* This prompt is read-only. Do NOT call any write tool on either server, including `salesforce-add-task`, `salesforce-update-task`, `salesforce-add-case`, `salesforce-update-case`, `salesforce-update-account`, `salesforce-update-opportunity`, `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-organization` or `zendesk-update-user`.

**Validation:**

* If no Zendesk organization matches, still run the `requester-email` searches, and say the organization link is missing.
* If a Zendesk requester email has no Salesforce contact, list it under "Ticket requesters not in Salesforce".