Most Dynamics 365 sales teams have an unwritten dollar line. Above it, quotes get a phone call. Below it, they wait. Nobody decided that on purpose. It just happens, because a ten-minute call about a $2,000 quote never feels worth it, today or tomorrow.
The usual fix is a rule: every open quote gets touched every two weeks. It fails for the same reason the calls do. When following up costs more than the quote seems worth, people make a sensible choice and skip it.
Add Up What You're Skipping
Here is a test worth running. Pull every open quote under $5,000 with no activity in the last thirty days, and group them by account. Then total each account. At a manufacturer we work with, a single customer could carry a dozen quotes of about $3,000 each, $36,000 that nobody had asked about, because no individual quote ever looked big enough to call on.
Count the Email Steps
Email is the obvious answer, so count what it takes in your system. Open the contact, find every open quote, copy the numbers and amounts, add them up, attach the PDFs, work out who else to copy, send, then log the follow-up on each quote separately. If that's the path, the problem isn't discipline. The CRM only makes one kind of follow-up easy, and it's the one that doesn't scale down.
What Fixed It
At P2 Automation we added an email routine to the follow-up screen we had already built for this team. An Email button next to each contact opens a builder that lists that contact's open quotes with amounts and a total, rewrites the message as quotes are clicked in or out, and puts the company's other active contacts one click from the CC line. Create Draft produces a standard Dynamics 365 email, sent from the rep's own Outlook mailbox. When it goes, every quote on it is marked as followed up. The email is the activity, so there is nothing left to log.
When a routine job isn't getting done, make it cheaper before you make it mandatory.
Read the full case study, with screenshots:
See more about how P2 Automation works with Dynamics 365 teams:
Or tell us the process your team hates most - twenty minutes is usually enough to know whether a My Day view would fix it, and if it wouldn't:

