Provider guide
Start, then continue through the provider flow.
The mobile guide keeps provider entry, services, verification, availability, showcase and support connected.
- StartBegin on the existing provider entry path.
- ServicesChoose the work you can safely support.
- VerificationPrepare review information without sharing private details publicly.
- AvailabilityKeep timing and service area realistic.
- ShowcaseUse permissioned proof and customer-safe examples.
- Work areaUse the existing reviewed board path only.
Next stepSet your services
Provider-safe guardrail: this continuity layer only links existing provider pages. It does not start a separate work, account, payment or support process.
Provider guideReady to continue
Follow the setup steps before checking work.
This mobile guide keeps provider entry, trust notes and empty states clear while reusing the current provider paths.
Empty-state guide
Nothing is waiting here yet. Continue through services, verification, availability and showcase first.
Start provider entry- Start with services
- Prepare verification safely
- Use the existing job board path
Provider-safe note: this panel only clarifies status, trust and empty states on existing provider pages. It does not start a separate work, account, payment or support process.
Provider final mobile review
Provider mobile start path is ready for review.
The segment start page now connects setup, support and board guidance using existing paths only.
Review setupOpen provider entry
This is the final review layer for the current provider mobile UX/UI path.
Provider recovery
Keep a safe fallback close to provider setup.
Provider start pages now explain what to do if a setup step, board or support path feels unclear.
Fallback pathOpen support
This only clarifies fallback copy on existing links.
Provider path readability
Keep provider setup readable before checking work.
The provider segment start page now has mobile guidance for forms, tap targets and clear next actions.
Continue setupOpen provider entry
This uses the current provider/customer-segment link and does not add a repeat provider system.
Provider discovery
Provider steps in one mobile-friendly guide.
Use this guide to move between existing provider entry, verification, services, availability, showcase and support paths.
Start as a providerUse the existing provider entry path for interest, role fit and next steps.Services and skill fitKeep services plain-English, specific and manually reviewable.VerificationPrepare evidence for human review without exposing private identifiers.AvailabilitySet realistic service area, timing and contact expectations.
More provider paths
Provider profileReview public-safe profile basics and provider pathway guidance.Showcase readinessPrepare permissioned proof, examples and profile confidence.Approved work areaUse existing board access screens only when review allows it.Ask a questionAsk for help if a service, profile, verification or board step is unclear.
Team review guardrail: this guide reuses existing provider, service, support and board paths. It does not start a separate work, account, payment or support process.
Easy to use on mobile: read the short summary, then choose the safest next step.
Provider readiness checklist
Use this checklist to prepare your profile, services, verification, permissioned proof and support path before relying on customer-facing trust signals. It helps you get ready without creating ranking, price competition or price-race pressure.
Profile basics
Customers can understand who you are, where you help and how to ask a question.
Ready when:Name, service area, contact path and plain-language intro are complete.
Review profileServices you can safely support
Your services are described clearly without overpromising or using confusing technical wording.
Ready when:Each service has a simple description, safe scope and next-step wording.
Review servicesVerification and team review
Admin can check your readiness before customer-facing trust signals are relied on.
Ready when:Required verification details are provided and waiting for, or have passed, team review.
Review verificationPermissioned proof only
Any proof, testimonial or example work is permissioned and approved by our team before public use.
Ready when:Proof is either permissioned and reviewed, or the page shows a safe no-proof-yet fallback.
Review proof guidanceSupport and escalation clarity
Customers know how to ask a question, add details or raise a concern without sharing private codes.
Ready when:Support links and safe-contact guidance are visible before real customer work.
Open support guidanceImportant: This checklist is private readiness guidance. It is not a customer-visible score and does not rank providers.
Provider path: get ready, stay clear, wait for approval
Use this path to explain the services you can genuinely support, complete verification, and prepare customer-safe proof before any customer work is shown or assigned.
Keep the journey consistent:
- Confirm your service area and contact details.
- Add only services you can safely deliver.
- Complete verification and trust/proof readiness before customer work.
Guardrail: This is not a provider comparison, price competition, price competition board or price competition. Work remains controlled by approval and team review.
Offer help clearly, safely and with team approval.
Add the services you can genuinely provide, confirm your area and keep approval steps clear before work is shown or assigned.
One option is still being checked, so this card is using the safest available link.
What happens next?
- Confirm your contact and service area.
- Add the services you can support.
- Complete manual verification before customer work.
This does not rank providers, compare bids or start price competition.
Provider onboarding completion polish
A calm completion guide for provider pilot readiness: profile, services, verification, availability, permissioned proof and support path. Everything remains human-reviewed.
Profile basics are clear
Make sure your name, service area, short intro and contact pathway are easy for the team to understand before pilot work is reviewed.
Ready when:Profile details are readable, current and do not promise unsupported services.
Review profileServices are easy to review
Keep service descriptions plain-English and specific. The admin team should be able to see what you can safely help with and what needs discussion first.
Ready when:Services are written clearly without price-race, price competition or comparison language.
Review servicesVerification is ready for team review
Upload only the evidence requested and avoid private codes or unrelated personal identifiers. A person reviews documents before they are trusted.
Ready when:Required evidence is present or there is a clear reason it still needs manual follow-up.
Open verificationAvailability expectations are sensible
Use availability notes to help the team plan manual follow-up. This does not create automatic dispatch or guaranteed booking.
Ready when:Availability wording sets realistic windows and avoids instant-response promises.
Review availabilityTrust proof is permissioned
Only share examples, proof or testimonials that can be safely reviewed and permissioned before public use.
Ready when:Proof is safe to review or the page uses a calm no-proof-yet fallback.
Review proof guidanceSupport path is visible
Know where to ask questions, add missing details or flag a blocker. Keep support in the same thread where possible.
Ready when:Provider knows the support link and does not need to guess the next step.
Open supportManual pilot guardrail: This guide helps providers complete their details for human review. It does not rank providers, compare quotes, create price competition, auto-book customers or automatically assign work.
Providers / screen 1 of 5
Provider entry
Capture provider details, role and service area.
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.
You were referred by someone who wants to help
You can look around first. Starting Quick Help does not mean paid work starts immediately; we check the request and explain the next step.
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.
Your referral link has been kept
You came through a referral link. You stay in control, and paid work does not start until the next step is clear.
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 guideA thank-you of up to 5% may apply
Open this small guide only if you want example amounts. The person you refer still chooses whether to get help, and any thank-you is checked after a paid job is completed.
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 they book and complete a paid job, we check whether a thank-you applies before confirming it.
No extra costThe referral thank-you does not add extra cost to the customer.
Example: a AUD 300.00 completed paid job could mean up to AUD 15.00 after we check it. It is not guaranteed and may not apply to discounted, cancelled, refunded, unpaid, repeat, fake, self-made or ineligible bookings. Simple sharing works best: “I thought this might help you.”
Fair sharingHow we keep referrals fair
You stay in control. Referrals are checked so the person who shared the link is only thanked when the rules allow it.
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.
We will review the safety concern carefully
The team reviews the information, looks for the safest next step, and contacts you if more detail is needed. Keep screenshots or messages if safe.