REQUEST A DEMO
Tell us what your team reviews, which knowledge sources matter, and how you expect the product to be deployed. We will prepare around that rather than run through a fixed sequence of screens. Use the note field for anything specific you want covered.
WHAT WE CAN GO THROUGH
Most evaluations cover some of each of these. Tell us which ones matter and we will weight the session accordingly.
Upload a document, watch it become questions and standalone requirements, and work through items with the suggested answers, the sources behind them, and the policy findings in view. This is the part worth seeing on a document of your own rather than on ours.
How the library is imported and prepared, what cited search returns and how a citation opens the stored excerpt, and how maintained reusable answers become sources for the next questionnaire.
The tenant boundary, sign-in against your identity provider, the permission profiles and customer assignments, and what does and does not leave your network in each deployment option.
If you would rather read before you talk to anyone, thehow it works page follows one questionnaire from start to finish, and theretrieval page describes the mechanics in technical detail.
EVALUATING ON BEHALF OF IT
A questionnaire tool is approved by the people responsible for systems and data, so a technical review is expected rather than an obstacle.
We can walk through the components, the isolation boundary, identity and authorization, data flow, model hosting, backups, and the upgrade process against the controls your organization applies. Thepage for IT and security teamssets out what is deployed and lists the questions we would expect to be asked. Reading it before the session makes for a better one.
USEFUL CONTEXT
The more of this we know beforehand, the less of the session is spent establishing it.
Prefer email? Write to docusense@curlybracket.nl.
Required fields are marked *
