iVendNext AI Copilot - Set expectations

iVendNext AI Copilot - Set expectations

Known limits and what to flag

Honesty builds trust. Set these expectations during the demo or blueprint so there are no surprises later.


Quote
Set these expectations early. None of these are blockers. Naming them up front makes you the trusted advisor in the room.


Point to flag

How to frame it

Accuracy depends on data quality

Copilot reflects what is in iVendNext. If item costs or valuations are incomplete, margin and turnover will reflect that. Position clean master data as a shared prerequisite, the same as for any report.

Analytics need a management role

Profit and loss, trial balance, margin, branch performance, and similar reports require a management role. Agree the role mapping in the blueprint so the right people see the right things.

Results are list-capped

Everyday lists return up to 100 rows and report tables up to 50 to 100. For very large extracts, the full iVendNext report or an export is the right tool. Frame Copilot as the fast first answer, not a bulk-export engine.

Confirm before you submit

This is a feature, not a limit, but flag it so customers expect the confirmation step on every write. It is what makes the assistant safe to give to frontline staff.

Phrasing affects matching

Fuzzy matching is strong, but a clearer name or code returns a more precise result. When several matches are close, Copilot offers a short list to choose from. Coach users to confirm the match.

Schedule windows

Scheduled tasks are checked on a short cycle, so a task set for exactly now may run within a few minutes rather than to the second. Set expectations for "shortly after" rather than "instantly."


What to steer away from in a first demo

  • Do not free-type extremely large or vague analytical questions on a thin dataset. Prepare the data so each scripted prompt has a strong answer.

  • Do not promise bulk data export inside the chat. Direct that needs to standard reports and exports.

  • Do not demo write actions against production data. Always use a prepared demo environment.

    • Related Articles

    • iVendNext AI Copilot - Appendix

      Limits, defaults & glossary Default limits at a glance Setting Default Notes Requests per minute, per user 10 Configurable by administrator Requests per day, per user 200 Configurable by administrator Actions per question 15 Multi-step questions may ...
    • iVendNext AI Copilot - Troubleshooting

      If something does not look right Most issues resolve in a step or two. Work down this list before escalating. What you see What to do The Copilot button is missing Confirm Copilot is enabled for your environment and that you are signed in. Refresh ...
    • iVendNext AI Copilot - Objection handling

      Cross-questions, answered The questions you will hear in the room, with answers grounded in how Copilot actually works. Can it see salaries, or data my staff should not see? No. Copilot can only access what the signed-in user is already permitted to ...
    • iVendNext AI Copilot - Demo script

      The demo, prepared and scripted A demo that fails is almost always a data problem, not a product problem. Prepare the data first, then follow the script. Data preparation checklist A company with a sensible name, currency, and country set. Six to ten ...
    • Connecting AI

      Overview iVendNext AI Gateway works by establishing a secure, authenticated connection between your iVendNext instance and an AI assistant — such as Claude Desktop or ChatGPT. Once this connection is in place, users can begin asking questions about ...