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.
Safe referral wording
Who can use this?
A student, family member, campus support page, teacher, local partner or friend can point someone to help. The referral should be a helpful introduction, not a promise of work, payment, speed, availability or outcome.
- Use the current referral and campus help links.
- Let the person choose what details they share.
- Do not ask for passwords, banking codes, medical details or private files.
- Use support when a request is urgent, private, unclear or already in progress.
validation polish
Check the referral details before you send them.
On mobile, keep the referral small and permission based. Use the existing form and only include details the person is comfortable sharing.
- Name, contact and a short help summary are enough to start.
- Do not include passwords, banking codes, recovery codes, medical details or private files.
- If details are sensitive or unclear, use support before submitting another referral.
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.
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.
Fair sharingKeep referral thank-yous fair
Share only with people who may genuinely need help. Thank-yous are checked before they are confirmed.
Referral links start through TheFixers and are reviewed with Your IT & Tech Mates. Referral details stay attached in the background so the customer can continue through one clear help path.
Trust wording is reviewed before it is shown
Public trust notes should be based on real review, referral, warranty or provider evidence, not self-claimed badges or automatic ranking.
Share friendly tech help
Send one simple link. The person you refer can accept it first, then continue to the Quick Help form when they are ready. They control what details they share.
Simple flow: copy the message, send it once, and let them choose whether to continue.
Best next step: preview the referral first if you want to check what your friend will see, then copy the message below.
Share the accept page first, not a separate booking form
The person you refer should accept the referral, then move into Quick Help with the referral details still attached.
Referral details help staff understand where the request came from. The repair request itself still uses the existing Quick Help path.
Share help, support real jobs, and keep the thank-you clear.
The best referral is easy: send one useful link to someone who genuinely needs help. If their suitable paid job goes ahead, your possible thank-you can be checked using the existing referral record.
Choose a message that sounds like you
People are more likely to trust a referral when the message feels natural. Pick one, copy it, and send it only to someone who may genuinely need help.
Copied. Send it when it feels useful.
Your link can stay connected without extra steps
When someone starts through your referral link, the existing referral details can stay attached to their Quick Help request. That helps the team review any possible thank-you fairly, without asking them to repeat the story.
A simple reason to share again
Send the link when it genuinely helps. A suitable paid job can create a possible 5% thank-you and send real work to the right support page.
Best next step: copy one natural message, send it to one suitable person, then let them choose whether to continue.
Copy and share your referral link
Use the link or the ready-to-send message below. The person you refer stays in control and chooses whether to ask for help.
Copied.
To help us count it, the person should start through your referral link before booking. Thank-yous are not guaranteed and may not apply to cancelled, refunded, repeat, fake or self-made bookings.
Privacy and safety
The person you refer chooses what details to send. Their private request is not shown back to you from this flow.
Please do not enter passwords, PINs, banking codes or one-time login codes.
Referral kept tidy
We keep the referral code consistent and avoid creating another record if these details already exist. If you already accepted this referral, continue from the same link instead of starting again.
Reference: not supplied
How it works
They see a plain “you’ve been referred” page first, with their choice clearly explained.
The referral is attached without showing their private request details to you.
Quick Help sends the request to our team before any next step is arranged.
Please do not share passwords, banking codes, PINs or one-time login codes in any form.
form safety polish
Keep the referral form light, clear and permission based.
Use the existing referral form only for details the person is comfortable sharing. A referral is an introduction to help, not a promise of work, payment, speed, availability or outcome.
- Start with name, contact and a short reason for the referral.
- Do not ask for passwords, banking codes, medical details or private files.
- Use support first when the request is urgent, sensitive, unclear or already in progress.
status and support polish
Need to check or correct a referral?
Use the existing support path. Do not submit the same referral again just to check progress, change contact details or ask a privacy question.
- Use support when details are wrong, repeatd or sensitive.
- Use the current referral share path for a clean new introduction.
- Use Campus Help when the person needs student or campus help now.
Safe handoff
Keep referrals simple and safe.
If the person needs help now, use Campus Help or Quick Help. If they are unsure, worried about privacy or already have a request open, use support before starting another path.