How it works

One question to your customer. The money waits for the answer.

Here is exactly what your tech does, what your customer sees, and what happens when someone is unhappy.

Your customer pays when they book, the way they already do. The difference is that the payment does not reach you yet. It is held, and they can see that it is held.

TrustLayerHeld
Job 4482 · Water heater replacement
$2,480.00
Protected until you confirmFull refund guarantee

Nothing changes for the crew. Your tech closes the job in the app they already use and adds one photo of the finished work. That is the whole ask.

Close out jobTech view
Work performedComplete
Photo of finished work added · 1 of 1 required
Time on site2h 15m

Your customer gets one message with one link and one question. Answering takes a single tap, and the answer is filed against the job with a timestamp.

Message to customerSent 4:12 PM
Your water heater job is marked complete. Is the work done to your satisfaction?
Yes, the job is doneSomething is wrong

A yes releases the payment. A problem pauses it where it sits and routes the customer back to you instead of to their bank. Nothing releases while an issue is open.

Job 4482Payment released
$2,480.00
  • Protected · Mon 9:04 AM
  • Marked complete · Mon 4:09 PM, photo attached
  • Customer confirmed · Mon 4:31 PM
  • Payment released · Mon 4:31 PM
1

Your customer picks a reason

Work incomplete, tech did not arrive, different than quoted, or their own words. Photos optional.

2

Your tech gets 24 hours

They see the specific complaint, respond with a note and a photo of the fix, and re-mark it complete.

3

Your customer decides

They confirm the fix, or they escalate.

4

You decide

If it escalates, you see both sides and enter two independent amounts: what your tech gets paid, what your customer gets refunded. Split it however the situation warrants. Not all-or-nothing.

Every one of those steps happened while the money was still in play. That is the difference between a service call and a chargeback.

The customer says something is wrong.

Instead of confirming, they tap the other button. No phone tree, no case number, and no call to their card issuer. The job is flagged the moment they answer.

The money stops where it is.

Nothing auto-releases while an issue is open. There is no clock running out in the background and no partial payment slipping through. The funds stay protected until the question is settled.

The complaint lands on your dashboard.

You see which job, which technician, which address and what the customer said. You reply, or you send someone back. Most of what becomes a chargeback is a callback nobody made in time.

The customer confirms the fix.

Once they are satisfied, payment releases and the whole exchange files itself against the job: what was raised, what you did, and when they agreed it was resolved.

Job 4482Issue raised
The new cylinder works, but the pressure drops when the upstairs tap is running.
Raised by customerTue 8:14 AM
Payment statusPaused
Amount protected$2,480.00
Scheduled releaseOn hold
Nothing releases while this issue is open.
Respond to issueAction needed
Explain what happened and how it will be resolved
Assigned technicianMarcus R.
Send response and schedule return visit
Job 4482Resolved
Return visitWed 11:02 AM
Customer confirmedWed 11:40 AM
Payment released$2,480.00

The approval record

Evidence you never have to go looking for.

Every confirmation files a record automatically. Ninety days later, dispute response is an export, not an archaeology project through your tech's camera roll.

Approval record document

Add-on charges

Extra work on site gets paid on site.

Tech finds something else that needs doing? They collect for it right there. Add-on charges are paid to your tech instantly with no protection window, itemized under the same job so your customer sees both charges together.

Protection is for the work you quoted. The add-on happened face to face with your customer standing there. No trust gap, no protection needed.

See the full permissions breakdown →

Who sees what

You decide who is on the dashboard.

Add your techs, your office, your bookkeeper. Four roles, and the dashboard changes for each one.

Your dispatcher does not need to see your margins. Now she does not have to.

The two questions every owner asks

Straight answers.

Will my techs actually use it?

They already mark jobs complete. This adds a photo and a note to that same tap, and most good techs shoot completion photos anyway. No second app, no separate login in the field. And the record protects them as much as it protects you.

What if nobody clicks?

The payment releases at 24 hours and the non-response is logged. You are never waiting on a customer to get paid. And if a customer actually raises an issue, nothing auto-releases. Ever.

Early access

See it running on your own jobs.

Apply for early access