Notification

RabbitBot’s notification system automates and customizes in-group updates, announcements, and reminders about quests, campaigns, and community events. By leveraging notifications, community managers can boost engagement, keep members informed about campaign progress, and celebrate milestones in real-time.

Notification Settings

RabbitBot’s notification system is highly configurable to align with each campaign’s specific timeline and engagement strategy.

1. Event Period

   • Start and End Dates: Define the timeframe during which an event, such as a quest or campaign, is active. For instance, set an event period from October 1st to October 15th if you want to run a two-week campaign.

   • This ensures that notifications are aligned with the event’s actual duration, providing timely updates.

2. Notification Execution Period

   • Pre-Event, During Event, and Post-Event Notifications: Notifications can be scheduled at different stages to engage users at optimal times. Consider splitting the notification period into three key stages:

     • Pre-Launch: Generate interest before the event begins. For example, if the event starts on October 1st, set notifications to begin September 28th.

     • During Event: Keep users engaged and aware of progress throughout the event period.

     • Post Event: Send a final message after the event ends to thank participants, provide updates on reward distribution, or announce winners.

   • Example Execution Period: If the event runs from October 1st to October 15th, the notification period could span from September 28th to October 16th, ensuring engagement before, during, and shortly after the event.

3. Frequency Settings

• General Message Frequency: Determine how often RabbitBot sends notifications, such as every 4 hours, to keep the group updated.

• Notification Gap Limit: Specify the minimum number of messages required between notifications. This prevents frequent notifications from cluttering the conversation. For example, setting a 100-message gap means that after a notification is sent, at least 100 messages must be sent by users in the group before RabbitBot sends the next notification.

  • Advantage of Notification Gap Limit: It will reduce the notification at night when less people are chatting, to avoid over notify to the group.

• Notification Cap: Limit the maximum number of notifications RabbitBot can send within a defined timeframe to prevent spam. For example, setting a cap of 5 notifications every 3 hours ensures that notifications don’t overwhelm the chat, allowing organic conversations to flow.

  • Advantage of Notification Cap: If you set up a Participant or New Group Joiner based notification, you might face a large amount of user inflow, to avoid over notify to the group, the Notification Cap will cap the time based notification cap.

Notification Templates

Templates allow RabbitBot to send customized messages for different stages of an event, ensuring that each notification is relevant and engaging. Here are the template options and their uses:

Type of notification

1. General Notification

   • The general template serves as the default message if no specific template is chosen. Use this template for straightforward announcements or campaign details.

   • Example: “Join our latest quest to earn points and rewards! Open RabbitBot in the group to view the active quests.”

2. Pre-Launch Notification

   • Pre-launch notifications build anticipation by informing users of upcoming events without fully revealing details.

   • Example: “Heads up! A new campaign is coming soon. Stay tuned for more details – you won’t want to miss it!”

3. Participant-Based Notification

   • This template triggers notifications based on user participation milestones. It’s ideal for large-scale campaigns or events where you want to highlight activity and motivate others to join.

   • Example: “🎉 We’ve reached 100 participants in our latest quest! Join now and be part of the excitement.”

4. New Group Joiner Notification

   • New joiner notifications are designed to welcome new members and encourage them to participate in ongoing events or explore RabbitBot’s features.

   • Example: “Welcome to the group! Check out our ongoing quest and start earning points today by participating!”

5. Post-Event Notification

   • Use post-event notifications to thank participants, announce winners, or provide information on reward distribution.

   • Example: “Thank you for participating in our campaign! Rewards will be distributed soon. Stay tuned for our next event!”

Choices of templates

Each template is tailored for specific timing within the event lifecycle, providing targeted messaging that maintains user interest and drives participation.

Notify Me and Send To Group Now:

After you setup Notification, you can choose to send to yourself to review it directly on your device.

• Notify Me:

• Send To Group Now:

You can see the next notification time as displayed, however if you want to notify the group at a flexible time, you can choose to send the notification to the group Now, which may be more effective when you need more active interaction with your community.

Publish Campaign without Notification setup:

Before and after setup notification:

After you setup the notification, and “Save” it, the notification icon will be updated with lines within.

When you Publish the campaign, the system will notify you to activate the notification as well.

After you successfully launch the campaign, both Status will turn to Publish and Activated.

Best Practices for Notifications

1. Engage at Key Moments: Use pre-launch notifications to build curiosity, especially if your event is exclusive or offers unique rewards. For example, send a pre-launch notification three days before the event begins to spark interest.

2. Celebrate Milestones: Use participant-based notifications to acknowledge community engagement. Announcing milestones like “100 participants” or “500 messages in the chat” encourages more users to participate and keeps the momentum going.

3. Avoid Over-Notification: Balance notifications by setting appropriate gaps and caps to prevent message overload. If the group is highly active, consider longer gaps or higher message thresholds to ensure that notifications feel timely rather than intrusive.

4. Customize for Different Campaigns: Tailor the notification frequency and templates based on the campaign type. A short-term flash campaign may benefit from more frequent updates, while a longer quest can use spaced notifications to sustain interest over time.

Notification Mapping: