Leaderboard

It's hard and sensitive for a financial services organization to deal with customer complaints, hence an AI agent is quite crucial. This is a very serious situation that needs to be dealt with in a careful, polite, and lawful way. This is a planned way to help an AI agent perform the appropriate thing in these kinds of situations: Chosen Process: How to Handle Customer Complaints in the Financial Services Sector Why it's hard and important: Customers have a lot of varied feelings. The SEC, FINRA, and GDPR are all laws and rules. Needs to know what's going on, such how the client has talked in the past. You need to do a couple things: find out what the problem is, talk about it, and then fix it. How to Keep AI Working and Running 1. Getting the prompt ready: How to Keep the Agent in Place Using the Role and Intent Method: At the start of the meeting, let the agent know what the tone and goal are. "You are an AI that helps people with their problems." Your main goals are to be clear, understand, be right, and, if you need to, move higher. Don't make any assumptions. Every time, read crucial items twice. Effect: This way of looking at things makes the agent immediately ready to be careful and pay attention to the user. 2. Flow Limits: How to Keep the Agent on the Right Path Divide the procedure into smaller steps, each with its own rules: Acknowledge: Be sure you understand what the issue is. Clarify: Use fixed dimensions like date, transaction ID, and client effect to get information. Putting things into groups, such urgent, legal, and technical, is called triage. Route: Either fix the problem or move it up. You can do this by utilizing logic flags and modifying the state between modules. Don't go forward until all of the important inputs are locked. For example, if the complaint isn't clear, stop what you're doing right now. 3. Checkpoints: Things to Do to Make Sure the Built-In Method Is Right: Add checkpoints before doing something important to make sure it's right. "To be clear, you're talking about a $1,200 charge that was questioned on June 3, 2025." Is that actually true? Effect: It makes it less likely that there will be a misunderstanding and makes sure that the AI and the user agree on the facts. 4. Questions to help you understand: Questions that are proactive and take the situation into account Instead of asking, "What went wrong?" try saying: "Please tell me what happened right before the problem." "Have you tried to fix it yet?" Use templates that match the type of complaint for follow-ups that are specific to the location. 5. Dealing with red flags: things that make you feel awful and make things worse. How to do it: Teach AI how to look for signs that things are becoming worse, like A lot of thoughts like "I'm so mad" and "This isn't right." There are words like "lawsuit" and "compliance" in the law. What to say: "I know this is really annoying," therefore you should know how people feel. The human escalation workflow should start on its own when certain conditions are met. 6. Things you can't know: How to Stop Giving Out Too Much Information: Use short response templates and seek for help if you need it. "I wrote this down for the people on our team who make sure we follow the rules." They will get back to you in a day. "This happened because it was hard to compare data from different countries..." Control: Based on how serious the complaint is, choose how many tokens and how much information to supply. 7. Things that help you recall and go over short sessions Check the facts every now and again to stay on track: "Here's what I've come up with so far: 1) They charged too much on June 3; 2) They haven't answered my support request since then; 3) I'm asking for a refund and an apology. Pro: It keeps both sides on the same page and makes it easier for conversations with more than one turn to go well. What happens in real life Checkpoints and modular flow make sure that things don't happen again or go in loops, which helps things run more smoothly. Boundaries help you stay on the right side of the law and make it easier to go forward. Using prompts and summaries that take tone into account indicates that you care about your users and know what you're doing. Conclusion AI agents can deal with tough situations rather effectively, but only if the interface is good. Usage of prompt-framing based on role-based, progressive flow control and empathy related checkpoints all together results in organized process but yet focused on customer/person. This enables the business to run smoothly with people on track with low risk and trust.

I would like to consider an example of an AI Agent handling employees queries to answer this requestion. Payroll queries for high-stake and very sensitive. If not addressed properly, it may directly impact on employees morale and unwanted escalations. This agent includes below steps: Understand nature of the query (Under payment, excess tax, leaves, bonus, etc.) Verifying KB (ERP, HRM Tool, Bank statement) Communicate responses Ensure compliance Techniques to keep AI interaction focus and efficient: Vague framing: “Let me help you on your question by referring database.” Role- based framing: “As your payroll assistant, I will guide you on underpayment issue and escalating if needed.” Structured Flow: Identifying issue and reconfirm from the user. Collect data, verify compliance from KB and summarize Escalation path as per the nature of query Resolution and follow up on the query Insert confirmation check point, e.g. “Is this accurate before we proceed?” Context retention by referring to the conversation in the past. Prompt should include emotions and avoid unwanted verbiage unless asked. Keep taking feedback and rating on user experience.

During multi-step or emotionally charged interactions like guiding a customer to raise a complaint in a Telecom company, AI agents can sometimes go off-topic, providing unnecessary or wrong details or misinterpreting the user’s response. It is important to keep improving or applying adequate measures to keep improving User experience. Here are some of the techniques that can be applied to keep the interaction meaningful, focused and efficient – 1. Use brief and clear messages describing the purpose of the agent. This helps to establish the purpose and clarifies the boundaries of the agent. 2. Breaking down the interaction into logical steps to be able to gather information in a concise manner – eg ; understanding the nature of problem (network issue, billing problem, etc.) , gathering relevant details like ( date of issue , phone number, effected service etc.) . It may take more than one question to determine the problem. 3. Summarize the problem statement and ask for user confirmation before moving ahead with the next step like raising a complaint. 4. In case of uncertainty or unable to determine the nature of complaint due to vague or phased answers from the user, offer fallback mechanisms like encouraging the user to rephrase their statement or offering the user to be able to speak with a customer care executive 5. Also, it is important to use polite expressions and add empathy as appropriate.

This is very important in a highly regulated and data sensitive domain like healthcare. I would include below features in an AI agent to ensure focus, efficiency and answer with precision 1. Prompting: Clear Role and context setting early in the conversation to avoid tangents- this will ensure the agent anchors to specific role. Example of such Prompt Framing could be : “Hey there! I’m your virtual assistant here to help you escalate claims issues quickly and accurately. I’ll ask a few questions to get to the bottom of the problem and guide you to the right solution or team. Let’s get started.” 2. Flow Constraints: Implement Decision Trees and Guardrails to Stop long-winded answers or unnecessary diversions. Agent should Create step-by-step flows based on known scenarios (for instance, if there’s a denial reason, check if documentation is missing, then escalate). Also, agent should offer limited options instead of open-ended questions where clarity is required. For Example, agent can ask: “Is the claim denial related to one of these and wait for user response?” · Authorization issue · Eligibility · Coding error · Not sure This makes sure to keeps both the user and AI focused on a clear path and makes it easier to map backend logic and escalation rules 3. Checkpoints: Agent should confirm understanding before moving forward to avoid misunderstandings and backtracking For eg,“Just to confirm — the claim was denied for CO-109 (missing documents), and you’d like to escalate this because you did submit supporting files. Is that correct?” AI agent should use yes/no confirmations along with summary feedback. This will ensure agent is aligned with the user and automatically cuts down on misdirected escalations or wrong team routing 4. Clarifying Questions: Agent should only Ask clarifying questions when Necessary and keep them specific Good AI question would be “Do you have the reference number or denial code?” instead of “Can you explain everything for the particular claim” 5. AI Agent should mention audit trail and explain the next steps. This is to ensure user knows why a step is necessary or who’s going to take care of it.. For eg: Agent should respond like” “This needs to go to the Membership Correction team because the provider ID seems to be mismatched. They typically resolve it within 48 hours.”

Any AI agent is adept in solving objective questions and is very simple. But when an AI agent is used for continuous interaction and workflows to solve a problem, then the AI design will have to consider factors such as clarification of the issue , summarize the questions at appropriate stages, managing the memory from previous interactions, focus on the goal which is the very purpose of the interaction, more importantly empathizing with the user etc to ensure the AI agent is helpful and focused and efficient in addressing the problem. I can think of a process which I was planning to implement in my company, and this question really picks my mind to consider many things though my plan is to start small and focus to a specific area. Let’s say, I have developed an AI agent to address user issues related to invoicing. Going by the ticketing history, most of the invoice related issues will have the ticket description as “Not able to print invoice” So, my AI agent will have to ask user to do some checks, based on the result of those checks, there will be some other checks and based on that some other action will be directed to the user. Sometimes it can go to 5 or 6 checks before identifying the root cause. This is basically emulating the manual trouble shooting by the support personnel. Let’s say a POC is as below. AI Agent – Hello, how can I help you with your invoice related issue? User – I cannot print invoice for an order AI Agent – Do you intend to run invoices for all the lines in the order or specific lines? User – Only one line in the order which must be urgently dispatched AI Agent – Is the status of the order line at “58” User – Yes AI Agent – Do you see in the application any hold code for the order line you intend to invoice User – No AI Agent – Is there a price for the line you intend to invoice? User – Yes AI Agent – Can you give me the version of the invoice you ran? User – INVSO3 AI Agent – Sorry, no version exists, please use version INVSO3I User – it was a typo; I ran the correct version INVSO3I AI Agent – will you be able to check the scheduled invoice date if it is today or lesser date? User – I don’t know AI Agent – Can you open application PSINV25U? User – Sorry I don’t have access AI Agent – Should we first create request for you to have access? User – I need this to be resolved urgently AI Agent – Sorry, please raise an IT ticket, so a support staff can assist you better. From the above POC, what I see is the design of the AI agent is vey direct and straight forward, but after reading about this topic I need to tinker a bit the design so the AI Agent will also exhibit the following: Being Empathetic, understanding user sentiments and respond accordingly: The user is in a hurry to take invoice print for the goods that must be dispatched from the warehouse. The trucks are waiting. So instead of “Do you intend to run invoices for all the lines in the order or specific lines”, I would recommend “Sorry to hear that, don’t worry we can resolve the issue together quickly”, would be a better response from AI that gives an assurance to the user and calms the user. Summarize the issue for better user engagement and focus: Instead of asking for repeated checks in isolation, I think after couple of checks there could be a summarization like” the status is correct, there is price, there are no holds, still not able to invoice, interesting, bear with me for few more checks”. So, the user would be engaged and not frustrated, and the user will know the AI agent is analyzing and really trying to troubleshoot with the inputs of the user Focus on goal though there are several checks and misleading inputs: Instead of asking user to solve the access issue, which was not the very purpose of the interaction , it could have said “ No problem, can I connect you with a support agent to resolve the invoice prints, so the issue will be resolved in the next 15 minutes, is it ok?” something like this I am wondering. Also, I am thinking of making communication very efficient, which would require more iterations and use cases. Overall, I feel using the above steps or techniques a conversational AI can navigate multiple step processes/workflows and emotionally charged interactions, effectively ensuring that the user feels engaged and the interaction is productive

To keep AI agents effective in complex or sensitive user journeys specially during complaints or escalations it is important to apply a structured conversational flow. Clear prompt creation followed by clarifying statements guiding through emotion aware language and paths. The result is helpful and trust building interactions reduce errors, help in reducing customer complaints and improve overall user experience. AI listens, learns, adapts and deliver with continuously improving

To keep an AI agent focused, helpful, and efficient during complex or sensitive tasks the most important steps are  Prompt Framing: Definitely what’s goes in is what comes out. We need to set the right expectations upfront. Clear Goal oriented prompt is required.  Flow Constraints: We need to breakdown the process step by step and have the limited scope of conversion with each step. This keeps AI away from guessing and molding the answer.  Clarifying Question: AI should be trained to ask question for clarification in case of vague prompt. Be precis to reduce misinterpretation.  Summarizing : Recap before progressing to the next stage for reconfirmation .  Understand the emotions and escalation detection: Recognise the shift in tone and handle sensitive issue appropriately. These Steps help us improve the accuracy & focus and also enhance user experience, trust and satisfaction. Nidhi

Our company use AI Agent for customer complaint solutions My Company use some techniques to keeping AI Agent focused on target and keep always efficient My company use some of the following techniques Prompt framing - Clear, simple, and concise language Use simple and direct language in prompts to ensure the customer understands the required very easy - Specific target Clearly define the goals and objectives to keep the customer focused - relevant Information Provide relevant information to help the AI agent understand the customer's needs Design of Flow - Structured of process flow This is very important technique Design and structure of process flow that guides the customer through the process - Decision Trees should be very clear Checkpoints - Regular summaries Provide regular summaries of the conversation to ensure the customer is on track and understands the progress -Confirmation Steps Include confirmation steps to verify the customers' understanding and agreement with the next steps. Clarifying Questions - Use Open and ended Questions - Use follow up questions to confirm understanding My company can use Natural Language Processing (NLP) to analyze customer input and detect potential issues or misunderstandings Also, we can use sentiment analysis to detect the customers emotional tone In additional, we can use customer Feedbac

For me personally, in several of my past prompts, especially when crafting scripts for my video contents as a content creator, or drafting a LinkedIn post or reflections on an event or workshop I attended, I have noticed ChatGPT would often go off track: too generic, too wordy, or just not sounding like me (Using big English words which is unlike me because my vocab isn't that great lol). One early example was when I asked for a LinkedIn post about my first time speaking on a panel. I wanted it to sound honest and personal, but the AI kept giving me something that felt too polished or like it came from a template. I had to keep replying: “This doesn’t sound like me,” or “This is too generic" or "This sounds cliche" Another time was when I asked for a birthday message to a friend and wanted it to sound like me. I was clear that it shouldn’t bring in generic birthday messages and big words, but then, it still found ways to bring it in. It took several tries to get it right, I had to be more specific and say, “Avoid anything this and that, and just keep it sincere and light.” One major shift happened when I learned to guide ChatGPT with better instructions after taking the CAISA training which had a section on prompt engineering. Instead of long, open-ended prompts, I now break things down: I start with the tone, then the structure, then the exact outcome I want, giving it proper context. Also, learning about temperature settings helped. When I need it to stay focused, like writing a formal email or drafting a workshop plan or even during complex conversations, I reduce the temperature, so it doesn’t get too creative. And when I noticed it repeating itself or giving extra fluff, I started using token and top-p adjustments to limit that. Over time, my prompts have become clearer and more direct, and the ChatGPT started responding better. I still have to correct it sometimes, but now I understand why it goes off-track and how to pull it back.