Intezaam runs your events where they already happen — a WhatsApp group per booking — and keeps an append-only record of every guest count anyone ever stated, with who said it and the message it came from. When the client says “I told you 400”, you have the message.
Every one of these is a WhatsApp problem, which is why the software has to live there too.
The count arrives in a voice note, changes twice on the phone, and lands in somebody's head. The kitchen produces against a guess and eats the difference.
“We said 350.” You remember 450. Neither of you can prove it, so the discount comes out of your margin to save the relationship.
Twelve people asked one by one across a dozen threads. Three never answered, and you find out at the venue.
A client messages the number they already have. The thread is logged, attributed and searchable — nothing is retyped into a form.
One WhatsApp group per event, created from the dashboard. Every message in it is attributed to that booking automatically, so a count stated at 11pm lands on the right job.
A reply of “435” is recorded as a revision with the sender and the message id. Twenty-four hours before service it locks, and the kitchen gets the count plus your buffer.
Nothing is edited. Nothing is deleted. Each revision keeps who stated it, when, and the WhatsApp message it came from — so the final bill is defended with evidence rather than memory.
Created from the dashboard, with the client added. Everything said in it is attributed to that event.
Rate, estimate and what it includes, sent on WhatsApp and stored append-only. Re-quote and both survive.
Ask twelve people at once whether they can work Saturday. The roster sizes itself from the confirmed count.
Not just events — how many people each day has to feed, and which days have no count yet.
Every message is queued, paced and recorded. A refused send is kept with the reason, never dropped.
Your team works from a dashboard; the client only ever sees the WhatsApp number they already know.
Software built on the official WhatsApp Business API cannot create a group, cannot run a poll, and cannot listen to a conversation between other people. Those three things are the whole job of running an event. Intezaam works differently, which is why it can sit inside the group where the work actually happens.
It also means we respect the limits that come with it. A number that has never written to you cannot be cold messaged — the system refuses, tells you why, and keeps the message rather than pretending it sent.
No. They use WhatsApp exactly as they do now. They never see a portal, an app or a login — only the number they already message you on.
No. Your existing business number is paired to the system by scanning a QR code on the phone, the same way WhatsApp Web works. Your history and your contacts stay where they are.
It is still recorded, with the time it arrived — but inside 24 hours of service the production number stops moving. The kitchen keeps working to the number it was given, and you have the evidence that the change came late.
No, and that is deliberate. WhatsApp rejects a first approach from a linked device, so the system refuses at the point of queueing and shows you the reason instead of failing silently later.
It is sold to caterers first, because a moving guest count costs them the most. Nothing underneath is catering-specific — decorators, venues and rental vendors run the same way.
We are onboarding the first vendors now, and pricing is agreed with each of them as their volume becomes clear. Create an account and set up at your own pace; we will talk about pricing once you are running.
Create your account, add your menu and bank details, and scan one QR code with your business phone. The bot starts answering your clients from the next message.
Already set up? Sign in