Facility service companies need to know their clients well. They also need to know what was done at each client's site this week. These are different records, and they are easier to manage when they are kept apart.
What a CRM should hold
- Client and contact details.
- Contracts, renewal dates and tender history.
- Sales conversations and proposals.
- Account notes that help whoever picks up the relationship next.
What it should not hold
- Individual service requests from a client's staff.
- Work orders, checklists and inspection results.
- Attendance and task progress.
- Photos and evidence of completed work.
Those belong in an operations system, where the people doing the work can update them from site.
How to connect them
Link the two by client, site and contract. A salesperson preparing a renewal should be able to see how service performed at the site. A supervisor should not need the CRM to dispatch a job.
Where Swipetask fits
Swipetask is not a CRM. It holds the service requests, tasks and evidence a CRM should not have to carry, and it reports on them so the account team can use the results.