The 'dekhte hain' decoder: what soft answers really mean

The first time I really understood "dekhte hain," I was standing in my kitchen at 11 p.m. counting confirmations for my cousin's roka on the back of an electricity bill. My tally had three columns: pakka, nahi, and a third, much longer column I had labelled "???". Almost everyone was in the "???" column. And every single one of them had, at some point, sent me a message that sounded warm, willing, and completely unusable as a headcount.

"Dekhte hain." "Aate hain, aate hain." "Try karenge." "Bataayenge." Lovely words. Zero plates.

I've since hosted and helped run enough functions — a griha pravesh, two birthdays, a satyanarayan katha, more than one wedding side-event — to realise that soft answers aren't a bug in Indian RSVP culture. They are the culture. Nobody is lying. They're being kind, keeping options open, and avoiding the small social pain of a firm "no." Your job as a host isn't to feel insulted by it. Your job is to decode it, and then convert what's convertible.

So here's the decoder I wish I'd had that night at the kitchen counter — a working dictionary of soft answers, and a repeatable way to turn the yes-shaped ones into real numbers.

Read the temperature, not the words

The mistake I made for years was treating every vague reply the same — chasing all of them equally, or ignoring all of them equally. What actually helps is sorting soft answers by temperature: how much genuine intent is hiding under the politeness.

• Warm (leaning yes): There's real intent; the person just hasn't nailed down logistics. These convert with one good nudge.
• Lukewarm (genuinely undecided): A real coin-flip in their head — depends on family, health, another event. These convert sometimes, and only if you make deciding easy.
• Cold (polite no): The words are soft, but the answer is already no. Chasing these costs you goodwill. Decode, accept, move on.

Once you sort by temperature, the whole thing stops feeling personal. A cold "dekhte hain" isn't rejection of you — it's someone sparing you an awkward refusal. Let them.

The decoder dictionary

Here's the reference table. I built this from my own functions and from watching beta hosts stare at their phones. Read the reply, find the temperature, take the move.

What they say	Temperature	What it usually means	Your move
"Aate hain, aate hain" (repeated)	Warm	Real intent, no logistics locked. Repetition = enthusiasm, not confirmation.	One personal nudge with a date and a headcount question. Converts easily.
"Pakka try karenge"	Warm–Lukewarm	Wants to come; unsure about time/work/family.	Give a reason to decide now: "caterer count Thursday tak chahiye."
"Haan bhai, aana toh hai"	Warm	Genuinely intends to; hasn't checked calendar.	Send the invite link personally, ask "kitne log?"
"Dekhte hain, confirm karta hoon"	Lukewarm	Coin-flip. Depends on something they can't control yet.	Wait 3 days, one warm reminder with the real deadline.
"Family se poochh ke bataata hoon"	Lukewarm	Honest — the answer really isn't only theirs.	Make it easy: "koi jaldi nahi, bas Thursday tak approx bata dena."
"Us din thoda tight hai, dekhta hoon"	Lukewarm–Cold	Probably not, softening the ground.	One light reply. If silence, count as no.
"Zaroor, agar Delhi mein hua toh"	Cold	Conditional on something unlikely. It's a graceful no.	Warm acknowledgement, no chasing.
"Aapka function hai, aana toh banta hai"	Lukewarm	Social nicety. Sincere warmth, uncommitted feet.	Convert with a direct, personal ask — not a group post.
"Bas kaam thoda dekhna hai, phir pakka"	Lukewarm–Cold	Work is the polite exit door.	Give one deadline. Then treat silence as no.
"Blessings hain, aane ki koshish karenge"	Cold	Especially from elders far away: love, not attendance.	Accept warmly. Don't put them in the yes column.
Seen ✓✓, no reply	Lukewarm	Unsure, hates saying no, or genuinely forgot.	One personal reminder after 4–5 days. Then no.
Long "congratulations" message, no yes/no	Warm–Lukewarm	Happy for you; hasn't processed the ask.	Reply thanking them, then ask the one question directly.

Print it, screenshot it, keep it open while you plan. The single most freeing line in that table is the repeated one: if silence follows a kind reminder, count them as not coming. That one rule saved my sanity.

The conversion method: name it, date it, permit it

Decoding tells you which soft answers are worth converting. This is how you actually convert them — a three-part message I use for every warm and lukewarm reply. I call it name it, date it, permit it, and it fits in one WhatsApp message.

1. Name it — use their actual name, one-to-one, never a group. "Rohit bhai" beats "Dear all" every single time. A named message reads as a conversation; a group blast reads as a flyer nobody has to answer.
2. Date it — attach the ask to a real, dated, human reason. Not "please RSVP soon." Instead: "caterer ko Thursday shaam tak final count dena hai." Aunties and uncles instantly relate to not paying for empty plates.
3. Permit it — explicitly allow a no. "Na aa pao toh bhi bilkul theek hai." Counter-intuitively, giving permission to decline gets you more honest yeses, because you've removed the guilt that was powering the silence.

Miss any one of the three and the message weakens. Name without a date is a nice chat that goes nowhere. A date without permission feels like pressure. Permission without a name is a broadcast. All three together is the whole trick.

Scripts you can send tonight

Here are ready-to-send messages built on the method. Edit the names and the deadline, send from your own number.

Warm reply → gentle confirm (Hinglish)

"[Name], aapne bola tha aana toh hai — bahut khushi hui 😊 Bas caterer ko Thursday tak final count dena hai. Ek chhoti si cheez: aap aur kitne log aa rahe ho, approx bata do? Na ho paaye toh bhi bilkul tension nahi."

Lukewarm reply → decision nudge (Hinglish)

"Namaste [Name], koi jaldi nahi, bas ek clarity chahiye taaki khaane ki vyavastha theek se ho. Thursday shaam tak agar 'haan' ya 'na' bata dein toh bada help ho jaayega. Dono jawab chalega 🙂"

Seen-but-silent → last light nudge (English + Hinglish)

"[Name], no pressure at all — bas final list bana raha hoon. Aa rahe ho ya iss baar miss? Ek word bhi kaafi hai. Agli baar pakka milte hain either way 🙌"

The plus-one hedge → head off the +4 surprise (Hinglish)

"[Name], aap zaroor aaiye! Bas seating aur plates ke liye pooch raha hoon — aapke saath kitne log honge? Bachchon samet approx number bata dena, taaki sab comfortable baithein."

Timing matters as much as wording. My rule: first personal invite goes out early, the decision nudge lands 4–5 days later, and the final light nudge 36–48 hours before your caterer's cut-off. Never more than one follow-up in a week — past that, you've crossed from host to debt collector.

When you should stop converting

I have to be honest about the limits, because a decoder in the wrong hands turns into pestering.

Some soft answers are complete sentences. "Blessings hain, koshish karenge" from a grand-uncle three states away is not a maybe you convert — it's affection you accept. A "dekhte hain" that stays silent through one warm, deadline-anchored, permission-giving nudge is a no. Reading it as "needs three more messages" is how you become the relative people mute.

And there's a whole category the decoder can't touch: elders who will never use a yes/no button. Nani, Bauji, the family priest — they confirm by phone, three days out, with "beta hum aa rahe hain, driver ka intezaam ho gaya." Don't wait for their tap. Call them, count them by hand, and keep that count in a separate line. If you want the mindset behind all this, I wrote a companion piece on why guests don't RSVP in the first place — the psychology under the phrases in that table above.

Where a little structure helps

Once your list crosses forty or fifty people spread across family, friends and colleagues, the decoding is easy but the bookkeeping is brutal — three WhatsApp chats, a broadcast list, and a notes app that never agrees with itself. That's the actual problem worth solving: one honest count in one place. This is exactly the itch behind Inyeet — you send your own card through your own WhatsApp, each guest gets a private link with a one-tap yes/no/maybe and a spot for family headcount, and if someone forwards their link, the new person is asked to confirm who they are so your numbers don't quietly inflate. It won't make an unwilling cousin willing. No app does that. But it does mean your "???" column lives on a dashboard instead of the back of an electricity bill.

For a twenty-person puja where everyone confirms by phone anyway, skip all of it — a few calls will do, and honestly they're nicer. Tools earn their place at scale, not at intimacy.

The takeaway

Soft answers aren't your guests being difficult. They're your guests being Indian — warm, hedging, allergic to a blunt no. The skill isn't forcing firmness onto people who won't give it. It's reading the temperature, converting the warm ones with a named, dated, permission-giving nudge, and gracefully counting the cold ones as no without a shred of resentment.

Pick your next function. Keep the decoder table open. Send three "name it, date it, permit it" messages tonight and watch how many "dekhte hain" quietly turn into real numbers. The ones that don't were never plates — just kindness in the shape of a maybe. And when you're ready to keep those numbers honest in one place instead of a midnight tally, you can join the Android beta at inyeet.com/early-access — a real message from a real person, no spam.