
I use ChatBot to support our packaging supply chain and client service work at EcoPack Solutions UK, and the feature I value most is its knowledge base training paired with configurable AI agent workflows. I upload our compliance guides, food-contact packaging specs, lead time matrices and sustainability data sheets, so our customers and internal site teams can pull answers anytime without pausing our production supervisors.
The file upload and website sync functionality cuts down my routine enquiry handling significantly. This setup saves me roughly three hours each week that I previously spent repeating answers about LFGB compliance checks, minimum order quantities and recycled material stock availability. I built separate chat paths for pharmaceutical packaging clients, retail brand buyers and our warehouse teams, with tailored response rules for each group.
An unexpected benefit is how it filters simple repetitive tickets before they land on my operations team. Basic questions about delivery lead times or certification document requests get resolved automatically, leaving my supervisors free to focus on urgent supply bottlenecks or quality non-conformity reviews. We embedded this bot on our client portal, and it links through to our shared document library. It also keeps a clean conversation log we can reference during our weekly compliance review meetings, helping us spot recurring client questions we should address in our public guidance packs. Review collected by and hosted on G2.com.
My main pain point with ChatBot is its limited granular permission and audit logging, which creates headaches for our UK packaging compliance work. We handle sensitive food and pharma packaging documentation, which falls under LFGB and UK REACH rules, and we need to track exactly which documents the bot accessed and which user pulled regulated specification data. The current logs only record basic chat messages, not the exact source file snippets used to form replies. This forces our quality team to manually verify every regulated response, adding roughly two hours of validation work each week.
I also struggle with its weak conditional logic for multi-stage supply chain queries. Our buyers often ask layered questions combining lead times, material availability and certification validity. The bot frequently fails to connect these data points and gives disjointed answers, so staff still escalate many complex supply questions straight to me.
Another issue is the clunky bulk knowledge-file management. When we update our compliance sheets after regulatory revisions, deleting or replacing outdated files one by one is tedious and error-prone. Outdated guidance can linger in the bot’s memory if I miss a file.
I’d like source-level citation logs for all bot replies, richer multi-variable conditional branching for supply chain questions, and bulk archive/replace controls for knowledge files. These tweaks would make it suitable for regulated packaging client support rather than just simple FAQ handling. Review collected by and hosted on G2.com.