Chatterbox can answer delivery-time questions from estimates your business has published. It can repeat the stated dispatch window, delivery range, and conditions. If the material does not settle when a particular order will arrive, it asks for contact details instead of turning a general estimate into a promise.
“How long does delivery take?” sounds like one question. It can mean when an item will be ready, when it will leave the workshop, how long the journey takes, or where an existing order is now. Chatterbox can repeat the delivery rule the business has written. It should stop when the visitor has moved beyond that rule into the circumstances of one order.
What does the customer mean by delivery time?
Break the journey into three clocks.
Preparation time begins when the business accepts the order. A stocked item may be ready quickly. Furniture made to a customer's measurements may not be. If both are described simply as “delivery,” the shorter figure can look like it applies to everything.
Dispatch time tells the customer when the item leaves the business. “Dispatched within two working days” does not say that it arrives within two days.
Travel time begins after dispatch and may depend on the destination or delivery method. It is the part most people mean when they ask when something will reach them.
Put the clocks together only when the business can support the combined range. Otherwise, publish each one separately. A chatbot cannot repair an unclear promise by choosing the interpretation that sounds most helpful.
How should you write a delivery estimate for the website?
Build the public answer from the conditions the team actually uses:
- what the estimate covers, such as ready stock or made-to-order work;
- when counting starts, such as payment, approval, or order confirmation;
- whether the number uses working days or calendar days;
- which destinations the range covers;
- what happens for weekends, holidays, or custom work;
- where a customer should ask about an order already in progress.
A useful sentence might describe ready-stock orders within a named area and give a range in working days. It does not need to forecast every delay. It needs to make the ordinary case unmistakable and leave the exceptions outside the promise.
Keep the approved wording in one place. Chatterbox can draw knowledge from a site crawl, uploaded file, pasted text, or hand-typed Q&A. Repeating the estimate in all four creates four chances for an earlier range to remain after the business changes it.
Which delivery questions can Chatterbox answer?
A standard question belongs with the published rule. If a visitor asks how long ordinary delivery takes and the page states a range, Chatterbox can surface that range. Each answer shows the source passage, so the visitor can see the condition beside the number.
A conditional question can also be answered when the condition is written down. If made-to-order work has its own stated preparation period, the answer should use that period rather than the ready-stock figure.
An individual-order question is different. “Will my table arrive before Friday?” may depend on approval, production, dispatch, destination, and the present state of that job. A general delivery page does not establish those facts merely because it contains a typical range.
At that boundary, Chatterbox says it cannot find the answer and requests the visitor's name, phone, and email. The enquiry goes to the dashboard and by email for a person to check. The widget has captured the question without converting “normally” into “definitely.”
What test catches a false delivery promise?
Use three questions, not one.
First ask about the normal case exactly as the page describes it. Confirm that the reply preserves both the range and the words that qualify it. A number without “working days” or “after approval” is not the same answer.
Next change one condition. Ask about custom work when only ready stock is covered, or name a place outside the stated area. The response must not carry the ordinary estimate across that boundary.
Finally ask about a specific order and date. Unless the supplied material settles that case, the safe result is contact capture. This is the question most likely to turn a rough guide into a commitment.
Run the same three-part check whenever the business changes preparation time, delivery coverage, or working-day rules. Correct the primary page, remove the old copies, and refresh the website source; Chatterbox permits one re-crawl per source each day.
The goal is not to make every delivery question receive a number. It is to give the ordinary estimate quickly, keep its conditions attached, and recognize the moment only a person can confirm the date.