Skip to main content

June 2025 Updates & Bug Fixes

New Updates for June 2025!

James Simboli avatar
Written by James Simboli
Updated over a week ago

Updates:

  1. Minimum Packing Hours - You can now set a minimum amount of packing hours to charge for the move. The default minimum hours can be set in Manage > Estimate Settings > Main Estimate Settings > Labor Price Estimate and you can also manually change this on estimate step 6.

  2. Hiding the Multi-Day Price - You can now have the Multi-Day price be hidden from the customer portal. This is to ensure that you can show all of the information for each day of the move while only showcasing the total cost or estimated price range of the job.

  3. Add Rooms with Move Size - We've now added this feature to work with surveys via the app!

  4. More Push Notifications for the App - You can now receive app notifications for when a customer pays their deposit and for when a customer has signed their estimate. This can be enabled in Manage > HR > select a profile > Login & Permissions then check the 'Receive Push Notifications button.

  5. Step 5 Storage Tab - You can now enter storage directly on step 5 of the estimate! This can be used for short term storage (up to 1 month), for anything longer you would use the standard storage feature in the software. This works based on a daily price you would charge which can be set up in Manage > Storage. Then select how many days they will be in storage for on step 5.

Bug Fixes:

  1. We had some customers experience an error when trying to resend an email to a customer. This has now been fixed.

  2. We fixed an issue where the truck count was defaulting to 1 when setting it to 0.

  3. For guaranteed quotes, the travel fee was still charging as an hourly rate. This should be working properly now.

  4. We had an issue where LiveSwitch would not send the proper link when the text/email was sent to the customer. This would occur if the account you signed up with was not the same one that was connected to your MoveitPro system. This should be fixed for future cases.

Did this answer your question?