Account call history desk your reps open before every call

I want an account call history desk that my reps open before every customer conversation. It is a browsing surface first: a searchable list of the companies and open deals in our HubSpot, where clicking an account opens a page showing every meeting we have ever recorded with that account in Fireflies, plus a button that has a background agent write the pre-call brief.

The landing view is a searchable list of accounts. Load companies with HubSpot Search Companies (name, domain, owner, last activity) and open deals with HubSpot Search Deals filtered to deals that are not closed, showing deal name, stage, amount and close date grouped under the company they belong to. A search box filters by company name or domain. Default the list to accounts owned by the person viewing the app, with a toggle to show the whole team's accounts, and remember that choice per viewer.

Clicking an account opens the account page. The header shows the company and its open deals, with the full properties for the selected deal from HubSpot Get Deal: stage, amount, close date, next step and owner. Below that is the call timeline, showing every Fireflies meeting with anyone from that account, newest first.

Match meetings to accounts by attendee email domain. Take the domain from the HubSpot company record and call Fireflies List Transcripts with a participant filter on that domain and a date range covering roughly the last two years, newest first. Each timeline row shows the meeting date, the attendees, the duration and the Fireflies summary. Fireflies is a GraphQL API, so select the summary fields inside that same list call rather than fanning out a separate request per row. The transcripts list caps at 50 results per page.

Fireflies rate limits are tight and the app has to be built around them. Free and Pro plans allow only 50 requests per day, while Business and Enterprise get 60 per minute. So: fetch the transcript list exactly once per account view, cache it in app storage keyed by company along with the time it was fetched, show that timestamp with a manual refresh button, and reuse the cache on repeat visits the same day. Only ever call Fireflies Get Transcript for the individual meetings the agent actually reads. Never loop Get Transcript across the whole timeline, and never prefetch transcripts for accounts nobody has opened.

Each account page has a Brief me for this call button that kicks off a background agent. The agent reads the three or four most recent meetings for that account with Fireflies Get Transcript (summary, action items, attendees and sentences) plus the open deal properties from HubSpot Get Deal, then writes a pre-call brief back into the app with four sections: where we left off, commitments we made, objections that were raised and never resolved, and the questions to ask next. Every claim should name the meeting and date it came from. Show a running state on the button while the agent works, and store the finished brief against the account with the date it was generated so it survives a reload and every rep sees the same one. Regenerating replaces the current brief and keeps the previous version visible underneath.

Once a brief exists, two actions appear. File as note writes the brief onto the HubSpot record using Create Note, associated with both the company and the open deal. Post to deal channel sends it to Slack using Slack Bot Send a Message, to a channel the rep picks the first time and the app remembers for that account afterwards. After either action, show on the account page that the brief was filed or posted, including who did it and when, so two reps never file the same brief twice.

Do not store Fireflies media links. Audio and video URLs are pre-signed and expire after 24 hours, so each timeline row should link back to the meeting page in Fireflies for playback instead of holding a copy of the URL.

Handle the edge cases properly. A company with no domain on its record cannot be matched, so say that plainly and let the rep type a domain to use for the lookup. An account with no recorded meetings gets an empty timeline that explains why rather than an error. And if Fireflies returns a rate limit error, show the cached timeline with a clear note that the data comes from the last successful fetch, rather than blanking the page.