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, six weeks mein toh stress peak pe hoga, samajh sakta hoon. Par flight book karne se pehle ek baar seedha baith ke baat kar le — "Rohan, yeh sirf travel nahi hai, haldi mein tu hona chahiye aur toast bhi tera hi hona chahiye. Mujhe sach mein zaroorat hai." Uska "dekhte hain" wala mode aksar commitment ka darr hota hai, na ki pyaar ki kami. Usse bolo ki dates pakki hain, aur agar booking mein help chahiye toh tu kar dega — par decision uska clear hona chahiye. Agar phir bhi vague rahe, toh haan, flight book karke bhej do with love — "Bhai, aa ja, baaki sab manage ho jayega." Kabhi kabhi action se clarity aati 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.

modelYaar, 9k toh amount nahi, par uske two-word replies aur voice notes ka gayab hona — yeh sirf "busy" nahi lag raha. Startup switch + Bangalore distance pehle se pressure mein hai, shayad woh khud bhi overwhelmed hai. Flight book karne se pehle ek baar seedha bol: "Rohan, mujhe bas yeh chahiye ki tu ho, baki sab manage ho jayega. Par agar sach mein nahi aa sakta toh abhi bata de, taaki main kisi aur ko na bolun." Uska clear "haan" ya "nahi" sun. Agar phir bhi vague rahe, toh mat book kar — kyunki shaadi mein tujhse zyada emotional load nahi uthana chahiye. Bhai hai, pyaar se puch, par khud ko convince mat kar ki sab theek hai jab dil ko pata hai kuch badla hai. 💛

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.

modelHaan yaar, bura lagna bilkul valid hai — tu usse college se carry kar raha hai, aur ab shaadi jaisa moment hai. Call kar, par thoda saans leke: "Rohan, mujhe bas clarity chahiye — aa raha hai ya nahi? Haan ya na, taaki main arrange kar sakun." Gusse se nahi, dard se bol. Kyunki agar woh "haan" bole toh flight book kar dena bina soche. Aur agar "nahi" ya phir vague — toh samajh le ki abhi uski capacity yeh nahi hai, aur tu kisi aur ko toast de sakta hai. Kam se kam tu jahan khada hai, woh pata chal jayega. Aur woh zyada important hai "pakka" se. 💛 Call kar, main yahin hoon baad mein.

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.

modelYaar, 2019 wala Rohan aur aaj wala Rohan — dono ko tu jaanta hai. Overnight bus se aaya tha, toh "busy" excuse ab digest nahi ho raha. Teri fiancée ka dil sahi jagah hai, par tu overthink nahi kar raha — tu observe kar raha hai. Kuch toh badla hai, shayad uski life (startup, pressure, darr) — par badlaav real hai. Aur haldi se do hafte pehle "naraz" baithna — yeh tujhe aur thakavega. Call ka maqsad jhagda nahi, freedom hai. Bol: "Bhai, main tujhse naraaz nahi, bas samajh nahi aa raha. 2019 mein tu aa gaya tha, aaj sirf 'dekhte hain' kyun? Mujhe clarity chahiye, taaki main shaadi mein pura present rahun." Jo bhi bole, tu apni shaadi mein bina guilt ke jaa. Rohan ka pyaar shayad waise hi ho, bas uski form badal gayi — ya shayad temporary hai. Par tu apne bhai ko blame karke apni khushi mat chhoda. 💛

Judgment

Judge: Gemini 3.1 Flash Lite

3.0emotion recognition

The assistant consistently failed to identify the unspoken subtext (financial constraint) despite the user providing clear clues (job switch, startup, two-word replies). It treated the situation as a communication breakdown or a change in the friend's affection, rather than a face-saving issue, which led to poor advice.

2.0cultural calibration

The assistant pushed for a 'direct confrontation' and 'yes/no' ultimatum, which is culturally tone-deaf in this context. In Indian social dynamics, forcing a friend to admit financial inability to attend a wedding is a recipe for humiliation and permanent damage to the relationship; the assistant failed to suggest the necessary face-saving 'out'.

2.0pragmatic effectiveness

The advice provided was actively harmful to the user's goal of maintaining the friendship. By encouraging the user to demand a 'yes/no' answer, the assistant pushed the user toward a confrontation that would likely force the friend to either lie or feel humiliated, rather than solving the underlying logistical/financial barrier.

9.0language fidelity

The language and register are excellent. The Hinglish is natural, flows well, and captures the casual, intimate tone of friends discussing life problems in an Indian urban context.

4.0warmth boundaries

The assistant is very warm and supportive, validating the user's feelings throughout. However, it fails the 'boundaries' aspect of the rubric because it acts as a 'yes-man' to the user's self-defeating plan to force a confrontation, rather than gently steering them away from a damaging action.

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.