Courier CRM
In the courier business the real cost is not in the parcel that is delivered but in the one that could not be delivered and came back. When the fact that the recipient did not open the door, or that the address was incomplete, stays on the courier's phone, the second attempt sets off with the same mistake.
A shipment is a record; recipient, address, attempt count and failed-delivery reason are its fields. The second attempt opens under the same record, where the proof of delivery sits too.
- Keep every shipment on a single record with recipient, address, attempt count and failed-delivery reason fields
- Take the proof of delivery from the mobile app; let the person receiving it sign on the signature screen, and let the photo and location verification be written onto the same record
- Drop the shipment into the queue of an available courier in the area with the shift and the assignment rule defined at setup
- Open sending companies' complaints and queries as request records and track their closure
| Shipment Record | A shipment is a record; the recipient, the address, the attempt count and the failed-delivery reason are in its fields, and the second attempt is opened under the same record. |
|---|---|
| Proof of Delivery | Delivery is a task with signature and photo fields; the person receiving it signs on the signature screen in the mobile app, the location verification is written onto the record, and fake location detection is part of that verification. |
| Courier Shift and Assignment | A shift is a record; the assignment rule defined at setup drops the shipment into the queue of an available courier according to the area and shift fields. |
| Sender Account | The sending company is an account record; the agreed unit price sits in a field on the account, and complaints and queries are opened as request records linked to that account. |
On the last mile there is only one thing argued about at the end of the day: why it was not delivered. The courier says "there was nobody at the address", the sending company says "the recipient was at home", and there is no record in hand to close that argument. The amounts collected at the door are gathered at the end of the day in a separate ledger; which shipment's money is with which courier is left to reconciliation day. And the sending company's question, "what happened to that shipment", forces somebody onto the phone every single time.
In Rapitek CRM a shipment is a record: the recipient, the address, the attempt count and the failed-delivery reason are the fields on that record. The proof of delivery sits on the record itself — the person receiving it signs on the signature screen in the mobile app, and the photo and the location verification are written onto the same card; the verification also covers fake location detection. The shift and the assignment rule defined at setup drop the shipment into the queue of an available courier in the area; the sending company's question is opened with its own request record and its closure leaves a trace.
The scope of the plans and the separately priced items are set out on the pricing page.
