The Gheemergency
There's a word we didn't invent. It emerged from our customers' WhatsApp messages before we had a name for it. We recognised it when we saw it, gave it a name, and started watching for it.
A gheemergency is what happens when someone runs out of Nei Native ghee at a moment when substitution is simply not on the table.
The pattern is consistent: it arrives without warning, usually late at night or early in the morning, and it carries a specific kind of urgency that is different from a regular reorder. A regular reorder says "I need more when you can." A gheemergency says "I need more now. Tomorrow. Today if possible. What are the options?"
The First Time We Noticed
It was close to midnight. A message came in: "I placed an Amazon order but it says Monday. I have no ghee left. Can you send one tomorrow?"
The specifics are ordinary. Someone ran out. Someone needed more. But what made it interesting was the precision of the distress. They had already placed an Amazon order. They knew it was coming. They still messaged us at midnight because Monday wasn't soon enough.
That's not a restocking problem. That's a dependency.
The ghee had become load-bearing in their kitchen — something they cooked with every day, something their family expected to be there. The gap between today and Monday wasn't acceptable, even though Monday was two days away.
We sorted it out. The order went out the next morning. First dispatch that day.
Then It Happened Again
A few weeks later. A different customer. Five in the morning.
"Just got back from travel. No ghee at home. Can you send asap?"
The message came before most of our team was awake. The customer had clearly just landed, or finished a long drive, and their first conscious thought — before unpacking, before sleep — was that there was no ghee at home.
Again: not a restocking message. A return-from-travel, 5 AM, no-ghee-at-home, asap message. The texture of urgency is different. It's specific.
We started calling these gheemergencies internally. Not to mock the urgency — the urgency was real — but because the word captured something precise. A gheemergency is not a complaint. It's a confession of dependence. It means ghee is no longer optional in that kitchen.
What Happens on Our End
The gheemergency became a real internal category. When a message came in that matched the pattern, a specific thing happened: it got escalated.
The internal dispatch group would get a message: "Gheemergency. Is anyone in office?"
If someone was there, the order went out the same day. The actual order note would read: GHEEMERGENCY. First dispatch, porter.
This is not a formalised SLA. There is no ticketing system. But it became consistent enough that the team developed an instinct for it. A gheemergency gets prioritised the same way you'd prioritise a message from someone you know, because in a way, we do know these customers. We've sent them ghee before. We know they ran out because they finished it, not because it sat in a corner.
The Word Travels
At some point, we started using the word in our replies to customers — not just internally.
When the order was confirmed and the dispatch was done, we'd write back: "If i may — the gheemergency, as we like to call it, is over." Half-joking, entirely meant. We didn't know how it would land.
The response, consistently, was laughter. "Hahaha yes thank uu." A string of emojis. Sometimes a voice note. The word landed every time — not because it was clever, but because it was accurate. The customer recognised themselves in it. They didn't need to be told what a gheemergency was. They had just lived one.
That matters. When your internal vocabulary makes a customer laugh instead of bristle, it means the word fits their experience closely enough that they're comfortable inside it. They're not being labelled. They're being seen.
A customer who feels seen by a brand is not the same as a customer who feels processed by one. The word is small, but what it represents is not. It's the difference between "your order has been placed" and "we know this matters to you right now."
From Customer to Customer-Partner
The gheemergency is the clearest signal we have that the relationship has changed.
A buyer places orders. A customer-partner places orders and texts at midnight. They message before unpacking from a trip. They adopt your language and use it back at you. They treat your dispatch team as people who are on their side — because, in their experience, you have been.
We don't use the phrase "customer-partner" in our marketing. But it describes something real: a person whose stake in the brand has grown past the last transaction. The gheemergency is where that shift becomes visible — not because of anything we said, but because of how they showed up.
What a Gheemergency Actually Tells Us
A gheemergency only happens when three things are true simultaneously: the ghee is the customer's primary ghee (not one of several options they rotate through), it's used daily (so depletion happens faster than expected), and it's irreplaceable in the short term (so the corner store won't do).
The midnight message and the 5 AM message came from different people, in different circumstances. But they arrived from the same place — a kitchen that had stopped working properly because one specific thing was gone.
That's not something you manufacture with marketing. It's what happens when someone has made your product part of how they live.
We track the gheemergency rate the same way we track reorder rates. It's a different signal. A reorder tells you the customer came back. A gheemergency tells you the customer cannot imagine not coming back.
There's a question embedded in all of this that we don't ask customers directly, but that we think about every time one of these messages arrives.
When did you last run out of something this fast?