The new (BETA) site for MessageBee offers additional views and filters for your library's data. One of the new features is the ability to view reports at the branch level, for multi-branch libraries.
To view these reports, you will need to use the 'Beta' site for MessageBee.
- Login to your library's MessageBee account
- Click on the orange 'Try the BETA site' button at the top of the screen
- Click on the Reports menu option at the top of the screen and select 'Transactional'
- By default, 'All Branches' will be selected from the report selections. Click on 'All Branches' to view other branches
- Select the branch, and then select the dates for your report. To select more than today or 7 days, click on the 'Custom' option and select the date range from the calendar.
- The total notifications, success rate, and engagement metrics will change based on your selections.
- Clicking on 'View Details' on the Total Notifications button will open the 'Successful Notifications Sent' report in the 'Communication' view further down the screen.
- To view daily, weekly, or monthly trends, scroll down the page.
- Each of the options (channel, notification type, and communication) can switch views to show trends by day, week, or month and can be exported.
- The Channel tab displays an overview of the email or SMS notices sent
- The Notification Type tab will show the general type of notice, e.g. Hold, Overdue, etc.
- The Communication tab will break down the data further to show each type (template) used. e.g. First Overdue, Second Overdue, etc.
- To view delivery failures, click on the 'Success Rate' view details button under the main report filters. This report option opens the Failed Notifications report
- Selecting the Engagement Rate button will open the 'Clicks and Opens' report
For more information about the new reports view the MessageBee help site at https://mbsupport.uniquelibrary.com/support/solutions/articles/70000657202-introduction-to-the-new-reports-page
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article