Summarise Customer History Before Calls
When a CSM triggers a run for a specific account, WebRun reads the customer's HubSpot history (notes, health score, contract), scans their last 10 Zendesk tickets, and writes a clean one-page briefing into a Notion page the CSM can open seconds before the call.
How can I automatically summarise a customer's history before a call?
When a CSM triggers a run for a specific account, WebRun reads the customer's HubSpot history including notes, health score, and contract details, scans their last ten Zendesk tickets, and writes a clean one-page briefing into Notion - ready seconds before the call, so the CSM walks in fully prepared.
- One-page briefing ready in Notion before every customer call
- HubSpot notes and last ten Zendesk tickets consolidated automatically
- CSMs enter every call fully prepared - no manual research needed
Built for customer success managers · account managers · SaaS companies · enterprise sales teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.hubspot.comin a real browser with your saved login - no setup, no API keys. -
1
HubSpot - read account history and health data
hubspot.com
WebRun opens HubSpot to read account history and health data. - Open the company record and read: contract value, plan, renewal date, health score, and account owner
- Read the last 5 CRM notes and any open tasks related to the account
- Note the customer's most recently logged goals or success metrics
Done when Account health, contract details, and recent CRM notes are captured.
-
2
Zendesk - pull the last 10 support tickets
zendesk.com
WebRun opens Zendesk to pull the last 10 support tickets. - Search for tickets from the account's email domain, sorted by most recent
- Read the top 10 tickets: subject, status, and resolution or current state
- Identify any recurring themes or unresolved issues across those tickets
Done when The last 10 tickets are summarised with recurring themes identified.
-
3
Notion - write the one-page call briefing
notion.so
WebRun opens Notion to write the one-page call briefing. - Create a new Notion page in the Call Briefs database with the account name and today's date as the title
- Write sections: Account Overview, Health & Contract, Recent Support Issues, Recurring Themes, Suggested Talking Points
- Save the page and copy the link for the CSM to open before the call
Done when A complete one-page briefing is saved in Notion and ready to share.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
How does WebRun know which customer to brief?
The CSM provides the account name or email domain when triggering the run - WebRun then searches HubSpot and Zendesk for everything linked to that account.
How long does the briefing take to generate?
Typically under two minutes - fast enough to trigger it right before jumping on a call.
Can the briefing include product usage data?
Yes - connect your product analytics tool and add a step to pull login frequency and feature adoption; WebRun will include it in the overview section.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.