FedEx case study | Shivam Arora
02 / FedExB2BWhatsAppLogistics

Research, Conversation Design and UX Writing

Simplifying the B2B support chatbot for FedEx

A global logistics brand, a WhatsApp bot that kept growing, and business customers who just wanted to get things done without calling support.

Year
2026
Role
Design Lead
Platform
WhatsApp, B2B

What we did

  • Benchmarking
  • AI agents
  • Intent restructuring
  • Meta guidelines
  • UX audit
  • Conversation design
  • UX writing
See the final flows
Package details in the new FedEx WhatsApp bot
FedEx WhatsApp welcome message with Track a Package, Manage Pickup and More Services
Pickup confirmed message with AWB and pickup reference
Final screens, as shipped on WhatsAppFedEx India

The problem

Solve it in the chat. Only send people elsewhere when the bot really can’t.

That was FedEx’s brief. Their B2B bot was live on WhatsApp, but customers struggled to use it, and support tickets and emails kept coming in.

  1. FedEx had launched a WhatsApp bot for its business customers, but most people couldn’t find what they needed in it. Queries still ended up as tickets and emails. We were brought in to make the bot easy to understand and resolve those queries in the chat.

  2. We led the benchmarking, and I set up the AI agent that did the heavy lifting on research. From there, I drove the IA, the user audit, the new flows and the copy.

  3. We restructured the IA and redesigned tracking, pickups and delivery changes, so each one ends with a confirmation inside WhatsApp.

    Pickup confirmed banner from the new bot
    • 42% fewer support tickets and emails
    • 68% of conversations resolved in the chat
    • Pickups booked 60% faster
01

Where we started

FedEx had a support bot live on WhatsApp for its business customers, and it wasn’t taking any load off the support team. People got lost in it and raised tickets or sent emails instead. Our job was to bring those down by resolving as much as possible inside the chat.

Current IAFour levels deep

We started by mapping the current information architecture. It went four levels deep, repeated the same tasks in different places and sent people back through menus.

Fourth levelRepeats a main taskBack step
Redesigned IAThree levels at most

We redesigned it around the three things customers come to do. Nothing sits more than three levels deep, and every task lives in one place.

02

The approach

We studied the market, understood the intents the bot already had, learned what WhatsApp allows and listened to the people using it. The audit told us to fix the intents one at a time. The language came last.

Market research

We benchmarked FedEx against the four strongest support bots on WhatsApp in India, on 10 parameters.

  1. 01Entry and discoverability
  2. 02Functional scope and depth
  3. 03Intent architecture and navigation
  4. 04Tone of voice and personality
  5. 05Exception handling and fallback
  6. 06Channel transition
  7. 07In-chat UI and message design
  8. 08Resolution quality and closure
  9. 09Human agent escalation
  10. 10Proactive communication

Setting up the research agent

I set up an AI agent to do the heavy lifting. We gave it a clear brief, the sources to read and a fixed format for what it sent back, so every output could be checked.

How the agent workedAI agent
InputCompetitor bots
InputMeta’s WhatsApp docs
InputFedEx’s current flows
InputSupport tickets and emails
AgentReads, scores and groups
OutputBenchmark scorecards
OutputIntent map and draft IA
OutputConstraint screens
UsEvery output reviewed before it went into the work
  1. 01Briefed it with our 10 parameters and FedEx’s goal of fewer tickets
  2. 02Asked for scored tables and grouped lists, never open summaries
  3. 03Checked a sample of every output by hand before using it

Understanding the current intents

The agent mapped every intent in the current bot and grouped them by what customers came to do. We validated each group with real tasks, and this became the redesigned IA.

MergedOverlapping groups combined
  • Duties, taxes and customs
  • Invoices, refunds and claims
  • FAQs into one short list
RemovedRepeats and dead ends
  • Three back to menu steps
  • Tracking repeated in FAQs
  • Delivery changes repeated in FAQs
RebuiltThe three core journeys
  • Tracking as one status card
  • Pickups with a single form
  • Manage Delivery with six options

Understanding Meta guidelines

FedEx wasn’t sure what WhatsApp allows. We studied Meta’s guidelines ourselves, and the agent turned every limit into a quick screen the team could design against.

ConstraintsDrawn by our agent
Buttons
Pick an optionTrack a Package15/20Manage Pickup13/20More Services13/20A fourth button
3 reply buttons, 20 characters each
Lists
Manage DeliveryLeave at Door13/24Leave with Neighbour20/24Self-Collect12/24
Up to 10 rows, 24 character titles
Forms
Pickup InformationDD/MM/YYTotal item countWeight (kg)
WhatsApp Flows for anything with fields
Timing
Customer last wrote 18 hours agoFree replies for 24 hours, templates after
24 hours to reply freely

Interviews and audit

We interviewed 24 of FedEx’s business customers, grouped them into 8 archetypes and had each of them complete 12 tasks on the current bot. AI helped us synthesise the sessions into a list of issues for every archetype.

Issues we found
Archetype 017 issues
Archetype 027 issues
Archetype 033 issues

The pattern was clear. Tracking, pickups and delivery changes caused most of the trouble, so we took them on one intent at a time.

Improving the verbiage

Last, we rewrote every message. One idea per message, key details in bold and a clear next step at the end.

Before

Thank you for your input. Your details have been successfully verified. Please confirm if you’d like us to schedule pickup from this location: DLF EXCLUSIVE FLOORS. If you wish to schedule a pickup from a different address, kindly contact Customer Care team to update the pickup location.

After

📦 Choose when and where you would like to schedule your pickup.

03

Solving the primary intents

Tracking, pickups and delivery changes made up most of the bot’s traffic and most of the tickets. We redesigned each one end to end, so it closes inside WhatsApp with a clear confirmation.

Track a package

Intent 01

The old reply put everything into one paragraph. We split it into a status card customers can scan, and moved package details one tap away.

BeforeRecreated from the old flow
9:41
FedExFedEx IN
Track Your Package10:01
Please enter your 12-digit FedEx tracking number.10:01
87198764123410:02

Shipment status for AWB 871987641234: Your delivery has been rescheduled. Estimated Delivery: Monday 9:30 AM to 12:30 PM. Current Status: Bethpage, NY - Fedex facility, Alternate delivery requested. Origin: Greer, SC. Destination: New Hyde Park, NY. Last Scanned Location: DUBAI WORLD CENTRAL (DWC) AE 11:01 AM. Packaging Type: Package. Total Weight: 1.5 kg (3.3 lb). Dimensions: 17 x 17 x 15 cm. Package Count: 1. Note: Your package may be late due to local delivery restrictions. Last Updated: 4 April 2026 4:42 AM.

10:02
Main Menu
Type a message

What went wrong

  1. 01Status, package details and the note in one block
  2. 02Nothing stood out, so the delay got missed
  3. 03The only way forward was back to the main menu
After
9:41
FedExFedEx IN
Track a Package11:13
Tracking card: delivery rescheduled, delivery details, shipment details and a note
Type a message
Status card
Package details: type, weight, dimensions and count, with Yes and No buttons
Package details

Schedule a pickup

Intent 02

The old flow asked for details one message at a time and sent address changes to customer care. The new one collects everything in a single WhatsApp form and confirms with the AWB and pickup reference.

Before
9:41
FedExFedEx IN
Hi Design, welcome to FedEx Customer Support! Get instant support for shipping, tracking, pickups, and more, right at your fingertips. Your convenience comes first. Just choose an option below to get started.10:00
Track Your PackageManage PickupMore Services
Manage Pickup10:01
Manage Pickup Services10:01
Schedule PickupCancel Pickup
Schedule Pickup10:01
📦Please enter your 12-digit FedEx tracking number to proceed with the pickup request. If you’re shipping multiple shipments, you’ll be able to specify them in the next steps of the booking process. Note: Only one pickup can be scheduled per date per location10:01
87120484841410:02
Please enter the sender postal code associated with this AWB.10:02
12200310:02
Thank you for your input. Your details have been successfully verified. Please confirm if you’d like us to schedule pickup from this location: DLF EXCLUSIVE FLOORS If you wish to schedule a pickup from a different address, kindly contact Customer Care team to update the pickup location.10:02
YesMain Menu
Type a message

What went wrong

  1. 01Two menus before the task even started
  2. 02AWB and postal code asked for one by one
  3. 03Long notes that most people skipped
  4. 04A different address meant calling customer care
After
Welcome message with Track a Package, Manage Pickup and More Services, then the Manage Pickup banner
Welcome and Manage Pickup
9:41
Pickup Information form with date, time slot, item count, weight and instructions
Pickup details form
Pickup confirmed with AWB, date and pickup reference number in bold
Pickup confirmed

Manage a delivery

Intent 03

Customers can change a delivery in six ways, and each one has its own flow. Before, every option opened with long paragraphs. Now each one is a few short steps that end in the same confirmation.

BeforeOne screen from each option
Deliver as planned
Leave at door
Future date
Leave with neighbour
Redirect
Self-collect
  1. 01Long, legal-sounding paragraphs before every choice
  2. 02The same warning repeated across messages
  3. 03A plain line of text as the only confirmation
AfterFinal flow for each option
New Deliver as Planned flow ending in Changes Confirmed
Deliver as planned
New Leave at Door flow ending in Changes Confirmed
Leave at door
New Deliver on Future Date flow
Deliver on a future date
New Leave with Neighbour flow
Leave with neighbour
New Redirect to New Address flow
Redirect to a new address
New Self-Collect flow
Self-collect
04

Impact

01

42% fewer support tickets and emails

Tracking, pickup and delivery queries now close inside WhatsApp instead of reaching the support desk.

02

68% of conversations resolved in the chat

Up from about a third before the redesign. Customers leave with a confirmation, not a phone number.

03

Pickups booked 60% faster

One WhatsApp form replaced a string of back and forth messages.

04

35% fewer drop-offs mid-conversation

A simpler IA, with fewer choices at every step, kept people moving to the end of their task.

Get in touch

Want the full walkthrough?

There’s more to this project than one page can hold. Leave me a message and I’ll take you through the research, the agent setup and every flow we redesigned.

shivamar275@gmail.com LinkedIn