Installers, fibre crews, service centres, haulage contractors and attached trucks do the work your customer pays you for. You find out how it went by ringing them. We build the job record they update and you pay from.
Most partner software is built for dealers and brokers. A crew on a roof needs something else.
They bring orders and leads. They need price lists, stock, schemes and their commission from you. Their record is a sale, and a partner portal usually fits.
They carry out a job in your name at your customer's site. You need evidence from them, stage by stage. They need a clear job, their payment status and nothing else of yours.
Think of it as an installer app with photo proof at every stage. Without the proof, the job does not move, and neither does the partner's payment.
Site address and contact, the approved design or scope, material issued with quantities, and the photo checklist for this job type.
They accept with a visit date or decline with a reason, so an ignored job shows up on day one rather than day ten.
Mounting photos from the roof, splice readings, a parts list from the bench or a ticket from the gate, each checked against the list.
Serials scanned on site, the customer's signature or acceptance, and the handover document your service team will need in two years.
Someone on your side accepts the evidence or returns it with a note, and only accepted work counts towards the bill.
Different trades, one shape: someone outside your company does the work, and the proof arrives late, partial or never.
Renewable energy installer partners upload stage photos when reminded and type panel serials later. The service team inherits half a project file and handles warranty calls blind.
A telecom fibre partner submits a job card twice on a weak connection, or reports completion before provisioning closes. The order should advance once, on both facts.
In transport, owners of attached and hired vehicles send the POD to whoever they remember. A light owner view shows their own trips and takes their documents.
Electronics brands rely on outside service centres to log diagnosis and spares. Without a job record, parts claims are paid on trust and repeat faults by model stay hidden.
Construction subcontractors raise running bills that the engineer checks from memory. Track subcontractor jobs against measured progress and the bill has something to be checked against.
In energy, an outside crew services a compressor and emails a scan a week later. An upload screen on the open work order files it against the right asset.
Mining and metals haulage contractors can bill trips the weighbridge never logged, in trucks whose insurance lapsed last month. Both checks belong before accounts sees the bill.
Smaller logistics agents and last-mile partners will not adopt another portal. Their updates must arrive by link, email or WhatsApp reply and still reach the shipment.
Assume most won't. Design for the one with a full phone gallery and no patience.
An installer who works for four brands won't keep four apps. A truck owner with six vehicles won't remember a password. A service centre already lives inside the portals of the brands that pay it.
So the job reaches them as a WhatsApp message with a link. It opens a plain web page for that one job: address, scope, checklist and an upload button. No install, no password, and the link stops working when the job closes.
Partners handling many jobs a week get a proper login, in effect a service partner portal, with their queue, payouts and documents. Access follows assigned jobs through roles and permissions, so no partner sees your pricing or a rival installer's sites.
Reminders go where the partner already reads. An unaccepted job by evening, a missing stage photo or an insurance renewal each sends a WhatsApp or SMS notification, then escalates to your coordinator if ignored.
Once every job carries its evidence, the scorecard and the payout come out of it, with no separate sheet.
A partner can be excellent and still be uninsured this month. Each of these needs a date and a rule for expiry.
No. Each partner sees just their own assigned jobs, at their own rates. Your team sees every partner side by side.
Photos taken through the job page can carry the time and place of capture. A roof photo taken far from the site, or before the job was assigned, gets flagged for your engineer. It won't catch everything, so spot checks still matter.
It works out what is payable per job after sign-off and deductions. The money still leaves through your bank, and Tally or your ERP stays the books.
One partner record with two roles works better. Both sides share the partner's details and documents, and each view shows only what that activity needs.
Usually one job type with your busiest partners: the job pack, stage evidence and engineer sign-off. Ratings, payouts and document expiry follow once jobs reliably close on the record. For partners offline for hours, see field and site teams.
Send one recent job on WhatsApp: the message you sent the partner, the photos that came back and their bill. We'll show where a job record would have caught the gaps.