Getting Started with Contractorfy

Launch in a controlled Android-first sequence: set up one workspace, run one full guided job automation, validate notifications and sends, then scale that same workflow across teams.

Implementation checklist

Android app is signed in to the intended workspace and group.
Jobs always include owner, due date, and location metadata.
Task extraction is active for both call and SMS workflows.
Document generation and send actions are logged in one job timeline.
No duplicate job records or conflicting group membership.
API keys are created only for approved integrations and limited scopes.
Document naming convention is enforced before claim submission.

Before you begin

Set the workspace and Android app context first so every guided automation runs in the correct team scope.

Use one workspace per legal entity when possible.
Use a consistent group naming pattern (market + team function).
Invite one workspace owner and one operations admin to avoid lockout risk.
Sign in on Android and confirm the correct workspace and group are selected before starting any job.

Days 1-2: Android guided baseline

Run one real job end-to-end using the same guided automation path your team already uses in the Android app.

Create one job in Android and set the status baseline: intake, estimate, execution, closeout.
Upload photos, proposal, permits, and claim files into that same job record.
Run one live call flow and confirm task extraction creates one field task and one office follow-up task.
Generate one document in-call and one by SMS workflow, then verify both appear in the job timeline.
Confirm notifications are received by both field lead and office lead.

Days 3-5: Validation and controls

Lock in guardrails before volume so automation stays predictable and auditable.

Turn on approval gates for high-risk sends and external-facing actions.
Confirm no duplicate jobs are created from repeated calls or message retries.
Validate document naming convention before claim submission.
Run one closeout and confirm owner, timeline, and document history are complete.

Weeks 1-2: Scale the same workflow

Scale by cloning the proven baseline, not by introducing new process variation.

Add templates for top job types and map each to the matching automation rules.
Move from manual reminders to scheduled follow-ups only after baseline validation passes.
Run weekly stale-job checks and ownership audits.
Onboard additional crews to the same Android guided workflow and permission model.

Recommended next page

Roofing CRM Storm restoration CRM Team Onboarding

Contractorfy roofing operations

Operations

Preparing the job workflow.

Bringing up roofing CRM records, documents, tasks, and handoff controls.

Roofing workflow modules

Opening route data and controls.

Syncing

Workspace

Records

Actions

Guide