FleetOS Guide

Complete FleetOS product documentation - Zero-signup fleet service coordination

Version: 2.0 (Consolidated) Last Updated: 2026-01-08 Consolidated From: FLEETOS_README.md, FLEETOS_PRODUCT_OVERVIEW.md, FLEETOS_TONE_GUIDELINES.md

---

Quick Links

• Product Overview

• Technical Architecture

• Business Model

• Tone & Voice Guidelines

• User Flows

---

Product Overview

FleetOS is a zero-signup, WhatsApp-native service coordination platform connecting fleets with suppliers.

The Problem

• Fleet operators manage 10-50+ vehicles with constant service needs

• All coordination happens via unstructured WhatsApp messages

• Lost messages, missed quotes, forgotten follow-ups cost thousands

• Suppliers struggle to track which fleet asked for what, when

The Solution

• Each supplier gets a dedicated WhatsApp agent number

• Fleet managers text that number → FleetOS routes it → Structured request

• Both parties track everything in clean dashboards

• No app download required for fleets (100% WhatsApp-native)

Key Innovation

Zero-Signup Philosophy: Competing with email & WhatsApp. Must be AS EASY or easier.

Flow: Receive → Respond → (Name+Email if first time) → Done

---

Technical Architecture

Components

• Landing: components/fleetos-clean/CleanLanding.tsx

• Request Form: components/fleetos-clean/FleetRequestForm.tsx

• Supplier Signup: components/fleetos-clean/MinimalSignup.tsx

• Tracking: components/fleetos-clean/RequestTrackingPage.tsx

• Dashboards: Supplier & Fleet dashboards

Services

• AuthService: Magic link authentication

• InviteService: Two-sided invitations

• RelationshipService: Fleet ↔ Supplier connections

• ViralTriggerEngine: Growth moments (First Request, Momentum, Relief, etc.)

Database Schema

Key Tables:

• users - Authentication

• user_profiles - Extended data (role, name, phone, city)

• relationships - Fleet ↔ Supplier connections

• service_requests - Core value (requests with tracking)

• invites - Invite tracking

• notifications - Multi-channel delivery log

---

Business Model

Free Forever (Phase 0 - Current)

• ✅ Unlimited WhatsApp agent number

• ✅ Unlimited service requests

• ✅ Basic dashboard

• ✅ Invite unlimited partners

• ✅ Message history (90 days)

Goal: Build network effects. 10,000 users by Q2 2025.

Paid Add-Ons (Phase 1 - Q2 2025)

Pro Tier ($29/month)

• Advanced analytics

• AI quote extraction

• Multi-channel support

• Extended history

• Priority support

Enterprise Tier ($99/month, min 10 users)

• Multi-location management

• ERP integrations

• Compliance tools

• Custom workflows

• SSO/SAML

Embedded Fintech (Phase 2 - Q4 2025)

• FleetOS Pay: Net 30 terms (2.9% transaction fee)

• FleetOS Card: Branded fleet card (1.5-2% interchange)

• FleetOS Capital: Working capital loans (8-15% APR)

---

Tone & Voice Guidelines

Core Principle

FleetOS is infrastructure. Infrastructure operators trust calm, competent, grown-up language—not hustle-culture hype.

✅ DO: Infrastructure Language

Approved Vocabulary:

• System of record

• Routing brain

• Trusted operating layer

• Structured coordination

• Audit trail

• Compliance-ready

• Reliable

Approved Phrasing:

• "All tracked. Organized."

• "Complete service history for every relationship"

• "Save 2-4 hours/day on administrative follow-ups"

• "Free forever. No credit card."

❌ DON'T: Hype and Manipulation

Prohibited Words:

• Chaos, nightmare, amazing, incredible, revolutionary

• Game-changer, crush it, wow, perfect, insane, epic

• NEVER use urgency commands: "Stop [doing X]", "End the [problem]"

Prohibited Patterns:

• Artificial urgency

• Manipulative CTAs

• Hustle culture language

• Comparison attacks

Example Rewrites

BAD: "Stop losing track of service requests!" GOOD: "Every request tracked. Nothing lost."

BAD: "Join 10,000+ fleets crushing it!" GOOD: "Serious operators trust FleetOS."

---

User Flows

Supplier Onboarding

1. Land on FleetOS page

2. Click "Get My Free Agent Number"

3. Fill form: Name, Email, Phone, City, Service Category

4. Receive magic link email

5. Click link → Logged in

6. See assigned WhatsApp agent number

7. Share number with fleet customers

Fleet Request Flow (Zero-Signup)

1. Fleet texts supplier's agent number

2. FleetOS receives message

3. Creates service request

4. Notifies supplier via WhatsApp

5. Supplier responds

6. Fleet gets confirmation

7. First-time only: Fleet provides name/email for tracking link

Viral Moments

• First Request: Supplier's first request ("It works!")

• Momentum: 3rd relationship added ("Network growing")

• Relief: Request completed smoothly ("Professional service delivery")

---

API Reference

AuthService

// Send magic link
await AuthService.sendMagicLink({
  email: '[e-mail]',
  product: 'fleetos',
  role: 'supplier',
  profileData: { name, phone, city, fleetos_data }
});

// Verify magic link
const session = await AuthService.verifyMagicLink(token);

InviteService

// Create invite
const invite = await InviteService.createFleetInvite({
  fleet_id: 'USER_123',
  invitee_email: '[e-mail]',
  service_category: 'TIRES'
});
// Returns: { invite_code, invite_link, expires_at }

// Accept invite (auto-called during signup)
const relationship = await InviteService.acceptInvite(code, new_user_id);

---

Deployment

Production URL: https://fleetos.t420.com (planned)

Current: Deployed via Vite on localhost:3000

Configuration:

VITE_PRODUCT=fleetos
VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SENDGRID_API_KEY=SG.xxx
VITE_TWILIO_ACCOUNT_SID=ACxxx

---

Related Documentation

• T420 Ecosystem Guide - Overall architecture

• Development Guide - Setup & testing

• Features Guide - Viral engine, agentic workflow

• Shared Guide - Shared components

---

Version: 2.0 (Consolidated) Consolidated From: 3 source files (1,719 lines → streamlined) Status: Active Development For detailed history: See original files in git history or archive