Visible services
0Service entries currently available as request-oriented support paths.
Services HubRequest-first support path
Services overview MVP
This page validates request-oriented service positioning, directory-level content slots, and the bridge from self-serve content into direct help.
Tell us what you need in China, and we help arrange the right support. This page is for choosing the right direction, understanding the process, and setting clearer pricing expectations before any payment step.
Human-reviewed requestsQuote before paymentSupport matched to context
Service types
0Distinct support categories already modeled in the current directory.
Pricing path
0Pricing modes are visible, but the final quote still follows request review and scope confirmation.
Why this page exists
Not a pay-now catalog. It is a low-pressure entry point for choosing a service and understanding how matching and quote confirmation work.
How this works
A clearer path from request to payment
The service flow is meant to reduce pressure and ambiguity. The page explains the path before asking for commitment.
Choose the closest service type
Start with the nearest fit. The goal is not perfect labeling, but a practical starting point for review.
Tell us your needs
Share the city, timing, context, and constraints that actually shape the request.
We review and match
Requests are reviewed by a human instead of being treated like a fixed package checkout.
We confirm scope and pricing
The scope is clarified before any payment step, especially when the support need is situational.
Review and pay
Payment belongs after review and quote confirmation, not at the start of the page journey.
Choose a service type
Find the closest support path
Pick the nearest fit, not a perfect label. The real request is reviewed in context on the next step.
No services yet
Create service entries in Payload admin to populate the service hub.
Pricing and trust
Explain the path, not just the offer
This hub needs to manage expectation, trust, and next-step clarity. That is the point of the middle modules.
Pricing and payment expectations
•
Guidance first, not final quoting
This page sets pricing expectations. It does not replace a real scope review or final quote.
•
Service detail pages go one layer deeper
A detail page can show starting guidance, common pricing factors, and when custom scope is likely.
•
Payment happens after scope confirmation
The commercial path stays visible without pushing the user to pay before the request is understood.
Why people use this page
•
They want fewer mistakes
They want human support for situations where misunderstanding or poor coordination has a real cost.
•
They want a clearer next step
They are deciding whether they need direct support, not just more reading.
•
They want confidence before paying
They want to understand fit, scope, and pricing path before the commercial step.
What you can tell us in your request
•City in China
•Date or date range
•People involved
•Main practical goal
•Budget range
•Any time-sensitive or difficult part of the situation
How matching and support arrangement works
•The request is reviewed in context instead of being treated like a generic directory click.
•Timing, location, people involved, and the real support need affect how the next step is proposed.
•When needed, related services, guides, or toolkits can sit on the same path instead of forcing one rigid model.
•When needed, the quote is confirmed before the user is asked to pay.
Why this is different
Not just another directory listing
The point is not only to find someone. The point is to make the support path easier to understand and easier to trust.
Someone reviews the real request
The request is checked in context instead of leaving the user to guess which listing fits alone.
Support can be coordinated across steps
Language help, planning, trip support, and student arrival needs can be handled as one practical path.
The commercial path is clearer
The user sees guidance first, then quote confirmation, then payment, rather than being pushed to pay too early.
Common questions
FAQ for the listing layer
Service detail pages handle service-specific FAQ. This layer only answers the repeated questions about process and pricing path.
Will I see a price before payment?
Yes. Pricing guidance can appear earlier, but the final quote is confirmed only after the request and scope are reviewed.
Why is there no pay-now button on this page?
Because these services are request-led. The right time for payment is after the scope is clarified and the quote is confirmed.
Can guides or toolkits still be the right first step?
Yes. Some needs are better solved by reading or a structured toolkit before direct support is necessary.
What should a good request include?
City, timing, people involved, practical context, and any budget or constraint that changes the support scope.
Related content
Guides and toolkits that support the service path
Service pages should not sit in isolation. They should connect back to guides and toolkits that warm up the request.
Need context before choosing a service?
Start with guides if the situation still needs explanation before a direct request.
Open GuidesNeed a lighter-weight bridge first?
Use toolkits when the user still wants structure and reusable assets before human support.
View ToolkitsReady to choose the closest support path?
Move into a specific service detail page and continue with a clearer request-oriented next step.
Pick a Service