FleetOS Quick Start - Test What We Built

Fast track to testing the complete flow in 5 minutes.

---

⚡ Quick Setup (5 minutes)

1. Check Supabase Credentials

Open .env and verify these are filled:

VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SUPABASE_ANON_KEY=your-anon-key-here

Don't have Supabase yet?

1. Go to https://supabase.com

2. Click "Start your project"

3. Create free project

4. Go to Settings → API

5. Copy URL and anon key to .env

---

2. Run Database Migration

Option A: Via Supabase Dashboard (Recommended)

1. Open https://app.supabase.com

2. Go to SQL Editor

3. Copy contents of database/fleetos/add-viral-tracking.sql

4. Paste and click Run

5. Should see: "Success. No rows returned"

Option B: Via Command Line

# Install Supabase CLI first (if not already)
npm install -g supabase

# Login
supabase login

# Run migration
supabase db push

---

3. Create Test Supplier

Run this SQL in Supabase SQL Editor:

-- Create test supplier
INSERT INTO suppliers (supplier_id, business_name, city, category, phone, email)
VALUES (
  'test-supplier-001',
  'Miami Tire & Service',
  'Miami',
  'Tires',
  '[phone]',
  '[e-mail]'
) ON CONFLICT (supplier_id) DO UPDATE SET
  business_name = EXCLUDED.business_name;

-- Create test user for login
INSERT INTO users (user_id, email, role, name, phone)
VALUES (
  'test-supplier-001',
  '[e-mail]',
  'supplier',
  'Miami Tire & Service',
  '[phone]'
) ON CONFLICT (user_id) DO UPDATE SET
  email = EXCLUDED.email;

-- Verify created
SELECT 'Supplier created!' as result, * FROM suppliers WHERE supplier_id = 'test-supplier-001';
SELECT 'User created!' as result, * FROM users WHERE user_id = 'test-supplier-001';

---

4. Start Dev Server

cd C:\Projects\robo-hub
npm run dev

Opens at: http://localhost:5173

---

🧪 Test Flow (2 minutes)

Test 1: Submit Request

1. Open: http://localhost:5173/request/miami-tire-service

2. Fill form:

   • Company: ABC Logistics

   • Phone: [phone]

   • Vehicle: Truck #402

   • Location: 1200 Brickell Ave, Miami

   • Urgency: TODAY (yellow)

   • Description: Flat tire, need service today

3. Click Submit

4. ✅ Should see success page with tracking link

Test 2: View Pending Queue

1. Go to: http://localhost:5173/fleetos

2. Click Login

3. Select Supplier → Choose "Miami Tire & Service"

4. ✅ Should see yellow Pending Fleet Requests section

5. ✅ Request from ABC Logistics appears

Test 3: Accept with Note

1. Click "✓ Add to Queue"

2. Enter note: "We'll handle this today between 9-4 PM"

3. Click Confirm

4. ✅ Request moves to Today's Dispatch section

Test 4: Complete Status Flow

1. In Today's Dispatch, click "✓ Accept & Start"

2. ✅ Button changes to "✓ Mark Complete"

3. Click "✓ Mark Complete"

4. ✅ Shows green "✓ Completed" badge

DONE! You've tested the complete flow.

---

🔍 Verify in Database

Quick check in Supabase SQL Editor:

-- See all requests with their statuses
SELECT
  fleet_name,
  vehicle_asset,
  urgency,
  status,
  supplier_action_status,
  is_manual_todo,
  source_channel,
  created_at
FROM service_requests
ORDER BY created_at DESC
LIMIT 5;

Expected to see:

• Your ABC Logistics request

• Status: 'completed'

• supplier_action_status: 'accepted_as_todo'

• is_manual_todo: true

• source_channel: 'web_form'

---

🧪 Bonus Tests

Test Invite Flow

1. Submit another request (different company)

2. In Pending Queue, click "📧 Invite Fleet"

3. Check database:

SELECT * FROM fleetos_invites ORDER BY created_at DESC LIMIT 1;

Test Decline Flow

1. Submit another request

2. Click "✗ Decline"

3. Enter reason: "Outside service area"

4. Confirm

5. Request disappears

Test Pre-population

Open: http://localhost:5173/request/miami-tire-service?fleet=PrepopCo&phone=[phone]

• Company and phone should be pre-filled and disabled

---

❌ Troubleshooting

"Cannot connect to Supabase"

• Check .env has correct VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY

• Restart dev server: Ctrl+C, then npm run dev

"Supplier not found"

• Run the SQL from Step 3 again

• Check spelling: 'test-supplier-001'

"Column does not exist"

• Migration didn't run properly

• Re-run the migration SQL from Step 2

Request doesn't appear in pending queue

• Check browser console (F12) for errors

• Verify supplier_id matches in database:

SELECT supplier_id FROM service_requests ORDER BY created_at DESC LIMIT 1;

---

📊 What's Working Now

After testing, you have a working system:

✅ Fleet Side:

• Public request form (no login needed)

• Success page with tracking link

• Pre-population from invite links

✅ Supplier Side:

• Pending queue for unknown fleets

• Accept with optional note

• Invite fleet to FleetOS

• Decline with reason

• Today's Dispatch queue

• Status workflow (accept → complete)

• Notifications (console logs)

✅ Database:

• All requests tracked

• Magic link tokens generated

• Status changes logged

• Invite system working

---

🚀 What's Next

Choose your path:

Option A: Complete Phase 1

• Build WhatsApp inbound webhook

• Build Email inbound parsing

• Build keyword routing (TIRES123)

Option B: Add Viral Mechanics

• Implement 6 viral UX moments

• Add R₀ tracking dashboard

• A/B test CTA copy

Option C: Production Deploy

• Set up real domain

• Configure WhatsApp Business API

• Deploy to production Supabase

---

Need help? Check TESTING_GUIDE.md for detailed instructions.