In a reply to @Harshit_t1999, I asked, “Pls share your order number, will get it looked into asap”. The captured post does not identify the issue or report an outcome.
At Honasa, I described a Dhanbad store team’s birthday celebration this way: “This weekend, our Dhanbad store team celebrated a regular consumer's birthday with a cake.”
The team learned about the birthday during a routine check-in call and invited the consumer to the store: “They'd called him for a routine check-in, learned his birthday was coming up, and invited him over.”
I said, “The area manager had already made it clear that teams could act without escalation.” That authority enabled the team to arrange the celebration.
I described the principle across our brands as: “if it genuinely delights the consumer, you have the authority to act”.
I said, “You cannot standardize delight.” I argued that a manual cannot reliably prescribe a birthday gesture and predict its sales lift.
The consumer was moved by the celebration and shopped more than planned: “He came in, moved by the gesture, and shopped more than he'd planned.”
The two purchases were “Two purchases—₹4,511 and ₹1,048.”
The reported total was “Total: ₹5,559.”
I advised business builders to “trust people with principles instead of handcuffing them with processes, and they will surprise you.” I qualified that this does not work always or perfectly, but said the trade-off is worthwhile often enough.
I anticipated word of mouth, writing: “His friends will hear the story. Some will visit because of it.” These were expectations, not reported outcomes.
In a reply to @hella__badid, I described the product as “it’s a toxin free shampoo with refreshing fragrance”.
I said, “we do not recommend using it as a mouthwash”. The captured reply does not specify the shampoo’s name or explain the reason for this recommendation.
These posts capture several distinct parts of customer experience: asking for information to investigate an issue, empowering store teams to create a personal moment, and communicating a clear product-use recommendation. The order reply gives no issue details or follow-up, and the birthday post does not report whether its anticipated word of mouth occurred.
I keep customer experience and service in view both through specific support interactions and through the moments people remember across a journey.
In a captured customer-service message to @ShoneThomas1, the sender said the item would not cause harm, asked them to contact customer care, and promised a replacement: “While it won’t harm, pls reach out to our customer care we will replace it.”
A captured post tagged @ShoneThomas1 and @mamaearthindia and said only “Yes”; what it agreed to is not specified.
A captured post tagging @aniket_bargotra and @mamaearthindia said “On it,” but does not identify the task or the post’s author.
I believe we remember associations through the highs and lows of experiences rather than through averages: “We don’t remember associations by averages but by the highs and lows of our experiences.”
I see this highs-and-lows perspective as applicable to onboarding, CX/UX journeys, and customer funnels: “You can apply this to on-boarding, CX/UX journeys, customer funnels etc.”
I used Stuart Broad as an example: despite his potentially strong average record, I remember him for being hit for 6 sixes by Yuvi.
The captured replacement message promises a next step but reports no outcome; the short “Yes” and “On it” posts likewise leave their context unresolved.
Related: team celebrations and morale, brand purpose and company story, partnerships and collaboration