Ingredients
The systems used by this policy are Loop Returns, Zendesk, and Kodif.
What are AI Policies?
At Kodif, we’re excited to announce the launch of Policies—a powerful, dynamic solution designed to revolutionize the way CX managers handle customer support. Unlike traditional flows, which are rigid and complex, Policies empower non-technical users to create and manage customer interactions with ease. Written in natural language, Policies make it simple to define and refine customer experiences without needing to rely on complicated flowcharts or scripting. This approach is not only user-friendly but also self-serve, enabling CX teams to quickly translate existing Standard Operating Procedures (SOPs) into automation, saving valuable time and resources.
The flexibility of Kodif Policies ensures that businesses can offer personalized, context-driven support while continuously improving customer experiences. With Policies, you can experiment with different strategies to optimize outcomes such as CSAT, revenue, and retention—all without the need to rebuild complex workflows. Whether it’s automating routine interactions or testing new approaches for high-stakes scenarios, Policies provide a scalable, adaptable solution that aligns with your business goals. While flows still have their place in sensitive, high-risk situations, Policies offer an agile alternative that helps businesses innovate faster and deliver exceptional, tailored experiences at scale.
“Return order for refund or replacement” ticket type explained
In customer support, the “Return order for refund or replacement” ticket type addresses customer requests to return a purchased item for either a refund or a replacement. This process is crucial for maintaining customer satisfaction and trust, as it directly impacts the customer’s experience with the brand. Handling these requests efficiently requires clear communication, prompt action, and adherence to the company’s return policies.
Which Platforms does this AI policy work on?
This AI policy works on Loop Returns, Zendesk, and Kodif. Additionally, Kodif integrates with all other major platforms, ensuring seamless automation and customer support across diverse systems.
When should I use this policy?
Use this policy when customers request a refund or replacement for their order. This scenario typically arises when a customer expresses dissatisfaction with a product or when there’s a defect or error in the order.
Describe the logic
Type @ to view available tools, use # to reference policies, and add contextual data with $. You can also edit the context in the test screen.
- Ask for the user’s email address
- Use @get_zendesk_account_details to check if the user with that email address exists in Zendesk.
- If the email address is not found, ask for a valid email address.
If the email address is still not found, route it to an agent for further investigation.
Display Recent Orders
- Use @get_loop_returns_orders to retrieve the user’s recent orders.
- Display the list of recent orders and ask the user which specific order they would like to inquire about.
If the order is not found, route to an agent for further investigation.
Check Refund Eligibility
- Use @loop_returns_order_details to check the status and eligibility of the selected order for a refund.
- If the order is eligible for a refund, verify the return and refund conditions (e.g., within the return window, product condition, etc.).
If the order is not eligible, inform the user that the order is outside the refund window or does not meet the conditions for a refund, and provide alternative options (e.g., store credit, exchange).
Initiate Refund Process
- If the order meets the refund criteria, ask the user to confirm their request for a refund.
- Use @loop_returns_issue_refund to initiate the refund process in Loop Returns.
Inform the user that the refund process has started, and provide them with an estimated timeline for when the funds will be credited back to their payment method (typically within 3-5 business days).
Notify the User
- Inform the user in the chat that their refund has been successfully initiated.
Loop Returns will send a confirmation email to the user regarding the refund status and details.
Refund Follow-Up
- Advise the user to check their bank or payment provider for any updates on the refund processing timeline.
If the user has questions regarding the refund status after the estimated time frame, encourage them to reach out for further assistance.
Escalation
- If the refund cannot be processed or if there are any issues, route the request to an agent or create a ticket for further investigation.
- If the user prefers a store credit or exchange instead of a refund, offer these options and use the appropriate tools to process them.
Example policy
Use the policy logic described above for handling return requests for refund or replacement. The commands and tools will reflect the specific integrations with Loop Returns and Zendesk to ensure a seamless customer support experience.
