Solar CRM and job management: agree the installation handover

Which native capabilities should you check first?

Sources: [3][5][4]

These tools already cover sales-related work. Test the specific solar handover you need before buying another layer.

Agree where each record belongs

• Customer and site: keep the linking reference and verify the address.
• Offer: identify the accepted version and its approved scope.
• Field work: name the scheduling and technician-evidence system.
• Payments: retain the source confirming collection and prevent duplicate billing.

Sources: [6][7][1]

Example: a linked job is not a second invoice

Illustrative workflow: an accepted ArcSolar job is associated with a ServiceM8 record. Both products offer financial actions. Before anyone issues an invoice, check which system owns billing and which quote and payment evidence already exist. A link or a synced status alone does not establish that an invoice was paid.

Sources: [1]

What does ArcSolar’s connection establish?

ArcSolar documents matching and associating ServiceM8 work when the integration is available to the organisation. Verify the account, job reference and observation time. Do not assume an AroFlo or Simpro connection, automatic job creation or every-field sync from a general integration claim. ArcSolar also provides its own project and field workflows.

Sources: [1][2]

Walk the accepted job into operations

Use one fictional accepted offer and an unresolved site item. In an ArcSolar demo, trace the scope, payment state and next owner through the handover.

• Check installation readiness →
• Use the integration test sheet →