Quotes and callbacks disappear when commercial state lives in the job system, the CRM, or chat — but not on the company. Keep Called / Visited / next step on the account across routes so follow-up survives the next run.
The gap teams describe when they search for lost quotes
Territory managers and ops leaders search quotes lost between CRM and field service or field service CRM disconnected when revenue numbers do not match activity stories. Reps were busy. Jobs got done. Pipeline still went quiet.
The gap is usually not malicious neglect. It is architecture: field service software optimizes work orders, dispatch, and invoicing. CRM optimizes entered opportunities. Quotes and callbacks often live in neither — Excel, email, text, or a notepad between visits.
What field service software is built to track
- Work orders, dispatch, technician time, parts, and completion.
- Invoicing and payment for executed service.
- Asset history at a customer site after they are a customer.
- Sometimes on-site quotes that sync back — if integration is configured and used.
What CRM is built to track
- Opportunities someone created with stage, amount, and owner.
- Activities logged by reps who use the CRM consistently.
- Forecast roll-ups from entered deals — not from every quote sent in the field.
Where quotes actually go missing
Rep visits account, prices work in a spreadsheet template, emails PDF from personal inbox — no opportunity stage updated. Manager asks for pipeline status; the quote does not appear because it was never an “opportunity,” only a file.
Or: quote logged in CRM as one amount, revised verbally on site, final version only in field service or email — systems disagree, follow-up stops because nobody trusts the number.
Teams searching sales quote not in CRM or why sales quotes go missing are usually describing quotes that exist commercially but not in the system of record the manager reads.
Where callbacks go missing
“Call me Thursday” lands in WhatsApp, a voice memo, or a sticky note. The CRM still shows last activity from six weeks ago. Field service shows a completed PM visit — unrelated to the sales callback.
Searches for callback lost WhatsApp CRM spike in teams where chat replaced the company record. Chat is fine for speed; without logging outcome and next action on the account, the callback did not happen as far as pipeline is concerned.
Why integration alone does not fix territory pipeline
Bidirectional CRM–field service integration helps once an account is a customer and quotes flow into work orders. It does not automatically map the whole licensed market, untouched accounts, or dormant quotes on companies that never became work orders.
Integration solves sync between systems of record. Territory conversion also requires one commercial thread per company — quote sent, revision, objection, revisit date — whether or not a job exists yet.
The company record as commercial system of record
Instead of asking “is it in CRM or field service?”, ask “is it on the company?” Every account worth working should show: last visit, quote status, open callback, owner, next action.
Field service can remain the execution system. CRM can remain the opportunity system for complex deals. The territory view holds the commercial narrative across both — plus the accounts that never entered either.
A minimum quote-and-callback discipline
- Every quote gets a company, date, amount band, version, and follow-up date — same day it is sent.
- Every callback promise gets owner and date — not only a chat message.
- Revised quotes supersede prior versions on the account; do not leave three conflicting numbers in three tools.
- Weekly queue: quotes open >14 days, callbacks due this week, visits without next step.
- Park or disqualify honestly — open loops inflate pipeline and hide real work.
Contractor and trade-specific patterns
Supplier and distributor reps selling into HVAC, plumbing, electrical, and construction see repeat patterns: quote for equipment bundle stalls while owner waits on job award; maintenance contract conversation pauses at season boundary; field visit identifies upsell but job ticket closes without sales follow-up.
In each case, the fix is the same: attach the commercial next step to the company before the rep drives away — not a batch upload at month end.
Frequently asked questions
Should we replace field service software? No. Use it for jobs and dispatch. Add territory-level commercial tracking for quotes and follow-ups across accounts — including ones not yet customers.
Do we need expensive CRM–FSM integration? Helpful for order flow after win. It does not replace logging quotes and callbacks on accounts still in pursuit.
Who owns the fix — sales or operations? The territory manager or owner-manager owns commercial continuity on the company. Systems support; they do not substitute for that discipline.
What is the first step this week? Export open quotes from email and Excel, match to companies, set follow-up dates on each account, run one manager review of overdue callbacks.