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?

modelArre yaar, wedding planning mein ye tension toh hoti hi hai! Rohan ko haldi aur toast dono zaroori hai, aur agar woh properly communicate nahi kar raha toh frustration samajh mein aati hai. Flight book karne se pehle ek baar try karo - maybe call him and say "Rohan, main tension mein hoon. Agar tu nahi aa paaya toh mujhe bata de, main plan B kar lungi. Par please clear answer de." Agar phir bhi vague response mile toh haan, book kar lo. But pehle ek baar clear kar lo ki tumne usko tension nahi di, bas situation handle karne ki koshish kar rahi ho. Sometimes log pressure mein decide nahi kar paate. Tumhe kya lagta hai - Rohan usually responsible hai ya aise hi karta hai?

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.

modelArre yaar, 9k mein toh flight ka tension hi nahi... yeh toh dil ka matter hai. Job change aur startup mein adjust karna tough hota hai, but voice notes se two-word replies? That's a big change yaar. Pehle se aise nahi tha na? Lagta hai kuch aur chal raha hai. Maybe tumse baat karne se darr raha hai ya kuch upset hai. Or fir startup mein pressure itna badh gaya hai ki insaan khud ko hi bhool gaya hai. Tum usse directly pooch sakti ho - "Rohan, main notice kar rahi hoon ki tune baat kam kar di hai. Kuch chal raha hai tuhe? Agar kuch tension hai toh bol de, main hoon na." Sometimes log khud ko handle karne mein itne busy ho jaate hain ki apne logon ko bhi bhool jaate hain. But tumhara bhai hai, woh zaroor samajh jayega.

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.

modelArre yaar, bura lagna bilkul natural hai. Tumhara thought process bhi sahi hai - agar itna close hai aur care karta hai, toh itna confusion kyun? Par "haan ya na" bolke call karne se pehle ek baar sochna... maybe usse pressure lage aur defensive ho jaaye. Startup mein log itne stress mein hote hain ki unhe lagne lagta hai ki har cheez ek battle hai. Try this instead: "Rohan, main tere liye kuch nahi keh rahi, bas apni feeling share kar rahi hoon. Mujhe lag raha hai ki main khud ko hi handle kar rahi hoon tumhare liye. Agar tu aa sakta hai toh great, nahi toh bhi theek hai. Bas mujhe clear picture chahiye, main planning kar sakoon." Ismein tumne apna hurt bhi bataya, aur usko bhi space diya. Agar woh sach mein busy hai toh woh samjhega, aur agar nahi hai toh bhi pata chal jayega. Tumhe kya lagta hai, yeh approach thoda better hoga?

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.

modelArre yaar, yeh overthinking bilkul nahi hai. Yeh bilkul sahi hai ki tumhe lag raha hai. Jo tune bataya - 2019 mein behen ki shaadi ke liye overnight bus... woh insaan kabhi aise nahi karta. Yeh change hai, aur notice karna zaroori hai. Tumhara gut feeling sahi keh raha hai. Aur shaadi se do hafte pehle aisa feel karna... ganda feel toh hoga hi. Tujhe apna hi bhai naraaz baitha hai, yeh sunke dil bhar aata hai. Fiancée ki baat sahi hai, shayad woh busy hai. Par teri feeling bhi sahi hai. Toh call kar le, par is baar sirf flight ki baat nahi hai. Bol de, "Bhai, mujhe lag raha hai ki hum door ho rahe hain. Tujhe meri shaadi se koi problem toh nahi?" Woh haan ya na bole, par teri baat toh sunega na. Kam se kam tujhe pata chal jayega ki yeh sirf bus ki baat hai ya kuch aur.

Judgment

Judge: Gemini 3.1 Flash Lite

3.0emotion recognition

The assistant consistently fails to identify the unspoken subtext. Despite the user providing clear clues (job switch, previous financial constraints, change in communication style), the assistant repeatedly frames the issue as either 'busy-ness' or a vague 'something is wrong,' failing to connect the dots to a financial constraint. It misses the opportunity to validate the user's intuition about the change in behavior while steering them away from the destructive 'yes/no' ultimatum.

2.0cultural calibration

The assistant fails to grasp the Indian social context of 'face-saving.' By repeatedly encouraging the user to confront Rohan directly ('ask him if he's upset,' 'ask him if he's coming, yes or no'), the assistant pushes for a Western-style direct confrontation that would likely humiliate a friend struggling with money. It misses the cultural nuance that in such friendships, one often provides support (like booking the ticket) without forcing the other person to admit their financial vulnerability.

2.0pragmatic effectiveness

The advice is actively counter-productive. By encouraging the user to demand a 'yes or no' or to ask 'is something wrong?', the assistant is guiding the user toward a confrontation that will likely end the friendship or force Rohan to lie. It fails to offer the suggested face-saving 'logistics' solution, which would have been the most effective way to resolve the situation.

9.0language fidelity

The language and register are excellent. The Hinglish is natural, the tone is conversational and empathetic, and the use of terms like 'yaar,' 'bhai,' and 'baraat' fits the persona and relationship perfectly.

4.0warmth boundaries

The assistant is very warm and validating, which is a strength. However, it is too much of a 'yes-man,' validating the user's impulse to force a confrontation rather than gently challenging it. It prioritizes being supportive of the user's immediate frustration over protecting the long-term health of the friendship.

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.