Thank you, Shayla—I appreciate you passing this along to the product team.
For our workflow, the two most valuable additions would be:
- A dedicated Project Status field.
- Scheduled Start Date and Time and Scheduled End Time / Date fields.
These would solve two related but separate problems for companies integrating CompanyCam with Salesforce or another CRM.
Project Status
Labels can technically represent a project’s status, but they become messy very quickly. We also use labels for job type, fuel type, paperwork, routing, technician workflow, and other operational purposes. When status is mixed into the same label system, a project can accidentally have Scheduled, Completed, and Cannot Complete selected simultaneously.
A dedicated, single-value Project Status field would prevent those conflicts. Suggested values could include:
- New
- Scheduled
- In Progress
- Completed
- Incomplete
- Cannot Complete
- Waiting
- Canceled
- Closed
Ideally, companies could customize their available status values.
In our workflow, Salesforce is the main office system, and the Work Order Status controls which queues, lists, and follow-up processes contain the job. Our technicians do not have Salesforce licenses; they work from CompanyCam.
We currently rely on the technician applying a matching CompanyCam label, which triggers an integration that updates the Salesforce Work Order. It works, but labels are not the cleanest tool for this. We must determine which label represents the newest status, remove the previous status label, and prevent multiple conflicting status labels from being applied.
A dedicated field would give every project one clear, authoritative status.
Structured status values would also give CompanyCam and its customers much more automation potential. A status change could trigger:
- A webhook update to Salesforce or another CRM.
- A customer completion message.
- An office follow-up task for an incomplete job.
- A parts request when a job cannot be completed.
- A payment request when work is completed.
- Automatic project archiving after a defined period.
- Different required checklists or documents.
- Management alerts and dashboards.
- Movement between project views without creating additional labels.
Labels could then remain available for what they do best: flexible categories such as Wood, Gas, Installation, Cleaning, Warranty, or Route Stop 1. Project Status would describe where the job is in its lifecycle.
For integrations, the minimum useful Project Status implementation would include:
- One current status value per project.
- Customizable status options.
- Read and write access through the API.
- A webhook event when the status changes.
- The user and timestamp associated with the change.
- Visibility and easy editing on web and mobile.
- The ability to filter, sort, and report by status.
- Optional automations based on status changes.
Scheduled Start Date and Time and Scheduled End Time / Date
For scheduling, having both a Scheduled Start Date and Time and a Scheduled End Time / Date would be considerably more useful than having a single date or timestamp.
I would keep the scheduled appointment information separate from the actual time worked:
- Scheduled Start Date and Time
- Scheduled End Time / Date, preferably optional
- Actual Clock-In and Clock-Out through CompanyCam’s Time Tracking feature
The Scheduled End Time / Date should not automatically close the project. Project Status should control whether the project is completed, incomplete, canceled, or closed. The scheduled fields would represent the appointment or arrival window promised to the customer.
Our office schedules a Salesforce Work Order for a particular technician and date. The integration then creates the corresponding CompanyCam project. Salesforce customer information maps very well into the CompanyCam project contact, but the scheduled date and time currently have no structured destination. We can only place that information in the project description or notepad.
That technically displays the information, but it cannot be reliably sorted, filtered, reported on, displayed prominently, or used by automations without parsing free text. The schedule can also become buried among the other project notes.
Our technicians often route the next day’s jobs themselves the night before. Structured scheduling fields could allow CompanyCam to:
- Display today’s and tomorrow’s projects chronologically.
- Show the arrival window prominently on mobile project cards.
- Sort and filter projects by their scheduled date.
- Improve map and routing views.
- Notify technicians when an appointment changes.
- Send appointment reminders or arrival-window texts to customers.
- Push technician scheduling changes back to Salesforce or another CRM.
- Compare the scheduled appointment with actual Time Tracking data.
- Report on travel time, arrival accuracy, job duration, and workload.
For example, a customer could be given an appointment window of September 16 from 9:00–11:00 AM:
- Scheduled Start Date and Time: September 16 at 9:00 AM
- Scheduled End Time / Date: September 16 at 11:00 AM
For a multi-day installation, the Scheduled End Time / Date could instead fall on a later date. Companies that only need a single scheduled time could leave the ending field blank.
The existing contact integration is a good comparison. Because customer information has dedicated fields, it remains structured and useful throughout CompanyCam. We would love project status and appointment scheduling to work the same way.
The minimum useful scheduling implementation would include:
- Scheduled Start Date and Time.
- Optional Scheduled End Time / Date.
- API read and write access.
- Webhook events when either value changes.
- Web and mobile visibility.
- Visibility on mobile project cards.
- Sorting and filtering by these fields.
Together, Project Status, Scheduled Start Date and Time, Scheduled End Time / Date, and Time Tracking would provide a clean progression:
Scheduled appointment → technician arrival → work performed → final project status.
That would make CompanyCam substantially more powerful for companies using Salesforce and other CRMs without requiring CompanyCam to become a full field-service platform. It would also create a strong foundation for customer communications, routing, reporting, payments, and workflow automation.
We would be very interested in beta-testing these features with our Salesforce-to-CompanyCam integration.
