Human-reviewed help
Requests, support notes and pilot issues are reviewed by a real person before any next step is suggested.
No automatic dispatch, provider assignment or customer-visible scoring.
Share friendly tech help in one simple step
Send the link to someone who may need help. They stay in control: they can read it first, ask a question, or start Quick Help when they are ready.
1. Send the linkUse a normal message: “I thought this might help you.”
2. They decideYour friend can read it first, ask a question, or start Quick Help.
3. We check itIf their job goes ahead, we check whether a 5% thank-you applies.
Only share with people who may genuinely need help. To be counted, they should start through your referral link before booking.
Share help. Get a small thank-you if it works out.
Send your link to someone who may need friendly tech help. They choose what to do next. If their job goes ahead, we can check whether a thank-you applies.
Example: a AUD 300.00 job could mean AUD 15.00 as a thank-you after we check it.
Thank-yous are not guaranteed. To be counted, the person should start through your referral link before booking.
Thank-you guideSee what 5% can look like
Open this small guide only if you want example amounts. The person you refer still chooses whether to get help.
Example job amountPossible thank-you
AUD 100.00AUD 5.00
AUD 200.00AUD 10.00
AUD 300.00AUD 15.00
AUD 500.00AUD 25.00
AUD 1,000.00AUD 50.00
Keep it friendlyShare it as a helpful suggestion, not a sales pitch.
We check itIf the job goes ahead, we check the thank-you before confirming it.
No extra costThe referral thank-you does not add extra cost to the customer.
Example: a AUD 300.00 job could mean AUD 15.00 after we check it. It may not apply to cancelled, refunded, repeat, fake or self-made bookings. Simple sharing works best: “I thought this might help you.”
Fair sharingKeep referral thank-yous fair
Share only with people who may genuinely need help. Thank-yous are checked before they are confirmed.
Do not refer yourselfA thank-you is for sending someone else to friendly tech help, not for your own booking.
One real request is enoughDo not create the same booking more than once or ask someone to submit fake details.
Only completed work can countA thank-you may not apply if the job is cancelled, refunded, unpaid, unsuitable or does not go ahead.
Use your link firstTo help us count it, the person should start through your referral link before booking.
No pressure: do not promise a guaranteed thank-you, create fake or repeat bookings, refer yourself, or pressure anyone to book.
If there is immediate danger, call emergency services first
For suspicious messages, account access, remote access requests, banking/code pressure or unsafe behaviour concerns, pause and contact support before taking the next step.
Clearer help path
This page is tuned for a 9.3+ customer experience: simple next step, human review, safer detail guidance and no pressure.
Choose one path
Start with help, job check or support. You do not need to understand the whole system.
Reviewed by a person
Important details are checked before anything is confirmed.
Safe details only
Do not share passwords, PINs, MFA codes, banking codes or recovery codes.
How we keep pilot help safe and human-reviewed
We are building trust through plain explanations, team check, safe support paths and permissioned proof — not ratings, public complaints, price competition or automated dispatch.
Safe detail handling
We ask for useful details without asking customers to share passwords, banking codes, recovery codes or private access details.
Support copy includes privacy reminders and safer follow-up wording.
Clear next steps
Customers can see what happens next, how support works and where to check an existing request.
Connected to the customer journey, timeline and support confidence layers.
Permissioned proof only
Trust messages should explain the service clearly without fake testimonials, pressure tactics or public complaint walls.
Proof and known issue publishing stay manual and permissioned.
Manual resolution paths
If something is unclear, the safest path is a human support review rather than a hidden automated decision.
Known issues, launch notes and handover notes remain admin-only.
Good to know: We keep trust wording practical and honest. Nothing here creates rankings, ratings, quote comparison, public complaints or automated booking/dispatch.
Local trust and safety for people recommending us
We explain device privacy, human review, provider checks, support escalation and story approval for safer word-of-mouth referrals.
Local help, human reviewed
Every pilot request is treated as a local support conversation first, with a real person checking the next step before customers are pointed anywhere.
Device privacy reminders
Customers should describe the problem without sharing passwords, verification codes, recovery keys, banking codes or private access details.
Provider checks without rankings
Provider readiness is reviewed privately by admins. We do not show public rankings, customer-visible scores, price races or price-race competitions.
Clear support escalation
If something feels unclear, sensitive or urgent, support can review the thread and guide the safest next step manually.
Safe to recommend locally
Customers can recommend The Fixers because requests stay private, calm and human-reviewed — not because of pressure, rewards or public review mechanics.
Real stories only with approval
Before/after stories should only use real outcomes, privacy-safe wording and permissioned admin approval before any future public use.
Recommendation promise: Customers should feel comfortable sharing The Fixers because support is clear, private and human-reviewed — not because of rewards, pressure, rankings or public review mechanics.
What this means
Practical trust promises
Human-reviewed help
Requests, support notes and pilot issues are reviewed by a real person before any next step is suggested.
No automatic dispatch, provider assignment or customer-visible scoring.
Safe detail handling
We ask for useful details without asking customers to share passwords, banking codes, recovery codes or private access details.
Support copy includes privacy reminders and safer follow-up wording.
Clear next steps
Customers can see what happens next, how support works and where to check an existing request.
Connected to the customer journey, timeline and support confidence layers.
Permissioned proof only
Trust messages should explain the service clearly without fake testimonials, pressure tactics or public complaint walls.
Proof and known issue publishing stay manual and permissioned.
Manual resolution paths
If something is unclear, the safest path is a human support review rather than a hidden automated decision.
Known issues, launch notes and handover notes remain admin-only.
What we do not do
No marketplace pressure tactics
The controlled pilot is designed around safer manual next steps, not price-race marketplace mechanics.
Need help?
Use support for anything unclear
If a request, support reply, provider profile or next step feels unclear, use the support page. A human can review the context and keep the conversation in the right thread.
Please do not share passwords, PINs, recovery codes, MFA codes, banking codes or private access details.
Public beta questions
What does public beta mean?
It means the service is open to invited local customers while we keep requests reviewed by a real person and improve the flow before a wider launch.
Who can use it now?
Right now it is intended for invited customers in Melbourne's northern suburbs, Australia. If you are unsure, contact support and we will confirm what is possible.
What if I am outside the current area?
You can still ask support. We may not be able to help immediately, but we can confirm availability or suggest a safe next step.
What happens after I make a request?
Your request is checked by our team. There is no automatic booking, automatic provider assignment, price competition, public price-comparison display or price race.
What happens next
Choose the closest next step. A real person reviews important details before anything is confirmed.
Support stays calm, threaded and human-reviewed
Customers can ask support first or add context to an existing job without triggering automatic assignment, public complaints or public scoring.
Use the same thread
Existing job support keeps updates connected to the same customer story.
Safe fallback
If online saving is unavailable, customers should still see a plain-language next step.
No public pressure
Support remains private and checked by our team.
Support stays private, connected and checked by our team
Customers see plain next steps after submitting, checking a job or asking for help. The wording keeps support calm instead of making the customer start again.
After submitting
Confirm receipt, explain team check and show the safest follow-up link.
Existing job
Keep updates connected to the same job or support thread where possible.
Unsure what to share
Remind customers not to send passwords, codes, banking details or recovery information.
Start with the simplest customer path
The public surface now keeps the main customer choices plain: get help, check an existing job, or ask support first. Role links stay secondary so the page does not feel like a portal maze.
Get help
Use this when the customer has a device problem and wants the team to review the best next step.
Check request
Use this when the customer already has a job or reference and wants an update.
Ask support first
Use this when the customer is unsure what to choose or wants privacy guidance before sharing details.
Trust and safety
Keep reminders visible: no passwords, PINs, MFA codes, recovery codes or banking codes.