A complete operating wiki for Turo fleet hosts.

Overview

Registration creates the client account that owns the fleet workspace. The user should confirm their name, email, company information, and password before entering the HostFleet environment.

Login is the gateway to the user workspace. After authentication, the user sees the HostFleet navigation, page title, search/actions area, theme controls, and account menu.

The expected first successful result is access to Dashboard with the MyHostFleet visual experience in light or dark mode.

Buttons and controls

Expected result

A user reaches the HostFleet dashboard, sees the correct company/user context, and can move through the workspace confidently.

Operator notes

• For training material, use demo examples and avoid showing real guest names, phone numbers, reservation IDs, or complete VINs.

Overview

Billing controls whether the fleet workspace can remain active and how vehicles are counted for the monthly subscription.

The billing view should explain the current plan, active vehicles, subscription status, payment status, and available account actions.

In mobile mode, Billing should be reachable from Settings and should return cleanly without changing the Settings tab layout.

Buttons and controls

Expected result

The user understands whether the account is active, which vehicles are billed, and how to manage payment without leaving the HostFleet experience unexpectedly.

Operator notes

• Archived/deleted vehicles should not be counted as active operational vehicles.
• Billing information should be reviewed only from the account owner or authorized billing contact.

Overview

The Turo integration is the bridge between the host’s Turo account and HostFleet. It supplies vehicle inventory, reservations, guest context, and messages when the integration is connected.

A new account should connect Turo before importing vehicles. The sync action refreshes known Turo vehicles and booking/message data available to HostFleet.

When importing vehicles from Turo, HostFleet should refresh the Turo vehicle list first, show the "Refreshing Turo vehicles..." loading state, then display importable vehicles.

Buttons and controls

Expected result

Turo appears as connected, new Turo vehicles become available for import, and booking/message synchronization can run without manual spreadsheet work.

Operator notes

• If the import button appears while Turo is disconnected, the visibility rule is wrong.
• If new Turo vehicles do not appear after Sync Data, try refreshing again and confirm that the Turo connection still shows as active.

Overview

The setup wizard appears for new accounts that are ready to begin operations. It is designed to help a host complete the first setup without guessing what to do next.

The first screen explains the purpose of the wizard and previews the steps: connect Turo, create or import vehicles, add integrations, match integrations to vehicles, and finish with a complete sync.

The wizard should not interrupt billing setup. Once the account is ready, it remains available until completed or intentionally disabled for that tenant.

A host can also open the wizard again from Settings when they want to repeat the guided setup path or help another user understand the onboarding flow.

Buttons and controls

Expected result

A new host finishes the wizard with Turo connected, vehicles available, integrations prepared, vehicle matches reviewed, and the first full sync complete.

Operator notes

• The wizard is a user helper, not a technical checklist. Use simple labels and visual progress so the host always knows the next step.
• If the Turo login window is closed before finishing, the connection attempt should stop cleanly and the wizard should return to a usable state.
• Loading screens inside the wizard should use the MyHostFleet logo animation for consistency.

Overview

Vehicles are the core objects of HostFleet. A vehicle can be created manually or imported from Turo after synchronization.

The list displays the vehicle photo, title, year/make/model, status, plate/VIN data, fuel/battery telemetry, last seen time, and separate actions for vehicle details, service, and commands.

A small optimized vehicle image is used across compact views and map pins so pages load faster and broken images are less likely.

Deleting a vehicle removes it from active work areas and reports. If the same vehicle is added again in the same account, HostFleet can bring that vehicle back with its account history available to the host.

Buttons and controls

Expected result

The fleet list stays dense and readable, vehicle images are large enough to identify the car, deleted vehicles vanish from every operational view, and command actions are clearly separated.

Operator notes

• Do not run real lock/unlock/honk commands during documentation unless explicitly authorized.
• If telemetry only reports that something is open without item-level detail, describe it as "one or more openings reported open" instead of inventing doors/windows.

Overview

Dashboard is the first operational view. It combines fleet status, vehicle cards, search, status filters, map pins, telemetry, and quick actions.

The map uses clear map colors in both light and dark mode so geography remains readable. Vehicle pins use the optimized compact vehicle image.

On mobile, the map remains fixed near the top and the vehicle list scrolls independently. Vehicle action buttons move into a modal to avoid overlapping card data.

Buttons and controls

Expected result

A host can answer: where are my cars, which ones are active, which need attention, and what action can I safely take next.

Operator notes

• Clusters were intentionally removed; pins should stay at their vehicle locations.
• Dashboard should look the same whether the user opens it directly or arrives from another view.

Overview

Bookings organize reservations imported from Turo or maintained inside HostFleet. Cards and tables show the guest, vehicle, booking number, dates, status, delivery location, and operational notes.

The detail modal lets the user review or edit booking data, inspect toll information, and confirm vehicle assignment. The vehicle select must remain populated after a page refresh.

The Today button scrolls the booking list to the current day so a host can jump directly to work that matters now.

Buttons and controls

Expected result

Bookings are searchable, current-day work is easy to reach, tolls use compact summary space, and selected vehicles remain visible even after refresh.

Operator notes

• Long status badges should never cover the booking number or vehicle name on mobile.
• Modal labels should be clear, consistent, and match the selected language.

Overview

Calendar shows the fleet over time so hosts can see reservations, gaps, and availability without opening each booking.

Filters include status, multi-select vehicles, and search. Search should filter vehicles as well as visible calendar rows.

On mobile, the vehicle column is compact: vehicle image plus plate, while day columns are sized so at least five days are visible without creating absurdly wide columns on large screens.

Buttons and controls

Expected result

A host can quickly know which cars are booked, available, or in progress across a practical time window.

Operator notes

• Horizontal scrolling must work on desktop and mobile.
• The mobile legend is intentionally hidden to save space when colors/status are already understandable from context.

Overview

Turo Messages centralizes guest conversations imported from Turo. The list shows recent conversations, guest names, reservation context, vehicle, last message, and pagination.

The chat modal/view shows guest and vehicle identity at the top, booking start/end/location below, message history in the middle, and a fixed typing bar at the bottom.

Message templates reduce repetitive typing. Dynamic keys insert booking/guest/vehicle values into templates so hosts can respond consistently.

The AI message assistant helps draft a reply from the guest conversation, improve a message already typed, match the guest language, and shape the response style so hosts can answer faster while staying consistent.

Buttons and controls

Expected result

Only the conversation list scrolls on mobile list view, only the message area scrolls in chat, and the typing bar always stays fully visible.

Operator notes

• Use real pagination, loading only the first 10 conversations initially on mobile.
• Never expose real guest conversations in public screenshots; use demo text or sanitized captures.
• AI suggestions should be reviewed by the host before sending, especially when the message involves policies, fees, damage, or trip changes.

Overview

Shared Access creates temporary guest links that grant only selected vehicle actions during a defined access window.

The internal Shared Access list lets hosts create, review, delete, and manage links. The guest-facing page shows the vehicle photo, plate, time remaining, allowed commands, and Turo listing link.

The feature is designed for secure, limited access. A guest should never receive broad account access, only the specific vehicle actions approved by the host.

Buttons and controls

Expected result

The host can issue a limited link, the guest sees a premium mobile digital-key experience, and expired/deleted links stop working.

Operator notes

• Shared links should be revocable, scoped, and time-limited.
• For public screenshots, sanitize guest name, vehicle plate, and vehicle photo if they came from real production use.

Overview

Customers collects guest records and helps hosts review who booked, what vehicle they used, and how to reach the related reservation or Turo profile.

The list should use compact, readable cards on mobile with proper light/dark colors, equal action button sizing, and no wasted vertical space.

Buttons and controls

Expected result

A host can recognize a guest quickly, understand their booking relationship, and jump to related reservations without hunting through Turo.

Operator notes

• Customer cards should look the same whether the user opens Customers directly or arrives from another view.
• Avoid capturing real guest data in documentation.

Overview

Fleet Costs records operational expenses: maintenance, repairs, fuel, insurance, registrations, tolls, recurring costs, and custom expenses.

The New Cost modal supports vehicle, booking number autocomplete, vendor, invoice, amount, odometer, dates, recurrence, additional details, and receipt attachment.

Receipt attachments let the user keep proof of expenses with the cost record, so receipts can be reviewed later from HostFleet.

Buttons and controls

Expected result

Expenses are searchable, receipts are easy to review, recurring costs stay understandable, and the fleet cost history remains organized.

Operator notes

• Vendor and invoice fields should sit side by side to save space.
• Use the receipt viewer from HostFleet instead of keeping separate receipt links in notes.

Overview

Income summarizes revenue for the selected period, normally defaulting the reservation table to the current month.

The view includes year/month controls, search, vehicle/status filters, reservation revenue, Turo/CSV import actions, and print/share report options.

On mobile, income should be more graphical and summary-driven instead of forcing dense tables into a narrow screen.

Buttons and controls

Expected result

The host sees current-month reservation income by default, can search the reservation table, and can print/share a clean report.

Operator notes

• The search bar must behave like the rest of HostFleet searches.
• Dropdowns should not overlap adjacent filters or become tiny on mobile.

Overview

Reports turns fleet activity into yearly summaries, charts, cost/revenue breakdowns, and printable/shareable reports.

The year selector should show only years that have available data and should match adjacent buttons in size and visual style.

On mobile, reports should hide complex filters by default and favor simplified charts/cards over wide tables.

Buttons and controls

Expected result

A host can understand yearly fleet performance without spreadsheet reconstruction, and print/share output looks aligned and professional.

Operator notes

• Avoid double select arrows or nested select silhouettes.
• When mobile screen space is limited, charts should communicate the same information with fewer numbers.

Overview

Geofences define important places or areas and connect vehicle location to operational awareness.

The view includes a clear map, a list of geofences, vehicle counts, type, radius/points, enter/exit notification settings, active switch, edit, and delete.

On mobile, geofence rows should be compact lists with name and vehicle count on the same line, then organized metadata below.

Buttons and controls

Expected result

A host can create and manage zones, see how many vehicles are affected, and keep the map readable in light and dark themes.

Operator notes

• Maps should generally keep light map colors for legibility unless a proper dark tile style is intentionally selected.
• Cards/lists should not visually cut off action buttons.

Overview

Notifications gives the host a recent activity view with summary cards, filter controls, activity table/cards, and pagination.

The Summary and Filters topbar buttons must adapt to light/dark mode and behave consistently whether the user refreshes the view or navigates into it.

Buttons and controls

Expected result

The host can inspect recent operational events without visual theme breaks or controls that disappear in dark mode.

Operator notes

• Filters should collapse cleanly on mobile.
• Notification types should remain understandable without relying only on color.

Overview

Settings controls the behavior of HostFleet: theme, notifications, Turo Connect, AI assistant preferences, maintenance intervals, vehicle actions, shared access, booking buffer, message templates, and billing navigation.

Mobile tabs should be touch-scrollable and compact: inactive tabs can show icon-only while the active tab shows icon and text.

Notification choices should use switches, not checkboxes. Vehicle action settings should be presented as a list for readability.

Message templates should use a dynamic key modal picker so the user can find and insert keys without scrolling up and down through a raw list.

AI assistant settings let the tenant enable or disable the assistant, choose the provider/model, select the response language behavior, choose a response style, save the access key, and test the connection before the assistant appears in Turo Messages.

Buttons and controls

Expected result

Settings feels like a compact control center rather than oversized cards. The user can move between tabs, configure automation, and return from Billing cleanly.

Operator notes

• Dark mode compatibility matters here because Settings contains many nested components and modals.
• Labels should be clear, consistent, and shown in the selected language.

Overview

Company and Profile pages should feel like part of the same MyHostFleet workspace as the rest of the product.

Company contains account/company details, country, default language, and optional custom fields. Custom Fields should be hidden when there is nothing to show.

Profile contains personal details, avatar, password change, and notification preferences. When no profile image exists, initials should be centered, readable, and properly contrasted.

Buttons and controls

Expected result

The user can manage company and profile data without losing HostFleet navigation, and every form works in light and dark mode.

Operator notes

• Select dropdowns need overflow/portal behavior or enough visible space to avoid clipping.