Estimate Deposits no longer honor existing Customer Credits

Issue: If a customer had enough customer credits, those credits were automatically used to cover Estimate Deposits in the Client Portal—allowing them to bypass the required deposit payment entirely.

Resolution: Customer credits are no longer honored when taking Estimate Deposits through the Client Portal, ensuring the full deposit amount is always collected as intended.

Bug Fixes

Issue: When creating new invoices, the system was not assigning invoice numbers in the correct numerical order, which could cause confusion or result in duplicate invoice numbers.

Resolution: We updated the invoice numbering system to always use the next highest available number, making it simpler, easier to predict, and more reliable. We also added protections to guard users from accidentally using the same invoice number twice when editing existing invoices.

Issue: The Truck Mileage Report was not tracking truck mileage correctly, resulting in missing or incomplete mileage records, or inaccurate total mileage costs.

Resolution: Improved the Truck Mileage Report with better tracking logic, a new Drive Time column, and accurate Total Cost calculations based on current MPG and fuel prices.

Issue: Rate Matrices were not calculating totals correctly when the “Calc x Qty x Rate x Visits” setting was used, causing the final cost and total values to be miscalculated.

Resolution: Updated calculation logic to use the correct calculation method when this setting is selected, so that the cost and total are now correctly based on the “Calc” value.

Note:
We have ensured that all existing rate matrices will continue working as they currently do unless manually edited. If your rate matrices have been working correctly, no action is required on your end.

Issue: When a visit was deleted after time had been tracked against it, the tracked time no longer showed its original category of "visit".

Resolution: Fixed this by saving the visit’s name and type directly with the time entry, so the tracked time keeps its category even if the visit is deleted.

Issue: When searching for text messages within a specific status tab (“All”, “Open”, or “Done”) the system showed results from all tabs instead of just the selected one.

Resolution: The search feature has been updated to correctly respect the selected status tab, so results will now only show messages from the chosen tab (“All”, “Open”, or “Done”).

Bug Fixes

Issue: Error message occurred when trying to remove a customer's pending bank account from the CRM.

Resolution: Fixed an issue with the connection to Stripe's API, so users can now successfully delete unverified bank accounts.

Issue: Users experienced an issue where the Text Messages list would get stuck with an infinite loading wheel when searching using an apostrophe (’).

Resolution: Fixed the problem so that searches using an apostrophe now work normally and no longer cause infinite loading.

Issue: Users were unable to add more than one "Stop" action within a Sequence Automation, which limited the flexibility of how automations could be set up.

Resolution: This has been resolved so users can now add multiple "Stop" actions in a single Sequence Automation, allowing for more control over when and how sequences end.

Issue: The "Events Assigned to This Property" section on Properties was displaying events out of chronological order, making it hard to follow the correct timeline.

Resolution: Fixed the sorting logic so that events now appear in proper chronological order, making it easier to track the sequence of activity for each property.

Issue: When users clicked a customer’s name on the Text Messages page, it incorrectly opened a deleted version of the customer profile instead of the current, active one.

Resolution: This issue has been resolved so that clicking a customer’s name now always takes you to the correct, active profile associated with the message, ensuring deleted profiles are not mistakenly accessed.

Issue: The "Show Account Standing" setting was incorrectly affecting the visibility of "Paid", "Outstanding", and "Past Due" roll-ups on the My Day page, even though it was only meant to affect "Paid".

Resolution: Fixed the issue so that the "Show Account Standing" setting now only applies to the "Paid" roll-up, and no longer impacts "Outstanding" or "Past Due".

Issue: When switching between different actions in Sequence Automations, the actions could sometimes behave irregularly, leading to unexpected or incorrect automations being triggered.

Resolution: Fixed the issue so that switching between actions in Sequence Automations now works properly, ensuring expected Sequence Automation configuration.

🚀 SMS Just Got Way Faster!

April 4, 2025

We’re committed to making your Copilot experience smoother and faster—and we’ve just made a big improvement to SMS.

📲 Text message pages now load 6.5x faster

🔍 Search now looks through all your messages, not just the ones currently loaded

📥 See everything — not just a limited 2,000 messages

Whether you're following up with leads or replying to clients, you'll move quicker and find what you need faster.

Hop in and see the difference 👇

Bug Fixes

Issue: Estimate Logs incorrectly showed that an estimate was sent and viewed via email if the estimate was sent while no estimate email template was set.

Resolution: Added a preventative warning when sending an estimate by Email or Text from the Estimates main page if no estimate template is set. Implemented the same style of warning for the same actions on the Invoices main page.

Issue: Address input fields would stop working if the Google Maps API couldn’t be reached, preventing users from entering an address to create a property.

Resolution: If the Google Maps API is unavailable, the address field will now automatically switch to a regular text input so users can still type in the address manually.

Issue: In Reports, cities were case sensitive, so entries like "Austin" and "austin" were treated as different cities, causing duplicates in reports.

Resolution: Updated Reports to treat city names as the same regardless of capitalization, so duplicates like "Austin" and "austin" are now combined correctly.

Issue: In the Client Portal, attached Photos/Documents would not display correctly when viewing estimates.

Resolution: Fixed attached Photos/Documents so that they are viewable on estimates in the Client Portal.

Issue: In the Client Portal, when viewing an estimate, bullet points in line item descriptions would disappear, causing the description to become crowded.

Resolution: Resolved the issue by ensuring estimate line item descriptions properly display bullet points when appropriate.

Modern Estimates v1 – A Faster, Smarter Way to Win More Work.

🎯 What’s New

We’ve overhauled the estimate experience in the Customer Portal to help you close more deals, faster—with a clean design, quicker payments, and smarter insights.

CLICK HERE to see Modern Estimates in action!

✨ Highlights

✅ One-Step Estimate Deposits

From 5 steps down to 1, It's easier than ever for customers to say yes to an estimate.

🎨 Modern Look

A polished, professional layout across desktop and mobile.

❓Decline Reasons

Gain insight into why an estimate was rejected by the customer so you can adjust and improve.

🔐 Improved Login Flow

A smoother, more secure customer login experience.

📱 Mobile Optimized

Better usability on mobile devices for customers interacting with estimates.

🔧 Built for the Future

Behind the scenes, we’ve rebuilt key infrastructure—new APIs, improved authentication, and a foundation for rapid updates. Expect faster innovation and more powerful features soon.

Enhancements

Enhancement: "Notes to Dispatcher" Merge Tag for Emails and Texts

What’s New?

We’ve added a new merge tag, "Notes to Dispatcher"! This tag lets you automatically include notes to the dispatcher into email and text messages!

How it Works
When setting up email and text templates, you can now use the "Notes to Dispatcher" merge tag to pull in any notes for the dispatcher added to events on the schedule. This means your dispatcher can be notified with job-specific info without needing to look it up manually.

💡 Example:

You set up an automation to notify the dispatcher when a job is completed.

Now, you can include "Notes to Dispatcher" in that automated email or text message, and the dispatcher will automatically see any notes that were left for them. This way, the dispatcher will not need to search through the schedule to find the notes that were meant for them, saving valuable time in their workflow.

Enhancement: New Search Library Implemented for the Wiki Search

What’s New?

We've improved the Wiki Search experience by upgrading the library behind it, using the same custom-built library we recently added to the Global Search Bar! This new, custom-built search library has replaced the old outdated library, which means searches are faster, more accurate, and more reliable.

How it Works
You won’t see any changes to the look of the search bar, but behind the scenes, we’ve swapped out the old library for a new and improved one we built ourselves. This means:

✅ Better performance – search results load faster.

✅ Improved reliability – fewer glitches and more accurate results.

✅ Future flexibility – we now have more control to continue improving search features.

That’s it! You can keep using Wiki Search as usual—just better.

Bug Fixes

Issue: When editing an Estimate in “Accepted” status, all line items were getting unchecked automatically, even if they were previously selected.

Resolution: Updated the system to use the same logic for handling line items in both the client and business views, so checkboxes now stay correctly selected when editing an accepted Estimate.

Issue: On the Estimate Page History, line breaks were showing up as <br /> code instead of creating a new line, making the estimate history hard to read.

Resolution: Fixed the formatting so that line breaks now display properly, making the history easier to read and understand.

Issue: When routing from the Dispatch Board, only "Visit" type events were being counted as routable events.

Resolution: Fixed the dispatch logic so that it now includes all event types with properties assigned to the event when determining routable events.

Issue: When sending text messages that included the Estimate and Invoice link merge tags, the populated merge tags were showing as raw code instead of clickable links.

Resolution: Fixed the issue so that Estimate and Invoice links now appear correctly in text messages, making them easy to tap and view.

Issue: When automations sent emails that included emojis, the emojis appeared as question marks ("?") instead of displaying correctly.

Resolution: Fixed this by updating the way our system stores email templates so it can now fully support emojis in automated emails. Accounts with existing email templates containing emojis will need to update the email templates for the emojis to display correctly. Simply edit the email template, then save without making any changes.

Enhancements

Enhancement: New Global Search Bar Library & "Recent Searches" section

What’s New?

We have upgraded the global search bar by implementing a new, more reliable library to improve search functionality and reduce errors. This replaces the previous outdated library, making searches faster and more efficient. This library was built in house from the ground up, which makes it easy to quickly add future enhancements to searching in Copilot CRM. Included in this update is a brand new "Recent Searches" section, which shows your 5 most recent searches using the Global Search Bar!

How it Works

The new library enhances search performance and is designed to be used in multiple areas of the system. While this update focuses on the global search bar, this library will begin to be utilized in other search functions across the platform in the future.

Bug Fixes

Issue: Some error messages when sending SMS were unclear and did not provide helpful feedback, making it difficult to understand why messages failed.

Resolution: Fixed this issue by ensuring SMS related errors now display clear and informative messages.

Issue: The "Receipt Link" merge tag was not displaying a receipt link in text messages or emails, causing confusion for recipients.

Resolution: Fixed this issue so that the "Receipt Link" merge tag now correctly populates with the right receipt link.

Issue: Time tracking records for Visits were not always saving GPS location on mobile devices.

Resolution: Updated the GPS service to attempt saving the user's location more often if the user has allowed location services, ensuring more accurate GPS data.

Issue: Users were unable to edit the BH field in a Meeting event after it was created.

Resolution: Fixed this issue by ensuring the BH field remains editable for Meetings and To-Dos after they are created.

Issue: The "Before a Visit Happens" automation trigger did not trigger for events that had been moved on the schedule.

Resolution: We have fixed this issue by adding a new flag to the automation history table, ensuring the automation trigger still works when event dates are adjusted.

Issue: Item/service descriptions were not being added to visits that were scheduled using Quick Dispatch, leading to missing details.

Resolution: Updated Quick Dispatch to automatically pull item/service data from the original source, ensuring all descriptions are correctly filled in.

Issue: Assessments scheduled from a work request were not appearing on the dispatch board, making it difficult to dispatch scheduled assessments.

Resolution: Fixed this issue by ensuring that scheduled assessments are correctly included when displaying events for the dispatch board, allowing for more accurate and holistic dispatching.

Issue: The text merge tags "Employee First Name" and "Employee First Name" were not displaying the correct employee names in texts, causing missing or incomplete information.

Resolution: Fixed this issue so that these merge tags now correctly populate with the relevant employee’s first and last name in automated text messages.

Issue: Sequence Automations were being incorrectly triggered for review even when the trigger conditions were not met, causing previously rejected Automations to reappear as pending.

Resolution: Updated the logic for handling reviewed automation jobs to ensure a record is kept, preventing them from being re-added incorrectly after rejection.

Issue: Users experienced an endless loading screen when creating a Legacy Automation with the "Run at a Certain Time" trigger and selecting a day in the future.

Resolution: Fixed this issue by ensuring that the request date from the frontend is correctly formatted to match the company's date-time format, preventing errors and allowing automations to be created successfully.

Issue: When converting an accepted estimate to an invoice, the estimate status was not changing to "Invoiced" if any item or service in the estimate had been deleted from the Items/Services list.

Resolution: Fixed this issue by adding warnings when creating an invoice from an estimate if the estimate contains a deleted item or service. A notification will now inform users to update the estimate before proceeding.

Issue: Emails sent from the Dispatch Board were not being delivered to CC recipients, causing missed communications.

Resolution: Fixed this issue by ensuring CC emails are properly handled by the email service when sending email from the dispatch board, so all intended recipients now receive the emails as expected.

Enhancement: Improvements to Budgeted Hours in Quick Dispatch

What’s New?
We’ve improved Quick Dispatch by making it where you set your budgeted hours per line item instead of as a whole on the visit. This allows for budgeted hours to be accurately shown on line items when the visit is created.

How It Works:

• When creating a Quick Dispatch template, or creating a one time Quick Dispatch, you will be able to set the BH amount per line item.
• The budgeted hours per line item will be added up and displayed at the top.
• When the visits are created, the line items on that visit will reflect the entered BH when setting up the Quick Dispatch.

Bug Fixes

Issue: When receiving notifications for different actions in the software, the timestamps were not displaying in the correct timezone.

Resolution: Switched the notification timestamp conversion from to UTC to user timezone instead of CDT to user timezone.

Issue: The "Use Property Location for Tax Rate" setting was not populating correct tax rates in certain circumstances.

Resolution: Included the city name in the lookup call to create a more precise tax rate lookup.

Issue: The merge tag "Use Property Location for Tax Rate" did not pull the correct text when a visit is skipped.

Resolution: Pointed the correct database values to the merge tag to display the skip reason.

Issue: Opening the notification page did not default to showing todays date which forces the user to need to update the filter in order to see the most recent notifications.

Resolution: Updated the default view to show messages from the last 7 days, and enhanced the sorting order to show newest notifications at the top.

Issue: Sometimes visit schedules are not following the recurring dates given.

Resolution: Updated the time zone conversion on the back end to ensure visits are created on the correct time zone of the user.

Issue: Sometimes the Sequence Automation stop trigger would re-trigger the automation.

Resolution: Refactored our stop trigger handling to ensure that any associated jobs are removed from the automation queue immediately, and won't retrigger the automation.

Bug Fix

Issue: Employees with “view-only” permissions for customers and payments were still able to delete customers or payments, even without the proper permissions.

Resolution: Employees with “view-only” permissions for customers or payments can no longer delete them unless they have explicit delete permissions.