Picture an MSP account executive’s Tuesday.
A discovery call at 9 with a prospect whose current provider keeps missing tickets. A QBR at 11 where the client mentions they’re opening a second office. A renewal call at 2 where the agreement comes up for its annual review. A scoping call at 4 for a Microsoft 365 migration.
By 5 o’clock she has four calls’ worth of notes in her head and one hour left in the day. Which ones get logged?
Honestly? Maybe one. Probably the last one.
That’s how a CRM turns into a record of the calls someone had time to log. Not the calls that happened.
The fix isn’t a sterner reminder in the Monday meeting. It’s taking the logging off the AE and making deal stages move on events instead of on memory. That’s what this post covers. For the short version, see how it works on our page for IT MSPs.
Why do MSP sales calls go unlogged?
Because logging happens at the worst possible time. It comes right after the call, when the next call is already starting.
And nothing breaks today if it’s skipped. The deal still exists. The client doesn’t know. The cost shows up weeks later, when a forecast is wrong or a promise from the call never gets kept.
MSPs have it harder than most because the calls are so different. A discovery call is about pain and the current environment. A QBR is about service performance and what the client needs next. A renewal call is about risk. Each one should leave something different on the record, and a rep in a hurry logs them all as “Good call.”
What should a call log hold?
A useful call log is short. It answers five questions, and the last two matter most.
| Question | Example from a discovery call |
|---|---|
| Who was on the call? | The office manager and the owner |
| What do they need, in their words? | ”Our backups have never been tested” |
| What did you promise? | A network assessment proposal by Thursday |
| What’s the next step, and when? | The assessment walkthrough on the 14th at 10 AM |
| What changed on the deal? | The stage moves to “Assessment” and the close date is set |
A call log without a next step is a diary entry. A call log without the deal change leaves the pipeline wrong even when the note is perfect.
What does HubSpot automate on its own?
HubSpot logs some activity on records for you and gives you a quick way to log the rest by hand. Its guide to logging activities on a record shows the manual flow. Pick the call outcome, add the note, and create a follow-up task in the same step. The default outcomes are Busy, Connected, Left live message, Left voicemail, No answer, and Wrong number.
On the pipeline side, HubSpot’s deal pipeline automation can create and assign a task when a deal enters a stage, on Sales Hub Starter, Professional, and Enterprise.
Both are worth using. Both depend on a person typing the note or moving the deal first. A rule can act on a field. It can’t listen to a call and decide the deal just moved.
Tie every stage to an event
Here’s the part most teams skip, and it’s the one that makes automation possible.
If a stage means “the AE feels good about it,” no system can move it. If a stage means “this specific thing happened,” something can see it happen and move the deal.
Here’s a simple MSP pipeline written that way:
| Stage | The deal moves here when |
|---|---|
| Discovery booked | A meeting with the prospect is on the calendar |
| Discovery held | The call happened and the note is logged |
| Assessment | A network or security assessment is scheduled |
| Proposal sent | The proposal email goes out |
| Verbal | The prospect says yes in writing |
| Closed won | The agreement is signed |
Your stages will be different. The rule is the same. Every stage should have an exit you could point to in an email, a calendar, or a transcript.
Once that’s true, logging the event and updating the stage become the same job.
How to automate call logging, step by step
- Capture the call where it already happens. Use the recorder or phone system your team already runs. If you’re on Fathom for video calls or Dialpad for phone, the transcript already exists.
- Turn the transcript into a note. Answer the five questions from the table above and skip the play-by-play.
- Draft the deal update with the note. Stage, amount, and close date, based on the event that just happened.
- Approve it before it lands. Read the note and the stage change, fix anything that’s off, and send it to the CRM.
- Let the easy parts run on their own. Once the notes are reliably right, let them log without asking. Keep stage changes waiting for your OK longer.
Steps 2 and 3 are the admin nobody wants. That’s the part to hand off.
What Go Fig does after a call
Go Fig is a sales admin that works in HubSpot or Salesforce. After a call, it drafts the note, the next step, and the deal update, including the stage and the amount. You approve it and it lands on the right record. Our hub covers this under calls and deal stages.
It works from what’s already there. In HubSpot, that’s the calls, emails, meetings, notes, and tasks logged against each deal. In Salesforce, it reads the tasks and meetings on each account and opportunity. If your team records calls in Fathom or takes them on Dialpad, Go Fig reads the transcript and drafts the CRM note from it. Meeting notes to CRM is one of the ready-made skills.
A few honest details:
- It only reads from Fathom and Dialpad. It never starts a recording or places a call.
- Timing follows your sync. Records come in once a day by default, at a time your team sets. Larger plans update every hour or every 15 minutes. So the draft shows up after the next sync, not the second you hang up.
- Nothing lands without your OK at first. Drafts wait in your Feed. You can approve them there, with the Approve and Reject buttons in Slack, or from email.
- Writing back is its own switch. An admin turns it on for your company and then for each tool. Every change Go Fig makes is recorded in a log your team can review.
Once you trust it, let logging a note run on its own and keep stage changes waiting for your OK. You choose, one action at a time.
What about QBR notes?
QBRs deserve their own mention, because they’re where expansion starts.
When a client mentions a new office, an aging server, or a compliance deadline, that’s a project deal waiting to be opened. Log the QBR as a meeting on the company. If something real came up, open the expansion deal right then with a next step on it.
The service numbers you showed in the QBR, like ticket volume and response times, stay in your PSA. Go Fig doesn’t connect to ConnectWise, Autotask, or HaloPSA. It handles the sales side of the conversation in the CRM. More on that split under your PSA stays your PSA.
The goal is a CRM that matches what happened
I’ll say what every sales leader already knows. The pipeline review is only as good as the last time someone updated the CRM.
When calls log themselves and stages move on real events, that review gets shorter and more honest. Your AEs stop retyping what they already said out loud. And the forecast starts reflecting the calls that happened, not the ones someone remembered.
See it on your own calls
A solutions engineer can connect your CRM and your call recorder and show you the drafts on your own deals.
Or start with a gut check on your sales system: Take the Agent Readiness Assessment →