Logistics & Courier Services

Every "where is my parcel" is a message you could have sent first

Half the day goes on status questions. Each one is two minutes and tells the customer nothing they would not have known if you had messaged them. Meanwhile drivers are coordinating in a group chat nobody can search.

How it runs

  1. 1

    The customer hears at pickup

    A utility template confirming collection, which is the message that prevents the first three questions.

  2. 2

    Status changes trigger messages

    Your system calls a webhook when a consignment moves; the automation sends the update.

  3. 3

    Questions arrive in a shared inbox

    Not on one dispatcher’s phone, and answerable by whoever is free.

  4. 4

    Delivery closes the loop

    A final confirmation, and the reply window it opens is where any problem surfaces immediately.

What you get

Status updates as utility templates

Collected, out for delivery, delivered — the cheaper message category, approved readily because the customer is expecting them.

Triggered from your own system

A webhook from your dispatch software fires the automation. PingPlug does not track consignments itself.

Shared inbox for the office

Status questions reach the team, with the customer’s history attached.

Contacts captured automatically

Anyone who messages becomes a contact, matched to their existing record by number rather than duplicated.

Broadcasts for disruption notices

When weather or a depot problem hits, message the affected segment rather than everyone.

Multi-branch for depots

Several depots under one account, each with its own team.

Questions

Does PingPlug track parcels?

No. It has no tracking of its own and does not know where a consignment is. Your system knows, and can call a webhook when the status changes — PingPlug turns that into a message.

How many updates should we send?

Fewer than feels natural. Collection and delivery cover most of it, with an out-for-delivery message if the window is long. Every extra message is a chance to be blocked, and blocks lower the quality rating that caps how many people you can message at all.

Can drivers use it?

It is a web app, so it works on a phone. But it is built around customer conversations rather than driver dispatch — there is no route planning, no proof-of-delivery capture and no driver app.

Can we message a customer about a failed delivery attempt?

Yes, as a utility template. That is exactly the kind of transactional message the category exists for.