Step 1: How to log in

Created by Matthew Lundeberg, Modified on Sun, 21 May, 2023 at 10:34 AM by Matthew Lundeberg

1. Once your dashboard is created, you will receive a welcome email from Veloce Solutions: Communications. This email will contain the necessary information to access your dashboard. 

*    If you cannot find this welcome email, be sure to check your spam folder. If you still cannot find it, contact Veloce Solutions Support.


2. To access the Veloce Solutions: Communications dashboard, go to the following URL in your web browser: https://app.velocesolutions.net/

3. Enter the email address associated with your communications dashboard and your password in the provided fields.

*    If you have lost or forgotten your password, you can click on the "Forgot password" option to receive a link that will allow you to set a new password.




4. The first time you log in on a new device, you will be prompted to enter a validation code. This code will be sent to the email address registered with your account. Once entered, your browser should remember this validation for future sessions. 

* Please note that if you log out of the communications hub or clear your browser cache, you may be required to revalidate your account, even on previously used devices.
* The same validation process applies to logging in via the mobile application on new devices.


5. Prior to signing in, you have the option to review the latest Terms and Conditions. You can find a link to the latest Terms and Conditions below the sign-in button. By signing in, you agree to adhere to the latest posted Terms and Conditions.  Find the latest Terms and Conditions here


Remember to keep your login credentials secure and confidential. If you encounter any difficulties during the login process or have any questions, don't hesitate to reach out to Veloce Solutions Support.


Happy logging in!



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article