Get your site ready for the first real job

1. Choose the workspace for this operation

A site is where your team manages its work and settings. Before entering a catalog or importing people, confirm the site name, timezone, currency, units, and who should have access. This prevents a correct setup from ending up in the wrong workspace.

Follow Manage organizations and sites. If the terms are new, read Jobs, stops, and routes first.

Ready when: the team can identify the right site and knows who is responsible for its settings.

2. Define the work you actually sell

Choose a service a customer can understand, such as scheduled parcel delivery. Add another service only when the promise or operating needs are meaningfully different.

• Set up service types with useful descriptions and realistic time on site.
• Define handling and equipment requirements when the work needs particular capabilities.
• Set customer prices, including a default rule and any relevant zone or option charges.
• Decide where you operate and what should happen outside normal coverage.

Ready when: you can explain what the service includes and compare the quote for a known job with the expected calculation.

3. Prepare the people and vehicles

A record in the Dashboard is only part of readiness. The driver needs to sign in, receive work, and use the right vehicle and capabilities.

• Follow the Driver App walkthrough, including location and notification permissions.
• Choose vehicle types and transport modes that reflect the fleet.
• Set driver earning rules when you use RouteIQ to calculate pay.
• Use custom fields for recurring business details and CSV imports when you already have a roster.

Ready when: a test driver can sign in, go on duty, and be selected for the example work.

4. Decide how work moves through the team

Agree who makes an assignment, whether a driver must accept it, and what the customer-facing states mean. Start with a process you can observe before expanding automation.

• Choose a dispatch method and, when useful, set up automatic dispatch.
• Choose meaningful job statuses without changing their underlying lifecycle meaning.
• Set route and stop timing rules around real customer commitments.
• Choose proof of work that answers a handoff question, then test it on a new job.

Ready when: the dispatcher and driver agree what to do when a job is offered, delayed, completed, or cannot be completed.

5. Prepare what customers see and receive

A clear booking experience should tell customers whose service they are using and what they can expect. Updates should help them act, such as being ready for a handoff.

• Prepare the Customer App and choose signup and location-sharing policies.
• Set useful customer updates and check the tracking page.
• Create a Booking Kit once the booking destination is ready.

Ready when: someone using a customer account can recognize your business, request the right service, and understand the tracking information.

6. Connect the services your workflow needs

Use Choose which services to connect to identify your mapping, messaging, payment, or other needs. Verify one customer or driver action after each connection; a saved credential alone does not prove the workflow works.

If you connect an order system, give it a dedicated API key and use webhooks for event updates. Review your plan and usage separately from the prices you charge customers.

Ready when: every connection has an owner and a successful check of the feature it supports.

7. Rehearse a complete job

Use a test site and people who expect the test. Keep real customer notifications and payment collection out of the rehearsal unless those actions are deliberately part of your test.

1. Create one representative job with resolved addresses, realistic timing, and clear stop instructions.
2. Check the quote, eligible driver, vehicle, and any required proof.
3. Dispatch it and follow the driver's acceptance and stop sequence.
4. Open the customer view and confirm the updates and location detail match your policy.
5. Complete the test flow, including proof and payment only where intended, and inspect the final job and any expected earning record.
6. Try one exception: an unavailable driver, an address outside coverage, or missing required proof. Confirm who handles it.

Ready when: you can trace the same job from request to final outcome and explain every unexpected result. Use Audit Log for supported events when you need to investigate a change.

Before you share the booking link

• The service, price, coverage, and booking destination are correct.
• Drivers and dispatchers know their responsibilities and the exception process.
• Customer messages reach the intended test recipient without unnecessary duplication.
• Required proof, access policies, and timing rules have been tested on a new job.
• Someone owns subscription billing and each connected provider account.

Then share the booking link or QR material with the people you intend to serve. Add more services and automation as the operation needs them.