Training your assistant when your business changes
Agentric Team ·
Your business isn't static — prices change, services come and go, hours flex with seasons. The assistant is only as current as the knowledge you feed it, so the real skill is keeping it in sync.
What drifts out of date
The common staleness patterns:
- Prices — updated on the van/in your head, forgotten in the knowledge base.
- Seasonal hours — summer evening openings, Christmas closure, January surge.
- Service list — added a service but never taught the assistant.
- Staff/coverage — new areas, new engineers, new capabilities.
- Policies — new cancellation policy, new deposit requirement.
The update disciplines
The trigger updates (immediate):
- Price change → update services + FAQs same day.
- New service → add to services before marketing it.
- Holiday closures → update hours before the dates.
- Policy change → new FAQ entry immediately.
The weekly review (from your 15-minute routine):
- Scan transcripts for "I'm not sure" moments → add the missing knowledge.
- Check the questions callers keep asking → new FAQs.
The seasonal sweep:
- Before busy season: review escalation rules, seasonal pricing, availability.
- After changes: test the assistant on the updated knowledge.
The mechanics
The knowledge base is plain text — updating it is editing, not programming. Services, FAQs and free-text notes all feed every call/chat the moment they're saved. There's no "retraining" — the assistant reads the current state every time.
The test-console habit
After any meaningful change, spend two minutes in the test console asking about it: "how much is a boiler service now?" Confirm it knows. That's the entire maintenance loop — update, test, done.
Why it matters
An assistant quoting last year's prices is worse than no assistant. Currency is the feature — and currency is a habit, not a project.