Skip to content
TheFixers + Your IT & Tech MatesClear brand promise

TheFixers is the customer entry point for local technology help. Your IT & Tech Mates helps review, coordinate and deliver requests safely.

You only need to start one request. Staff keep the right Quick Help, referral or support context attached behind the scenes.

Campus support page explain page

Help students find the right tech support without becoming the support desk.

Campus support pages are trusted connectors. They point students, parents, staff and local communities into existing Campus Help, Quick Help and referral pathways. They do not collect passwords, diagnose privately, quote jobs, take payment or promise outcomes.

Mobile support page handoff

When someone asks for help, send them to the existing Campus Help flow.

This keeps campus support pages as safe connectors, not a private support desk. It also avoids a second referral, support, quote, payment or assignment process.

Say: “Use Campus Help so the team can check the next step.”
Do not ask for passwords, login codes, bank details or private student files.
Do not promise price, timing, paid work, income or a guaranteed fix.
Use support if the request feels private, urgent or unclear.

Support pages guide people back to the checked campus flow.

Campus support pages can explain where to start, but they should not create private side arrangements, collect passwords, quote work, promise income or run their own support desk.

Say: “Please use Campus Help so the team can check the safest next step.”
Pause if the request includes payment pressure, private files, login codes, urgent safety worries or unclear consent.

What a campus support page does

Listen for common tech problemsLaptop, Wi-Fi, printer, email, login, study software and scam worries can start in the current Campus Help path.
Use approved linksCampus support pages point people to existing student, campus, referral or Quick Help links instead of creating a private side process.
Keep privacy safeNo passwords, banking codes, private files, one-time codes, medical details or account takeover.
Leave review to staffSuitability, risk, service next steps, payment and provider assignment remain staff-controlled.

Use the existing campus and student surfaces

This page is an explanation layer only. It reuses the current campus and student links so the student journey stays simple and staff can keep the same review controls.

Safe campus support page boundaries

Point people to the official path.
Use Campus Help, Quick Help or the approved referral link instead of collecting private details yourself.
Explain what the support page is not.
A campus support page is not automatically staff, a verified provider, a technician, a tutor or a payment collector.
Let staff check the request.
Safety, privacy, suitability, quote handling and provider assignment stay inside the existing system.
Use approved ambassador/campus links if sharing.
Referral source and local income handling must stay attached to current ambassador and referral tools.

Do not promise these things

No guaranteed incomeCampus support pages must not promise reward amounts, payment timing, jobs or commissions.
No guaranteed fixesDo not promise speed, outcome, availability, pricing or provider assignment.
No private troubleshootingDo not take over devices or accounts, ask for passwords or collect screenshots with private details.
No bypassing reviewCustomers and students should use the existing intake path so staff can check risk and next steps.

status and safety polish

Need to change, check or pause a referral?

Use the existing support path instead of creating repeat referrals. This keeps the person on one safe thread and reduces confusion on mobile.

link consistency polish

Every referral action stays on an existing checked link.

This controlled stage links only to current referral, student, campus support page and support pages. It does not add another referral system, matching path or support queue.

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.

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.

Campus support page referral path

When a campus support page is also part of the ambassador pathway, use the current campus and student referral surfaces. This build does not add a second referral tracker, QR system, share-code generator or reward calculator.

Best next step

If someone needs help now, send them to Campus Help or Quick Help. If someone wants to become a connector, send them to the ambassador eligibility and onboarding wrapper.

This page adds public explanation and links only. Existing campus, student, ambassador, referral, skill-tag and Quick Help systems remain the source of truth.

Not sure where to go next?

Use the ambassador and campus support page path guide to move between the existing explain pages, onboarding, referral tools, room guidance and help handoff without starting a repeat flow.

Trust evidence

What our trust notes mean

Reviews, referral proof, warranty notes and provider trust signals are shown only after staff have evidence to support them.

Please do not share passwords, banking codes, PINs or one-time codes in any request.

Student pathway

Campus support page launch boundary

Support pages can guide people to existing links. They should not collect passwords, quote work, take payment, assign jobs or promise outcomes.

Referral next steps

The next step should be clear before anyone continues.

Use this as a final mobile check: share the link, let the person accept or join when ready, and move questions to support rather than opening another process.

Referral help map

Final referral help map before the next support step starts.

Every action below points to an existing help page. This closes the student referral mobile loop without adding another process, payment path or provider step.