Everything you need to know before your launch.

Yes. A delivered RideOps site can give customers a branded, mobile-friendly reservation experience on the operator’s own domain. The customer selects the trip details established in the launch scope and reviews the fare before submitting.

Yes. Fares can be calculated from configured routes, zones, trip types, vehicles, fees, and approved pricing rules. The customer sees the calculated amount before submitting the reservation.

Yes. One-way and round-trip workflows can be configured, including return details and pricing rules appropriate to the operator.

Yes. Available vehicle classes can display capacity, luggage limits, descriptions, and pricing. Essentials includes up to three configured vehicle classes.

Yes. RideOps can support controlled promotion codes with clear discount and adjusted-fare display. The number and rules included are confirmed in the launch plan.

Yes. The customer booking experience is designed to work across current desktop and mobile browsers.

The manager can present upcoming reservations, trip details, status, assigned driver, payment state, customer notes, and priority work in a mobile-friendly operating view.

Yes. Driver assignment and reservation-status workflows are part of the operating model. Exact statuses, permissions, and notifications are configured for the customer’s process.

The manager is designed for practical mobile access, including reviewing reservations, assignments, payments, trip details, and customer-update actions. A desktop remains useful for broader administrative work.

It can. Online card payments and an operator-controlled pay-driver option can be configured through approved buyer-owned payment accounts. Processing charges and provider requirements are separate from RideOps fees.

Configured passenger and luggage limits can warn or prevent a customer from choosing a vehicle that cannot accommodate the stated party.

Data migration is available for compatible source data but is not included in Essentials. The source, field quality, volume, and required cleanup must be reviewed before it is quoted.

Yes. RideOps can be configured with a fare-finder or trip-planning step that uses the operator’s approved routes, service zones, vehicle choices, and pricing rules before the customer continues.

Exports can be scoped for compatible reservation and operational data. The exact fields, format, permissions, and retention rules are confirmed during implementation.

Yes. Transactional confirmation and approved reservation-update emails can be configured using the customer’s business email and booking environment.

Yes, when SMS is included in the selected scope and the buyer’s messaging account, sender registration, transactional consent language, opt-out handling, and usage billing are ready. Essentials does not include SMS onboarding; Growth includes standard SMS onboarding.

Yes. The Growth and Custom scopes can include a direct driver-arrival notification workflow using the customer’s approved messaging setup.

Yes. A completed-ride workflow can direct customers to the operator’s own Google review page. RideOps does not create, filter, or guarantee reviews.

Not by default. Transactional reservation consent is not marketing consent. Promotional messaging requires a separately approved compliance and consent process.

Yes. The customer-facing experience is configured with the operator’s approved company name, identity, content, service area, and contact details.

The customer owns and pays for the domain, hosting, operational accounts, and customer data. RideOps retains its reusable software, methods, and system components and licenses the delivered components under the signed agreement.

Depending on scope and provider compatibility, RideOps can connect payment processing, SMS, business email, maps, calendars, accounting, analytics, consent tools, review links, and selected operational services. Optional integrations are quoted separately unless a plan explicitly includes them.

A supported QuickBooks Online connection can be scoped as an add-on. The buyer supplies the appropriate QuickBooks subscription and authorizes the connection.

Mapping, distance calculations, and calendar connections can be scoped when the selected provider and workflow are compatible. Provider subscriptions and usage charges are separate unless the launch plan says otherwise.

Yes. Privacy-conscious analytics and consent tools can be configured to match the operator’s approved site practices. The operator’s production privacy notice must describe the services actually enabled.

A mobile-friendly website is standard. A progressive web app or installable shortcut can be scoped when the operator needs a more app-like experience; device behavior varies by browser and operating system.

Yes. Custom pricing, workflows, integrations, migration, permissions, content, and design can be scoped through the Custom plan or a written change order.

Essentials is designed for a focused one-to-three-vehicle operation. It includes up to three vehicle classes and ten configured routes or fare zones, with a $1,495 setup fee and $149 monthly care.

Growth includes the Essentials foundation plus broader route, vehicle, and business-rule configuration, standard SMS onboarding, the driver-arrival workflow, and up to one hour of routine configuration changes per month. It is $2,995 for setup and $199 per month.

Custom is appropriate for complex fare logic, extensive routes or fleets, data migration, accounting or other integrations, specialized workflows, or substantial design and development. It starts at $4,995 for setup and $249 per month.

Yes. Plan on approximately $600 per year, paid directly to providers, for the domain, managed WordPress hosting, Amelia, and business email. Payment processing, SMS usage and registration, taxes, premium services, and optional integrations are separate.

The standard schedule is 50% at agreement and project start, 30% when the configured staging system is ready for acceptance testing, and 20% before production launch. The signed statement of work controls the final schedule.

A focused Essentials launch is generally planned for three to four weeks after the deposit and complete customer materials. Growth and Custom projects are generally planned for four to six weeks or according to the written scope. Provider approvals and customer readiness can affect timing.

Every plan includes managed updates, routine backup and uptime oversight, regression checks after material managed changes, and support for the delivered configuration. Essentials includes focused maintenance; Growth includes up to one hour of routine configuration changes monthly; Custom support follows its written scope.

No. Standard support hours are 8:00 a.m.–8:00 p.m. Eastern Time, with response targets based on issue priority. Emergency or after-hours coverage requires a separate written add-on.

The recommended managed hosting baseline includes SSL, daily backups, malware scanning and removal, a firewall, WordPress updates, and CDN services. Exact protection and retention depend on the buyer’s selected provider and must be confirmed at launch.

No. RideOpsSystems.com is a sales and demonstration website. A buyer receives a separately configured operating site on the buyer’s domain and accounts.

No. It uses fictional information, stores temporary demo state in the visitor’s browser, sends no email or SMS, creates no charge, and automatically clears demo changes after two hours.

Yes. The interactive demo lets visitors switch between light and dark mode, and the preference stays on that browser until changed or cleared.