Skip to content
Urgent support

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.

Verification

Prepare review details safely.

Keep private identifiers out of public copy and continue to availability when ready.

  1. StartBegin on the existing provider entry path.
  2. ServicesChoose the work you can safely support.
  3. VerificationPrepare review information without sharing private details publicly.
  4. AvailabilityKeep timing and service area realistic.
  5. ShowcaseUse permissioned proof and customer-safe examples.
  6. Work areaUse the existing reviewed board path only.

Provider-safe guardrail: this continuity layer only links existing provider pages. It does not start a separate work, account, payment or support process.

Verification statusAlmost ready

Prepare review details without exposing private information.

Use existing verification paths and keep sensitive identifiers out of public-facing copy.

Empty-state guide

No verification details are shown here yet. Prepare the information requested on the existing verification path.

Add availability

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.

Verification review

Verification guidance stays safe and understandable.

The mobile loop keeps verification privacy-safe while guiding providers to availability and support when needed.

Privacy safePrivate information is not exposed in public copy.
Recovery pathSupport is clear when blocked.
Continues cleanlyAvailability follows verification.
Next review stepContinue to availability

No public private-data prompt is added.

Verification recovery

Give a privacy-safe fallback for verification blockers.

When a provider is unsure about documents or checks, the page points to support and avoids public private-data prompts.

Document unclearAsk a question before uploading the wrong item.
Private detailsKeep identifiers out of public-facing notes.
Next linkContinue to availability only when ready.
If verification is blockedAsk about verification

This page does not collect, display or store new verification data.

Verification readability

Make verification steps easier to review on mobile.

Verification copy stays privacy-safe while making field spacing and next-step guidance clearer.

Privacy firstAvoid exposing private identifiers in public copy.
Readable promptsKeep requested details easy to understand.
One next stepAvailability remains the next link after verification.
After verificationAdd availability

Sensitive details stay on existing verification paths; no public identity data is added here.

Trust check

Prepare verification for team review.

Only add what is requested. Do not publish private document numbers, identity details or unrelated personal information.

More provider paths

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.

provider readiness

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 profile

Services 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 services

Verification 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 verification

Permissioned 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 guidance

Support 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 guidance
Important: This checklist is private readiness guidance. It is not a customer-visible score and does not rank providers.
provider journey

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:
  1. Confirm your service area and contact details.
  2. Add only services you can safely deliver.
  3. 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.
provider onboarding

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 profile

Services 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 services

Verification 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 verification

Availability 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 availability

Trust 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 guidance

Support 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 support
Manual 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.

Provider entry screen

Verification checks

Provider onboarding is separated from customer job requests. It captures verification, services, availability, showcase readiness and approved board access.

Provider flow

Provider entry

Separate provider onboarding screen.

Open
Provider details

Separate provider onboarding screen.

Open
Verification checks

Identity, insurance, WWCC-aware or role-specific checks where relevant.

Open
Services and skills

Separate provider onboarding screen.

Open
Availability

Separate provider onboarding screen.

Open
Showcase readiness

Separate provider onboarding screen.

Open
Next step

Separate provider onboarding screen.

Open
What happens next

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.