Q: What unique challenges have you faced trying to implement solutions using these large language models?
CIBC approaches emerging technology thoughtfully and with a client-focus, prioritizing that risks and regulatory requirements are thoroughly addressed. Our journey to being #1 in mobile banking is a testament to this; we were first to market and it has been years of meticulous design, development, and deployment to create Canada’s leading mobile banking platform.
GenAI has sparked public interest in a different way than mobile banking. As a result, we’re seeing widespread eagerness from our clients and teams to leverage this technology to simplify daily tasks. The unique challenge has been that eagerness, and that this technology is so new that we needed a more clear and unified understanding of how to effectively implement and use these models.
With so many teams across our bank and the many creative ways to use this technology, we needed a singular view on how people were exploring GenAI – what tools they were looking at and how they wanted to use them. At the same time, we needed to make sure we were collaborating where it made sense to make our implementations more efficient. To manage this, we established a new AI Oversight Committee to centralize and oversee all AI-related activities, ensuring that all risk control groups had visibility into ongoing projects, shared resources and knowledge, and to make sure we were all informed and aligned rather than working in siloes.
Our first significant deployment of GenAI was in our Contact Centres. We introduced a Knowledge Central chatbot (basically the directory where all our process documentation and policies are stored) to answer common client inquiries, with the goal of reducing the time and effort our team members spend escalating calls. Initially, this seemed a straightforward application of a retrieval-augment-generate (RAG) system. However, we learned early on that not all our data was fit for the needs of the models we were using, due to formatting or various factors, and addressing that was definitely a unique challenge. In a business where response time and accuracy are critical, it meant scaling back the content to a more manageable volume for the pilot release. Another interesting challenge was finding some LLMs struggled to deliver specific responses with 100% accuracy when required. This technology limitation meant we had to scale back the chatbot’s scope to exclude use cases involving strict verbatim instructions.
Overall, it’s been an incredibly positive learning experience and has already informed our approaches to other use cases across the bank. The chatbot is showing promising results that are continually improving, team engagement with the system is high, and most importantly we are seeing this enhance our clients’ banking experience as a result.