The E-booknow documentation page guides company administrators through the setup work required before a transportation business begins taking live reservations. It is written for owners, managers, dispatchers, and office staff who need a practical order of operations rather than developer documentation. The guide starts with account creation and then moves through the records that shape the reservation and dispatch experience.
A new company should first create the company admin account, confirm basic preferences, and add the vehicle types that customers and staff will use. After that, the setup process continues with service types, job types, rates, add-ons, taxes, company profiles, merchant accounts, and user access. Each section explains what the item controls and why it matters before a passenger or dispatcher creates a reservation.
The documentation also helps administrators avoid incomplete launch setups. A company should test at least one reservation before going live, confirm that rate calculations match the intended pricing policy, review payment collection, check reservation statuses, and make sure dispatchers understand how trips move through the dashboard. These steps reduce confusion once real customers begin booking service.
Use the documentation as a launch checklist and as a reference when the company changes operations later. If the fleet changes, if a new service type is introduced, if a DBA profile is added, or if payment behavior changes, the same setup sections can be revisited. The page is meant to keep company setup organized so the dashboard, booking flow, billing records, and dispatch workflow stay aligned.
Administrators can also use the guide to train new office staff. A dispatcher can review how reservation fields, pickup and drop-off details, vehicle classes, passenger records, driver assignments, and payment status labels work together before handling live customer requests. Managers can use the same sections to confirm that internal procedures match the way the E-booknow dashboard is configured.
The recommended setup order keeps important dependencies clear. Vehicle types should exist before rate testing, service types should be reviewed before booking links are shared, and merchant account settings should be checked before collecting payments. Completing these items early helps the company avoid missing prices, unavailable vehicles, incomplete customer records, and dispatch confusion after the booking widget is published.