Look up any customer's support, billing and CRM in one page

Build an internal customer lookup app that our account managers open before a renewal call or a check in. I type in a customer email address and get one page combining that customer's entire support history with their billing status and their CRM status. Help Scout cannot show me this today because it displays conversation threads but no per customer rollup.

The app is a single page with a search box at the top. I enter an email address and the page loads three sections: Support, Billing and CRM. Above them, show a header with the customer's name, their email, and three small match indicators saying whether a matching record was found in Help Scout, Stripe and HubSpot.

The Support section is built from Help Scout. Use List Conversations filtered to that customer's email address to pull their conversation history. Note that the Help Scout Mailbox API exposes no standalone per customer report operation, so the rollup has to be computed in the handler from that conversation list rather than fetched ready made. Show total conversations, how many are still open, their most common tags, and the most recent subjects with each one's status and date. Also show how their conversation volume has trended over the last several months, bucketed by month, so I can see at a glance whether their support load is climbing. Let me click a recent conversation to pull its detail with Get Conversation and List Threads and read the actual messages inline.

The Billing section is built from Stripe. Find the customer with Search Customers, which uses Stripe's search query syntax, so the email lookup is a query string. Then use List Subscriptions and List Invoices for that customer id. Show their plan, their subscription status, and call out any unpaid or failed invoices with amount and date. Unpaid and failed invoices should be visually prominent, since that is the thing most likely to matter on a renewal call.

The CRM section is built from HubSpot. Use Search Companies to find the company behind that customer and Search Deals to find their open deals. Show the account owner and each open deal with its stage, amount and close date.

Match customers across the three systems by email address. When no Stripe customer or no HubSpot company is found for that email, say so explicitly in that section, for example "No Stripe customer found for this email", rather than silently rendering an empty section. I need to be able to tell the difference between a customer with no open deals and a customer who was never added to the CRM.

Add a "Write account brief" button that kicks off a background agent for the customer currently on screen. The agent reads the actual conversation threads using Get Conversation and List Threads across their recent conversations, alongside the billing context from Stripe and the CRM context from HubSpot, and writes a short brief back into the app. The brief covers their top recurring issues, whether their tone is trending unhappy over time, and any risk flags worth raising on the call, such as repeated unresolved issues, failed payments, or a renewal deal sitting open while support volume spikes.

When the agent finishes, the brief renders on that customer's page. Give me an option to also post that brief as an internal note on their most recent Help Scout conversation using Create Note, so the support team sees it too. Internal notes are team only and never reach the customer, and the UI should make that clear. Do not post the note automatically; post only when I ask for it.

Save each generated brief against the customer's email along with the timestamp and who ran it, so when anyone on the team opens that customer again they see the most recent brief and when it was written, with the option to regenerate.

A few details to get right. Help Scout list responses are paginated, so page through the customer's conversations rather than reading only the first page when computing the rollup and the monthly trend. Help Scout is rate limited per account, so when the agent reads threads, scope it to the most recent conversations rather than every thread ever written. Load each section independently so a slow Stripe or HubSpot lookup does not block the support rollup from rendering.