Specifications include, but are not limited to: • Automatic ingestion of existing knowledge base sources from websites • Automatic ingestion of existing knowledge base sources from FAQ files/documents • Continuous monitoring for updated website information and adjusts responses accordingly. • Cloud-hosted (aka Software-as-a-Service) offering requiring no on-premise storage or processing • Integrate with UNH ticketing systems (TeamDynamix) to create tickets. • Ability to capture user contact information for additional follow up and lead generation. • Authentication via SAML-based single-sign on for access to the backend administrative interface. • Ability to report on the nature and number of questions asked and answered or unanswered. • Able to have multiple independent instances to meet the needs of different campuses or departments. For example, a separate UNH admissions service from a Keene State admissions service. • Chatbot can be embedded in Drupal-based websites. • Chatbot can be embedded in WordPress-based websites. • Chatbot can be embedded in SharePoint websites • Canvas Integration • Language Translation. • Salesforce Integration. • Bot interface should be branded to look-and-feel like our existing websites. • Different branding for different instances. • Security Compliant (FERPA, GDPR, ADA, HIPPA) • User interface is accessible (compliant with WCAG 2.1 AA) • Chatbot should be compatible with multiple web browsers. • Chatbot should be accessible from mobile devices. • Preferably the end-user can send input via Texting/SMS. • A workflow that allows for follow-up when the bot has no answer. • Ability to transfer to a live agent. • Describe services that are provided to assist in the initial setup and ongoing maintenance of the chatbot knowledge base.
