Phone & routing
Document live numbers, call routing, after-hours handling, recordings and transfer destinations. Number migration must be separately planned.
OPERATIONS / INTEGRATION READINESS
Your systems first.
Automation second.
Before enabling an AI workflow, establish where each customer record lives, what data can move, what system controls the calendar, and who owns exceptions.
INTEGRATION INVENTORY
Map the customer journey
to real systems.
CRM & customer history
Confirm authoritative records, duplicates, contact permissions, job IDs and how records will be reconciled.
Calendar & dispatch
Identify which application owns real availability, territories, travel buffers and technician assignments.
Quotes & job stages
Define how estimates are created, approved, sold, canceled, and excluded from automated follow-up.
Invoices & payment records
Define whether “won” means booked, sold, invoiced or collected. Use transaction identifiers to support reconciliation.
Access & consent
Set minimum permissions, opt-out handling, data retention, human ownership and permitted actions.
PRACTICAL RULE
We check compatibility.
We don’t assume it.
Field-service tools, scheduling products and accounting systems vary by plan and enabled API. An integration is proposed only after the actual client's environment and permitted access are checked.
Client readiness checklist ↗Bring to the Revenue Review
- CRM and field-service software names
- Current phone and scheduling setup
- Sample lead, estimate and job lifecycle
- Data permissions and access owner
- Existing automation and failure points
- Reporting definitions and source-of-truth system