An AI receptionist for florists should establish what needs to arrive, where and when. Its job is to capture the request accurately while the florist designs arrangements, serves the shop or prepares deliveries.
The difficult part is commitment. A requested bouquet, delivery window and budget are an enquiry until the shop has confirmed stock and delivery capacity.
Start with the type of order
Separate everyday flowers, weddings and events, sympathy enquiries and questions about an existing order. An event consultation needs a different appointment and follow-up from a same-day birthday bouquet.
For an everyday request, collect the preferred delivery date, destination suburb, budget range and the sender’s callback details. Ask whether the customer has an existing order reference before discussing a delivery issue. Keep spelling corrections attached to the right order request.
Make cutoff rules explicit
Give the receptionist approved rules for delivery areas, order cutoffs and public-holiday opening hours. If those rules depend on driver capacity, require a live check or human approval. An old website sentence about same-day delivery should not become an unconditional promise on a peak day.
For a requested flower that may be seasonal, record the preference and ask whether the florist may discuss substitutions. Do not silently replace a premium stem or promise an identical arrangement from a reference image.
Protect the surprise and the recipient
Recipient addresses, phone numbers and card messages need careful handling. Collect only what the shop needs, restrict who can read the notes and avoid repeating a private card message into a general staff notification. If someone calls asking who sent flowers to another person, route the request to staff rather than exposing the order history.
A useful script is: “I can record the delivery request and your preferred flowers. The team will confirm availability and the delivery window before the order is accepted.”
Rehearse peak-day calls
Test a Valentine’s Day request after cutoff, a hospital delivery with incomplete details, a changed address and a caller asking about another person’s order. Review whether the florist can act on each message and whether the caller understood the next step. Monitor unconfirmed delivery promises and correction rates, not just calls answered.
The florist’s delivery brief
- New order, event consultation or existing-order issue.
- Requested date, destination suburb and delivery timing.
- Budget, colour or flower preferences and substitution questions.
- Sender contact details and an order reference where relevant.
- Explicit status: request recorded or order accepted.
Illustrative example: A customer asks for white roses delivered this afternoon. The assistant captures the request and callback number. The florist checks stems and the delivery run before accepting it; a pleasant conversation alone has not placed the order.
Common questions
Can it read a card message back?
Read it back to the sender when needed for accuracy, using your approved process. Keep the message with the order and avoid sharing it in an open team notification.
What if the requested flower is unavailable?
Ask whether the customer would like the florist to discuss alternatives. Record that preference rather than choosing an unapproved substitution.
To assess this workflow for your business, request a Wattle demonstration using a typical enquiry and a difficult handoff from your own operation.
Sources and further reading
Sources reviewed 27 October 2026.