how to send quotes on WhatsApp with AI without getting the price wrong.

Quoting on WhatsApp looks simple: the customer asks, you reply with a number. In practice, mistakes keep showing up in the same places. The quote uses the wrong season's rate because nobody checked whether the requested Saturday falls in high season. Travel to a distant venue is forgotten. An add-on is added up wrong. An old rate goes out because it was copied into a quick reply. And when an unchecked language model writes the quote, a new risk appears: it makes up an amount that sounds reasonable but that your business never set.

A price mistake in a chat cannot be undone: the customer already took a screenshot. The question is not whether AI can quote, but how to split the work so the number never depends on what the model "thinks".

The split that works is this: the AI agent understands the conversation and decides what is being quoted (date, time slot, package, add-ons and venue), and a deterministic function calculates how much it costs with the current price list. The system writes the text with the amount, not the model. If a price is missing, the right answer is not to quote and to alert the team, never to fill the gap with an estimate.

So the agent names products ("Plus package", "Extra hour") and the system looks them up in your list. If the customer asks for something that does not exist, the agent asks or escalates.

Almost every rental or events business has prices that change with the date. The problem is that "high season" usually lives in someone's head. To quote without errors, each season needs written rules, and there must be a clear order when two rules match the same date. A sensible order, from most specific to most general:

• Specific date: a holiday or the eve of one with its own price.
• Weekdays: for example, Fridays and Saturdays.
• Date range: December through February.
• Base season: the one that applies when nothing else matches.

With that order, a January Saturday that is also a holiday takes the holiday price, no debate. Before letting anyone (or anything) quote, test your rules with a simulator or, at least, a list of tricky dates: the first Saturday of high season, the last day of a range, a holiday that falls on a weekday.

An incomplete quote forces a second quote, and the second one almost always has a different number. Define which details are required before giving a price. In an events business they are usually: date, time slot, event type, package, add-ons, venue or district (for travel) and guest count if it changes the service. A good agent asks for them one at a time, in the conversation, and only quotes once it has them.

Not every quote needs the same level of control. The sensible path is to start with human review and switch to automatic sending once you trust your price list.

Ideally you can mix them: automatic in low season and review in high season, or review only for one event type.

Many double bookings start with a misunderstanding: the customer got a quote and believes the date is theirs. Make it clear in the message that the quote has an expiry and that the date is held separately, with a deadline to pay the deposit. If you hold dates, set an expiry time, send a reminder beforehand and release the date if the deposit does not arrive. We cover it in detail in how to prevent double bookings.

A quote with several lines, add-ons and conditions can be long. WhatsApp accepts messages of up to 4,096 characters, but Instagram cuts off at 1,000 and rejects anything longer. Split the text into shorter messages instead of truncating it, and avoid asterisk bold or other formatting the channel shows literally. If you quote by email, reply in the same thread.

An agent that can lower the price ends up lowering it. If you give discounts, have a person on the team give them, and make sure the quote is not recalculated on its own over a price someone set by hand.

In heysteff these rules live in the Bookings module. You set up packages, add-ons, rule-based seasons, prices by unit type and travel by venue or district, and test any date in the simulator. The agent passes date, slot, package and add-ons by name; the system calculates the total and the quote goes out as its own message. The model never sees or writes an amount, and with no price there is no quote.

You choose the mode (automatic, review or manual; review is the default) and can change it by season or event type. The quote is split to fit the channel's length, and if the team set a price or a discount, the agent does not requote. And if you turn on holds, the agent can take the date only after a sent quote with the current total, for the time you define (48 hours by default), with a reminder and automatic release. Your team always does the confirmation, when the deposit arrives.

For events businesses, see also AI for event rental businesses; for tours and equipment rentals, AI for tours and experiences.

Related: Bookings module, how to prevent double bookings, WhatsApp payments and copilot mode.