Running a commercial motor fleet on WhatsApp: additions, deletions, certificates

A fleet is a client who writes every day. The fleet manager of a logistics firm, a construction company or a car-hire business asks to add a bakkie on Monday, needs a confirmation of cover on Tuesday for a site access permit, reports a bump on Thursday and removes a sold truck on Friday. By phone, every request interrupts a consultant; by email, it waits; on WhatsApp, it arrives with a photo of the registration document and goes back with a PDF.

The risk is well known: an addition request read on a consultant's personal phone while on leave, a vehicle on the road that the insurer has never heard of, and a claim repudiated. Fleet servicing on WhatsApp only works if the exchanges sit on a brokerage number, visible to the team and tied to the policy.

This guide describes how a brokerage in Durban, Nairobi, Lagos or Birmingham organises it: the ground rules agreed with the client, handling an addition, sending confirmations of cover and certificates (a motor insurance certificate in the UK, a COMESA yellow card for cross-border trips in East and Southern Africa), deletions, fleet claims and the annual renewal. It spells out what falls inside the 24-hour window and what needs a template, and repeats one absolute rule: nothing is on cover until the insurer confirms.

The journey, step by step

1. Agree the ground rules with the fleet manager. When the fleet policy incepts, the brokerage appoints a single contact on the client side (the fleet manager) and gives them the brokerage's WhatsApp number, not a consultant's. A welcome message sets the rules: what can be requested over WhatsApp (addition, deletion, confirmation of cover, claim notification), the information to attach to each type of request, processing hours, and the principle that nothing is on cover until the insurer confirms in writing. That message is the reference point when a misunderstanding arises.
2. Process a vehicle addition with four pieces of information. To add a vehicle, the brokerage needs a photo of the registration document, the use (goods carrying, sales rounds, hire), the regular driver where the policy requires it, and the requested effective date. The consultant acknowledges inside the window opened by the request, submits to the insurer and comes back with the confirmation, the additional premium and the effective date. Where the insurer or the binder requires payment before inception, say so explicitly: the vehicle is not covered until the premium is collected. The fleet vehicle addition template serves as the written confirmation.
3. Send confirmations and certificates in the thread. Confirmations of cover are the most frequent request: a policy schedule extract or cover note for a site permit or a finance house in South Africa, the motor insurance certificate that UK law requires, the COMESA yellow card for drivers crossing into Zambia, Zimbabwe or Tanzania. When the fleet manager asks, the window is open and the PDF goes back as a reply. When the brokerage takes the initiative (annual re-issue of certificates for the whole fleet), it opens with a utility template such as certificate delivery, followed by the documents.
4. Delete, replace, reconcile. A deletion is confirmed in writing with the off-cover date so that the premium is adjusted pro rata and a sold vehicle does not stay on the schedule. A replacement is handled as a deletion plus an addition. Every month or quarter, the brokerage sends the fleet manager the schedule as the insurer holds it and asks them to check it: this reconciliation is what prevents the discovery at renewal of twelve undeclared vehicles or three trucks sold a year ago and still insured. The fleet register itself lives in the broker management system or the insurer's portal, not in WhatsApp.
5. Organise fleet claims. Drivers do not message the brokerage: they report to the fleet manager, who forwards. The initial ground rules say so. For each claim the brokerage asks for the accident report or police case number, photos, the driver's details and the odometer reading, then follows the file as it would for an individual, with regular progress updates. The difference is volume: a thirty-vehicle fleet has several open claims at once, and quoting the insurer's claim reference in every message is what keeps Tuesday's van and Thursday's sedan apart.
6. Prepare renewal with a claims experience report. Two months before the annual renewal, the brokerage emails the fleet manager, on a durable medium, the year's report: vehicles on cover, claims, cost, the insurer's proposed premium movement, and recommendations (driver training, excess structure, telematics where insurers offer it). WhatsApp is used to flag the email, set up the renewal meeting and answer quick questions. The advice and the renewal proposal stay formalised in writing, as FAIS record-keeping, the FCA's commercial customer rules and plain commercial-lines practice require.

Sample messages

Acknowledging an addition request, inside the window

Confirming the addition after the insurer's reply

Annual certificate re-issue, utility template

Pitfalls to avoid

• Letting one consultant run the fleet from a personal number: the addition request read on leave and forgotten becomes an uninsured loss.
• Treating a consultant's "ok, adding it" as binding the insurer: only the insurer's confirmation, and where required the premium collection, puts the vehicle on cover.
• Accepting requests from ten different drivers: one contact on the client side, otherwise nobody knows what has been requested.
• Keeping the fleet register in the WhatsApp thread: the schedule lives in the broker management system, WhatsApp is only for requesting and confirming.
• Sending a confirmation of cover without checking the vehicle is on the schedule at that date: an inaccurate certificate exposes the brokerage.
• Waiting for renewal to reconcile: undeclared additions and deletions surface all at once, with an adjustment premium the client disputes.

How ORIS organises this use case

In ORIS the fleet manager is a client in Customers & Segments whose policy is typed business or auto, and every request lands in the shared inbox where the whole team can see it. The Window Open / Window Closed indicator shows whether the consultant can reply in free text or must open with a template; the annual re-issue of certificates runs as a Quick Campaign to a "fleets" segment with an approved utility template.

Notes on the client record keep the policy reference and the open claim numbers; the AI classifies requests and raises a notification for those that need a human, such as a serious accident. The fleet register, endorsements and certificate PDFs are still produced by the broker management system and the insurer: ORIS does not issue policy documents and has no native integration with those tools, but the CSV export of clients and opportunities makes reconciliation straightforward.

Frequently asked questions

Does a WhatsApp request to add a vehicle put it on cover?

No. Cover runs from the insurer's confirmation (and, where the binder or the insurer requires it, from premium collection). The brokerage should state this in the initial ground rules and repeat it in every acknowledgement so that no vehicle drives uninsured.

Can I send a certificate or confirmation of cover as a PDF on WhatsApp?

Yes, inside the 24-hour window opened by the request, or after a utility template when the brokerage takes the initiative. The document must match exactly the vehicle and the period on cover; check before sending.

Do fleets need a dedicated WhatsApp number?

Not necessarily: a brokerage number with a shared inbox is enough, provided fleet conversations are identifiable and several consultants can reply. What matters is not depending on one person's handset.

What if the fleet manager forwards drivers' accident messages as they come?

Accept them, but insist on the structured elements for each file (report or case number, photos, driver, date) and reply with the insurer's claim reference as soon as it exists so that each claim stays identifiable in the thread.