Webinar recap: How to make AI work for support teams

e-Core • June 20, 2025

Earlier this month, our team hosted a live session discussing how customer support leaders can prepare their operations for AI. Whether you’re running a mature support org or a startup in “founders mode,” the core message was the same: AI will amplify whatever structure you already have, whether it’s working or not.


Below are the main highlights and takeaways from the conversation, led by Adriele Radmann, IT Support Leader at e-Core, and Bernardo Costa, Service Delivery Manager.


Key support challenges and how AI helps

Adriele started the session by pointing out a pattern that’s been seen across organizations of all sizes: rising ticket volume, more technical escalations, and customers expecting faster, more accurate answers.


Although it’s tempting to throw AI at these problems right away, she highlighted that AI is only as good as the structure behind it. If the foundation is broken, AI will only scale that dysfunction.


Still, AI has tremendous potential when applied with the right strategy. Bernardo’s section of the webinar focused on six common challenges it can help solve:


High ticket volume and repetitive inquiries
AI can reduce response times by up to 70% by handling repetitive cases with your company’s own data and workflows.



Poor ticket prioritization
When everything feels urgent, it’s hard to focus. AI can automatically learn from past tickets to flag what really matters, and act accordingly.

The image below illustrates the ideal process to address this challenge.

Misdirected escalations
Instead of wasting time bouncing between teams, AI can route tickets accurately and even resolve some on its own, using your documentation and playbooks.


Lack of sentiment analysis
AI can detect tone and emotion in customer messages in real-time, helping deliver more empathetic support and escalate to humans when needed. This helps uncover 
unspoken customer needs and prioritize accordingly.


Outdated documentation
Let AI detect patterns in closed tickets, generate root cause analyses, and proactively
 update knowledge base articles.



The image below illustrates how this cycle is truly meant to function, with each stage closely connected to the next.


Balancing cost and quality
Yes, AI reduces costs, but it also unlocks opportunities for better support and upsell. In one of our 
client cases, a tailored AI solution led to:

  • 50% longer sales calls (more engagement)
  • 20% more effective calls
  • Instant feedback for sellers

What AI needs to deliver results
According to Adriele, before jumping into implementation, there are three things you absolutely need to get right:


1. Data quality

Start by collecting all your historical customer interactions: tickets, chats, emails, etc. Clean up your knowledge base and make it easy to find, use, and update.

Don’t underestimate the power of internal comments and contextual notes; they can serve as the training ground for your AI assistant. Assign ownership for content, and treat documentation as a living part of your support system.

Plus, we included a tip that might make this process easier for you:

Knowledge Base


Tip: Well documented tickets can be source of knowledge for both AI and
human agents and drive continuous improvement


2. Clear processes

AI depends on well-defined workflows for ticket triage, escalation, prioritization, and resolution.

Map your entire ticket journey, from first contact to resolution. Regularly review and adjust your support tiers, SLAs, and internal handoffs. If your Tier 2 can now handle Tier 3 issues, that should be reflected in your processes. AI will only follow what it’s trained on.


3. Integrated tools

Your ticketing platform should centralize all contact channels and workflows. That’s where AI will live, learn, and act. If the setup is fragmented, AI will be too.

And don’t forget your metrics: monitor not only FRT and CSAT, but also how AI is performing on resolution accuracy and escalation rates. Combine these with qualitative feedback to get the full picture.


The human-AI balance in customer support

To close the session, Adriele took on one of the most pressing questions support leaders face today: Is AI replacing human agents? In her view, AI isn’t here to replace human agents, it’s here to empower them.

Let AI handle:

Let humans handle:

  • Empathetic conversations
  • Edge cases
  • Strategic decision-making
  • Training and fine-tuning the AI

As Adriele said during the session, “Put the right player in the right position.”

By taking the time to structure your support team, your data, your workflows, and your tools, you’ll be setting up both your people and your AI for long-term success.



If your team is exploring how to apply these strategies in a real environment, our Product Support Services are designed to help.

 

From structuring your support layers to implementing AI and automation, we work as an extension of your team to turn every interaction into an opportunity to grow.


Ana Quaresma

Marketing Analyst at e-Core


e-Core

We combine global expertise with emerging technologies to help companies like yours create innovative digital products, modernize technology platforms, and improve efficiency in digital operations.


You may also be interested in:

By e-Core July 31, 2025
Energisa modernized 70 systems by migrating to AWS with e-Core’s support, gaining scalability, availability, and performance in the energy sector.
By e-Core July 22, 2025
A strategic approach to modernizing code At e-Core, we often partner with organizations whose software technically “works” in production, but just barely. Over time, shifting teams, competing priorities, and tight deadlines lead to codebases that are fragile, expensive to maintain, and risky to enhance. In this context, software refactoring becomes more than a technical task. It’s a business strategy that preserves continuity while unlocking future growth. Defining refactoring: Evolution without disruption Software refactoring is the disciplined restructuring of existing code, improving readability, modularity, and performance, without altering its external behavior. Unlike a full rewrite, refactoring delivers incremental value by: Accelerating feature delivery through cleaner, more modular code. Reducing operational risk by eliminating brittleness and regressions. Lowering total cost of ownership by making enhancements less labor-intensive. Why refactoring matters for business  Healthy codebases have a direct business impact: Faster Time-to-Market: Modular components support parallel development and faster releases. Greater resilience: Decoupled services isolate failures and simplify maintenance. Easier onboarding: Clear architecture and design patterns help new developers ramp up quickly. Sustainable cost savings: Less firefighting, fewer regressions, and lower maintenance overhead. What may look like a simple “cleanup” is often the first step toward digital reinvention. Refactoring techniques In enterprise environments built on Java, C#, or Python, we apply proven object-oriented refactoring techniques to increase cohesion and extensibility: Class decoupling: Split monolithic classes into focused, single-responsibility components. SOLID principles: Apply interface segregation and dependency inversion to stabilize architecture. Composition over inheritance: Build flexible, interchangeable structures. Testability enhancements : Isolate side effects and inject dependencies for better test coverage. These techniques form the foundation of our incremental software refactoring roadmaps. Beyond OO: Choosing the right tools for each paradigm Modern languages blend programming paradigms. We help clients apply the right tools to the right problems: Functional patterns in Python to create concise, side-effect-free data pipelines. Kotlin/Scala hybrids that combine OO structure with expressive functional constructs. C# LINQ and Async for declarative data queries and scalable concurrency. This multi-paradigm approach ensures that systems remain robust, flexible, and expressive. A refactoring story: From debt to differentiation Case Study: Regional logistics provider
By e-Core July 16, 2025
Background Ricksoft is known for its popular work and project management apps on the Atlassian Marketplace, including WBS Gantt-Chart for Jira and Excel-like Bulk Issue Editor for Jira. Originating in Japan, the company has grown to serve over 8,000 customers worldwide through nine apps. Their tools are trusted by some of the world’s most innovative companies to boost productivity and manage complex work. By 2019, Ricksoft was seeing growing demand from customers in the Americas and Europe, and needed to scale its support operation beyond Japan. To serve new markets effectively, they had to provide fast, high-quality service in English and across time zones, while maintaining the responsiveness and care that defined their brand. That’s when they turned to e-Core. Our approach We designed a support solution based on three key principles: timezone alignment, consistent high-quality service, and cultural alignment . To get things right from the start, our analysts flew to Japan for in-depth training. They didn’t just learn the products; they learned how Ricksoft works , communicates, and supports customers. Once training wrapped, we built the support operation around Ricksoft’s priorities: timely responses, consistency, and a thoughtful, human tone. We created detailed documentation and a clear process for hiring and onboarding, ensuring every new analyst could step into the role with confidence and alignment. We also introduced monthly updates to the knowledge base and took responsibility for keeping existing articles relevant. That work paid off: most tickets are now resolved in just two to three exchanges , and self-service performance has improved across the board. Today, Ricksoft holds a satisfaction rate of 89 percent and a CSAT of 4.63 out of 5 , well above industry averages. As new analysts joined over the years and support expanded to more products, the service quality remained consistent. “We place great confidence in e-Core’s hiring decisions,” says Alessandro Cristiano, Support Manager at Ricksoft. “They understand how we work, and their mission, values, and culture attract good talent. We had five different generations of agents in seven years, and the work was consistent all the time.” Building long-term value through support. To make support even more impactful, we set up a feedback loop between support and product. Recurring issues and feature requests are flagged and shared with product managers, turning support into a valuable channel to inform product strategy. Tone and empathy matter, too. Ricksoft’s brand is rooted in respect, clarity, and thoughtful communication. We greet returning customers by name, tailor our closings, and have consistently met their SLA targets—with 99% first-response compliance within 12 hours or less. “What is special about e-Core is that they listen first,” Cristiano says. “They don’t try to mold things just for efficiency if it doesn’t work for you. First, they absorb your culture, and then transform it.” To strengthen Ricksoft’s presence in the Atlassian Marketplace , we introduced a post-ticket review request process. That simple step led to more customer reviews, better app ratings, and increased visibility. “We’re now at the top search results, which helps increase our app installs, and ultimately our revenue,” says Cristiano. We also monitor Ricksoft-related activity in the Atlassian Community. When their apps are mentioned, our team responds quickly and accurately, helping Ricksoft remain visible, helpful, and credible in the ecosystem .