Every delivery call connected, no number shared
Couriers and customers talk through your business number, with an order code on the keypad when the caller is unknown, every call recorded against the order, and mappings pushed straight from your dispatch system.
Numbers hidden both ways ✦ Recorded on every connect ✦ India and US numbers
Sofia · customerDials +91 22 4890 1140Calling…
Dev · delivery agentSees +91 22 4890 1140—Order #7731 · in the CRM
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo Hotels
Every order. Every call. Every doorstep.
The customer's WhatsApp update, the courier's call from the gate, the recording, the failed-delivery callback and the disposition all attach to one record, searchable by your order reference. A dispute a week later is a listen, not an argument.
- Your reference on the call, back on every webhook and in the record.
- What happened on each side: answered, busy, unreachable, hung up while ringing.
- Recording from the moment both connect, transcribed when transcription is on.
Built for the last mile
Mask every number, both ways
The courier sees your business number, the customer only ever dialled it. Unknown callers match with an order code or their registered number on the keypad.
Learn moreMap from your dispatch system
Push, update and remove customer-to-agent mappings through the API as orders are assigned, or bulk-import by file. Connect two numbers with one API call and your order reference.
Learn moreTell customers before they chase
Dispatch, ETA and failed-delivery updates as WhatsApp utility templates, tracked per recipient, with replies in the inbox and Kaylee answering the predictable ones.
Learn moreRecorded, reported, in your region
Every connect recorded and reportable, data kept in the region you choose, and the outcome on each side logged for the dispute you have not had yet.
Learn moreYour order system drives the calls
Mappings arrive from your dispatch system through the partner API or a file. Connect calls place a call between two outside numbers with your order reference and an idempotency key, so a retry never dials twice. Signed webhooks return every call outcome and every message, Shopify order notifications go out on WhatsApp, and Zapier carries the rest. Voice runs on Tata Tele Smartflo, Airtel MSIP, Lodgestory Voice or SignalWire.
- POST calls/connect with your reference; same key, same call.
- Caller id from a pool of your numbers: in turn, random, or sticky per customer.
- Shopify order, shipping and delivery notifications.
Webhooks · dispatch.example
Dispatch, ETA and the failed drop, on WhatsApp
Three utility templates cover the day: dispatched with the courier's name, arriving with a window, and could not deliver with a reschedule choice. They go out from your systems or a journey with named placeholders, and every recipient shows sent, delivered, read or failed. Replies thread into the inbox where Kaylee confirms new slots and your team handles the rest.
- Per-recipient status, with retries and failure reasons.
- Template TTL from 30 seconds to 30 days, short for a courier at the gate.
- Replies answered by Kaylee with staff approval for exceptions.
Delivery · #7731
The callback campaign that closes the loop
Upload the day's failed drops, or push them from the API, and the dialer calls each customer at the rate you set: customer-first to keep agents busy, or agent-first so nobody hears silence. Up to five attempts with a backoff, only inside the business-hours schedule you attach, and a personalised voice broadcast can read the new slot without an agent at all.
- Do-not-call checked on every dial; flagged at upload.
- Sticky caller id so a customer calling back reaches the number they saw.
- Dispositions on every answered call, reported by agent.
Solutions for every team in the operation
Mappings from the system you already run
As an order is assigned, your dispatch system pushes the customer-to-courier mapping. When it is delivered, it removes it. No spreadsheet, no dispatcher in the loop.
- Push, update, remove mappings by API
- Bulk import by file for the morning run
- Connect calls with your order reference
One number to dial, nothing to install
The courier dials your business number from their own phone and reaches the customer for the order they are on. The customer sees your number, never theirs.
- Follow-Me mobile, no app needed
- Order code on the keypad when the caller is unknown
- Recording on every connect, for the courier too
“Where is my package?” answered before it is asked
Dispatch and ETA templates go out from your systems; replies land in one inbox where Kaylee answers the predictable ones and a person handles the exception.
- WhatsApp, email and web chat in one queue
- Tickets for damaged or missing items
- Kaylee asks staff before any refund
Every connect, counted
Calls per hour, outcomes per side, failed-drop callbacks and their results, dispositions by agent and the recording behind any dispute, exported as CSV or read through the API.
- Look calls up by order reference
- Business hours on every campaign
- Reports API and MCP for your dashboards
How to run last-mile calls with Lodgestory
Get numbers and set masked connect
Request India or US numbers, choose a provider, and point a number at a masked-connect routing with your greeting, ringback and the order-code prompt.
Connect your dispatch system
Push mappings and connect calls from the API with your order reference, subscribe to call webhooks, and bulk-import the first day by file.
Add the updates and the callbacks
Three utility templates for dispatch, ETA and failed delivery, a journey or API send for each, and a failed-drop campaign with business hours and retries.
In practice
A city delivery fleet, one order at a time
The dispatch system assigns order #7731 to Dev and pushes the mapping. The customer gets a WhatsApp with Dev's name and a window. At the gate, Dev dials the business number from his own phone and the customer's phone rings showing the same business number. A neighbour calls from an unknown phone, enters the order code, and is connected too. Both calls are recorded against #7731. The failed drops from the morning are dialled back at four a second, agent-first, inside business hours, and the new slots go out as a template.
Private by design, recorded by default
Neither side learns the other's number. Every connect is recorded from the moment both are on the line, kept in the region you choose, and reportable by your own order reference. Connect calls never start an automation and never create a lead.
Visit the trust centerGuides for logistics teams
Routing, the order-code fallback, media, recording and mappings.
Caller id from a pool, idempotency keys, talk-time limits.
The failed-drop callback run, start to finish.
Ready to connect every delivery call privately?
Point a number at masked connect, push the first mappings from your dispatch system and listen to the first recording today.
Questions, answered
The things delivery operations ask before they mask their calls.
Masked connect is a routing type on a Lodgestory Voice number. It looks up the number a customer is calling from and connects them to the mapped delivery agent's phone, showing your business number to both sides. If the caller is not recognised, they enter an order code or their registered number on the keypad to be matched. Every connected call is recorded and reportable.
Yes. The partner API pushes, updates and removes customer-to-agent mappings as orders are assigned, or you bulk-import them by file. Connect calls, where your system connects two outside numbers through one API call, carry your own order reference, which comes back on every webhook and in the call record.
No. The agent's phone shows your business number, never the customer's, and the customer only ever dialled your business number. Both sides see one of your Lodgestory Voice numbers as caller id.
Outbound campaigns dial a list at a rate you set, agent-first or customer-first, with up to five retries and a configurable backoff, dialling only in business hours if you attach a schedule. A personalised voice broadcast can read the new slot to each customer with no agent on the line, and a WhatsApp utility template can carry the same update.
Approved WhatsApp utility templates with named placeholders, sent from a campaign, a bot journey or your systems through the API, and tracked per recipient as sent, delivered, read or failed. Replies land in the inbox, where Kaylee answers the predictable ones and your team handles the rest.
On the call record, searchable by your order reference, with what happened on each side: answered, busy, unreachable, or hung up while the other side was ringing. Recordings start when both are connected. Call webhooks carry the reference and business-hours status, and dispositions and reports cover every connect.
Masked connect works on India and US numbers. Voice runs on Tata Tele Smartflo, Airtel MSIP, Lodgestory Voice in India and the US, and SignalWire in the US, with several providers coexisting in one CRM.