Half your calls are four words long: where is my order
GreetKeeper answers the shipping and timing questions you have written down, and passes the rest to your team with the order number already captured.
Caller
“I ordered a week ago and there's still no tracking email. Order number's 48821. Is that normal or has something gone wrong?”
What happened next
- Explained your stated dispatch window from your own notes
- Captured order number 48821 and the missing tracking email
- Routed to your fulfilment team with the detail already written
The cheapest call you get is also the most frequent
Nobody rings to say the order arrived. They ring when the tracking email is late, and the answer is usually a sentence you have said four hundred times.
It is the volume, not the difficulty. A hundred of these a week means a hundred interruptions, each pulling someone off a job that actually needed thinking about.
The calls also crowd out the ones that matter. A customer with a damaged delivery waits behind six people whose parcels are simply in transit and on time.
GreetKeeper can carry the routine ones. It tells people what your dispatch window actually is, and gets the order number down for anything that needs a person.
What it does with a status call
Be clear about the shape of this. The AI answers from what you wrote, not from your order system.
Get the order number early
First question, read back to confirm. Every call that ends up with a person is worth more when the number is already in the record.
Answer the standard timing questions
How long dispatch normally takes, when tracking emails go out, what the courier's usual window is. You write these once, and most callers need nothing else.
Pass anything specific to a person
A caller asking where parcel 48821 is right now needs your system, not the AI. It says so, takes the detail, and routes the call to the team that can look.
Send the order number onward if you want to
There is no connection to any order system, so no live order data reaches the call. Afterwards, our webhook can hand the order number and the reason for calling to your own tools.
Cost per status call
This is the one use case where cost per call is the whole argument, because the calls carry no revenue.
| Plan | Monthly | Calls included | After that |
|---|---|---|---|
| StarterFor a single location taking calls one line at a time. | $49 | 200 | $0.45 per call |
| ProfessionalBooking, routing and transfers included, not an add-on. | $149 | 750 | $0.35 per call |
| ScaleFor busy phones and longer opening hours. | $349 | 2,000 | $0.25 per call |
Starter is $49 a month for 200 calls at $0.45 over. Professional is $149 for 750 at $0.35. Scale is $349 for 2,000 at $0.25.
On Scale, 2,000 calls works out well under twenty cents each before overage. Compare that to the minutes your team spends reading out a dispatch window, and the argument makes itself.
Status calls are short, so the per-minute comparison is worth running carefully. Many services bill a minimum of one minute, which is most of a call like this.
The important caveat
Questions people ask
Can it look up my customer's tracking number?
No. It has no connection to your order system. It captures the order number and routes the call, and our webhook can pass both to your tools afterwards.
What does it say when it cannot answer?
It says plainly that it will pass the call to someone who can check, then takes the order number and details. It does not invent a shipping date.
Is it worth it for calls this small?
Work it out from your own volume. If you take 300 status calls a month, divide the plan cost by 300 and compare that to the staff time those calls eat.
Hand over the routine ones
Tell us your dispatch window and hear it answer.