What is our primary use case?
I use ChatBot at CGI primarily to quickly find information, understand technical concepts, and improve the quality of my day-to-day work. Since I'm still relatively early in my career with around six to seven months of experience, I often use it as a productive tool to help me learn faster and complete my tasks efficiently. A specific example would be when I'm working on a ticket or trying to understand a new process. If I come across a technical term, tool, or requirement that I'm not fully familiar with, I use ChatBot to give a quick explanation and context about the relevant topic.
It helps me understand the issue faster and draft professional responses, reducing the time spent searching through multiple resources. This allows me to work more productively and confidently in my daily work.
One additional aspect I would mention is that ChatBot helps me learn and become more independent in my role. Since I have around six to seven months of experience at CGI, there are times when I need quick guidance on a process, technical concept, or best practice. Instead of spending a lot of time searching through different resources, I get a clear starting point from using ChatBot and then valid information that I need.
ChatBot also helps me with drafting my emails, summarizing information, and organizing thoughts before meetings or discussions. Overall, it saves me a lot of time and makes my tasks more efficient while helping me build my knowledge and confidence in my day-to-day work.
What is most valuable?
The best feature ChatBot offers in my experience is its ability to provide quick and relevant answers, explain complex topics in a simple way, and assist with content creation. These features are especially useful in a fast-paced work environment where getting information quickly can improve productivity. One feature I use frequently is its ability to summarize information and provide clear explanations of technical concepts. This helps me understand new topics much faster.
Another valuable feature is content drafting. Whether it's creating email drafts, refining responses, or organizing information into a more professional format, I also appreciate how conversational and interactive it is because I can ask follow-up questions and get more detailed explanations without having to start over.
I have noticed improvements in metrics since I have been using ChatBot. From my perspective, ChatBot has a very positive impact by improving productivity and helping employees access information more quickly. It reduces the time spent searching for answers, drafting communication, or understanding new concepts, which allows team members to focus more on their core responsibilities.
One improvement I've noticed in myself is the simplification of routine tasks such as preparing emails, summarizing information, and researching technical topics. This helps improve overall efficiency and reduce the amount of time needed to perform everyday activities. ChatBot also has supported knowledge sharing by making information easier for me to understand and access.
What needs improvement?
Based on my experience, ChatBot has been positive, but there are a few areas I think it could improve. One area is the accuracy of highly specific or organization-related information. Sometimes the responses need to be verified against internal documentation or official sources. Better integration with trusted enterprise knowledge bases would be valuable. Another improvement would be more up-to-date data, contextual awareness, and stronger integration with workplace tools.
For example, being able to seamlessly work with internal document projects, management platforms, or knowledge repositories while maintaining security and compliance would make it even more useful in the professional environment. I would also like to see improvements in handling very complex multi-part queries. More customization options would make ChatBot even more effective.
Different teams and roles have different requirements, so the ability to customize responses based on user roles, projects, or preferred levels of detail would be very helpful. For example, having personalized settings that remember common workflows, writing styles, or frequently used topics could enhance the experience.
I would also appreciate more proactive suggestions based on the context of a conversation, such as recommending relevant sources, best practices, or next steps. These improvements would make ChatBot feel even more personalized and valuable for day-to-day professional work while helping users get the most out of the platform.
For how long have I used the solution?
I have been using ChatBot for quite a while as part of my work at CGI.
What do I think about the stability of the solution?
According to my experience with ChatBot, I have not found any issues with downtime. I have occasionally experienced minor issues such as slower response times during peak usage periods or the need to refresh the session, but these have been infrequent and usually resolved very quickly. I have not encountered any major outages or technical problems that significantly impacted my work. Overall, I would consider ChatBot to be a very stable platform. The reliability has been good enough that I regularly incorporate it into my daily workflow for research, content creation, summarization, and learning activities.
What do I think about the scalability of the solution?
According to my experience, ChatBot appears to scale effectively and has been able to support users effectively without noticeable issues in day-to-day usage. Even as the adoption of AI tools continues to grow, I have generally experienced consistent performance and availability. While I am not involved in managing the platform's infrastructure, I have not observed any major limitations that would suggest difficulty handling additional users or increased workloads. I cannot provide specific stability metrics, but my overall impression is that ChatBot is well-suited for organizations looking to expand with AI.
The cloud-based nature of the platform and its consistent performance suggests that it can accommodate growth.
How are customer service and support?
According to my preference, I did not need to contact customer support frequently because the platform has generally been stable and easy to use. Most of the questions or issues I encountered were resolved very quickly through the documentation, help resources, or by exploring the platform itself. On the few occasions where I looked for support information, I found the documentation and self-service resources to be helpful and easy to understand. The platform is fairly instructive, which reduces the need for direct support in many situations.
Which solution did I use previously and why did I switch?
Before ChatBot, I used ChatGPT. I primarily relied on traditional methods such as search engines, internal documentation, knowledge bases, and discussions. The main reason I started using ChatBot was its ability to provide quick conversational responses and consolidate information from multiple sources into a clear and easy-to-understand format.
What stood out to me was the combination of speed, ease of use, and versatility. It helps me with research, learning, summarization, and content creation in a single platform, which makes it more efficient for many day-to-day tasks. As a result, I now use ChatBot as a complement to traditional resources, especially when I need quick insights.
How was the initial setup?
My setup cost with pricing was very straightforward, and I was not directly involved in my purchasing decision, contract negotiation, licensing, or any setup cost. Therefore, I do not have detailed visibility into the price structure for that. What I can say is that the onboarding and access process was straightforward from a user standpoint, and I was able to start using ChatBot without significant setup or effort.
The experience felt smooth, and there was very little learning curve before I could begin using it productively in my daily work.
What was our ROI?
I have seen a return on investment with ChatBot. From my perspective, the biggest return on investment is time savings and productivity rather than reducing headcount. I have not seen situations where fewer employees were needed because of ChatBot, but I have seen that employees work more efficiently and complete their tasks much faster.
Based on my personal experience, I estimate that ChatBot saves me around one to two hours per week on activities such as researching technical topics, summarizing information, drafting emails, and creating documentation. Another area where I have found value is in faster learning and onboarding. As someone with six to seven months of experience, ChatBot has helped me understand unfamiliar concepts more quickly, reducing the time needed to get up to speed on new topics.
I do not have access to the organization-wide ROI metrics or cost-saving figures, but based on my overall assessment, the productivity gains, time and money savings, and improved efficiency provided by ChatBot offer a positive return on investment for regular users.
What's my experience with pricing, setup cost, and licensing?
My setup cost with pricing was very straightforward, and I was not directly involved in my purchasing decision, contract negotiation, licensing, or any setup cost. Therefore, I do not have detailed visibility into the price structure for that. What I can say is that the onboarding and access process was straightforward from a user standpoint, and I was able to start using ChatBot without significant setup or effort.
The experience felt smooth, and there was very little learning curve before I could begin using it productively in my daily work.
Which other solutions did I evaluate?
Before choosing ChatBot, I was aware of other AI assistants in the market, such as Microsoft Copilot, Google Gemini, and Cloud AI. However, I did not conduct a formal evaluation of these tools myself. My feedback is based on hands-on experience with ChatBot over the past six or seven months, during which I found it effective for research, content creation, summarization, and learning new concepts.
Therefore, I cannot provide a direct comparison because I was not part of the evaluation or the purchasing process.
What other advice do I have?
The advice I would give to others looking into using ChatBot is to view it as a productivity and learning tool rather than a replacement for human expertise. It delivers the most value when used for tasks such as research, summarization, content creation, brainstorming, and understanding new concepts.
I would also recommend investing a little time in learning how to write effective prompts. The quality of the output often depends on how clearly the request is described; providing context, objectives, and specific requirements usually leads to much better results.
Based on my experience with ChatBot, there are a few areas that need improvement. One additional improvement would be integration and workflow connectivity. While ChatBot is already very useful as a standalone tool, it could provide even more value if it had deeper integration with commonly used enterprise applications, knowledge management systems, and collaboration platforms.
This would allow users to access relevant information more seamlessly. Overall, the platform is already very strong, but deeper integration, improved traceability of information, and a more personalized user experience would make it even more valuable.
My additional thoughts about ChatBot have been very positive. Over the past six to seven months at CGI, it has become a valuable tool that helps me work more efficiently, learn new concepts faster, and improve the quality of my day-to-day tasks. What stands out most is its versatility. Whether I need help with research, summarizing information, drafting content, or understanding technical topics, it consistently provides useful support and saves time.
As someone who is still relatively early in my career, it has also been a very helpful learning resource that enables me to become more productive more quickly. I would rate my overall experience with ChatBot as an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
