Supporting article · Knowledge Governance
How to Keep Chatbot Prices, Promotions and Service Information Accurate
Create ownership and review controls so automated replies do not continue sharing expired promotions, old prices or conflicting branch information.
Reply.my Editorial Team
Practical guidance reviewed for clear implementation steps, responsible AI boundaries and honest claims. How we prepare our guides.
Business fit
The client problem this guide helps solve
Best suited for: Businesses whose services, prices, promotions, hours or branch availability change regularly.
Pain point
Important information is copied across documents and staff messages without a named owner or reliable update process.
Business impact
The business risks choosing the wrong scope, paying for unused capability or launching a workflow that creates more manual work instead of a measurable improvement.
How Reply.my addresses it
- The Reply.my team starts by helping you inventory every customer information source.
- We prepare the conversation around information your business reviews and approves.
- During discovery, the team works through how to assign an owner by information type and separate brand and branch fields.
- The agreed implementation also defines how to set expiry and review triggers.
- When judgement or follow-up is needed, the conversation can be handed to staff with the customer context collected so far.
- After launch, the workflow can be reviewed and improved before adding more channels, branches or customer journeys.
Before buying more technology, audit where the current customer journey breaks. For businesses whose services, prices, promotions, hours or branch availability change regularly, the warning sign is that important information is copied across documents and staff messages without a named owner or reliable update process. The repair should produce one controlled approval workflow for customer-facing answers, local exceptions and time-sensitive updates.
Run a 15-minute customer-conversation audit
Sample enquiries from different times, channels or branches. Mark every point where important information is copied across documents and staff messages without a named owner or reliable update process.
Warning signs worth fixing first
Prioritise issues that lose ownership or force customers and staff to repeat work.
- Copying promotions without expiry dates
- Allowing conflicting sources
- Updating one language only
- Letting the assistant guess missing information
Repair order
Do not automate the broken process unchanged. Agree on the correct answer, required customer detail and responsible team first.
- Inventory every customer information source
- Assign an owner by information type
- Separate brand and branch fields
- Set expiry and review triggers
- Test updated answers before release
Where Reply.my contributes
Reply.my manages the approved opening journey and the handover rules needed to support one controlled approval workflow for customer-facing answers, local exceptions and time-sensitive updates. It does not remove the need for staff judgement or accountable follow-up.
- Which source is authoritative?
- Who may approve a price change?
- How are local exceptions recorded?
- What happens when information is uncertain?
Evidence that the repair is working
Compare the repaired journey with your baseline. Look for fewer ownership gaps and more complete next actions, not simply more automated messages.
- Staff time spent on repeatable enquiries
- Complete qualified enquiries received
- Handover completion rate
- Cost per successfully handled conversation
- Customer journeys improved before expanding the scope
Evidence checklist for the How to Keep Chatbot Prices, Promotions and Service Information Accurate audit
Gather timestamps, conversation samples, routing records and follow-up notes. The purpose is not to blame individual employees; it is to understand where the operating system makes good service difficult.
Look specifically for evidence that important information is copied across documents and staff messages without a named owner or reliable update process. Separate isolated mistakes from repeated patterns that justify a workflow change.
- Copying promotions without expiry dates
- Allowing conflicting sources
- Updating one language only
- Letting the assistant guess missing information
Rank issues by customer and business risk
Fix incorrect answers, sensitive-information risks and missing human escalation first. Next, address lost ownership and incomplete lead details. Cosmetic wording changes can wait until the core journey is dependable.
For this topic, the useful business outcome is one controlled approval workflow for customer-facing answers, local exceptions and time-sensitive updates. That outcome should be visible in the way customers progress, the information staff receive and the next action recorded after handover.
- Which source is authoritative?
- Who may approve a price change?
- How are local exceptions recorded?
- What happens when information is uncertain?
Repair policy before automation
If branches or staff disagree about the correct answer, resolve that policy gap before adding it to Reply.my. Automation makes approved information consistent; it cannot decide which conflicting rule the business intends to follow.
Give every policy a named owner and review trigger. Prices, promotions, opening hours and service availability may need more frequent updates than general brand information.
- Inventory every customer information source
- Assign an owner by information type
- Separate brand and branch fields
- Set expiry and review triggers
- Test updated answers before release
Prove the fix with matched samples
Compare similar enquiries before and after the change. Use the same channels, time periods and customer intent where possible. This provides a fairer view than selecting only successful conversations.
Keep a short list of remaining exceptions. Some should become approved flows; others should remain deliberately human.
- Staff time spent on repeatable enquiries
- Complete qualified enquiries received
- Handover completion rate
- Cost per successfully handled conversation
- Customer journeys improved before expanding the scope
Procurement brief for How to Keep Chatbot Prices, Promotions and Service Information Accurate
Give shortlisted providers a written brief containing the current problem, channels, customer volume, branch structure, required languages, approved information owners and staff handover expectations. State that the intended result is one controlled approval workflow for customer-facing answers, local exceptions and time-sensitive updates. This prevents a proposal from being shaped around whichever features are easiest to demonstrate.
Ask each provider to separate included implementation work from customer responsibilities and third-party dependencies. The reply should identify who maps the journey, prepares content, configures accounts, tests the workflow, trains staff and maintains information after launch.
- Defined pilot journey and audience
- Required channels and account ownership
- Business information and approval owner
- Staff roles and escalation times
- Integration assumptions and exclusions
- Review schedule and expansion decision
Decision record and approval gates
Document why the selected approach fits the business, which alternatives were considered and which assumptions still need validation. Agree on a pilot acceptance checklist before signing off on broader deployment. This gives management a clear basis for reviewing progress instead of changing expectations after configuration begins.
The decision should also record the risks identified during evaluation, including copying promotions without expiry dates, allowing conflicting sources, updating one language only, letting the assistant guess missing information. Assign an owner and mitigation for each risk. If a critical dependency cannot be confirmed, reduce the pilot scope rather than hiding the uncertainty.
- Information approved by the business
- Required conversations tested
- Human handover accepted by receiving staff
- Privacy and access responsibilities confirmed
- Baseline and review measures recorded
- Expansion requires a separate approval
For a practical example, explore our Compare Reply.my implementation packages.