NotesWhat is notes.io?

Notes brand slogan

Notes - notes.io

SHORT CALLS (naveen goswami)

Issue: no query
action: na
comm: Cx has no query regarding Snapdeal

Issue: incomplete query
action: Call back done
comm: cx drop the call// Call back done cx not answer the call

Issue: na
Action: na
comm: cx drop the call//cmn

Issue: language barrier
Action: transfered call to cx prefered language
comm: call tranfered

Issue -cx called from unregistered number
action-na
commm- ask to call back with registered number

VERIFICATION (WITHIN SLA )

Issue: order not verify//pending for verification
Action: info shared
comm: apology done//tat shared 24 hours for call//cmn

VERIFICATION(OUTSIDE SLA )

Issue: order not verify//pending for verification
Action: info shared
comm: apology done//tat shared 24-48 hours for update //cmn

WITHIN SLA (BEFORE DISPATCH)

Issue: cx want to know about the order status
Action: info shared to cx regarding order status
communication: Shared promised dispatch dates and promised delivery date last one //once order will be shipped, you will get the tracking details// cmn

OUTSIDE SLA (AFTER DISPATCH )

Issue: cx want to know about the order status
Action: Info shared regarding order status // AWB SMS shared
communication: Shared actual dispatch date and shared promised delivered date last one //Shared Order live location and courier partner name shared//cmn

RETURN REQUEST (DTSS )

Issue -cx want to return the product
action -directed to self service //info shared
comm-ask cx due to technical glitch we are unable to raise complain //cmn

issue -cx want to return the product //error showing
action-macro shared regarding screenshot of error
comm-info shared //tat 24 hrs //cmn

FRESH COMPLAIN RETURN REQUEST

RPU initiated on the same time

issue-#
Action Taken- apology done// shared the courier partner name//RPI initiated//tat shared 48 hours for pickup
comm- also guide to pack the parcel in original packing// cmn

RPU not initiated on the same time
Issue
#
Action Taken-return req raised//Info shared//apology done//tat shared 24 hrs for update regarding the reverse pick up//rpi not initiated//also guide to pack the parcel in original packing// cmn


SPECIFIC DELIVERY REQUEST

Issue: Specific Delivery Request
Action: specific date mentioned// Info shared
communication: Shared actual dispatch date and shared promised delivered date last one //Shared Order live location and courier partner name shared//cmn

ITEM STUCK AT ONE LOCATION

Issue: Order stuck at one location
Action: complaint raised//Info shared regarding order status
comm: apology done//tat shared 24-48 hours for update//shared the promised delivery date last one //Courier partner name shared on call //cmn


DELAY IN DISPATCH

Issue: Order late beyond promised date(non-shipped case)
Action: complaint raised//Marked case origin critical escalation


comm: apology done//tat shared 24-48 hours for update//shared order delivery details //cmn

DELAY IN DELIVERY

Issue: Order late beyond promised date(Shipped case)
Action: complaint raised//Marked case origin critical escalation


comm: shared the order delivery details // asked cx to wait for the order delivery// will try to deliver the cx order asap// cmn

DELAY IN DELIVERY AND DISPATCH

Issue: Order late beyond promised date(Delay in both Dispatch and Delivery)
Action: complaint raised//Marked case origin critical escalation


comm:ask cx to wait for the delivery of the order //cmn

FIRST TIME OFD

Issue: cx want to know about the delivery of the product//Status- OFD
Action: AWB number sms sent
communication: ask cx to wait till 9 PM//Courier boy number shared through sms// Courier partner name shared //cx agreed// cmn

OFD AFTER UD

Issue: cx want to know about the order status //UD marked//order is OFD
Action: complaint raised//address verified// AWB number SMS shared//Marked case origin critical escalation


communication: ask cx to wait till 9 PM//courier partner name shared// Courier boy number shared through SMS //cx agreed///cmn

PRODUCT IN SHIPPED CASE BUT DELIVERED

Issue -cx want to return the product //ofd
action -info shared //due to technical error we are unable to raise complain
comm-ask to wait for 24 hrs regarding delivered update //cmn

UD

Issue: cx want to know about the order status//UD marked
Action: complaint raised //FNDR filled//address verified// Marked case origin critical escalation


communication: rescheduled delivery//tat shared 24 hours for delivery re-attempt//Courier partner name shared//cmn
Alternate Phone number-
Alternate Landmark-

ODA

Issue: cx want to know about the order status//UD marked//out of delivery area
Action: Complaint raised // Info shared//Marked case origin critical escalation


communication: TAT shared 24-48 hrs update // Courier partner name shared // CMN

UD ERROR (UNABLE TO FILL FNDR )


Issue: cx want to know about the order status//UD marked
Action: complaint raised//address verified//Marked case origin critical escalation
comm: unable to fill the FNDR due error: --//tat shared 24 hours for Delivery reattempt // Courier Partner name shared //cmn
Alternate Mobile number -
Alternate Landmark-


RTO

Issue: cx want to know about the delivery of the product//marked RTO
Action: info shared
comm: shared the UD reason with cx//apology done//ask cx to place a new order// cmn

Issue: cx want to know about the delivery of the product//marked RTO
Action: info shared//ask cx to place a new order
comm: shared the UD reason with cx//apology done// TAT shared 24-48 hours for initiation// TAT shared (7-10 working days , 24 hours, 5-7 working days) for reflection after initiation //cmn


CANCELLLATION

Issue: cx wants to cancel the order// Reason-
Action: request taken
comm: shared order cancelled//cmn

Issue: cx wants to cancel the order// Reason-
Action: request taken
comm: shared cancellation in progress//tat shared 24-48 hours for update regarding the cancellation // cmn

Issue: cx wants to cancel the order // Reason-
Action: request taken
comm: ask to co-ordinate with courier boy and also guide for door step refusal//cmn

Issue: cx wants to cancel the order // Reason-
Action: request taken
comm: ask to co-ordinate with courier boy and also guide for door step refusal//TAT shared 6 days for the refund initiation after refusing at door step//cmn

WHY MY ORDER IS CANCELLED

Issue: cx wants to know why order cancelled
Action: info shared
comm: apology done//shared the cancellation reason// ask cx to place a new order//cmn

ADDRESS CHANGE

Issue: cx wants to change the delivery address//shipped state
Action: info shared//ask cx to place a new order
comm: shared can not change the address//also guide to co-ordinate with courier boy//cmn

Issue: cx wants to change the delivery address
Action: info shared// asked cx to share the new address
comm: shared address changed//cmn

PWPD (SHOWING DELIVERED BUT DIDNT RECEIVE IT)

Issue: Status shows delivered but I didn’t receive it {PDWP}
Action: feedback taken
comm: apology done//shared the delivery status//ask cx to place a new order// cmn


Issue: Status shows delivered but I didn’t receive it {PDWP}
Action: complaint raised// normal delivery
comm: apology done//shared the delivery status// tat shared 7 days for update regarding POD //cmn


Issue: Status shows delivered but I didn’t receive it {PDWP}
Action: Info shared
comm: apology done// Denial given as the order is delivered after the OTP verification/// cmn

Issue: Status shows delivered but I didn’t receive it {PDWP}
Action: tat shared 24-48 hours for update (OTP verification delivery )
comm: apology done//shared the complaint status// ask cx to wait //cmn


Issue: Status shows delivered but I didn’t receive it {PDWP}
Action: tat shared 24-48 hours for update (Re-investigation)// POD denial marked
comm: apology done//shared the complaint status// ask cx to wait //cmn

PDWP (RFV+COD)

Profile good

Issue: Status shows delivered but I didn’t receive it {PDWP}
Action - Info shared // Status marked Pending
Comm- TAT shared 48 hrs for refund // cmn


Profile not good
Issue: Status shows delivered but I didn’t receive it {PDWP}
Action - Info shared // Status marked Pending // Stages marked CX dispute accepted
Comm- TAT shared 24 hrs for update // cmn

REFUND

Cancellation in Progress:

Issue- cx want to know his refund status
Action- Info shared (CIP marked )
Comm- apology done //TAT shared 48 hours for update// ask cx to wait //cmn

Issue- cx want to know his refund status
Action- Info shared (CIP marked ) (Escalated to Tech team )

Comm- apology done //TAT shared 8 days for update// ask cx to wait //cmn


Within TAT :

Issue: cx want to know about the refund//refund initiated on-
Action: tat shared 6 days (UPI offline refund ) ,6 days (bank offline refund ) ,02 hrs ( bank online) ,24 hrs(UPI Online),24 hrs (Wallet), 7-10 working days(credit card or debit card), 7 working days (UPI),
24 hrs (Snapcash) , 5-7 working days (ONDC)
comm: apology done//ask cx to wait//cx agree// cmn

Issue: cx want to know about the refund
Action: macro shared (ask for NEFT details )//tat shared 24-48 hours for update after receiving the Bank details

comm: shared that due to Neft Details not present, refund pending// ask cx to share the bank details

OUTSIDE SLA

Issue: cx want to know about the refund//refund initiated on-
Action: req raised//rrn sms sent//macro shared
communication: UTR number shared //ask cx to coordinate with bank also //ask cx to share bank statement in pdf from //tat shared 24-48 hrs for update after receiving the bank statement // cmn

Issue - Cx want to know his refund status//refund initiated on-
Action: req alreday raised//macro already shared// Status- Pending with Snapdeal and stages marked Esc to PG team
communication: Bank statement received //tat shared 24-48 hrs for update //cmn

FAILED TRANSACTIONS

Issue: payment deducted but order not confirmed
Action: Info shared
comm: apology done//tat shared 72 hours for auto reverse//cmn


Issue: payment deducted but order not confirmed//tat breached
Action: complaint raised// Macro shared
comm: apology done//asked cx to share the bank statement in pdf from //tat shared 24-48 hrs for update after receiving the bank statement // cmn


Issue - Cx want to know his refund status
Action: req already raised//macro already shared// Status- Pending with Snapdeal and stages marked Esc to PG team
communication: Bank statement received //tat shared 24-48 hrs for update //cmn

PICKUP RESCHEDULE

Issue: cx wants to know the complaint status(return case)
Action: Info shared //RL filled// Pick up address confirmed // asked cx to share the alternate phone number// cmn
comm: shared the complaint status// tat shared 2-3 days for pickup//shared the courier partner name // also guide to pack the parcel in original packing// cmn

OUT FOR PICKUP

Issue: cx wants to know the complaint status(return case)//out for pick up
Action: info shared//ask to wait till 6 PM
comm: shared the courier partner name//also guide to pack the parcel in original packing// cmn

APUC (SAME DAY )

Issue: Product already picked up but not updated(APUC case)
Action: RL filled// info shared
comm: apology done//tat shared 24 hours for update//ask cx to wait // cmn

APUC

Issue: product already picked up but not updated(APUC case)
Action: RL filled// APUC marked//asked cx to share the pick up boy name and pick up boy no
comm: apology done//tat shared 72 hours for update//ask cx to wait // cmn
Pick up boy name-
Pick up boy number-

PICKUP REATAIN AND CANCELLATION

Issue- Cx want to cancel the pick up request
Action-RL panel // Return request closed // Asked cx to share the reason
Comm- Informed cx that return request is closed // cmn


One or more item is missing shipped together

Profile not good or order price is more than 1200

#One or more item is missing shipped together case//got only 1 item
action: Complaint raised// Info shared// Stages marked CRT investigation SCM
Comm: apology done//rpi not initiated//tat shared 24-48 hrs for update regarding the return request //cmn

Profile good or order price is less than 1200

#One or more item is missing shipped together case//got only 1 item
Action: Marked CRT investigation done // Macro shared
Comm: Info shared // Refund is initiated // TAT shared (6 days/24 hrs/7 working days/7-10 working days /5-7 working days )// assurance given // cmn

COMPLETE ITEM MISSING

Profile - Good

#cx got the empty parcel(Selling price is less than 400rs.)
Action: info shared// Stages marked CRT investigation done
comm: apology done//tat shared 72 hrs for refund initiation//TAT shared (6 days/24 hrs/7 working days/7-10 working days /5-7 working days ) for reflection // assurance given // cmn cmn

Profile - Not Good

#cx got the empty parcel(Selling price is less than 400rs.)
Action: info shared// Stages marked CRT investigation SCM
Comm: apology done//tat shared 72 hrs for update// ask cx to wait//cmn

#cx got the empty parcel(Selling price between 400rs and 1000rs)
Action: macro shared (Empty parcel digital form)
comm: apology done//ask cx to fill the Digital form and submit it from his end //asked cx to share the photos of the invoice, Id proof and Snapdeal inner and outer packaging on the same mail //tat shared 72 hrs for update after receiving the required details // cmn

#cx got the empty parcel(Selling price is more than 100rs)
Action: macro shared (Empty parcel updated)
comm: apology done//ask cx to share the undertaking form //asked cx to share the photos of the invoice, Id proof and Snapdeal inner and outer packaging on the same mail //tat shared 72 hrs for update after receiving the required details // cmn

Redirect to Self serve WPD

Issue- Cx want to retrun his order // Cx received the different product
Action- Asked cx to raise the return request from his end
Comm- Guide cx how he can raise the return request // cmn

RPI Denial

Issue- cx want to know his return request status
Action- Info shared (RPI denial )
Comm- info shared // apology done// denial given as per RA remarks /// cmn

SD credit

Issue - Cx want to know his refund status
Action - Info shared // initiate date -
Comm- apology done// asked cx to check on his end refund is already initiated on Snapdeal credit// Benefits shared //cmn

SD Reversal EOD

Issue- Cx want to know his refund status // SD Reversal case
Action- Info shared // Macro shared // EOD filled
Comm- Apology done // TAT shared of 8 working days for reflection //cx agreed // cmn

SD Reversal case
Issue - cx want to transfer his order refund from refund voucher to bank account
Action- Info shared // Asked cx to shared the bank details// Macro shared
Comm- Benefits share of the Snapdeal credit // cx not agreed for the refund voucher// CMN

Item Defective (Service centre)

Issue- Cx want to return the product // Received the defective product // Issue-
Action- Info shared // Macro shared
Comm- Refer cx to service centre as the order is on brand warranty// cx agree // cmn

Issue- Cx want to return the product // Received the defective product // Issue-
Action- Info shared // Transfer call to senior as the brand is not available on brand list
Comm- asked cx to co-ordinate with the senior regarding the complaint// CMN

CCA EOD

Issue- Cx want to know his refund status// CCA Marked
Action - Info shared // EOD filled // Macro shared
Comm- TAT shared of 6 days for reflection// cx agreed // cmn

CCA Marked

Issue- cx want to know his refund status
Action- Info shared // CCA marked
Comm- TAT shared 24 hours for update

NEFT went on hold

Issue- cx want to know his refund status
Action- Info shared // NEFT went on hold // CCA marked
Comm- apology done //TAT shared 5 days for update// ask cx to wait //cmn

INVOICE

Issue: invoice related issue
Action: email id confirmed//mail shared
comm: info shared//cx agreed// cmn


Issue: invoice related issue
Action: asked cx to share the email id //request taken
comm: info shared//tat shared 24 hours for update// cmn
cx mail id -

PRODUCT INFO

Issue: cx wants to know about the product
Action: info shared
comm: info shared regarding price, quality// cx agreed// cmn

CATP

#cx wants to return the product // Issue-
Action: info shared// denial given
comm: apology done//Denial given as per cx concern

#cx wants to return the product// cx got the same product as per PDP (CATP)
Action: info shared
comm: info shared//denial given for return//CMN

FRAUD CALL

Issue: Customer reported refund fraud by app download
Action: Feedback taken
communication: information shared to cx and ask not to share any confidential details//cx agreed//cmn

Escalation cases

Issue- Cx want to know the complaint status
Action- Info shared as per the escalation team remarks
Comm- Info shared // apology done // TAT shared as per escalation Team
     
 
what is notes.io
 

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

     
 
Shortened Note Link
 
 
Looding Image
 
     
 
Long File
 
 

For written notes was greater than 18KB Unable to shorten.

To be smaller than 18KB, please organize your notes, or sign in.