AI Chatbot Numbers and Dates: Keep Prices and Deadlines Correct

AI chatbot numbers and dates are where small mistakes become expensive ones. A wrong colour description is forgotten in a minute. A wrong price is quoted back to you at the checkout. A wrong deadline sends a customer to your door a day late. An opening hour from last year makes a visitor drive across town to a locked shop. A chatbot that answers from your own content can avoid most of these errors, but only if the numbers and dates in that content are clear, current and consistent. This guide explains why numbers and dates are risky, how to publish them so that Mio repeats them correctly, how to test them and how to keep them fresh.

Talkmio is an AI live chat for websites. Its assistant, Mio, reads your website, FAQ and uploaded documents and answers only from that content, so it never invents prices or policies. That rule puts the responsibility where it belongs: if your content is right, the answer is right; if your content is wrong or unclear, the answer will be too.

Why Numbers and Dates Go Wrong

People read numbers with context. A human colleague knows that last year’s Black Friday price is over. A chatbot reads text, and if an old page still says “30 per cent off until Friday”, it sees a fact. Several things make numbers and dates fragile.

• Old pages stay online. Archived promotions, past events and expired offers are still public pages, and a crawler reads them.
• Two pages disagree. The pricing page says one amount, a blog post says another, and a PDF says a third.
• Dates are ambiguous. “03/04” means March in one country and April in another. “Friday” means nothing without a week.
• Times lack a time zone. “Open until 18:00” is unclear for a visitor in another country.
• Numbers hide in images. A price list saved as a picture cannot be read as text.
• Units and currencies are missing. “From 20” could be euros, dollars, minutes or kilometres.

The general topic of date formats around the world shows how easy it is to be misread by a visitor in another country, and the same care applies to any number, as the basics of ISO 8601 date notation show.

What Mio Does and Does Not Do With Numbers

Mio finds the relevant pieces of your content and writes an answer from them. It does not calculate your prices from a formula you have not published, and it does not know today’s stock, a live delivery date or the status of an order. When the visitor asks for something that your content does not state, Mio should say so, and when the visitor asks about a specific order, it hands the chat to your team. That is a strength: an assistant that refuses to guess is better than one that answers confidently and wrongly.

Tell Mio the same rule in the business instructions: “Quote prices, dates and hours only as they appear in our content. Never calculate totals, never promise delivery dates and never state stock levels. If unsure, say so and offer to connect the visitor with the team.” Our guide to writing instructions for an AI chatbot offers more wording.

Publishing AI Chatbot Numbers and Dates So They Read Correctly

Good habits make answers reliable. Apply them to every page that contains numbers.

Habit	Weak	Better
State the currency	From 49	From EUR 49 per month
State the unit	Delivery 3	Delivery takes 3 working days
Write dates in words	03/04/2027	3 April 2027
Add a time zone	Open until 18:00	Open until 18:00 Vilnius time
Say what is included	Price 99	Price EUR 99, VAT included, delivery excluded
Give validity	10 per cent off	10 per cent off until 30 November 2026

The simple pattern is number, unit, scope and validity. Apply it in headings, tables and sentences alike. When you publish a price list, use text or a table, not an image. You can also upload PDF, DOCX, TXT, MD, CSV and HTML files up to 15 MB each, and a CSV price list is easy for Mio to read. Our guide to AI chatbot pricing questions explains how to keep every price answer correct.

One Source of Truth for Every Number

The biggest source of wrong answers is disagreement between two of your own pages. If the pricing page says one thing and an old blog post says another, a visitor and an assistant may both receive the old number. Choose one page as the source for each type of fact: prices on the pricing page, delivery on the delivery page, hours on the contact page. Let other pages link to it instead of repeating the number. When you must repeat a number, search your site for it whenever it changes.

When two sources do conflict, remove the wrong one from the knowledge base, edit it or delete the page. The plan limits how many pages Mio keeps, so a clean-up also saves space. Our guide to AI chatbots and conflicting sources explains how to find and fix such conflicts.

Dates: Make Time Explicit

Dates need extra care, because they expire. A sentence such as “Our sale ends on Friday” is useless a week later, but it stays on the page. Write the full date, add the year and remove the page when the date passes. For recurring times, such as weekly opening hours, state the days, the hours and the time zone. For exceptions, such as holidays, put the dates in a separate, clearly labelled section, and delete them afterwards. If you have events, mark each one with a status, such as open for registration, full or finished.

Also think about relative words: today, tomorrow, next week, this month. They are fine in a live conversation with a person and risky in published text. Replace them with absolute dates. Our guide to live chat in the holiday season shows how to prepare dated content for a busy period.

Testing Numbers Before Visitors Do

Use Try Mio to test numbers before the widget goes live. It shows the answer, which knowledge pieces were used and how long it took. Build a list of the twenty most common number and date questions: price of each plan, delivery time, return window, opening hours, deadline for an offer, minimum order, warranty length. Ask each one in two or three phrasings, including mistakes and other languages. Compare each answer with the source page, line by line.

Include trick questions: “What is the total for three items?” (Mio should not calculate unless you published a rule), “Will it arrive by Friday?” (Mio should not promise a date) and “Is it open tomorrow?” (Mio should use the published hours and the holiday section). When an answer fails, trace it to the source page, fix the page, re-read the source and test again. Our guide to testing an AI chatbot before launch offers a fuller checklist.

Keeping Numbers Fresh

Good habits around ai chatbot numbers and dates are cheap to keep and expensive to skip.

Numbers change after launch. Build a small routine so that the chat never lags behind the site.

1. Update the page first. Change the number on the page that owns it.
2. Re-read the source. In the Talkmio knowledge base, use the re-read option on the changed page or site, since sources are re-read on demand.
3. Test two questions. Ask the old and the new version of the question in Try Mio.
4. Check related pages. Search for the old number elsewhere.
5. Write the date of the change in a simple internal log.

Put a quarterly reminder in your calendar to review every page that holds a price, a date or an hour. A ten-minute review is cheaper than one angry customer.

Examples for Different Businesses

The same rules about ai chatbot numbers and dates apply everywhere, but the risky numbers differ from one business to another.

An online shop

The biggest risks are delivery times, returns windows and promotions. Publish delivery as a range per region, state the return window in days from delivery and put an end date on every offer. Let Mio hand over order questions.

A software company

Prices, plan limits and trial lengths change. Keep one pricing page, show the currency and billing period and avoid repeating limits elsewhere. Talkmio itself shows prices in euros on its pricing page, with monthly and yearly options, and anything Mio says about plans should match that page.

A local service

Opening hours, holiday closures and appointment lead times matter most. Use the full week in one table, add holiday exceptions with dates and remove them when they pass.

Rounding, Ranges and Honest Approximations

Not every number is exact, and pretending that it is creates problems. Delivery takes “about three days”, a repair costs “from EUR 80” and a class has “around twelve places”. Publish ranges and minimums as ranges and minimums, and say what changes them. Mio will repeat the wording, so a careful sentence such as “Delivery usually takes 2 to 4 working days to most countries; remote areas take longer” produces a careful answer. If you prefer that Mio never quotes approximate figures, say so in the instructions and provide a person for quotes. For safety, state the date on which a range was last checked, so that visitors understand that it may change.

Handling Questions About Totals, Discounts and Tax

Visitors often ask for a total: three items, with delivery, with a code, with VAT. The safest rule is that Mio quotes published prices and rules, but does not do arithmetic on them unless your content gives the formula in full. If your site has a calculator or a checkout page that shows the total, link it. For quotes that depend on a person’s judgement, hand over to the team. State clearly whether published prices include tax, and in which countries. Talkmio’s own pricing page, for example, says that prices are in euros and that VAT is added at checkout, and a good answer from Mio repeats exactly that and nothing more. Tax rules differ by country, so never let a chatbot give tax advice.

The same caution applies to discounts. Publish the code, the rule and the end date, and let Mio quote them. Never let it invent a discount to close a chat, because a made-up offer is still an offer from your company.

Frequently Asked Questions

Can Mio calculate a total price for a visitor?

Mio answers from your published content and does not calculate totals unless you publish the rule. Tell it in the business instructions to quote prices as written and to hand over quotes that need calculation to your team or a calculator page.

How do I stop Mio from quoting an old price?

Update the page that owns the price, delete or edit older pages that repeat it, then re-read the source in the knowledge base. Test the question in Try Mio. Old promotions should have an end date and be removed afterwards.

Can Mio promise a delivery date?

It should not. Mio does not see your orders or live stock, so tell it in the business instructions never to promise delivery dates and to hand order questions to your team. Publish typical delivery times as ranges on your delivery page.

How should I write dates and times for a chatbot?

Write dates in words with the year, such as 3 April 2027, add a time zone to every time, and avoid relative words like tomorrow or next week. Remove dated content when it expires so that Mio does not repeat it.

How often should I review numbers in the knowledge base?

Review every price, date and hour whenever it changes and at least once a quarter. After each change, use the re-read option on the source and test two questions in Try Mio, one with the old number and one with the new.

What happens if two pages give different prices?

The answer may use either one, which is why you should keep a single source of truth. Find the conflicting page, edit or remove it and re-read the knowledge base. Talkmio cannot know which of your pages is the correct one.

The Bottom Line

AI chatbot numbers and dates are safe when your content is clear: one source for each fact, units, currency and time zones written out, dates in words and old pages removed. Tell Mio not to calculate or promise, test twenty number questions in Try Mio and review everything every quarter. Start free with Talkmio and let your chat repeat the right price on the right day.