# AI customer delivery enquiry handling.

URL: https://levystreet.com/industries/logistics/customer-delivery-enquiry-handling/
Updated: 2026-10-19

AI customer delivery enquiry handling for NZ retailers and carriers: answer where-is-my-order questions from tracking, verify who asks, escalate claims.

## Short answer

AI customer delivery enquiry handling answers 'where is my order' questions by matching the customer to their order, reading live carrier tracking and replying with the current status and next step. In New Zealand the design has two hard edges: it must not disclose delivery details to someone who is not the customer, and it must not promise delivery dates without reasonable grounds under the Fair Trading Act 1986.

- Most delivery enquiries are status questions that live tracking data can answer directly.
- Verify the enquirer against the order before sharing addresses, photos or delivery times.
- A retailer that arranges delivery stays responsible under the Consumer Guarantees Act, courier included.
- Lost, damaged and redirected deliveries always go to a person.

## Which delivery enquiries AI can answer alone

Status questions, once the enquirer is verified. Everything else gets a draft and a person. The split below is the one we would start with; your own history will move the lines.

| Enquiry type | Example | Handling |
|---|---|---|
| Status | "Where's order 4417?" | Auto-reply from live tracking after identity check |
| Delivery window | "Will it come before Saturday?" | Draft quoting the carrier's estimate; agent approves |
| Failed delivery | "I got a card, now what?" | Auto-reply with depot and rebooking details |
| Lost or no scans | "Nothing since Monday" | Agent, with tracking history and POD attached |
| Damaged or wrong item | "Box arrived crushed" | Agent, with photos and POD |
| Address change or redirect | "Send it to my work instead" | Agent only |

## How an enquiry moves through the system


- **Inputs**: Emails, web chat and contact forms; the order record (contact details, items, carrier, tracking number); carrier tracking events; the proof of delivery record where one exists.
- **Systems**: Your helpdesk (Zendesk, Intercom or similar), the store or order system (Shopify, WooCommerce or Cin7), carrier tracking APIs, and read-only access to POD images.
- **Steps**: Classify the intent; find the order; verify the enquirer against the order's contact details; fetch the latest scan; pick the reply type from the table; send or draft; tag and log.
- **Human review**: For the first four weeks agents approve every reply. After that, status replies auto-send and a team lead samples 10% weekly; every other category stays draft-only.
- **Outputs**: Sent status replies, approval-ready drafts, tagged tickets, and loss or damage cases opened with tracking history attached.
- **Measures**: First response time, share resolved without an agent, reopen rate within 48 hours, auto-replies that should have escalated (target zero), and disclosure complaints.
- **Risks**: Details sent to the wrong person, delivery dates invented, stale tracking quoted as current, and customer messages that try to instruct the system.


## Illustrative example: an online retailer's month

Illustrative example: a Wellington online homewares retailer shipping 4,000 orders a month through two courier companies. Assumptions: 15% of orders prompt a delivery enquiry (600 a month); 65% are status, 20% delivery window or failed delivery, 15% loss, damage, redirect or complaint; agents currently take 3, 4 and 10 minutes for those groups. All figures are synthetic.

| Group | Enquiries a month | Agent minutes now | Agent minutes after (assumed) |
|---|---|---|---|
| Status | 390 | 1,170 | 39 (10% sample at 1 minute) |
| Window or failed delivery | 120 | 480 | 180 (approve drafts at 1.5 minutes) |
| Loss, damage, redirect, complaint | 90 | 900 | 630 (7 minutes with history attached) |
| **Total** | **600** | **2,550 (42.5 hours)** | **849 (14.2 hours)** |

The pricing model matters. Intercom [lists its Fin agent at $0.99 per outcome](https://www.intercom.com/pricing), and Zendesk [charges for AI agents per automated resolution](https://www.zendesk.com/pricing/) and bills in USD, EUR, GBP or BRL, not NZD (both as listed on 19 October 2026). At about a US dollar each (check the currency on your quote), 390 automated status replies cost roughly US$390 a month to save about 19 agent hours. A custom build swaps that for token costs of cents per reply plus build and maintenance.

## The New Zealand rules your replies must respect

**Who owns a lost delivery.** Where a supplier is responsible for delivering or arranging delivery, the [Consumer Guarantees Act 1993](https://www.legislation.govt.nz/act/public/1993/91/en/latest/) guarantees the consumer receives the goods at the agreed time, or within a reasonable time, and treats the carrier as the supplier's agent (section 5A). A retailer's assistant must never tell a consumer to sort it out with the courier.

**What it may promise.** The [Fair Trading Act 1986](https://www.legislation.govt.nz/act/public/1986/121/en/latest/) bars unsubstantiated representations in trade (section 12A): a delivery promise with no reasonable basis breaches it even if the parcel happens to arrive on time. Dates come from the carrier's estimate, attributed as such.

**Who it may tell.** Under [privacy principle 11](https://www.privacy.org.nz/privacy-principles/11/), personal information should be disclosed only on reasonable grounds, such as disclosure to the person it is about. An address, door photo or delivery time sent to the wrong email is a privacy breach; if serious harm is likely, the [Privacy Act 2020](https://www.legislation.govt.nz/act/public/2020/31/en/latest/) requires notifying the Commissioner as soon as practicable (section 114).

## Where a person must take over

- Address changes and redirects after dispatch, which carry fraud and personal safety risk.
- Declaring a parcel lost, and any refund or replacement decision.
- Damage reports, which need the evidence from [proof of delivery extraction](/industries/logistics/proof-of-delivery-extraction/).
- Anyone distressed, or asking about someone else's delivery.
- Wider delays, which the ops desk sees first in its [shipment exception summaries](/industries/logistics/shipment-exception-summaries/) and should announce once, not ticket by ticket.

## Controls to have in place before auto-replies go live


- The identity rule is written down: which fields must match before any delivery detail is shared.
- The assistant has read-only access to orders and tracking; it cannot change addresses or issue refunds.
- Every date in a reply is quoted from the carrier with its scan time ("last scanned in Palmerston North at 6.12am").
- Fifty real past emails per escalation category have been tested and none auto-sent.
- Instructions inside customer messages are treated as text, not commands; see [recognising prompt injection](/learn/recognising-prompt-injection/).
- Reopen rate and the weekly sample are reviewed by a named team lead.


The drafting habits behind good replies are covered in [using AI for customer support drafts](/learn/using-ai-for-customer-support-drafts/), and store connections in [AI and Shopify](/integrations/shopify/). For a build, see [AI customer support systems](/services/ai-customer-support/) and the wider [AI for logistics in New Zealand](/industries/logistics/) guide.

## Questions people ask

### Can a chatbot tell customers when their parcel will arrive?

Only by quoting the carrier's own estimate and saying that it is an estimate. The Fair Trading Act 1986 prohibits representations made in trade without reasonable grounds, whether or not they turn out to be false. A reply such as 'the courier's current estimate is Thursday' has a basis; 'it will definitely arrive tomorrow' generated from nothing does not.

### Who is responsible when a courier loses an online order in New Zealand?

If the retailer was responsible for delivering the goods or arranging delivery, the Consumer Guarantees Act 1993 guarantees the consumer receives them at the agreed time or within a reasonable time, and treats the carrier as the retailer's agent. The customer's remedy is against the retailer, so a reply telling them to chase the courier themselves is the wrong answer.

### How should the system check who is asking about a delivery?

Write the rule down before launch. Common choices are replying only to the email address or phone number on the order, or requiring the order number plus the delivery postcode in chat. If the check fails, give generic help only. Never send an address, delivery photo or exact delivery time to an unverified contact.

### Should we use our helpdesk's AI agent or build our own?

A helpdesk's built-in agent is quicker to start and charges per resolution, which suits moderate volumes and simple status questions. A custom build costs more upfront but pays per model token, can apply your own identity and escalation rules exactly, and can read several carriers and order systems. High volumes and unusual rules tend to favour building.

### What happens if the AI gives delivery details to the wrong person?

Treat it as a privacy breach. Assess whether it is likely to cause serious harm, considering how sensitive the information is and who received it. If it is, the Privacy Act 2020 requires notifying the Privacy Commissioner and, usually, the affected person as soon as practicable. Then fix the rule that allowed it before turning auto-replies back on.


## Sources

- [Consumer Guarantees Act 1993, section 5A (guarantee as to delivery)](https://www.legislation.govt.nz/act/public/1993/91/en/latest/)
- [Fair Trading Act 1986, section 12A (unsubstantiated representations)](https://www.legislation.govt.nz/act/public/1986/121/en/latest/)
- [Privacy Act 2020, sections 112 to 115 (notifiable privacy breaches)](https://www.legislation.govt.nz/act/public/2020/31/en/latest/)
- [Principle 11: Disclosure of personal information](https://www.privacy.org.nz/privacy-principles/11/)
- [Intercom pricing](https://www.intercom.com/pricing)
- [Zendesk pricing plans](https://www.zendesk.com/pricing/)

Published by Levy Street (https://levystreet.com), Wellington, New Zealand.