Our Information Changes All the Time
Authava keeps your bot current: must-be-right facts are edited in one place, your website can be re-crawled, and documents can sync automatically from where your team keeps them. When your prices, hours, or policies change, your bot changes with them.
Why Do Bots Go Stale?
Most bots are trained once and forgotten. Then prices change, a service is added, holiday hours come and go, and the bot keeps giving last season's answers.
What Do Businesses Usually Try?
- Retraining or rebuilding the bot. It's accurate afterward, but slow, so it doesn't happen often.
- Updating the website and hoping. The bot only knows about it once someone re-crawls the site.
- Telling the staff. The team knows, but the bot doesn't.
The update happens in one place but not the others.
How Does Authava Solve It?
- Authoritative text holds must-be-right facts like prices and hours. Edit them once and they take priority over everything else.
- Re-crawl your website after you update it, so the bot picks up the changes.
- Upload or replace documents in Studio. See Update Your Bot's Knowledge.
- Automatic document sync. Our team can set up a workflow that watches your Google Drive, OneDrive, or SharePoint folders and uploads new and changed documents, using a workflow tool such as n8n, Zapier, or Make.
What This Looks Like in Practice
You raise a price on Monday. You change it once in authoritative text, and the bot quotes the new price from then on, ahead of any older page or document.
Frequently Asked Questions
How do I update my bot's prices or hours?
Update them as authoritative text in Studio, and they take priority over older information.
Does the bot pick up changes to my website?
Yes, after a re-crawl. Choose Re-crawl in Studio when your site changes.
Can documents update automatically?
Yes. A workflow can watch your Drive, OneDrive, or SharePoint folders and upload new and changed documents to your bot.
How is this different from retraining a chatbot?
You edit the fact once, and it takes priority from then on, without rebuilding the bot.