Topics:
Billing Sync Update: Contact ID
We’re excited to introduce a new enhancement for our billing sync feature: an optional Contact ID field is now available in the contact details section! This field provides a more reliable way to match and manage contact records when syncing updates from your internal system via CSV—helping ensure cleaner, more accurate data integration.
For Customers Using Billing Sync
You’ll now see the new Contact ID field displayed in the UI, but it will be view-only to prevent any unintentional changes. This ensures your current sync process remains unchanged.
No need to take action just yet—your current setup will continue to work smoothly, and we’ll be sharing more soon about how this new field can enhance your workflow and how to plan for a potential transition, if needed.
For Customers Not Using Billing Sync
You’ll be able to view and edit the Contact ID directly in the UI. While this field is especially useful for syncing contact info with a CIS via billing sync, it can also serve as a helpful reference for storing external system IDs.
Interested in learning how billing sync can streamline your processes? Reach out to to our support team —we’d love to help!
Test Kit Calibration Update: No Longer Needs an Approved User
Test Kit Calibration just got easier!
We’ve made a small but helpful update to streamline test kit calibration. Now, when selecting a reporter during calibration, the dropdown will include all users associated with the service provider—even those who are still pending approval.
No more waiting for user approval just to log a calibration—this change helps you move faster and keep things running smoothly.
"Send Back Report" is Back - With Improved Clarity
A few weeks ago, we updated the button names and behavior for test reports in Submitted status. While the intention was to simplify the workflow, we heard from several customers that the changes caused some confusion and made it harder to track report status.
Thanks to your feedback, we’ve made an adjustment:
The button has been renamed back to “Send Back Report” (instead of “Reset to In Progress”), and we’ve updated the behavior to match.
Now, when a report is sent back, its result will remain visible in the table—so you can clearly tell it’s in progress because it was returned, not because it hasn’t been submitted yet.
Thanks for helping us make things better!
Here's a screenshot of how the record will look when wanting to "Send Back Report".
In the new screenshot below, you’ll notice two test reports with a status of In Progress:
The top report was reset from Accepted status using the old "Reset to In Progress" option, so the test result shows as “?”.
The bottom report was sent back using the updated “Send Back Report” option from Submitted status, and you’ll see the original test result is still visible.
This change makes it easier to understand why a report is in progress—whether it’s newly started or has been returned for updates.
