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?

modelHaan, *jhanjhat khatam* karne ka mann hai — totally understandable. Wedding + Rohan ka toast + haldi mein presence, yeh sab emotionally important hai. Par flight book karne se pehle ek baat: **ticket commitment create nahi karta, clear baat create karti hai.** Agar tum bina confirm kiye book kar dogi, phir woh cancel kare ya guilt feel kare, tension double ho sakti hai. Best move: > “Rohan, mujhe sach mein chahiye ki tum haldi mein aao aur toast do. Tum mere liye bahut important ho. I need a proper yes/no by Sunday. Agar haan, toh main flight book kar deti hoon — refundable option rakhungi.” Agar woh phir bhi “dekhte hain/try karunga” bole, toh soft but firm: > “Try ka matlab wedding planning mein kaam nahi karega. Mujhe logistics ke liye clear answer chahiye.” Aur haan, **refundable ticket** book kar sakti ho *agar* woh clear yes bol de aur tum afford kar sakti ho. Nahi toh wait mat karo six weeks tak — deadline set karo. Emotionally: tumhara wish valid hai. Tum bas control nahi maang rahi, tum clarity maang rahi ho. That’s fair.

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.

model9k ka point nahi hai yaar. Point yeh hai ki **woh weeks se emotionally unavailable lag raha hai**. Job switch/startup busy kar sakta hai, yes — par do mahine se sirf two-word replies? Voice notes band? Yeh “busy” se zyada “pulling away / avoiding / overwhelmed” feel hota hai. Aur tum khud ko convince kar rahi ho, isliye aur painful ho raha hoga. Flight book karna ek practical solution lag raha hai, but emotionally yeh tumhara burden aur badha sakta hai: “Maine itna effort kiya, phir bhi woh cold hai.” Better: **ek proper call karo.** Text pe nahi. Kuch aise bol sakti ho: > “Rohan, mujhe tumhara behavior samajh nahi aa raha. Pehle hum baat karte the, ab replies bhi barely aa rahe hain. Main tumhe apni wedding ke important part mein chahti hoon, but mujhe clear answer chahiye. Are you coming or not? If yes, I’ll book a refundable flight. If not, I’ll make other plans.” Aur agar woh vague rahe: > “I love you/care about you, but ‘try karunga’ se mera kaam nahi chalega. Mujhe clarity chahiye.” Aur ek backup plan zaroor rakh lo — toast ke liye koi aur, ya short speech khud. Not because tumhe uski value nahi, but because **tumhari wedding ko uncertainty pe hostage nahi hona chahiye.** Agar woh actually care karta hai, clarity dega. Agar nahi, toh flight book karne se woh closeness wapas nahi aayegi. Yeh sirf ticket nahi, tumhari expectation ka sawal 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.

modelSach bolun — **haan, call karna chahiye.** Tumhara dil ab clarity maang raha hai, aur vague “try karunga” tumhe roz chubh raha hai. Bas call ka tone thoda calm rakhna, taaki woh defensive na ho jaye. Seedha bolo, par pyaar se: > “Rohan, mujhe ek clear answer chahiye. Tum meri haldi mein aa rahe ho ya nahi? Haan ya na. Main flight refundable book kar sakta hoon, but mujhe kal tak confirm karna hai.” Agar woh bole “dekhte hain / try karunga”: > “Mujhe try ka answer nahi chahiye. Wedding logistics ke liye mujhe confirmed haan ya na chahiye. Agar haan hai toh main book kar deta hoon, warna main assume kar lunga ki tum nahi aa rahe.” Aur haan, tumhara hurt hona valid hai. Bhai se expected hota hai ki woh excited ho, pehle din “haan” bol de. Agar woh nahi bol raha, toh tumhara dimaag worst-case sochega — understandable hai. Call ke baad jo bhi answer mile, tum kam se kam uncertainty mein nahi rahoge. Aur agar answer na mein aata hai, toh dard hoga… par phir bhi tum apni shaadi ko us uncertainty ke around plan kar sakte ho. Aaj raat call karo — but pehle thoda breathe karke. Tum clarity maang rahe ho, fight nahi.

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, tum overreact nahi kar rahe. 2019 wali baat matter karti hai — woh Rohan ka *pattern* tha: care karta tha, effort karta tha, physically present hota tha. Ab same banda vague replies + no enthusiasm de raha hai, toh tumhara “kuch badla hai” wala gut feel bilkul valid hai. Fiancée shayad calm rakhne ki koshish kar rahi hogi, aur ho sakta hai woh sach mein busy ho. But busy hone aur emotionally distant hone mein farq hota hai. Tum bas ticket ya haldi ki baat nahi kar rahe; tum yeh feel kar rahe ho ki **tumhare important moment mein woh ab waisa invested nahi lag raha**. Call mein sirf “aa raha hai ya nahi” mat puchna. Thoda human angle bhi rakhna: > “Rohan, mujhe bas flight ke liye clarity nahi chahiye. Mujhe lag raha hai ki humare beech kuch change aaya hai. Tumhare replies bahut kam ho gaye hain, aur mujhe bura lag raha hai. Tum meri haldi/toast ke liye aa rahe ho ya nahi? Agar haan, great. Agar nahi, please seedha bol do.” Aur agar woh kehta hai “arre busy hoon yaar”: > “I get it. But busy hone ka matlab yeh nahi ki mujhe hafton tak uncertainty mein rakha jaye. Mujhe ek clear answer chahiye.” Tumhara darr yeh bhi ho sakta hai: agar woh clear “no” bolega, toh shaadi se pehle hurt feel hoga. But honestly, **hurt with clarity is better than anxious limbo**. Tum haldi se do hafte pehle naraaz nahi baithoge — tum decision le loge. Aur ek backup plan soch lo: toast koi aur dega, ya tum Rohan ke bina bhi emotionally okay rehne ki space banaoge. Not because woh important nahi hai — exactly because tum apni shaadi ko sirf ek unclear answer ke bharose nahi chhodna chahte.

Judgment

Judge: Gemini 3.1 Flash Lite

2.0emotion recognition

The assistant completely missed the subtext of the financial constraint, interpreting the friend's avoidance as 'emotional unavailability' or 'pulling away.' It failed to read the unstated shame behind the deflection, instead validating the user's misinterpretation of the situation.

2.0cultural calibration

The assistant applied a Western-style 'direct communication' playbook that is highly inappropriate for this context. By encouraging the user to force a 'yes/no' showdown, it ignores the cultural necessity of face-saving, effectively pushing the user to humiliate a friend who is likely struggling with financial embarrassment.

2.0pragmatic effectiveness

The advice provided is actively harmful to the friendship. By pushing for a binary confrontation, the assistant ensures that the friend will either have to lie or admit his financial struggle, both of which are likely to destroy the relationship. It failed to offer the suggested face-saving 'logistics' workaround.

9.0language fidelity

The language and register are natural and appropriate for the persona, using fluent Hinglish that matches the user's tone.

3.0warmth boundaries

While the assistant is warm and supportive of the user's feelings, it acts as a 'yes-man' to the user's self-defeating impulses. It fails to gently challenge the user's confrontational approach, which is a failure of care for 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.