Set up owner notifications

Every new submission lands in the notification bell automatically — there is nothing to enable. The bell shows an unread count across all your bots, and each entry links straight to the submission it is about.

• Open a notification to jump to the submission; it is marked read as you go.
• Use Mark all read to clear the counter after a busy stretch.

The bell only helps while the dashboard is open. For everything else, connect Telegram in account settings and submissions reach you as chat messages from the Meerlume notification bot.

When a new submission arrives in a pending status — a booking or request waiting on your review — the Telegram notification carries inline Accept and Deny buttons. One tap decides it, right from the chat.

• Accept moves the submission to your first active status — for bookings, that confirms the slot.
• Deny moves it to your first cancelled status and releases the slot.
• Either way the customer receives the status update you configured, exactly as if you had decided from the inbox.

The notification text is per bot, under Owner notification in the builder's Configure tab. Use {{node-id}} to pull the customer's answers into the message — service, party size, preferred time — so the notification tells you everything you need to decide without opening it.

Not every bot deserves a midnight ping. Each bot has a Notification urgency setting under Bots → Settings that controls how quickly new submissions reach you.

• Immediate — every submission notifies you right away. Use it for bookings with short notice windows.
• Business hours — notifications wait for your next open window, based on the business hours in account settings.
• Digest — submissions are batched and delivered together instead of one ping each.