See a Salesforce case with the customer's 2Checkout billing

**Objective:** For Salesforce case `{case-number}`, collect the customer billing context from 2Checkout so the agent can answer without opening a second system.

This prompt needs both servers connected: salesforce (tools whose names start with salesforce-) and 2checkout (tools whose names start with 2checkout-).

**Step 1: Read the case**

Call `salesforce-get-case` (salesforce server) with `case-number` set to `{case-number}`. If it returns nothing, stop and say the case was not found. Note the subject, status, priority and the contact email.

**Step 2: Find the customer in 2Checkout**

Call `2checkout-get-customer` (2checkout server) with `email` set to the case contact email. If none is found, report the case as having no 2Checkout customer and stop after Step 4. If several are found, list them and use the one whose name matches the case contact; if still unclear, stop and ask.

**Step 3: Pull the billing records**

Call `2checkout-get-subscription` (2checkout server) with `customer-reference` set to the customer's reference. For each subscription, call `2checkout-get-subscriptionpayment` (2checkout server) with `subscription-reference`. If `{order-lookup}` is yes, also call `2checkout-get-order` (2checkout server) with `billing-last-name` set to the customer's last name.

**Step 4: Report**

Show the case summary, then the customer, then each subscription with status, expiration date and its latest payments, then any orders. Finish with one or two sentences on what in the billing data may explain the case, for example a failed or declined payment.

**Rules & Guidelines:**

* Salesforce tools are on the salesforce server; 2Checkout tools are on the 2checkout server.
* Read-only. Never call `salesforce-add-case`, `salesforce-update-case` or any other write tool on either server.

**Validation:**

* Say plainly when the data does not explain the case; do not speculate beyond it.
* Treat `{order-lookup}` as no when it is empty.