# Platform User Journey The typical user journey on OpenVPP would go as follows: **User Connection into VPP:** * User lands on a utility or device vendor hosted web page * User enters qualification information into the web page * Device make, model, and identifier (e.g. serial number) * Address and other site data if needed (may be pre-populated by the device vendor or utility) * Payment is gathered if needed (depending on program, the cost may be paid by the device vendor or utility instead of the user) **Enrollment** * Enrollment request is passed to the OpenVPP Routing Service via API * Connectivity parameters, certificate, and any other data needed for authentication are returned * Device connects to utility server **User Successfully Connected Device to Utility** * Any other utility side program enrollment continue ̈ * User device can now be controlled and compensated for based on terms of the program * It’s expected the $OVPP to connect would be in the $1-20 equivalent range, with value to the user per device around $100-1,000/year depending on the program and capability of the device. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://openvpp.gitbook.io/openvpp-docs/onboarding-process-and-platform-usage/platform-user-journey.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.