Preparing a controlled Charlotte-area launch Check your ZIP
Create account
Support designed around booking context

Help center

Useful answers without the runaround.

Browse the essentials for customers, helpers, accounts, payments, service boundaries, and safety.

SEARCHABLE HELP

Find the useful answer quickly.

Getting started

How to describe a household outcome

Choose the closest service, then include quantity, condition, access, timing, and what finished should look like.

Ask a follow-up
Requests

What makes a request ready for review

A supported service, useful scope, launch ZIP, future arrival window, address, and boundary confirmation are required.

Ask a follow-up
Pricing

How the customer total is decided

Vizubly validates the selected service on the server and keeps any later material change subject to customer approval.

Ask a follow-up
Photos

Share useful task photos privately

Use task-focused images without faces, documents, valuables, or unrelated personal information.

Ask a follow-up
Helpers

What happens after a helper application

Identity, screening, service eligibility, training, capability, and launch readiness must be approved before offers.

Ask a follow-up
Safety

When to pause or stop

Move to safety first, use emergency services for immediate danger, and use booking support when it is safe to do so.

Ask a follow-up
Coverage

Initial launch ZIPs

Booking is initially limited to 28031, 28036, and 28070 while Vizubly learns service by service.

Ask a follow-up
Accounts

Keep every booking in one account

Requests, schedules, totals, messages, task photos, checkout handoffs, and support context stay connected.

Ask a follow-up
ROUTE YOUR QUESTION

Who can we help?

For urgent safety concerns during an active booking, use the in-product safety path or local emergency services as appropriate.

CustomersRequests, accounts, and paymentsHelpersApplications, opportunities, and payoutsPartnersCommunity and commercial programs

Explore the story

Understand the whole experience.

Start

Begin with the issue—not the department.

Account, booking, payment, quality, cancellation, safety, accessibility, and helper questions should route from one understandable starting point.

  • Customer and helper paths
  • Urgent concern guidance
  • Accessible contact options

Designed with purpose

A system people can understand.

Every capability advances only when the supporting product, operations, trust, legal, analytics, and support work is ready.

01

Understand

Start with the outcome and see the boundaries before committing.

02

Describe

Guided questions turn a vague need into a workable request.

03

Coordinate

Status, messages, approvals, and support stay together.

04

Complete

Confirm the outcome, receipt, tip, review, and next step.

01Context

The story stays together

Support begins from the booking record.

02Ownership

A named next step

Cases route to the right operational queue.

03Learning

Patterns improve the system

Issues can inform policy, training, and product design.

Vizubly principle

“Tell the truth about what is ready. Make the next step clear. Build trust through the whole experience.”

Useful detail

What people ask before the next step.

Visit support

No. Contact local emergency services for immediate danger, then notify Vizubly when safe.

Be part of the launch

When life needs
an extra set of hands.

Tell us what kind of help you need, where you are, and when you may need it. Your response helps plan the controlled launch.