The Tuesday-morning phone call that turns into a five-minute self-service exchange
Spent forty minutes on a Tuesday explaining to an agent’s bookkeeper which property the £160 was for. She rang again at half-past nine on Wednesday. I haven’t started a job yet this week.
The agent’s bookkeeper rings about an invoice query on the September batch and you’re forty minutes in before you’ve made tea. The property manager at the housing association emails for the photo-set from last Tuesday’s roof inspection. The syndicate owner who has a 25% share in the four-year-old wants to know what last month’s livery, vet, and farrier came to. The mum at the dinner table wants to know whether her seventeen-year-old is reverse-parking competently or just frustratedly. The sponsor of the £40k rear extension wants to see what happened on site this week, from her phone, on the train.
There’s a third party in the room for half the work most UK SMEs do - not the buyer, not the operator, but the person who needs to see the status. They can’t pick up the phone every Tuesday morning, and you can’t keep replying to the same ten emails a week. This is a read-only portal that surfaces the right slice of the operational record to the right third party - no software they need to learn, no login that locks them out of the answer they need, no Tuesday-morning phone slot. The shape is sealed against HC Electrical, where the agent-side portal closed the every-Tuesday phone slot to a five-minute self-service exchange on the EICR + EV-installer letting-agent book, and ports cleanly across letting-agent retainer work, commercial-property maintenance, syndicate-led equine yards, parent-side comms at driving schools and tutoring, and homeowner-side comms on the longer domestic builds.
What gets lost between we did the work and they know we did the work
The third party is the friction. A few moments - pick the ones that sound like your week:
- Letting-agent EICR / CP12 / property-maintenance workthe bookkeeper’s Tuesday-morning “can you re-send the invoice for 14 Mill Lane in March”, the cert PDF she can’t find, the photo-set she binned, the three open lines she wants to query at once.
- Commercial-property maintenance and FMthe property manager at the housing association who has 200 buildings across three counties and a Tuesday-afternoon Excel KPI report she’d rather not assemble by hand from your emails.
- Domestic extensions and high-ticket installsthe customer who’s spent £40k on the extension wants to see what’s happening from her phone; she rings every other day because nobody’s told her what week 12 is supposed to look like.
- Storm-damage roof claimsthe homeowner wants to know where the claim is in the loss-adjuster pipeline; the loss adjuster wants the photo-evidence pack; both ring you, neither knows the other rang.
- Driving instructorsthe parent paying for the lessons wants to see the seventeen-year-old’s progression on the DVSA seventeen-competency chart; the pupil is allergic to mum asking “how did it go”.
- Tutors and nurseriesAisha’s mum wants Aisha’s progress only; Tom’s dad wants Tom’s progress only; the class WhatsApp gets every parent and nobody gets a private answer.
- Equine yards and syndicate-managed horseseach syndicate owner needs to see the per-horse account for the share they hold (monthly livery, vet, farrier, physio, race entries, race-share splits); they don’t need to see the other syndicate members’ contributions.
- Repair shops and inbound-items service businessesthe customer who left her phone at 10am wants to know whether it’s fixed without ringing the bench at 4pm; the repair tech wants to be on the bench, not on the phone.
These aren’t problems for a generic customer portal that asks the third party to learn yet another login. They’re the bit between we did the work and they know we did the work - which is where your Tuesday morning actually lives.
What solved looks like
1. Each third party gets the right slice - and only the right slice
The “everything in one inbox” moment: the agent’s bookkeeper asks for one cert and you re-attach the whole batch out of muscle memory. The syndicate owner asks for last month’s livery and you accidentally show him the contributions of the other three syndicate members. The class parent group on WhatsApp gets every parent in every conversation. Privacy by accident.
Solved looks like: each third party gets a personal URL that shows only their slice. The letting agent sees the properties they manage - every cert PDF, every photo-set, every open invoice, every payment link. The syndicate owner sees the per-horse account he holds a share of - monthly livery, vet, farrier, physio, BHA entries, race-share splits - and nothing he doesn’t have the right to see. The parent sees her own child’s progression, attendance, and balance. The class group disappears as a comms tool because the per-family channel replaces it. The slice is configured per third-party-type; privacy is the default, not a retrofit when the ICO writes.
2. No password they’ll forget, no login that locks them out of the answer
The “I can’t remember my login” moment: the agent’s bookkeeper has been emailed the portal link three times this quarter and binned it twice. Every time she needs the cert PDF, she rings you instead of digging through her trash folder.
Solved looks like: no password. A one-tap email link gets the third party into their personal dashboard; the token refreshes on next-use so it never expires mid-relationship. For institutional third parties (an agency with multiple bookkeepers, an FM company with a regional team), per-user access with role-based permissions sits behind the same one-tap entry. The portal is a bookmark, not a system they have to learn - the bookkeeper opens it on Tuesday morning the same way she opens her email.
3. Live data, not a Monday-morning export
The “this report is two weeks out of date” moment: the property manager opens the spreadsheet you sent and it’s last Monday’s data because that’s when you exported it. She rings to ask whether the seven jobs you completed since then are reflected. They’re not. You spend Tuesday afternoon explaining the gap.
Solved looks like: the portal reads from the same operational record that drives the rest of the build - the Booking & Review Loop done-event, the Invoice & Dunning Ladder chase state, the Recurring Service Recall next-due dates, the Stage Payment & Retention Ledger milestones. When you close a job at five past five on a Tuesday, the agent sees it at five past five on a Tuesday. The Monday-morning export disappears because there’s nothing to export - the live view is the report.
4. One-tap self-service for what used to be a phone call
The “can you re-send 14 Mill Lane” moment: every recurring query is the same shape - re-send the invoice, download the cert, confirm the variation, pay the outstanding balance. You’ve done each of them a hundred times.
Solved looks like: the actions the third party would have rung you for become one-tap from their phone - “re-send the invoice for 14 Mill Lane in March”, “download the EICR cert for 22 Park Road”, “confirm I’ve accepted the variation order on the extension”, “pay the outstanding balance for August”, “approve the photo-set as evidence on the storm-damage claim”. The payment route uses whichever provider you’re already on; the cert PDFs land in the third party’s inbox without your inbox being involved. The bookkeeper’s Tuesday-morning phone slot becomes a five-minute Tuesday-morning self-service slot.
5. Query-routing instead of phone-tag
The “I think this invoice line is wrong” moment: the bookkeeper spots a £40 line she doesn’t recognise and rings to query it. You explain it; she queries another line. The other twelve lines she was going to pay this week get held while she waits for you to call back.
Solved looks like: where the query genuinely needs human input from your side - “I think the kitchen-fitter line on this invoice is wrong, can you check?”, “the photo for unit 4 doesn’t match the description”, “the variation order has the wrong floor area” - the portal routes the query into a triage queue with the original context already attached. The other batch lines don’t get held; the bookkeeper queues the rest for payment while you resolve the one. When you reply, the resolution writes back to the agent’s view automatically. The Tuesday-morning “hold everything while we sort one line” pattern stops happening.
6. Audit trail by default - so “we never received it” gets answered from the log
The “we never got the cert” moment: six months on, the agent’s bookkeeper claims a cert was never sent. You spent the original Tuesday morning sending it. Your reply-all inbox doesn’t go back far enough to prove it. You re-send.
Solved looks like: every view, every download, every action the third party takes lands in the audit log per third party. The “we never received the cert” dispute six months later gets answered from the timestamp of the bookkeeper’s download from her own IP. Subject-access requests, retention policies, and deletion routes run through the same audit layer. The log is the quiet receipt the relationship runs on - most third parties never need it, but the chronic-disputant ones see it once and stop disputing.
How the portal runs, by default
The default shape per third party runs:
- First touchthe third party gets a personal-URL invite by email at the start of the relationship. One-tap login, lands on their dashboard. No password, no install, no app store.
- Ongoingthe portal reads the live operational record; the third party opens it when they need to. Most days they don’t; on the days they do, the answer’s there.
- Notificationsper third-party preference, the portal sends a soft “there’s a new cert / invoice / photo-set / progress update on your page” nudge on the channel the third party reads - email by default for institutional third parties, SMS for parent-side comms, WhatsApp where opt-in is on the record. No nudges louder than the actual change warrants.
- Self-service actionone-tap from the third party’s phone fires the action against your operational record (re-send invoice, download cert, accept variation, pay outstanding). The audit log records the action; your view reflects it within the same minute.
- Triage queuequeries that need your input land in the triage queue with the original context attached. You resolve from your own dashboard; the resolution writes back to the third-party view automatically. Other items don’t get held while one is in triage.
- Audit logevery view, every download, every action timestamped per third party, available to you on demand. Dispute six months later → answered from the log in under two minutes.
Per third-party tuning lives on top of the default - a letting agent gets the cert / invoice / photo bundle on a per-property-row view; a syndicate owner gets a per-horse account-card view with quarter / share weighting; a parent at a driving school gets the seventeen-competency chart with the latest lesson note pinned; a customer on a £40k extension gets the project plan, this-week’s photo-set, the variation log, the next stage payment, and the snagging list as it builds. Same engine; per-third-party voice; per-slice configuration.
Who this is for
The shape repeats anywhere there’s a third party in the room who needs to see what’s happening but can’t keep ringing you for the answer.
Letting-agent retainer work and the trades that do it - letting agents, plumbers/lettings, decorators/property-maintenance, gas-engineers/landlord-cp12, electricians/eicr-specialist. The agent’s bookkeeper gets per-managed-property view - every cert PDF, every gas-safety record, every EPC, every last-PAT, every photo-set, every open invoice, every payment link - in one place she can self-serve without a Tuesday-morning phone slot. Pairs with the Invoice & Dunning Ladder agent-side cadence as the depth view behind the dunning summary.
Commercial-property maintenance and FM-side work - commercial-maintenance roofers, commercial plumbers, commercial electricians, commercial-grounds landscapers, commercial-contract decorators. The property manager at the housing association / managing-agent / FM company sees every active job’s status, every cert on file, every photo-report, every retention release tracked, every outstanding invoice. The Tuesday-afternoon Excel KPI report assembles itself.
High-ticket domestic builds and installs - extension-specialist builders, bathroom-fitter plumbers, boiler-installer gas engineers, MCS solar PV and battery installers. The customer who’s £40k into the extension sees the project plan, this-week’s photos, the next stage payment, the variation log, and the snagging list as it builds; she stops ringing every other day. The view feeds the Stage Payment & Retention Ledger customer-side wording.
Storm-damage and insurance-pipeline work - storm-damage roofers, leak-detection plumbers. The homeowner sees where the claim is in the loss-adjuster pipeline; the loss adjuster sees the per-claim photo-evidence pack tagged by stage; both stop ringing you for the other’s status.
Driving instructors and tutors / nurseries - driving instructors, tutors and nurseries. The parent’s view of progression - the DVSA seventeen-competency chart on the driving side, the per-term reading / phonics / maths progression on the tutoring side, the attendance and balance on the nursery side. The seventeen-year-old’s dinner-table conversation changes from “how was the lesson” to “I can see you nailed reverse-parking - try roundabouts next?”
Equine yards and syndicate-managed horses - equine yards and syndicate managers. The syndicate hub where each owner sees the per-horse account they hold a share of: monthly livery, vet, farrier, physio, BHA entries, race-share splits - weighted by their stake, never showing the other syndicate members’ contributions.
Inbound-items service businesses - device repair shops, independent garages. The customer who dropped the phone at 10am sees the diagnosis at 11:30, the estimate at 12:15, the fixed status at 15:40 - without ringing the bench.
Same engine; different slice; different vocabulary; different audit posture.
The closest thing we’ve already built
HC Electrical - the live agent-side portal running across the EICR + EV-installer letting-agent book. Each agent’s bookkeeper sees their managed properties, certs, invoices, photo-sets, and payment links from one personal URL; pre-build the agent-side queries occupied a Tuesday-morning phone slot, and the build closed it to a five-minute self-service exchange. (Named pull-quote + final-£ outcome figures hold behind the permission checklist; see Hc Electrical for the build detail.)
mendmyi - the founder’s own UK device-repair business runs the customer-facing repair-status portal as the per-customer view of the same engine: drop-off at 10am, diagnosis at 11:30, estimate at 12:15, fixed status at 15:40, the customer never rang the bench.
pharmaceutical-analytics.com - the dashboard shape. Per-stakeholder visibility on operational data is the shared engine underneath every per-third-party slice; the per-syndicate-owner, per-parent, per-agent view is the same pattern with the slice rule changed.
Tell us what your third-party comms look like
Who rings you most often - bookkeepers, property managers, parents, syndicate owners, homeowners on long builds, claim assessors - what they’re usually asking, and how you currently answer. Tell us the most-repeated email or phone call you’ve handled twice in the last month and we’ll come back with a sketch of what we’d build to make that conversation self-serve. No demo, no calendar widget. Email reply, scoped sketch, you decide.
FAQ
How does the third party log in - is it another password they’ll forget?
No password. The portal uses email-magic-link authentication - the agent or parent or sponsor enters their email, gets a one-tap login link, and lands on their personal dashboard. Tokens refresh on next-use so they don’t expire mid-relationship. For institutional third parties (an agency with multiple bookkeepers, an FM company with a regional team), per-user access with role-based permissions sits behind the same one-tap entry.
Will it work with the agent’s existing systems (Reapit / Alto / Jupix / PayProp) - or with FM-helpdesk and property-management platforms?
Where the agent or property manager runs their own platform, we either feed our portal data back into it (so the agent’s bookkeeper sees invoices inside her own system) or we surface the portal as a link the agent clicks from inside her platform’s notes / docs area. Where the third party has no platform, the portal is the access point. We integrate; we don’t ask the third party to learn anything new.
What if a major third party wants a feature the portal doesn’t yet have?
The portal is configurable per third-party-type. Common requests - a different photo-arrangement on a per-job view, a different export format, a different KPI summary at the top - are tunable on the monthly arrangement. Bespoke per-third-party requests get scoped on the retainer. The build is shaped around easy to extend per third party, not one rigid layout for everyone.
Is the audit trail GDPR-clean?
Yes. The log records what was accessed, not the content of what was accessed - data-minimisation by construction. Subject-access requests, retention policies, and deletion routes run through the same compliance layer that runs across the rest of the build. The audit log is your defence if a third party later claims they never received something; we don’t pretend to be your solicitor for contested cases, but the evidence trail is what a solicitor will ask for first.
What about the third party who wants email instead - can the portal stay optional?
Yes. Email-with-link is the default behaviour even where the portal exists - the third party can self-serve from the portal or keep replying to your emails. The portal makes the repeat requests one-tap; email handles the bespoke ones. The third party never has to use the portal to get their answer; the portal exists so they don’t have to ring.
Will the portal stand up to a bookkeeper who’s used to ringing you every Tuesday - or will she just keep ringing?
Most do, for the first two or three Tuesdays. By the fourth, the muscle memory of “open the portal and download the cert” replaces “ring him and ask”. We tune the soft-nudge cadence (the “there’s a new cert on your page” email at the moment the cert lands) so the bookkeeper learns the portal carries her answer before the question forms. After a quarter of running, the Tuesday-morning phone slot is gone.
Can different team members at the third-party side have different access?
Yes. For institutional third parties (an agency with three bookkeepers, an FM company with a regional team, a multi-owner syndicate, a co-parenting family), per-user access with role-based permissions sits behind the same one-tap entry. Senior people see everything in their slice; junior people see the bits relevant to their role. The configuration sits on the third-party record, not on you remembering.
Does it replace our existing back-office software / CRM / job-management system?
No. The portal sits on top. The slice it shows is read from your existing back-office system (Tradify, ServiceM8, Powered Now, Commusoft, Reapit, Alto, PayProp, your own internal app, whatever) or from the operational record we already maintain for you across the rest of the build. We integrate; we don’t replace.
What does it cost?
Every build is scoped per client - depends on the third-party types you serve, the slices they need, the back-office systems you’re already on, and the audit posture the relationship requires. We talk it through, agree the scope and the price in writing, then build. No per-third-party seat fees, no per-login charges. See pricing for how we work.