Join Online Event for Subscription E-commerce: Learn How Dollar Shave Club and Hallo Collar Resolved 75% Chat Tickets with AI.

Returns: Happy Returns & Salesforce

Tomek Nowinski
01.05.2025

Share this article

Tomek Nowinski
01.05.2025

Ingredients

Happy Returns, Salesforce Service Cloud, and Kodif.

What are AI Policies?

ai policies for customer support

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, “Return order for refund or replacement” tickets deal with requests from customers seeking to return products they are unsatisfied with or have received in error, and either wish to obtain a refund or replace the item. This process is crucial for managing customer expectations and ensuring satisfaction by providing a streamlined, transparent way to handle returns. Efficient handling of these tickets can enhance customer trust and loyalty, reduce churn, and ultimately reflect positively on a brand’s reputation.

Which Platforms does this AI policy work on?

This AI policy operates seamlessly on Happy Returns, Salesforce Service Cloud, and Kodif. Furthermore, Kodif is designed to integrate with all other major platforms, ensuring comprehensive support across diverse systems to enhance customer interaction management.

When should I use this policy?

You should use this policy when customers want a refund or replacement for their orders. It is especially useful in scenarios where customers express dissatisfaction with a product or have received an incorrect item and wish to resolve the issue promptly.

Policy logic

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.

  1. Ask for the user’s email address
  2. Use @get_salesforceservicecloud_account_details to check if the user with that email address exists in Salesforce Service Cloud.
  3. If the email address was not found, ask for a valid email address.
  4. If the email address is still not found, route it to an agent for further investigation.

  5. Display Recent Orders

  6. Use @get_happyreturns_orders to retrieve the user’s recent orders.
  7. Display the list of recent orders and ask the user which specific order they would like to inquire about.
  8. If the order was not found, route to an agent for further investigation.

  9. Check Refund Eligibility:

  10. Use @happyreturns_order_details to check the status and eligibility of the selected order for a refund.
  11. If the order is eligible for a refund, verify the return and refund conditions (e.g., within the return window, product condition, etc.).
  12. 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).

  13. Initiate Refund Process

  14. If the order meets the refund criteria, ask the user to confirm their request for a refund.
  15. Use @happyreturns_issue_refund to initiate the refund process in Happy Returns.
  16. 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).

  17. Notify the User

  18. Inform the user in the chat that their refund has been successfully initiated.
  19. Happy Returns will send a confirmation email to the user regarding the refund status and details.

  20. Refund Follow-Up

  21. Advise the user to check their bank or payment provider for any updates on the refund processing timeline.
  22. If the user has questions regarding the refund status after the estimated time frame, encourage them to reach out for further assistance.

  23. Escalation

  24. 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.
  25. 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

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.

  1. Ask for the user’s email address
  2. Use @get_salesforceservicecloud_account_details to check if the user with that email address exists in Salesforce Service Cloud.
  3. If the email address was not found, ask for a valid email address.
  4. If the email address is still not found, route it to an agent for further investigation.

  5. Display Recent Orders

  6. Use @get_happyreturns_orders to retrieve the user’s recent orders.
  7. Display the list of recent orders and ask the user which specific order they would like to inquire about.
  8. If the order was not found, route to an agent for further investigation.

  9. Check Refund Eligibility:

  10. Use @happyreturns_order_details to check the status and eligibility of the selected order for a refund.
  11. If the order is eligible for a refund, verify the return and refund conditions (e.g., within the return window, product condition, etc.).
  12. 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).

  13. Initiate Refund Process

  14. If the order meets the refund criteria, ask the user to confirm their request for a refund.
  15. Use @happyreturns_issue_refund to initiate the refund process in Happy Returns.
  16. 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).

  17. Notify the User

  18. Inform the user in the chat that their refund has been successfully initiated.
  19. Happy Returns will send a confirmation email to the user regarding the refund status and details.

  20. Refund Follow-Up

  21. Advise the user to check their bank or payment provider for any updates on the refund processing timeline.
  22. If the user has questions regarding the refund status after the estimated time frame, encourage them to reach out for further assistance.

  23. Escalation

  24. 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.
  25. If the user prefers a store credit or exchange instead of a refund, offer these options and use the appropriate tools to process them.

Explore more AI policies

Share this article

Related Articles

Go the extra mile,
without lifting a finger.