Rate the support health of any Zendesk customer

**Objective:** Review the support relationship with organization `{organization-name}` over the last `{lookback-days}` days (default 90) and rate its health.

**Step 1: Find the organization**

Call `zendesk-get-organization` with name `{organization-name}`. If nothing matches, retry with the name through `zendesk-get-organization-member` using organization-name.contains to find the closest organization-name values, list them and stop. If more than one organization matches, list them with organization-id and domain-names and stop.

**Step 2: Who they are**

Call `zendesk-get-organization-member` with the organization-id to list the members (user-name, user-email). Then call `zendesk-get-user` with organization-name set to the confirmed name to get role, active, suspended, last-login-date and open-tickets for each person.

**Step 3: Their tickets**

Call `zendesk-get-ticket` with organization-name set to the confirmed name and created.from set to today minus `{lookback-days}` days (YYYY-MM-DD), max-records 500. Count by status, priority and type, and find the oldest unsolved ticket.

**Step 4: Their satisfaction**

For up to 10 members with the most tickets, call `zendesk-get-satisfaction-rating` with requester-id set to the member's user-id and created.from set to the same date. Count good and bad scores and keep the comment on each bad one.

**Step 5: Report**

1. Account header: name, organization-id, domain-names, group-name, tags, created-date.
2. People: member count, how many are active, anyone suspended, and the three heaviest requesters.
3. Tickets: volume by status and priority, the unsolved list (ticket-id, subject, priority, age), and recurring subjects.
4. Satisfaction: good vs bad, and the bad-rating comments.
5. A health rating (Healthy, Watch, At risk) with the two or three facts that decide it, and suggested follow-ups.

**Rules & Guidelines:**

* This prompt is read-only. Do NOT call `zendesk-update-organization`, `zendesk-update-user`, `zendesk-update-ticket`, `zendesk-add-organization-member` or any other add, update or make tool.
* Treat At risk as needing evidence: several bad ratings, urgent tickets left unsolved, or a rising volume. Do not rate on volume alone.

**Validation:**

* If the organization has no tickets in the period, say so and report people only.
* If satisfaction returns nothing, say ratings are not collected or none were given, rather than treating it as neutral.