The Five CRM Updates That Now Happen the Moment Your Call Ends
Done right, one call generates five separate CRM actions:
Each action takes 3-5 minutes when done carefully. Together, a single call requires 20-30 minutes of post-call work. At 5 calls a week, that is 100-150 minutes of CRM entry per week; before meeting prep, prospecting, or anything proactive.
The rep who skips it trades short-term time for long-term pipeline chaos. The rep who does it properly loses nearly 3 hours a week to data entry.
What the Sequence Looks Like When It Runs Itself
The trigger is the transcript. When tl;dv, Gong, or Fathom finishes processing the call and the transcript becomes available, Assist picks it up immediately.
By the time the rep starts their next meeting, the previous call is fully logged.
Writing the Instruction Is All the Setup There Is
Setup works the way a rep would brief a new assistant. They type out what they need in plain English:
"After every tl;dv call, update the deal in HubSpot and draft a follow-up email."
Expertise Assist builds the automation from that description. The rep connects tl;dv, HubSpot, and Gmail. The trigger fires when a new transcript becomes available. From there, every call updates the CRM automatically, without the rep touching it, with no code, no ops ticket, and no third-party automation platform to configure.
What HubSpot Looks Like the Next Time You Open It
After finishing a call, the rep moves to the next meeting. The CRM update runs in the background.
When they check HubSpot later, the deal is already updated: call notes written, next step set, due date populated. The follow-up email draft is in Gmail, ready to send. The entire post-call sequence took under two minutes of their time: just the review and send.
What Changes for Your Manager
Every manager who depends on reps to manually update the CRM is building their forecast on partial data. When the update happens automatically after every call, the pipeline reflects actual outcomes. The forecast becomes reliable regardless of which rep is disciplined about admin and which one is not.
The specific next step and due date fields give managers visibility into what each rep has committed to doing and by when. Coaching conversations become specific rather than speculative.
What It Plugs Into
Expertise Assist integrates with the tools most AEs already have in their stack:
No new tools required. The workflow connects the stack the rep already uses.
For a broader look at how AEs reduce admin time across the full week, see How Account Executives Reduce Admin Work With AI.
Before You Run Your First Automation
Does this work with Salesforce as well as HubSpot?
Yes. Assist connects to both HubSpot and Salesforce and matches call transcripts to the correct deal in whichever CRM the team uses.
What if the transcript misses something from the call?
Assist extracts what the transcript contains and can flag gaps for rep review before pushing to the CRM. Approval gates can be added so the rep reviews the proposed update before it goes through.
Can the rep decide what gets pushed without reviewing everything manually?
Yes. The rep controls the level of automation. They can set Assist to push CRM updates automatically, to draft updates for review before pushing, or to prompt them only when a next step is unclear. The workflow matches their preference.
Does Assist create custom fields or only update existing ones?
Both. Assist can populate standard HubSpot or Salesforce fields and create custom fields; including fields like next step and next step due date that the rep defines during setup.
What call recording tools does it support?
tl;dv, Gong, and Fathom are all supported out of the box. Assist triggers on transcript availability regardless of which tool generates it.
How long does setup take?
Most reps have the tl;dv-to-HubSpot workflow live within 30 minutes of connecting their tools and describing the workflow in plain English.