Guide FloatChat

Floatchat- User Guid

How to reduce return to origin (RTO) orders

Event                                   Tag Name and Updated Against #

 

A user places a prepaid order                                 => prepaid

A user places a COD order                                      => pending

A user confirms the COD order                              => confirmed

A user cancels the COD order                                 => cancelled

A user converts the COD order to prepaid           => cod_canceled, converted_cod_to_prepaid

A user places a COD order again                             => cod_confirmed, cod_after_cod_canceled

To filter orders in the Floatchat Admin Console, agents can utilize the following tags: #

– Prepaid: This tag is assigned when a user places a prepaid order.

– Pending: This tag is assigned when a user places a COD order.

– Confirmed: This tag is assigned when a user confirms the COD order.

– Cancelled: This tag is assigned when a user cancels the COD order.

– Cod_canceled: This tag is assigned when a previous COD order is cancelled and converted to prepaid.

– Converted_cod_to_prepaid: This tag is assigned when a COD order is cancelled and converted to prepaid.

– Cod_confirmed: This tag is assigned when a user places a COD order again using a prepaid link.

Triggers can be added for the following events

– Cod_after_cod_canceled: This tag is assigned when a newly placed COD order is cancelled after a previous COD order was cancelled.

Agents can utilize these tags to effectively filter and manage orders in the Floatchat Admin Console. If you have any further questions or require assistance, please feel free to ask!

What are your feelings
Scroll to Top