Why do salespeople stop updating the CRM?

Usually because updating it costs them time and gives nothing back. Reduce typing by capturing leads from email aliases and web forms, and make sure the pipeline view helps them plan their own day.

Can Odoo show me which leads nobody has touched?

Yes, if the team uses activities. The documented unattended leads report filters the Pipeline Analysis for leads with due or past due activities, and it cannot be complete if activities are not used.

Should I make every CRM field required?

I would not. Odoo's own documentation keeps the lost reason optional while recommending it. Require only what a manager cannot do without, and ask for it at the moment the person already has it in front of them.

Getting Your Team to Actually Use the Odoo CRM

Short answer: people use a CRM when it is quicker than the alternative and when it helps them, not only their manager. In Odoo 19 that means letting leads arrive by themselves (email aliases, web forms), keeping activities as the one habit you ask for, and building reports that the salespeople themselves would open. Training and targets come after those, not instead of them.

Applies to

Odoo version: 19. I compared the relevant CRM documentation pages with the 20.0 versions and the wording I rely on is the same.
Edition: Community and Enterprise. The crm module is in the open-source 19.0 repository. The web contact form needs the Website app.
Apps: CRM, with Website and Discuss (activities) mentioned where relevant.

Why does the CRM go quiet after the first month?

Think of it as a cost problem. Each field you ask for is a small tax on the person typing. The benefit of the data usually lands with someone else: a manager, finance, the forecast.

When the tax is higher than the visible benefit, people move the real conversation to their inbox, phone or a private spreadsheet. The CRM then holds stale rows, and managers trust it less, which gives salespeople even less reason to update it.

So the fix is mostly about reducing the tax and returning some value quickly. Mandates alone will not do it.

How do I reduce the typing?

Let the system create records for the team.

Each sales team can have its own email alias under CRM ‣ Configuration ‣ Sales Teams. The Accept Emails From field controls who may write to it. A message sent there becomes a lead or opportunity, with the subject as the title and the sender in the email field, and the email itself lands in the chatter.

For the website, the Contact Us form can be set to Create an Opportunity and pointed at a sales team. If the Leads setting is on, it creates a lead instead.

From a developer’s view, both are the same idea: the data enters through a door you configured once, so nobody has to remember to copy it across.

Which habit should I ask for?

One, and I would pick activities.

Odoo’s documentation says a lead’s activity should be marked Done as soon as the interaction happens, so the next one can be scheduled. That single habit powers a lot: the overdue indicators on cards, the reminder emails, and the unattended leads report.

You can tune activities without code. Under CRM ‣ Configuration ‣ Activity Types you can set a default user, a default deadline and a chaining type, so finishing one activity suggests or triggers the next. CRM ‣ Configuration ‣ Activity Plans bundles a sequence for a common case.

A small, honest pipeline with every deal holding a dated next step beats a perfect form with half the fields blank.

What should managers do with the data?

Read it with the team, and be consistent.

The documented unattended leads report (in CRM ‣ Reporting ‣ Pipeline) filters for active leads with a salesperson and an activity due today or earlier. It only works if people log activities, which is a good reason to protect that habit.

If a manager uses the report to punish, people will tidy the data right before the review and stop trusting the screen the rest of the time. If they use it to clear blockers, it becomes a normal part of the week.

On the stage side, the 19.0 crm.stage model has a Days to rot setting that highlights opportunities not updated for that many days. Treat it as a prompt for a conversation, not a score.

When it fits and when it doesn’t

All of this fits a team that sells through repeatable conversations: enquiries by email, a website form, a few follow-ups.

It fits less well if most of the real selling is a long relationship held by one senior person who dislikes screens. Forcing the full pipeline on them first will backfire. I would start by capturing their meetings and next steps with minimal fields, and widen later.

Worked example: a small architecture practice

The director holds every prospect in memory. Two associates answer the shared inbox and forward things as they remember.

A sensible first month: create a sales team with an email alias that the shared inbox forwards to, point the website enquiry form at Create an Opportunity, and agree one rule. Every open opportunity has a dated activity. Review the pipeline together once a week using the Kanban view, nothing else.

Only after that works, add stages, expected revenue and lost reasons.

Common mistakes

Adding custom fields before people use the standard ones.
Making the CRM the place for “reporting” only.
Importing five years of old contacts as live leads, so the pipeline starts as noise.
Measuring adoption by logins. Count dated next steps instead.

Pick a platform before you pick a rollout plan, and the earlier Odoo vs Salesforce vs Dynamics checklist covers that part. For the wider split, see ERP vs CRM. There is a plainer, non-technical version of this advice on sajjalbajaj.in.

Official references

How this article was checked: I read the 19.0 documentation pages above, compared them with 20.0, and read the crm.stage model in the 19.0 source for the Days to rot field. Menu names come from the documentation. I did not run a live database.

If you are planning a CRM rollout for a small team, see what I work with and get in touch.