The Vendor is required to provide unified communications platform.
- System include:
• Analytics and reporting on message delivery, delivery failures, and message interactions
• Ability to ingest information such as class rosters and other data fields from SIS and other systems (SIS, ERP, and User generated .csv files)
• Ability to maintain custom recipient lists that can be shared for use by other users/groups
• Ability to include and manage non-district recipients of emergency and non-emergency messages
• Ability to add custom fields, tags, flags, or other taxonomies in relation to recipients which can be used for message filtering and scheduling
• Multiple contact fields for each user/family with ability for recipients to set preferences for the categories of communications received for each contact type (SMS, email, voice, etc.)
• Ability to limit the delivery time of non-emergency messages to within a window of approved times, with the ability to set different time windows for certain user groups
• Documented SLAs and send rates for email, text, and/or phone messages per volume of recipients
• Ability to stage and schedule messages including recurring communications
• The ability to set the delivery time of non-emergency messages to within a window of approved times, with the ability to set different time windows for certain user groups.
• Ability to create workflows or automations to send messages based on recipient data, previous message status, etc.
• Repository of sent messages (newsletters/emails) that can be referenced and linked in future communications
• Ability to build approval workflows for certain types of communications or certain groups of users, customizable not hardcoded
• The ability for groups of users to co-manage mailing lists and templates (district wide, by school, by department)
• Ability to centrally create, manage, maintain and distribute message templates to schools, departments, and users.
• The platform should meet or exceed industry standard SLAs
• The platform should provide documented SLAs and send rates for email, text, and/or phone messages per volume of recipients.
• Two-Way messaging, with the ability to toggle off and on from one way to two way messaging
• Ability to categorize messages as emergency, non-emergency and/or other user defined types 
• Ability by the recipient to prioritize and distinguish emergency messaging from other messages
• The system must be able to include and manage non-district recipients of emergency messages.
• Ability to send messages to recipients based on characteristics (grade level, school, club participation, job title, etc.)
• Ability for sender to preview messages as they will appear based on delivery method(s)
• Send unlimited messages to recipients via voice call, text message, email, mobile app push notification, social media, and desktop alerts. 
• Ability to send notifications out to recipients within seconds from any device, at any location.
• Ability to preview and customize SMS messages with consideration to message length
• It is desired that the platform supports multiple language support including two-way translation.
• Users should be able to embed media including URLs, PDFs, and images (including linked images) when sending via email or other platform-specific delivery options, without the need for HTML coding knowledge.
• The platform should also allow users to copy/paste content with retained formatting from other applications (MS Word, Google Docs, and html).
• The ability to personalize messages with mail merge information fields sourced from SIS and other sources.
• The platform should also facilitate the integration of content from the district website (WordPress) to minimize duplication of effort in communication.
• Ability to categorize messages as emergency, non-emergency and/or other user defined types 
• Ability by the recipient to prioritize and distinguish emergency messaging from other messages
• Ability to send messages to recipients based on characteristics (grade level, school, club participation, job title, etc.).  
• Ability for sender to preview messages as they will appear based on delivery method(s)
• There should be the ability to limit the delivery time of non-emergency messages to within a window of approved times, with the ability to set different time windows for certain user groups.
• Send unlimited messages to recipients via voice call, text message, email, mobile app push notification, social media, and desktop alerts. 
• Ability to preview and customize SMS messages with consideration to message length.
- Contract Period/Term: 1 year
- Questions/Inquires Deadline: June 5, 2025