P
AI for Delivery Route Supervisor

Claude Project: Build a Driver Q&A Bot from Your SOPs

For Delivery Route Supervisors

Tools: Claude Pro | Time to build: 1–2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude as a writing assistant. See Level 3 guide: "Build Your Route Supervisor Writing Assistant in Claude"

What This Builds

Instead of fielding the same questions from drivers every week ("What do I do if the customer isn't home?" "How do I report a damaged package?" "What's the process if my van breaks down?"), you'll build a Claude Project that already knows your company's procedures and can answer these questions accurately, any time, from any device. New drivers can use it to self-onboard. Experienced drivers can use it as a quick reference. And you save hours of interrupted work every week.

Prerequisites

  • A Claude Pro account at claude.ai ($20/month, required for Projects)
  • At least a few documented procedures, even rough ones (you'll write them into the bot)
  • Optional: existing SOPs, employee handbooks, or carrier guidelines you can paste in
  • Cost: $20/month (Claude Pro)

The Concept

A Claude Project is like having a new coworker who has memorized your entire operations manual. When drivers ask questions, they're talking to someone who already knows the right answer, not waiting for you to respond. You write the knowledge base once; the bot uses it forever.

The difference from just using ChatGPT: the context is permanent. Every conversation a driver has with the bot starts with full knowledge of your procedures. No re-explaining, no hallucinated answers.

Build It Step by Step

Part 1: Set Up the Project

Step 1.1: Go to claude.ai, log in to your Claude Pro account.

Step 1.2: Click "Projects" in the left sidebar → "New Project."

Step 1.3: Name it: "[Your Company] Driver Reference Guide" (something drivers will recognize).

Step 1.4: Click "Edit Project Instructions." This is where you'll write the bot's knowledge base and personality.

Part 2: Write the System Instructions

This is the most important part. Paste the following template and fill in your actual procedures:

Copy and paste this
You are a driver reference assistant for [Company Name], a [DSP operator / courier company / etc.].

Your job is to answer drivers' operational questions accurately based on company procedures. Be direct, clear, and practical. If you don't know the answer, say so and tell the driver to contact their supervisor.

FAILED DELIVERY PROCEDURES:
- If customer is not home: [describe your procedure — leave notice, attempt redeliver, return to hub, etc.]
- If address doesn't exist: [describe your procedure]
- If apartment building has no access: [describe your procedure]
- Required documentation for failed attempt: [what drivers must do in the app]

PACKAGE DAMAGE PROCEDURES:
- If package is damaged before delivery: [describe]
- If customer claims damage at door: [describe]
- Photos required: [yes/no, how many, of what]
- Who to notify: [supervisor / dispatch / carrier portal]

VEHICLE ISSUES:
- If van breaks down mid-route: [pull over safely, call [number], stay with vehicle until...]
- If check engine light comes on: [complete route / call supervisor / return to hub — your policy]
- Who to call: [dispatch number, roadside number]

ACCIDENTS:
- Step 1: [stay at scene, check for injuries, call 911 if any injury]
- Step 2: [call supervisor at [number]]
- Step 3: [do NOT move vehicle until...]
- Documentation required: [photos, police report number, witness info]

CUSTOMER INTERACTIONS:
- If customer is angry or confrontational: [describe your de-escalation policy]
- If customer requests supervisor call: [take their number, notify supervisor]
- Language for difficult interactions: ["I understand your frustration, I'll make sure this is documented..."]

SCANNING AND DELIVERY CONFIRMATION:
- Every package must be scanned: [when and how]
- Proof of delivery photo: [required / optional / required for specific package types]
- Signature required for: [list package types]

END-OF-SHIFT PROCEDURES:
- Vehicle inspection: [what to check, where to document]
- Undelivered packages: [where to return, how to document]
- Fuel: [company card procedure, when to refuel]

EMERGENCY CONTACTS:
- Dispatch: [number]
- Supervisor direct: [your number or on-call number]
- Roadside assistance: [number]
- Safety incidents: [number]

COMMON QUESTIONS:
[Add the questions drivers ask you most often and your standard answers here]

Fill in every section with your actual procedures. The more complete this is, the more useful the bot.

What you should see: A saved set of Project Instructions visible in the sidebar.

Part 3: Test the Bot

Step 3.1: Start a new conversation inside your Project.

Step 3.2: Ask it the questions your drivers ask most: "What do I do if a customer isn't home?" / "My van is making a noise, should I keep driving?" / "A package fell and broke, what do I do?"

Step 3.3: Evaluate the answers. Are they accurate? Do they match your actual procedures? If something is wrong or missing, go back to your Project Instructions and fix it.

Step 3.4: Keep testing with 10–15 common questions until you're confident the answers are correct.

Part 4: Share the Bot with Your Drivers

Step 4.1: Currently Claude Projects are personal, so you can't directly share a Project link with drivers. But you can:

  • Share your login credentials with drivers on a shared device (a tablet in the hub)
  • Screenshot the most common Q&A exchanges and post them in your team group chat
  • Use the Project yourself to quickly answer driver questions by voice or text

Step 4.2: For future sharing, Claude is expanding Project sharing features. Check claude.ai for the current sharing options.

Alternative for team sharing: Export your SOPs as a Google Doc and share that. Then use the bot yourself to generate answers and forward them to drivers. This way you control the information flow.

Real Example: Full Workflow

Setup: You built the Project with all your company's exception procedures, vehicle policies, and emergency contacts.

Input from driver (7:15am, mid-route): Driver texts you: "Customer says their package is damaged. What do I do?"

Instead of calling the driver back, you type it into your Project: "Driver says customer claims package is damaged at delivery. What should the driver do according to our procedures?"

Output: "Per company procedure: (1) Document the damage with 3 photos: package exterior, the item, and the label. (2) Have customer sign the delivery confirmation noting 'damage reported.' (3) Complete the delivery. Do not take the package back unless it's a clear safety hazard. (4) File a damage report in the [app/system] before end of shift using the 'Damaged Goods' form. (5) Notify your supervisor by end of shift. The customer should contact [carrier/company name] at [number] to file a claim."

You forward the answer directly to the driver. Takes 45 seconds vs. pulling over to call, looking up the procedure, explaining it verbally.

What to Do When It Breaks

  • Bot gives wrong answer → Go back to Project Instructions and update the relevant section. The bot is only as good as what you wrote.
  • Driver asks something not in the instructions → The bot will say it doesn't know and recommend contacting you. That's correct behavior. Add the question and answer to the Instructions for next time.
  • Instructions are too long and bot gets confused → Break into clear labeled sections with headers. Claude handles long instructions well but clear formatting helps.

Variations

  • Simpler version: Just write a Google Doc FAQ and search it manually. It doesn't need AI, but saves you the typing every time.
  • Extended version: Add your company's employee handbook, safety guidelines, and carrier-specific rules to the Project Instructions to give the bot more knowledge depth

What to Do Next

  • This week: Write the first version of your Project Instructions. Even 5 procedures is a useful start.
  • This month: Test with all the questions you get asked most and refine the answers
  • Advanced: As Claude Project sharing improves, set up a shared team access point for new driver onboarding

Advanced guide for delivery route supervisor professionals. Claude Pro required for Projects feature ($20/month at claude.ai).