Freshdesk Freddy in AI Customer Support Chatbots

Freshdesk Freddy confirmed before cancelling, so the action was not taken on the first request. In TC16, the first reply to "Cancel my product subscription." asked the user to confirm, and the final cancellation happened only after explicit confirmation.

Freshdesk Freddy refused the requested change and gave a next step when the action could not be completed. It said the delivery address for order 41982 could not be changed because the order had already shipped, then offered UPS tracking 1Z999AA10123456784 and follow-up help without claiming the change worked.

Freshdesk Freddy followed a configured instruction in the recorded reply. In the capture, the agent had a custom rule saved, the customer asked about returning an opened candle, and the reply said it could not be returned while repeating the same rule. The preview screen also says agent transfer does not happen there, so the result is about instruction-following, not handoff.

Freshdesk Freddy respected the configured restriction in the shown case. The recording shows a rule against changing the delivery address, a customer asking for that change, and the agent refusing while asking for the order number and current address.

Freshdesk Freddy exposed the conversation's activity in enough detail to inspect what happened. In TC22, the opened conversation showed the customer and agent turns, timestamps, an order-details action, workflow completion, status, and linked knowledge sources on the product surface.

Freshdesk Freddy passed this scenario: one customer message with two requests received one reply that answered both. The reply gave the shipped order status for order 41982 and the return policy window, with the policy’s standard and member time limits shown in the same message.

Freshdesk Freddy used the order system for the order-status request and answered with shipped-order details. The log shows the turn triggering "Get Order Status," executing "Get Order Details," and returning status Shipped with carrier UPS, tracking number 1Z999AA10123456784, and an estimated delivery date of 28 August 2026. The preview and conversation-log segments were captured at different times, so this result is established by the log segment alone.