Security Services CRM
In private security the service is sold as sites and shifts; the contract sets out how many people will be on site and at what hours. When an officer's ID card expires or a shift handover goes wrong, the problem shows up at the customer first, not in the office.
Every customer site is an account record; the headcount in the contract, the shift pattern and the monthly fee sit in its fields. Certificate and ID card expiry are dates on the staff record.
- Keep the customer sites and the number of people to work at each site on an account record, and build the shift plan with working hour definitions
- Have patrols and site checks marked from the mobile app and confirm the location with GPS verification
- Have the incident report written on site, attach it to the site record and send a push notification to the person responsible
- Follow staff certificate, ID card and contract renewal dates and drop the ones coming up into the list
| Service Site | Every customer site is an account record; the headcount in the contract, the shift pattern and the monthly fee sit in the fields of that record. |
|---|---|
| Shift Plan | The guard duty is set up with shift and working hour definitions; who goes to which site is determined by the assignment rules defined during setup, and any change is read from the plan. |
| Patrol Record | The patrol round is marked from the mobile app; the location is verified by GPS and spoofed location reports are detected. |
| Document Expiry Dates | Certificate and ID card expiry are date fields on the staff record; the ones coming up drop into the list, and the renewal task is opened from there. |
A security company's work turns in two places at once: the officers standing guard on site and the contract running in the office. When the two are kept in separate books, familiar failures appear — who stood in for the officer who did not turn up for their shift is only learned in the morning, the incident report written on site reaches the customer days later, and the fact that a private security ID card has expired is noticed during an inspection. The same happens on the contract side: the renewal conversation starts two weeks before the annual contract ends, because nobody sees the date in advance.
In Rapitek CRM the customer site is an account record; how many people will work on which shift at that site is planned with shift and working hour definitions, and the assignment rules defined during setup determine who goes where. Patrols and site checks are marked from the mobile app, the location is verified by GPS and spoofed location reports are detected. The incident report is written on site and attached to the site record, and a push notification is sent to the person responsible. Because staff certificate and ID card expiry dates and the contract renewal date are all date fields, the ones coming up drop into the list on their own.
What the plans cover and which items are priced separately are set out on the pricing page.
