Alert account teams when Zendesk ticket volume climbs

**Objective:** Find customers that raised {min-tickets} or more Zendesk tickets (default 5) in the last {lookback-days} days (default 30), show the trend, and after the user confirms, create one follow-up task per account in Salesforce, due {due-in-days} days from today (default 7).

**Step 1: Count recent tickets in Zendesk**

Call `zendesk-get-ticket` with `created.from` set to {lookback-days} days ago (default 30) and `max-records` set to 1000. Group by `organization-name` and keep the groups with at least {min-tickets} tickets (default 5). Then call `zendesk-get-ticket` with `organization-name` and `created.from` / `created.to` covering the previous period of the same length, to compare. For each group note the count now, the count before, how many are `urgent` or `high`, how many are unsolved, and the three most common words or themes in `subject`. If no organization reaches the threshold, say so and stop.

**Step 2: Find the Salesforce account**

For each organization, call `zendesk-get-organization` with `name` set to the `organization-name`. If its `external-id` is filled in, call `salesforce-get-account` with `account-id` set to it; otherwise call `salesforce-get-account` with `name` set to the `organization-name`. If there is no match or more than one, list the organization under "Not matched" and do not create a task for it.

**Step 3: Avoid duplicate tasks**

For each matched `account-id`, call `salesforce-get-task` with `account-id`, `closed` set to false and `subject.contains` set to `Zendesk ticket trend`. If an open task already exists, show it and skip that account.

**Step 4: Propose, then confirm**

Show one table of the proposed tasks and STOP for confirmation:

| Account | Owner | Tickets now / before | Urgent/high | Unsolved | Themes | Proposed subject | Due date |

The subject is `Zendesk ticket trend: <N> tickets in <lookback> days` and the comments list the themes, the counts and up to five `ticket-id` values with their subjects. Ask the user to confirm all, pick some, or cancel. Do not create anything until they answer.

**Step 5: Create the tasks in Salesforce**

For each confirmed account only, call `salesforce-add-task` exactly once with `subject`, `what-id` set to the account's `account-id`, `due-date` set to today plus {due-in-days} days (default 7) as an ISO date, `priority` set to `High` when any ticket is urgent and `Normal` otherwise, and `comments` as above. Leave `assigned-to-id` empty so the task goes to the connected user, unless the user asks to assign to the account owner; then call `salesforce-get-user` with `name` set to the account `owner` and use its `user-id`.

**Step 6: Confirm what was written**

Report each created task's returned `id` next to the account name, plus any accounts skipped and why.

**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.
* The only write allowed is `salesforce-add-task`, once per confirmed account, after the user confirms in Step 4.
* Do NOT call `salesforce-update-task`, `salesforce-add-case`, `salesforce-update-account`, `salesforce-update-opportunity`, `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment` or `zendesk-update-organization`.

**Validation:**

* If `salesforce-add-task` returns `success` false, report the failure for that account and continue with the rest; do not retry automatically.
* If a ticket has no `organization-name`, leave it out of the counts and say how many were left out.