Skip down to the research record

CRM logging: 4 habits to keep deal records current

Quota Forecast Editorial Team · Published · 9 min read

Four CRM logging habits help keep deal records current: follow new Leads, log calls and SMS, create Leads from email, and test Kanban.

Key takeaways

  • Check auto-follow for new Leads before the next forecast call.
  • Measure calls and SMS messages missing from deal records each week.
  • Write a one-sentence rule for which inbound emails become Leads.
  • Test the Kanban view for Leads against your pre-call list.

The habits draw on EspoCRM's user guide and Copper's public resource pages.

Why deal records drift

A deal record is only as current as its most recent update. The updates most at risk are the ones that depend on someone typing them after the fact. Copper's resource page on media companies makes the same point in its own words: according to Copper, "If logging a client call feels like homework, your team will quietly go back to Gmail, spreadsheets, and a file called “real_pipeline_FINAL_v7.xlsx.”"

That line is a vendor's warning rather than a measured finding, so treat it as a prompt to check your own team, not as proof of how your team behaves.

Two kinds of drift are worth separating. The first is missing information, such as a call that never reached the record. The second is outdated information, such as a stage that no longer matches the last conversation. Each needs a different check. The habits below mostly target the first kind, because each one is about getting information into the record.

Start by listing every place a deal update can land: the CRM, the shared inbox, call notes, and any spreadsheet the team still keeps. Mark each place as current or behind. The places marked behind show where the record and the real pipeline have separated, and the four habits below each touch one of them.

Pick a handful of deals from the coming forecast and walk each one through the same list. Note where the most recent update for each deal lives. A deal whose latest update sits only in a call note or an inbox is a deal whose record is likely to lag behind.

Before the call: follow new leads

The EspoCRM documentation gives the purpose of the setting: according to EspoCRM, "To prevent overlooking of new Leads, users can add the Lead entity type to the Global Auto-follow list in Preferences." Confirm the behavior in your own system before relying on it.

Open Preferences and look at the Global Auto-follow list. If the Lead entity type is not on that list, add it. Then write the date of the change in the team's shared notes, so the next person who reviews the setup can see when it changed.

If the Lead entity type is already on the list, leave the setting as it is and move straight to the review of older Leads described below.

Before each forecast call, compare the Leads created since the last call with the Leads that have a written next step. Any Lead without a next step goes on the agenda for that call, so the call covers it rather than leaving it for a later cleanup. Build the list with three columns: the Lead name, the person who created it, and whether a next step is written down.

Because that wording speaks about new Leads, review the Leads created before the change by hand. Ask the person who owns each one to state the next step in a single sentence, and record that sentence on the Lead itself rather than in a private note.

Walk it from the oldest unreviewed Lead to the newest, so the items that have waited longest get the first discussion time.

For a companion list of signals to check before the call, see Stale deal signals to check before the call.

During the week: check call and SMS records

Copper's page, according to Copper, says: "Log calls and SMS automatically so accounts are always up to date." That statement describes Copper's own product. Test it in your own system before assuming another CRM does the same.

Each week, list the calls and SMS messages from the past week that do not appear on the matching deal record. Those are the items still depending on manual entry, and the list shows the size of that gap. Start with the most recent days, because those calls are the easiest to recall accurately.

Keep calls and SMS messages on separate lines of the list. A missed text and a missed call can have different causes, and mixing them makes the list harder to act on. Write the cause in a few words beside each line, such as a message sent outside the team's usual tools.

When a call has to be logged by hand, write what was agreed in one sentence, so the next reader does not have to contact the person who made the call. Record the deal name, the date, and the person who made the call. Add the missing items to the deal record before the next forecast call.

Spot-check a few entries that were logged automatically each week against the deal they were attached to. Note any entry that appears on a deal it does not belong to, and fix it on the same day you find it.

Keep the list in the same place every week so the comparison stays consistent. A list split across several tools is hard to compare from one week to the next. If the same kinds of items keep appearing, the setup or the routine probably needs a change, and that question belongs with whoever runs the CRM.

For a weekly comparison setup, see Weekly deal review filters across sales systems.

Illustrative example: check missing calls

Suppose you review 10 calls from the past week. Some appear on the matching deal records; others appear only in call notes. List the missing calls separately from missing SMS messages, add the agreed next steps to the matching records, and check the same list before the forecast call.

Create leads from email

The EspoCRM page, according to EspoCRM, says: "Users can also create a Lead from an Email – from the top-right dropdown menu." Check the steps in your own system before using this route.

Decide which inbound emails should become Leads. A first reply from a prospect the team has not spoken to before is a clear case. An email from an existing account is usually a question for that account's deal rather than a new Lead. Write the rule in one sentence the whole team can read, such as a first reply from a new prospect becomes a Lead.

When a message from a new prospect arrives, check that the sender is outside the team and that the company name appears in the email. Then use the top-right dropdown menu in EspoCRM and create the Lead as soon as the message is read. Once the Lead exists, record its next step in the same one-sentence format used on the pre-call list.

Once the Lead exists, paste the subject line of the email into the Lead's own record, so the origin of the Lead can be traced later.

Some messages are harder to classify, such as a forwarded email from a colleague that contains a prospect's question. Decide in advance who rules on borderline cases, and have that person check each week, so the same prospect is not entered twice.

Review the inbound emails the team received last week and note which ones started a conversation with a new prospect. Those are the cases the rule is meant to cover, and they show whether the rule is clear enough to repeat.

For the rules on which deal a seller's email should be logged to, see Log seller emails to the right deal.

Use the Kanban view

The EspoCRM page, according to EspoCRM, says: "It may be useful to enable the Kanban view for Leads." The wording is a hedge, so treat the view as an option to test.

Enable the Kanban view for Leads for a trial period. Limit the trial to the Leads already on the pre-call list, so the comparison stays manageable. For each Lead, ask three questions: is it in the right place, does it have a written next step, and does the record match the last call?

Choose one person to run the trial. That person checks the pre-call Leads against the view at the start of each week and brings the results to the forecast call, so the notes come from one source.

Write the decision rule down before the trial starts. Note what would make the team keep the view and what would make it stop, so the outcome is judged against a standard agreed beforehand rather than an impression formed afterwards.

Keep two short lists during the trial: Leads the view made easier to check, and Leads that were harder to find or check. Give each Lead one line and a reason written in a few words.

Record notes during the trial rather than from memory at the end. Note what the team saw and what it still had to fix by hand. Those notes are more useful for the next forecast call than a general impression of the view.

At the end of the trial, bring the decision rule and both lists to the forecast call, and decide whether the view stays on for Leads. If it stays on, name the person who opens it and the day of the week they do so.

What to keep on file

Keep a short record of which habits are switched on in your system, who checked each one, and the date of the check. Store the record in one place that the revenue lead can open before a forecast call, and keep the pre-call list beside it.

Review the record before each forecast call and update any habit that has changed. A habit checked some time ago may no longer match the current setup, so the date of the check matters as much as the result.

Write setting names exactly as the vendor documentation words them, such as Global Auto-follow list and Kanban view, so a later reviewer can find the same setting in the documentation.

Today, check the Global Auto-follow list in Preferences and add the Lead entity type if it is missing.

FAQ

Can calls be logged automatically?

Yes, Copper offers automatic call and SMS logging. For another system, look for the equivalent setting in its documentation and record what you find, with the date you checked.

How do I follow every new lead?

In EspoCRM, use the auto-follow setting described above. After making the change, check a few new Leads the following week to confirm it works in your own account.

Can I create a lead from an email?

Yes, in EspoCRM. Apply the one-sentence rule for which emails qualify first, so the Lead comes from a message that meets it.

Is there a Kanban view for Leads?

Yes, EspoCRM offers a Kanban view for Leads. Run the trial described above and decide from the written notes whether to keep it.

Sources