Justin Butterworth’s team at Snug had meeting notes. Turning those notes into something the next salesperson could use was the difficult part.
In Pipedrive’s published customer story, the Australian property technology company describes a sales operation with two business development managers, an onboarding specialist and a founder who joins larger deals. Shared documents created duplicated work and missed details. General-purpose AI note-taking still left people deciding what belonged in the CRM.
The case describes Pipedrive Nova’s September 2026 launch and reports savings of up to an hour per sales meeting. That is a vendor-reported customer result, not a forecast for another business. The useful lesson is the operational problem: a conversation can be recorded while the next person still lacks the context needed to act.
A small company can test that problem before expanding its automation. Choose one customer request, hand it to another colleague and check whether the promised next step survives.
Start With the Promise the Customer Heard
A pipeline stage such as “contacted” says little about the next obligation. The customer may be waiting for a quote, a demonstration, an answer about compatibility or a call at an agreed time.
Record the commitment in plain language. Include what the customer requested, what the business promised and where the original conversation can be found. Separate the customer’s preferred timing from an internal reminder. “Call after 2 p.m.” and “prepare the quote before lunch” belong to different actions.
The receiving colleague should be able to understand the obligation without asking the customer to repeat it. A short summary helps, but the original message matters when timing, scope or wording is uncertain.
Use a Test Request That Is Easy to Get Wrong
Create an internal test inquiry: “Please send a quote tomorrow for five users. I am unavailable before 2 p.m., and I would like the quote by email.” Use an address controlled by the business and keep the record clearly labeled as a test.
Ask one colleague to handle the inquiry and another to take over the follow-up. The exercise should produce a record that looks like this:
|
Customer request |
Quote for five users, sent by email |
|---|---|
|
Customer constraint |
No call before 2 p.m.; confirm the relevant time zone |
|
Next action |
Prepare and email the quote tomorrow |
|
Accountable owner |
The colleague who has accepted the follow-up |
|
Evidence |
Link to the test conversation and any agreed changes |
The second colleague should explain the next action using the record alone. If they need a separate chat to understand what was promised, identify the missing information and improve the record.
Pay particular attention to conflicting instructions. The customer requested an emailed quote; the availability note does not automatically create permission or a need to call. A workflow that turns every inquiry into a phone task can preserve the data while changing the customer’s request.
Transfer the Work as Well as the Contact
Changing a contact’s owner can leave related work with the previous colleague. Check the quote task, scheduled callback and any queued message separately.
Use an explicit acceptance step. The receiving person confirms responsibility and the due time, while the previous owner remains accountable until that confirmation is recorded. Name a backup for absence or workload problems. A notification to several people gives visibility, but someone still needs to accept the action.
This is especially useful when sales and support share an inbox. A technical question may need an answer before a salesperson follows up. Keep those dependencies visible so that the customer receives a coherent response instead of separate messages from people working from different assumptions.
Try the Awkward Cases Before Adding More Automation
A successful first test provides a starting point. Repeat it with a few common disruptions:
- The owner is absent: verify that the backup receives the request, context and deadline.
- The same person switches from chat to email: check whether the team recognizes the existing conversation.
- The customer changes the requested time: update the active task and inspect any previously queued reminder.
- A colleague starts a personal reply: check whether another automated message could still be sent.
- The customer withdraws the request: close the follow-up work as well as updating the contact’s status.
Record each failure as a specific observation. “The callback remained assigned to the absent employee” gives the team something to fix. “The CRM needs better automation” leaves the problem too broad to act on.
Choose Software by Replaying the Handoff
When evaluating CRM software, run the same exercise with two people. Check whether the second person can find the original conversation, identify the current owner and understand the next obligation without rebuilding the history.
Then examine how the software handles corrections. A useful summary can still omit a constraint or suggest the wrong next action. Someone needs a straightforward way to inspect the source, correct the record and resolve conflicting tasks.
Use the test to decide which capabilities matter for the team: conversation history, task ownership, due times, reassignment or control over automated messages. A feature earns its place when it solves an observed problem in the workflow.
Expand From a Handoff the Team Trusts
Begin with one channel and one type of inquiry. Keep the initial process small enough that colleagues can explain how it works and notice when it fails.
During rollout, review unresolved commitments together: requests without an accepted owner, tasks past their agreed time and conversations where the next action is unclear. These checks give the team a practical way to catch work that might otherwise disappear between inboxes.
Add another channel or automation after correcting the failures in the first workflow. Use evidence from the team’s own work to decide which automation is ready to expand.
Choose one inquiry that needs attention today. Give the next colleague the customer’s request, the original context and an agreed action. Then ask them to explain what they will do. That small exchange gives the team a concrete place to begin improving its follow-up process.