Before
- Each outlet takes cake orders on its own number, and counter staff type them up between customers.
- Flavour, weight, eggless, the message on the cake, the time and the address arrive over several messages, and one missed detail means a wrong cake.
- Nobody sees how full the kitchen already is for that slot, so late "can't do it" calls happen.
After
- Orders from all outlets land in one queue, with the details already read from the message (Hindi, English or Hinglish).
- Missing details become one short question; lead times (photo, fondant) and kitchen capacity for that slot are checked before anyone says yes.
- A reply with the price in ₹, the advance and the slot is drafted, plus a kitchen ticket. Staff edit and approve; nothing is sent on its own.
Order queue
Sample messages from five outlet numbers, demo time Mon 16 Nov, 11:00 AM. Click one, or paste your own below.Paste a new message
Try your own mix of Hindi, English and Hinglish. Anything the desk can't read becomes a question, never a guess.
How the desk works
- Collect. Messages from each outlet's number come into one queue, tagged with the outlet and time. In a pilot this connects to the chat accounts you already use, only after you agree to it in writing; customers keep the same numbers.
- Read. Flavour, weight (aadha kilo, 1.5 kg), eggless, photo or fondant, the message in quotes, the day (aaj, kal, parso, Saturday) and the time (shaam 7 baje, 4pm). "Wahi cake jo pichli baar" pulls up that number's last order. This demo uses a deterministic parser on a sample menu; a production build adds a language model held to your menu, with this parser kept as a test check.
- Check. Lead times (photo 24 h, fondant 48 h), same-day cut-off, seasonal flavours and the kilograms the kitchen still has free in that slot. Anything that doesn't fit gets two or three options to offer.
- Draft. The reply lists the order, the price in ₹ and the 50% advance; a kitchen ticket is created once confirmed. Staff edit and approve every message.