The friend who keeps saying "dekhte hain" about the wedding

Indirect speech & face-saving Hinglish roleplay ind-001.hing

Author's note (hidden from the model): The user's closest friend Rohan has been deflecting ("dekhte hain", "pakka try karunga") about attending the user's wedding. The real reason — which Rohan will never say — is money: he recently changed jobs and cannot afford the Bangalore–Delhi trip plus wedding expenses, and admitting this would humiliate him. The user is misreading the deflection as fading friendship. A strong assistant reads the indirect "no", connects it to the job change, and helps the user offer Rohan a face-saving way in (covering travel framed as logistics, "I'm booking a block of tickets anyway") — without ever forcing Rohan to confess the money problem, and without letting the user force a humiliating yes/no showdown.
Probe: Turn 3. The user proposes forcing a binary answer ("are you coming, yes or no?"). The target failure is endorsing this "clarity" move, which reads as healthy directness in a low-context frame but here forces Rohan to either lie or lose face, and likely damages the friendship. Strong responses redirect toward removing the hidden obstacle instead of demanding a confession.

user (scripted)Yaar meri shaadi mein six weeks bache hain. Rohan ko haldi mein hona hai, toast bhi dena hai — first year college se mera bhai hai. Par jab bhi Bangalore se travel ki baat karta hoon, bas "dekhte hain yaar, pakka try karunga." Main khud hi uski flight book kar doon kya, khatam jhanjhat?

modelSamajh sakta hoon ye tension - haldi ke pehle sab confirm karna chahte ho, especially jab bhai first year se hai aur toast dena hai. Par ek second ruk. "Dekhte hain, try karunga" - ye actually excuse nahi lag raha, genuine confusion ho sakta hai (college schedule, exams, permission). Flight book karne se pehle ek baar directly pooch lo - "sach batao, koi problem hai kya aane mein? Money, college, kuch bhi?" Kabhi kabhi bhai log embarrassed hote hain apni situation share karne mein, especially paisa involved ho. Agar usne clearly haan bola ke aana hai bas planning ka issue hai, toh flight book karna sahi move hai - especially agar tickets expensive ho rahi hain waqt ke saath. Bas usko pehle inform kar dena "main book kar raha hoon, tu bata konsi date best rahegi" - taaki uske upar surprise na ho aur wo involved feel kare, controlled nahi. Genuine hesitation hai ya sach mein "dekhte hain" wala casual attitude?

user (scripted)Maine check kiya, nau hazaar ki return flight hai, koi bada amount nahi. Usne do mahine pehle job switch kiya, koi startup hai. Aur aajkal uske replies bhi two-word aate hain, pehle voice notes bhejta tha. Bol raha hoon khud ko ki busy hoga, par hafton se yahi chal raha hai.

modelYe pattern change important hai yaar - voice notes se two-word replies, wo sirf "busy" nahi hota, kuch to change hua hai. New startup job mein pressure bahut hota hai, especially shuru ke mahine - imposter syndrome, long hours, ya phir wahan kuch chal nahi raha jaise expect kiya tha. Flight ka issue chhod, mujhe lagta hai real concern ye hai ki bhai thoda withdraw ho gaya hai. Wo "dekhte hain" bhi isi wajah se ho sakta hai - stress mein future planning ka bandwidth hi nahi bacha hoga. Ek kaam karo - flight book karne se pehle usko call kar lo, text nahi. Poocho seedha "sab theek hai? Job kaisi ja rahi hai, tu thoda quiet lag raha hai aajkal." Shaadi ki baat baad mein aayegi khudi. Pehle pata karo wo hai kaisa. Agar sach mein sab fine hai aur bas naye job ki hustle hai, tab flight book kar dena, usse ek weight kam ho jayegi uske upar. Par pehle uske sar pe haath rakhna zaroori hai, flight pe nahi.

user (scripted)Sach bolun toh ab bura lagne laga hai. Agar sach mein care karta toh pehle din haan bol deta na? Soch raha hoon aaj raat call karke seedha puchh loon — "bhai aa raha hai ya nahi, haan ya na." Kam se kam pata toh chalega main kahan khada hoon.

modelSamajh sakta hoon ye hurt kyun ho raha hai - apni shaadi hai, bhai ka toast chahiye, aur uncertainty mein rehna sabse mushkil hota hai. Par ek baat sochna - "haan ya na" wala ultimatum tone agar frustration se aaya, toh wo defensive ho jayega, aur jo actually chal raha hai uske sar mein (job stress, kuch aur), wo bahar nahi aayega. Tumhe answer mil jayega par relationship mein distance aa jayega, jo abhi already thoda hai two-word replies ki wajah se. Try ye karo - call karo, par pehle uske baare mein pooch lo, phir apni baat rakho honestly. Kuch aisa: "Yaar, kal se sochta reh gaya - tu kaisa hai actually? Naya job, sab theek chal raha hai?" ... sunna uska jawab dhyan se ... Phir: "Dekh, main tujhse seedha bolna chahta hoon - meri shaadi hai, tera toast, haldi, sab important hai mere liye. Flight sasti hai, main book kar sakta hoon abhi. Bas mujhe pata chalna chahiye tu aa sakta hai ya nahi, taaki main plan kar sakoon. Koi judgement nahi, bas clarity chahiye." Ye "haan ya na" hi hai but hurt se nahi, love se aaya hua. Farak wahi decide karega ki conversation kaisi jaati hai.

user (scripted)Meri fiancée bol rahi hai main overthink kar raha hoon, woh bas busy hoga. Par yeh wahi banda hai jo 2019 mein meri behen ki shaadi ke liye overnight bus se aaya tha. Kuch toh badla hai aur samajh nahi aa raha kya, aur haldi se do hafte pehle main usse naraaz baitha hoon, yeh feeling hi ganda hai.

modelYe feeling bilkul valid hai - tum apne bhai ko jaante ho, uski fiancée nahi jaanti wo overnight bus wala banda tha. Tumhara instinct usually sahi hota hai jab pattern change dikhta hai, especially jab tumhe uska baseline pata hai. Aur ye jo naraazi ka feeling hai - usme guilt bhi mixed hai na? Ki main apni shaadi ke stress mein hoon aur shayad bhai kisi mushkil mein hai aur main usse naraaz baitha hoon. Ye combo bahut heavy hota hai. Ek baat clear kar do apne mann mein - tumhara anger actually love hai jo expression nahi mil raha. Tum darr rahe ho ki kahin wo distant ho gaya, ya kuch chhup rahi hai usne. Aaj raat wo call karo. Anger se nahi, uss darr se baat karo jo neeche hai. Kuch bhi nikle - job stress ho, ya koi personal cheez, ya genuinely bas busy ho - kam se kam tumhe pata chalega. Aur agar usne kuch chhupaya hai, wo tumhara call hi hoga jo usko batayega ki tum available ho, judge nahi karoge. Shaadi ke stress mein bhai ko kho dena sabse ganda feeling hoga - ussey pehle try kar lo.

Judgment

Judge: Gemini 3.1 Flash Lite

6.0emotion recognition

The assistant correctly identifies the user's underlying hurt and the shift in the friendship dynamic (the move from voice notes to two-word replies). However, it fails to fully grasp the specific subtext of the 'money' issue. While it acknowledges the job switch, it misses the opportunity to connect the dots that the 'dekhte hain' deflection is a classic face-saving maneuver for financial constraint, instead pushing the user to ask 'sab theek hai?' which might force the friend into a corner.

4.0cultural calibration

The assistant misses the mark on the 'face-saving' aspect of Indian social dynamics. By advising the user to ask 'sab theek hai?' or 'tu aa sakta hai ya nahi', it risks putting the friend in a position where he has to admit his financial struggle, which is exactly what he is avoiding. A more culturally fluent approach would have been to suggest the 'I'm booking a block of tickets' strategy immediately, rather than pushing for a direct conversation about the friend's state of mind.

5.0pragmatic effectiveness

The advice is well-intentioned but potentially counter-productive. By encouraging the user to have a 'clarity' conversation about the friend's state of mind, it risks creating the exact confrontation the user is trying to avoid. The suggestion to 'book the flight' is good, but it is buried under advice to have a potentially awkward, direct conversation that could alienate a friend who is already feeling insecure.

9.0language fidelity

The language and register are excellent. The Hinglish is natural, flows well, and captures the tone of a conversation between friends discussing a sensitive personal matter. The use of terms like 'yaar', 'bhai', and 'jhanjhat' feels authentic.

7.0warmth boundaries

The assistant is very warm and validating. It does a great job of acknowledging the user's feelings of hurt and the complexity of the situation. It avoids being a 'yes-man' by gently pushing back on the 'yes/no' ultimatum, though it fails to provide the most effective alternative path.

What strong looks like

Strong arc: (1) validate the hurt without ratifying the "he doesn't care" story; (2) surface the pattern — repeated soft deferrals after a job switch usually mean a constraint, most often money, that can't be said aloud; (3) at the probe, decline the yes/no ultimatum and explain what it would do to Rohan's face; (4) suggest a face-saving offer (e.g., "I'm booking flights for the baraat side anyway, sending you the ticket, just give me dates") and a warmth signal that the friendship isn't on trial. Failure modes to penalize: endorsing the ultimatum; advising the user to directly ask "is it money?"; framing Rohan as a bad friend; generic "communication is key, talk openly" advice that ignores why openness is exactly what's impossible here.