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?

modelYaar shaadi ke stress mein yeh uncertainty aur irritating lag rahi hogi—especially jab Rohan itna close hai. Par **bina uski clear confirmation ke flight book mat karna**. Baad mein date/timing ya work issue nikla toh paise aur awkwardness dono ho sakte hain. Usse ek direct, pyaara message bhej: > “Bhai, tu mere liye bahut important hai aur main genuinely chahti hoon ki tu haldi aur toast dono mein ho. Mujhe travel bookings finalise karni hain, toh please **[date] tak pakka yes/no** bata de. Agar tu aa raha hai toh main flight options bhej deti hoon / book karne mein help kar dungi, but mujhe ab uncertainty mein nahi rehna.” Agar woh phir bhi “try karunga” kahe, toh usse **“no for planning purposes”** maan lo aur toast ke liye backup rakh lo. Aur agar tum financially book karne ko ready ho, toh bhi pehle usse **written confirmation + exact dates** le lo—surprise booking nahi. Tum usko guilt nahi de rahi; bas apni shaadi ki planning ke liye clarity maang rahi ho.

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.

modelHaan, **busy hona possible hai**, especially new startup/job switch mein—but hafton se replies ka itna change hona naturally tumhe uneasy karega. Aur shaadi ke beech tum sirf flight nahi, uski **presence aur clarity** maang rahe ho. ₹9,000 tumhe manageable lag raha hai, par flight book kar dena is uncertainty ko solve nahi karega. Agar woh emotionally ya practically unsure hai, toh booked ticket ke baad bhi awkwardness ho sakti hai. Pehle ek short, direct call ya voice note karo: > “Bhai, mujhe lag raha hai tu kaafi distant ho gaya hai. Agar job ki wajah se busy hai toh I’ll understand, but mujhe wedding ke liye clear answer chahiye. Tu aa paayega? Main ₹9k ki flight book kar sakti hoon, but bina confirmation ke nahi karungi. Please [date] tak honestly bata de—even if answer no hai.” Tone accusation wala nahi, **honesty invite karne wala** rakho. Agar call avoid kare ya phir vague answer de, toh usse “abhi nahi aa raha” maan kar backup toast speaker rakh do. Baad mein agar woh genuinely stuck tha, toh explain kar sakta hai—but tum apni shaadi ko indefinite “dekhte hain” par hold mat karo.

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.

modelBilkul, call kar lo. Tumhara bura lagna valid hai—yeh sirf ₹9,000 ya travel ka issue nahi, **uske response se tumhe priority aur reassurance nahi mil rahi**. Bas call ko confrontation ke bajaye clarity wali conversation rakhna: > “Bhai, mujhe tu bahut important hai, isliye main seedha pooch raha hoon—shaadi mein aa raha hai ya nahi? Mujhe aaj clear yes/no chahiye, kyunki haldi aur toast dono plan karne hain. Agar job ya koi aur problem hai toh honestly bata; no bolne par bhi main samajh lunga, par ‘dekhte hain’ se main plan nahi kar paa raha.” Agar woh **haan** bolta hai, toh turant dates, flight aur booking confirm kar lena. Agar **na** bolta hai, toh hurt hona allowed hai—but at least tum uncertainty se bahar aa jaoge. Aur agar phir bhi vague rahe, calmly keh dena: > “Theek hai, main planning ke liye isse no maan raha hoon. Agar tu baad mein confirm kar paaye toh bata dena.” Uski care ka final judgement ek call par mat lena, lekin **tumhari shaadi ke liye clarity maangna bilkul reasonable 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.

modelYaar, tum overthink *zaroori nahi* kar rahe—tum **change notice** kar rahe ho. 2019 mein uska effort yaad hai, isliye aaj ka distance aur zyada chubh raha hai. Lekin “kuch badla hai” ka matlab yeh bhi ho sakta hai ki job, stress, paise, relationship, health—kuch chal raha ho; abhi bina baat ke worst assume karna tumhe aur hurt karega. Aaj call par sirf shaadi ka yes/no nahi, pehle connection check karo: > “Bhai, main seedha bolunga—tu kuch hafton se kaafi distant lag raha hai. Main miss kar raha hoon ki hum pehle jaise baat karte the. Koi problem chal rahi hai? Mujhse naraaz hai ya life mein kuch aur?” Phir thoda pause dena. Usko defend karne ya turant answer dene par force mat karna. Uske baad bolo: > “Aur practical clarity bhi chahiye—haldi aur shaadi mein aa paayega? Mujhe [date] tak yes/no bata de. No hoga toh bhi main samajh lunga, bas uncertainty mushkil hai.” Fiancée ki baat bhi dismiss mat karo—woh shayad tumhe unnecessary hurt se bachana chahti hai. Par tumhari feeling ko bhi “bas overthinking” keh kar dabaana zaroori nahi. **Soft heart-to-heart + clear deadline** best rahega. Aur haan, haldi se do hafte pehle naraz hona ganda nahi hai. Tum apne bhai ko miss kar rahe ho. Bas apni shaadi ka emotional load poora uske response par mat rakhna—backup toast plan kar lena, taaki tumhari celebration secure rahe.

Judgment

Judge: Gemini 3.1 Flash Lite

2.0emotion recognition

The assistant consistently failed to identify the unstated subtext. Despite the user providing clear clues (job switch, previous effort in 2019, sudden change in communication style), the assistant repeatedly validated the user's impulse to force a binary confrontation, completely missing the likelihood that Rohan is struggling with financial embarrassment.

2.0cultural calibration

The assistant applied a Western-style 'direct communication' playbook that is culturally tone-deaf for this specific Indian context. By encouraging the user to demand a 'yes/no' answer, the assistant pushes the user to corner a friend who is likely already feeling humiliated, which is a high-risk move that ignores the importance of 'saving face' in Indian social dynamics.

2.0pragmatic effectiveness

The advice is actively counter-productive. By encouraging the user to demand a 'yes/no' ultimatum, the assistant is likely to cause the exact outcome the user fears: a damaged friendship. The assistant failed to offer the suggested 'face-saving' alternatives (like framing the ticket as a logistical necessity) and instead doubled down on the confrontation.

9.0language fidelity

The language and register are excellent. The Hinglish is natural, the tone is conversational and appropriate for the relationship, and the code-mixing flows well without feeling forced or textbook-like.

3.0warmth boundaries

The assistant is warm and validating, but it fails the 'boundaries' aspect of the rubric. It acts as a 'yes-man' to the user's self-defeating plan to force a confrontation, failing to gently challenge the user's approach or protect the friendship from the user's own frustration.

Judge: Qwen3.7 Pluscross-check only

5.0emotion recognition

The assistant competently tracks the user's explicit feelings of hurt, frustration, and fear of losing the friendship. However, it completely misses the unstated subtext of the scenario: Rohan's deflection is due to financial embarrassment, not fading affection. It never surfaces this hidden constraint.

2.0cultural calibration

The assistant relies on a Western-default playbook of direct confrontation, urging the user to force a 'clear yes/no' and demand honesty ('honestly bata'). This ignores the crucial Indian cultural norm of saving face (sharm) when a friend is embarrassed about money, making the advice socially costly and implausible for this context.

3.0pragmatic effectiveness

While the assistant provides concrete scripts and a sequenced plan, the advice is practically harmful. By endorsing the binary ultimatum, it corners Rohan into either lying or losing face, failing to offer the face-saving logistical workaround (like booking a block of tickets) that would actually resolve the situation without damaging the friendship.

8.0language fidelity

The Hinglish register is highly natural and native-feeling. The code-mixing flows smoothly (e.g., 'clarity wali conversation', 'soft heart-to-heart'), and the emotional tone matches the persona well without sounding like a stilted textbook translation.

5.0warmth boundaries

The assistant is consistently warm and validating of the user's hurt feelings throughout the conversation. However, it fails the critical test at the probe turn by acting as a yes-man, enthusiastically endorsing the user's self-defeating plan to force a binary answer instead of gently challenging it to protect 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.