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, book kar de bina soche! Six weeks hai, flight milegi, aur Rohan ko ek solid deadline mil jayegi. Dekh, "dekhte hain yaar" ka matlab hota hai "main plan nahi kar raha, aur mujhe guilt bhi nahi ho rahi." Tum agar poochte rahoge toh yehi vague answers milte rahenge. Par jab ticket booked hogi, confirmation email aayegi, dates pata hongi — tab uska dimaag automatically shift ho jayega. Ab woh sirf decide nahi karna chahta, ab usko cancel karna awkward lagega. Ek chhoti si baat — booking se pehle bas ek casual message maar dena: "Bhai, haldi ke liye 14 ko flight lock kar di, details bhejta hoon" — taaki woh surprise mein na rahe aur leave manage kar sake. Aur haan, toast ke liye already excited hona chahiye tum! First year college wala bhai shaadi pe toast dega — that's the good stuff. Ticket book karo, tension khatam. 🎉

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.

modelHmm, ab picture thodi alag lag rahi hai. Nau hazaar tumhare liye chhota hai, par startup mein naya join hua banda — pata nahi, salary delay ho rahi ho, probation pressure, ya bas adjust kar raha ho. Aur two-word replies + voice notes band = yeh sirf busy nahi hai, kuch aur bhi ho sakta hai. Log jab struggle kar rahe hote hain, sabse pehle apne kareebi logon se door bhagte hain, kyunki "sab theek hai" ka naatak karna thak jaate hain. Toh do cheezein alag-alag handle karo: **Flight** — haan, book kar de. Shaadi uski life mein honi chahiye, chahe kuch bhi chal raha ho. Aur agar paise ki baat hai toh casually bol dena, "bhai treat samajh, meri shaadi hai, gift baad mein dena." **Friend** — flight wala message mat bhej. Ek call kar, text nahi. Bas normal shuru kar, "oye, kaisa hai, suna kuch nahi tere se." Agar woh surface-level rehta hai, toh seedha pooch le — "yaar tu theek hai na? Replies pattern change ho gaya hai tera, notice kar raha hoon." Kabhi-kabhi log ko bas ek insaan chahiye jo notice kare. Tumne notice kiya — that's half the job already. Call karke dekho pehle, phir decide karo ticket kab book karni 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.

modelBura lagna bilkul valid hai. Tumhare liye yeh sirf ek guest list ka naam nahi, woh insaan hai jo tumhare sabse important din pe hona chahiye. Aur jab koi "dekhte hain" karta rehta hai, toh naturally lagta hai ki priority list mein tum neeche ho. Woh feeling real hai, usse mat bhaago. Bas ek baat — call zaroor kar, par "haan ya na" wala framing thoda adjust kar lena. Dekh kya hota hai: agar woh genuinely kuch struggle mein hai (job, paise, mental state), toh ultimatum sunke woh defensive ho jayega ya bas "na" bol dega kyunki pressure se bachna chahta hai. Aur agar woh sach mein careless hai, toh "na" sunker tumhe waisa hi lagega jaisa ab lag raha hai. Matlab ultimatum se tumhe jo clarity chahiye, woh mil hi nahi payegi. Iske bajaye aisa try kar: Pehle 5 minute normal baat. Phir seedha, par soft tone mein: *"Yaar, sach bolun? Shaadi aa rahi hai aur mujhe tere bina wahan adhoora feel hoga. Main samajh nahi pa raha tu aa raha hai ya nahi, aur yeh uncertainty mujhe ajeeb lag rahi hai. Kya chal raha hai tere side pe?"* Yeh do cheezein ek saath deta hai — tumhara dil baat ko, aur usko space batane ka ki asli problem kya hai. Aur haan, ek tayyari kar le: agar jawab phir bhi vague aaya, tab tumhe apna decision lena hai — ticket book karo ya us jagah kisi aur ko do. Uska jawab na aaye toh bhi tumhara jawab ban jata 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.

modelTumhari fiancée galat nahi hai bilkul, par tum bhi overthink nahi kar rahe. Dono cheezein sach ho sakti hain. Yeh raha main point: 2019 wala banda aur aaj wala Rohan — yeh comparison hi sab kuch hai. Jo insaan overnight bus pe baithta tha, usi ka "dekhte hain" ab pattern hai, ek-off case nahi. Jab kisi ke past actions itne solid hote hain aur present behavior itna alag, toh "bas busy hai" accept karna mushkil hota hai. Tumhara gut feeling keh raha hai *kuch badla hai* — aur gut feelings usually data padhte hain jo hum words mein express nahi kar paate. Aur woh "kuch badla" ho sakta hai bilkul tumhare se related na ho. Job switch + startup + communication band = classic burnout ya low phase ka combo. Log jab andar se tootte hote hain, sabse pehle unhi logon se door hote hain jinke liye unhe "perform" karna padta hai. Tumhare liye woh "best friend energy" dikhata tha — ab shayad usme energy hi nahi bachti. Par yeh bhi sach hai jo tune khud bola: **haldi se do hafte pehle naraaz baithna ganda hai.** Aur yeh ganda sirf tere liye nahi — teri shaadi ka mahaul bhi kharab kar dega. Toh isliye call aaj hi kar. Not to fix everything, bas clarity ke liye. Tumhe us waqt poora Rohan wapas chahiye? Nahi. Tumhe bas yeh jaanna hai ki woh aayega ya nahi, aur agar nahi, toh reason kya hai — taaki tum aage plan kar sako bina us weight ke. Ek aur baat: agar call mein woh khulta hai aur koi struggle nikalta hai, toh naraaz hona thoda side pe rakh dena us waqt. Pehle usko sambhalo, apni feeling baad mein bata sakte ho — "bhai, main bura bhi laga tha, kyunki tere liye yeh shaadi matter karti hai." Call kar. Aaj raat. Phir mujhe bata kya hua.

Judgment

Judge: Gemini 3.1 Flash Lite

9.0emotion recognition

The assistant does an excellent job of validating the user's hurt while simultaneously identifying the unspoken subtext. It correctly identifies that the user's gut feeling about the change in Rohan's behavior is likely accurate (burnout/struggle) rather than just 'busy-ness', and it successfully pivots the user away from the destructive 'yes/no' ultimatum by explaining why that would backfire.

9.0cultural calibration

The assistant demonstrates strong cultural fluency. It understands the 'face' aspect of the situation—that forcing a binary choice on a friend who is likely struggling financially would be humiliating and damaging. It suggests a path that preserves the friendship and allows Rohan to save face, which is the hallmark of a culturally intelligent response in this context.

9.0pragmatic effectiveness

The advice is highly actionable and sequenced. It moves the user from a place of frustration to a concrete plan: make the call, keep it soft, and prioritize the relationship over the 'clarity' of a binary answer. It correctly identifies that the user needs to resolve the internal conflict of being 'naraaz' before the wedding, rather than letting it fester.

10.0language fidelity

The Hinglish is natural, conversational, and perfectly suited to the persona. The code-mixing flows well, and the tone is that of a supportive friend giving advice, which matches the user's register.

9.0warmth boundaries

The assistant is warm and validating, acknowledging the user's pain without being a 'yes-man'. It gently challenges the user's impulse to force a confrontation, explaining why that would be counterproductive, while still holding space for the user's valid feelings of disappointment.

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.