Skip to main content

Manage shipment requests with address, location and tracking data

Customers create shipments, share an address or live location, set delivery preferences and track movement on WhatsApp. When an exception occurs, operations take over the same record.

Scroll down
Logistics team managing shipment status at a distribution centre
The workflow in practice

In Logistics, Exception Handling Makes the Difference

Address not found, recipient absent, damage, delay or delivery change: a sound system knows what to say and who should own the next action.

01

Verify the Shipment

Tracking information resolves to the right customer and record.

02

Apply Change Rules

Address and timing preferences update only when carrier status allows.

03

Give Exceptions an Owner

Loss, damage and delay become owned operational work.

What Might the Customer Write?

“My parcel is out for delivery, but I will not be there today. Can we move it to tomorrow?”

Critical Check

Shipment ownership, current status, route, change window and carrier rules are verified.

Resulting Action

The delivery preference is updated when allowed; otherwise an operations request is created.

Where Human Handoff Is Needed

Damage, loss, customs, proof-of-delivery disputes and off-route changes pass to the team.

Sample WhatsApp Flow

Customer: “Can I change the location to here?” Meta Reva: “Your shipment is already out for delivery, so the address cannot be changed automatically. I can send your location to operations and open a callback record.”

Find the Repetitive Work in Your Operation

Let us start with the requests your team answers and copies into another system every day.

Discuss Your Process