Practical help center

Help should move owners to the right next step without route confusion

This page now supports builder-first workflows: launch the site, understand plans, manage visuals, and know where to get support.

Launch guidanceSupport routesAdmin media workflow
Help page illustration placeholder
Common owner paths

What help now needs to solve first

The help center is no longer just about claims and listings.

Choose the fastest route into launch for a new or existing business.

Understand when to stay on a simple site and when to expand into a store.

Know where hero visuals and campaign illustrations are updated in admin.

Move between pricing, setup, and support without restarting context.

Support expectations

What the team can help with

Use the support layer for high-value blockers, not for work the admin area is already designed to handle.

Clarify the right launch structure for products, services, or hybrid businesses.

Guide owners on language setup, trust content, and sales-channel choice.

Help teams replace placeholders with final vectors and images through admin media slots.

Point owners to the correct plan when the current structure becomes too limited.

Help questions

Questions that should be answered without support friction

These answers keep the help center aligned with the new builder position.

Where do we upload the final homepage images later?
In the admin media area. This rebuild adds dedicated marketing asset slots for the homepage and related public sections.
Can BizLink work for services and shops together?
Yes. The public surface is intentionally designed to support both service-led and product-led businesses.
What if we already have some public presence?
Use the owner launch route or create flow and migrate the strongest content into the new structured surface.
Does support replace the builder?
No. Support helps with decisions and blockers, but the product is being shaped so routine public-site changes stay self-serve.

Use help to unblock launch, then keep the public site moving inside the product

The goal is faster execution, not a dependency on manual support for every public-facing change.