Notes
Notes - notes.io |
cx concern - fake offer query , information shared ,
(QUALITY ISSUE ):-
cx had issue with qulaity of order , quality not as expected , request taken , TAT shared .
(SIZE ISSUE) :-
cx concern - size issue , request taken , TAT shared .
(DAMAGED ITEM) :-
cx concern - damaged order , request taken , TAT shared .
(WRONG ITEM):-
cx concern - wrong item delivered , request taken , TAT shared .
(ITEM NOT WORKING):-
cx concern - item wasn't working , request taken , TAT shared .
(RETURN STATUS AFTER PUC) :-
cx concern- return status , order was marked PUC on 12 Aug , no update of RPR after that, asked cx to wait for 1-2 days more , cx agreed .
(REPLACEMENT STATUS) :-
CX concern-replacement status , order was already in transit , estimated delivery date of replacement shared , cx agreed .
(REFUND STATUS ):-
cx concern - refund status , refund done , cx informed .
(BANK STATEMENT REQUIRED ):-
cx concern - refund status , refund initiated , cx refused , bank statement were required , macro sent , cx informed .
(NEFT DETAILS REQUIRED ):-
cx concern- refund status , NEFT details required , macro sent , cx informed .
(NEFT DETAILS INVALID):-
cx concern- refund status , bank details were invalid , asked cx to share some other bank account , cx agreed , macro again shared as cx asked for the same .
(ORDER STATUS ):-
cx concern- order status , estimated delievry date shared .
(UD ):-
cx concern- order status, order UD, FNDR filled , cx informed .
(FNDR ERROR) :-
cx concern order status , order out for delivery on 19 Aug
FNDR not filled.
Error:
Exception while fetching ndr questions
(UD CASES UPDATE NO.) :-
cx concern - order status , order UD and FNDR was filled , cx wanted to update no. , FNDR filled again , cx informed .
(RL pANEL ):-
cx concern - pickup status , RPI initiated on but order still wasn't picked up , RL filled , TAT shared .
(RL PANEL ALREADY PICKED UP ):-
cx concern - return status , cx said order is alredy picked up on but we didn't have any update regarding the same , RL filled with alreday picked up , cx informed.
(PUC-RPR STATUS) :-
cx concern - return status , PUC marked on , PUC-RPR TAT shared .
(PUC BUT NO RPR) :-
cx concern - return status , order was marked puc on but no update of rpr after that , asked cx to wait till , cx agreed.
(IMAGES REQUIRED) :-
cx asked about return status , images were required , asked cx for the same , cx agreed .
cx wants order by today , kindly check and do needful .
cx wanted to cancel order as he no longer wanted it , MFG created , request taken , asked to refuse at time of delivery .
(ORDER CANCELATION MFG CREATED) :-
cx wanted to cancel order , MFG was created , asked cx to deny at time of delivery.
(OUTSIDE SLA) :-
cx asked about order status , order was outside SLA but not UD , compliant already raised , asked cx to wait for 24-48 hours , cx agreed .
(BEYOND PROMISED DATE COD) :-
cx asked about order status , order was beyond promised date , asked cx to place a new order , cx agreed .
(WARENTY RELATED ISSUE) :-
cx asked about request status , images of brand denial letter were required , cx said he sent the same at [email protected] , kindly check and do needful .
(PDWP):-
cx concern - PDWP , case was already opened on 26 Aug , asked cx to wait for 6 working days , cx agreed .
(SOCIAL MEDIA ESCELATION) :-
cx asked about complaint status , case was escalated to social media team , asked cx to wait till 24 hours , cx agreed.
(SHORT CALLS):-
cx disconnected call without saying anything .
CX : asked about reverse pick up status // RL filled // TAT SHARED //
(OUT FOR PICK-UP):-
cx asked about request status , order was out for pick -up , cx said he received notification from courier regarding the same , asked cx to wait till pickup , cx wanted replacement instead of refund , replacement selected , cx informed, cx agreed .
(RTO) :-
cx asked about order status , order was marked RTO , as it was COD asked cx to place new order .
(REFUND AFTER REPLACEMENT) :-
cx only received refund of RS 88 as he opted replacement first , at the time of replacement the order's amount got reduce for Rs 88 so we refunded RS 88 to cx account , but then he canceled replcament and asked for refund , RS 449 is left , request taken , cx informed , TAT shared .
(Freebies are missing) :-
cx's free gift was missing, request taken , TAT shared .
(ALREADY PICKED UP ):-
cx asked about return status , cx said order was picked up but we didn't had any update regarding the same , asked cx to wait for 24 hours for updation , cx agreed .
azharhoda29@gmail
|
Notes.io is a web-based application for taking notes. You can take your notes and share with others people. If you like taking long notes, notes.io is designed for you. To date, over 8,000,000,000 notes created and continuing...
With notes.io;
- * You can take a note from anywhere and any device with internet connection.
- * You can share the notes in social platforms (YouTube, Facebook, Twitter, instagram etc.).
- * You can quickly share your contents without website, blog and e-mail.
- * You don't need to create any Account to share a note. As you wish you can use quick, easy and best shortened notes with sms, websites, e-mail, or messaging services (WhatsApp, iMessage, Telegram, Signal).
- * Notes.io has fabulous infrastructure design for a short link and allows you to share the note as an easy and understandable link.
Fast: Notes.io is built for speed and performance. You can take a notes quickly and browse your archive.
Easy: Notes.io doesn’t require installation. Just write and share note!
Short: Notes.io’s url just 8 character. You’ll get shorten link of your note when you want to share. (Ex: notes.io/q )
Free: Notes.io works for 12 years and has been free since the day it was started.
You immediately create your first note and start sharing with the ones you wish. If you want to contact us, you can use the following communication channels;
Email: [email protected]
Twitter: http://twitter.com/notesio
Instagram: http://instagram.com/notes.io
Facebook: http://facebook.com/notesio
Regards;
Notes.io Team