Elevator CRM
An elevator company runs two businesses at once: selling new installations to the contractor and keeping up the monthly maintenance of hundreds of buildings. When the maintenance list sits in a spreadsheet, the fault calls on the phone and the shortcomings from the annual inspection in the engineer's notebook, what is outstanding in which building only comes out at the next inspection.
Every elevator car is a separate record: the building, the capacity and the contract end date are its fields. Maintenance tasks, fault requests and annual inspections accumulate under the same card.
- Keep every elevator as a separate record; let the building, the capacity, the year of installation and the contract status sit on its card
- Tie monthly maintenance visits to a periodic task and let the technician close the form from the mobile app with location verification
- Turn fault calls into request records and read from the history which elevator they recur on
- Write the non-conformities found at the annual inspection and the re-inspection date into the record, and let the task fall in before the time runs out
| Elevator Asset Record | Every car is a separate record; the building, the capacity, the year of installation and the contract status are its fields, and its history accumulates on that card. |
|---|---|
| Periodic Maintenance Task | Maintenance is a task; the date and the technician are its fields, the field team closes it from the mobile app and the location verification is written into the record. |
| Fault Request | A fault call is a request record; it falls into the queue, the assignment rule defined during setup routes it to the technician in that area, and its closure stays in the elevator's history. |
| Annual Inspection and Non-Conformity | The inspection result and the label issued are fields on the elevator record; the task tied to the re-inspection date falls into the list before the time runs out. |
In an elevator company the thing that has to be recorded is not the customer but the elevator: under the same building manager there can be several cars of different ages, different capacities and with different lists of outstanding items. When the maintenance cycle, the non-conformity found at the annual inspection and the fault call that comes in at night are kept in separate places, the person going to the contract renewal meeting sits down at the table without knowing how many times a fault call was answered at that building in the last six months.
Rapitek CRM keeps every elevator as a separate asset record; the maintenance visit, the fault request and the annual inspection result accumulate under that record. Periodic maintenance tasks fall into the calendar by themselves, the technician fills in the form from the mobile app and the building manager signs on the signature screen in the same app; when the contract end date approaches, the renewal task comes in front of you together with that building's fault history.
The scope of the plans and the separately priced items are written on the pricing page.
