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.

Ask a question to check it Worried About a Scam?Report a safety concern

Service fit

Choose work you can safely support.

Describe service areas plainly so review and customer expectations stay clear.

Next stepPrepare verification

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

Service statusChoose work you can support

Show the work you can safely support.

Keep service names practical and avoid over-promising. Customers should understand what help is available.

Empty-state guide

No services selected yet. Add the work you can support, or come back when you are ready.

Prepare verification

Use plain service labels
Avoid unsupported promises
Keep service area details current

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.

Services review

Service setup has final mobile guardrails.

Providers can choose work, read clear notes and continue without unsupported matching or booking promises.

Readable choicesServices are easier to scan.

Safe wordingNo unsupported work promises are introduced.

Next actionVerification remains the next step.

Next review stepContinue to verification

Service choices remain on existing service links.

Service recovery

Handle missing or unclear service choices.

Provider service recovery keeps the message practical: add only the work you can support or ask for help.

No service yetAdd the work you can safely support.

Too broadKeep service wording specific and practical.

Unsure fitUse support rather than guessing.

If service choices are unclearAsk about services

No service matching or booking promise is added.

Service form readability

Choose services with clearer mobile spacing.

Use plain service choices and readable descriptions so providers can review what they can support before continuing.

Service labelsKeep service wording practical and easy to scan.

Large actionsActions stay comfortable for thumb taps.

Review before nextProviders are reminded to avoid unsupported promises.

After servicesPrepare verification

This does not add service matching, booking or dispatch logic.

Service fit

Describe what you can safely help with.

Keep service wording specific, local and easy to review. This does not create automatic matching or price competition.

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.

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.

Continue provider setup Review verification

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.

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.

Open provider start Check verification Open

Provider entry screen

Services and skills

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