Skip to content
Back to Business Operations
Business Operations

Solar Field-Team CRM Acceptance Tests: Five Mobile and Site Scripts

Run five solar field-team CRM acceptance tests for site identity, interrupted capture, permissions, design handoffs and persistent contact preferences.

Arshia Jahangiri
3 min

Table of contents

A solar field-team CRM acceptance test should let the intended users complete site tasks on their normal devices and permissions. A CRM demonstration should include the people who collect site information and hand projects to delivery. A feature shown on a desktop may behave differently on a phone, without connectivity or under restricted permissions.

1. One record for the right property and customer

Test a household with more than one contact and a customer with more than one property. Confirm that notes, appointments and quotations attach to the right project. Avoid using a single address field to represent both billing and installation locations.

2. Mobile capture that handles interruptions

Create a field note, attach a permitted photograph and update the next action. Test poor connectivity, duplicate uploads and conflicting edits. Ask what is stored on the device and how it is protected if the phone is lost.

3. Controlled document access

Check that a field user can see the current scope and necessary site information without receiving unrestricted financial or identity records. Review access removal when a worker or subcontractor leaves. OPC business guidance provides context for protecting personal information.

4. Reliable handoff and task ownership

Move a sample opportunity from assessment to design review. Confirm that the receiving owner sees missing information and the correct drawing version. A status change should not silently imply technical approval or utility permission.

5. Communication controls that persist

Test opt-out and contact preferences across mobile and office workflows. A salesperson should not accidentally restart a stopped marketing sequence by editing a project. CRTC guidance explains consent and unsubscribe requirements for commercial electronic messages.

Record pass, fail and workaround for each test. Compare the implementation burden and total subscription cost, including permissions or integrations that require a higher plan. Use sample data for vendor demonstrations.

Choose the system the team can maintain accurately. A long feature list has little value if site information still arrives through untracked personal messages.

Run five field scripts with fictional data

Script Steps to demonstrate Pass evidence to define
1. Identify the site. Open two projects for one customer and add a note to the intended property. The office retrieves the note under the correct project.
2. Recover interrupted capture. Create a permitted sample note/photo, interrupt connectivity and reconnect. The documented behaviour preserves or clearly flags the work without silent loss.
3. Use restricted access. Open the work package as the proposed field role, then revoke access. Necessary records are available; unrelated restricted data and revoked access behave as specified.
4. Hand work to design. Submit assessment information with an unresolved question. The receiving owner sees the correct version and the open issue.
5. Preserve preferences. Update a project whose sample contact has stopped marketing. The edit does not silently restart the relevant sequence.

Ask the field user to drive the demonstration while the office checks the receiving record. Record the device, role, connection condition, configuration and subscription tested. Offline capability must be verified; this script does not assume a product provides it.

Keep a result record for every script

Use expected outcome, observed outcome, pass/fail/not tested, evidence reference, workaround and correction owner. A workaround may be acceptable for a limited task, but its effort and risk should remain visible in the decision.

For an interrupted upload, confirm whether the user can tell the difference between saved, queued and failed. Ask the supplier to explain recovery and have staff repeat the relevant task without the salesperson driving.

Review failures with the people doing the work. A desktop feature list is useful context; the acceptance decision should rest on the field workflow and support burden actually demonstrated.

Share this article