The Neebora platform
One portal for the messages behind every event you run: invitations, updates, replies and RSVPs, kept separate for each project.
Businesses and projects
An event company signs up as a business on Neebora. Inside it, every event you run becomes a project. Each project has its own WhatsApp number, its own guest list and its own conversation history, so nothing overlaps, even when several events run at the same time.
Ananya & Rohan wedding
- WhatsApp number
- +91 ••••• ••4210
- Guest list
- 320 guests
- Conversations
- Kept separate
Annual Partner Summit
- WhatsApp number
- +91 ••••• ••7788
- Guest list
- 180 guests
- Conversations
- Kept separate
Desai family reception
- WhatsApp number
- +91 ••••• ••1935
- Guest list
- 96 guests
- Conversations
- Kept separate
A dedicated number for each project
Each project connects to its own WhatsApp number through Meta's Coexistence feature. Coexistence lets a business keep using the WhatsApp Business app on a number while that same number is also connected to the WhatsApp Business Platform.
In practice, your team can keep chatting with guests from the app, while Neebora handles broadcasts, replies and RSVP tracking from the portal.
You connect each number yourself through Meta's own sign-in flow and approve exactly what Neebora can access. Neebora is not an official Meta product or partner programme.
What the platform covers
Broadcasts with approved templates
Send invitations, schedule changes and reminders to a whole guest list. Messages sent outside a guest's active conversation use WhatsApp-approved templates.
A shared inbox per project
Guest replies collect in one place for the project, so your team can respond without hunting through personal chats.
RSVP tracking
Follow attending, declined and pending counts as replies arrive, for each event separately.
Isolated data
Guest lists and message history never mix between projects, even under one business account.
Compared with sending manually
Many event teams start by messaging guests from an ordinary number. Here is how that differs from working in Neebora.
| Task | Manual sending from a personal number | Neebora |
|---|---|---|
| Sending to a guest list | Messages sent by hand or through broadcast lists | One message to a project's guest list, using approved templates |
| Replies | Spread across personal chats and phones | Collected in the project's inbox |
| RSVP tracking | Counted by hand in a spreadsheet | Attending, declined and pending counts per event |
| Separating events | One contact list for everything | Separate number, guest list and history for every project |
| Getting connected | Official access historically meant a Business Solution Provider | Connect a number you already use in the WhatsApp Business app, through Meta's sign-in flow |
Responsible messaging
Neebora is designed for opt-in communication with guests about events they are part of. Customers must have each guest's consent before messaging them, use approved message templates for business-initiated messages, and honour opt-out requests.
Customers must also follow the WhatsApp Business Terms of Service and WhatsApp Business Messaging Policy. These requirements are set out in our Terms of Service, and our handling of guest data is described in the Privacy Policy.
Where we are
Neebora is in active development. We're working with a small group of event companies before opening more widely, and features described on this site may change before launch.