Software must: • Be a web-based cloud application • Be supported by all widely used browsers, (Chrome, Edge, Firefox) • Work consistently between all widely used browsers (Chrome, Edge, Firefox) • Not use proprietary hardware or downloads required, as well as no local servers needed. • System must allow ticket issuance without collecting client PII. • Support ticket-based queuing with no requirement for name or phone number (anonymous option). • Have ticket-based queueing that allows tickets to be printed by self-service kiosk as well as manual ticket issuance for reception area staff without kiosk login, especially for low-traffic areas. • Have ability to reprint lost tickets from both kiosk and staff interface. • Have an optional phone number input for SMS notifications but not required. • Include SMS text notifications for appointment reminders, queue updates, etc. • Include application for waiting area monitors that show waiting ticket numbers and that also allow for voice call outs of ticket numbers and area to proceed towards. • Include application for waiting area monitors that works consistently between all browsers (Chrome, Edge, Firefox) including voice call outs. • Must take tickets as first come first serve but also allow for ticket triaging as either a built in function or by allowing workers to pull specific tickets by service type. • Be operable over both wired and wireless networks. • Must be resilient to minor internet disruptions, especially in wireless environments. I.E, Application does not require a restart after any disruption in wireless network • Have automatic software updates that do not interfere with application during working hours. • Support Single Sign-On (SSO) via Microsoft Azure Active Directory, including usernames with apostrophes • Support two-factor authentication. • Must accept usernames with apostrophes. • Have role-based access control with: o 750 named user/agent licenses o 15 named admin licenses • iOS, Android and Windows compatible.
