Smarty address verification is now available for New Business
BriteCore is excited to announce that Smarty address verification is now available in BriteQuote V1, V2 and Policy Builder screens, which enhances the address suggestion and verification process for improved user experience and data accuracy. The Smarty feature is triggered upon completion or modification of Address Line 1 and Zip Code fields. A popup will prompt users with a list of suggested Address Line 1, City, State, and Zip Code options. If the address isn’t presented, users have the flexibility to select the "None of Them Applies" button, allowing the ability to edit and save a custom address as needed.
API users can now request address suggestions through the /api/v2/contacts/retrieve_address_suggestions endpoint. In cases where the integration service provides County names, the UUID-based Business Location definition will be returned if a match is found, enhancing the accuracy of location-based ratings.
With the Smarty integration, BriteCore users can benefit from a streamlined and efficient address suggestion and verification process, reducing data entry errors and ensuring accurate address information for new policies. Visit the help site or research out to your customer representative for further details (BC-10480).
eSignature via DocuSign is now available in BriteQuote V2
BriteCore is excited to announce the availability of DocuSign eSignature in BriteQuote V2, offering seamless electronic signing of new business documents for agents and policyholders. This feature eliminates the need for traditional wet signatures and provides greater flexibility in policy completion, even in remote settings.
- Seamless Integration: Connects policyholders and agents to DocuSign for quick document signing.
- Efficient Policy Creation: Agents can easily initiate the e-signature process when writing new business.
- Email Notifications: Policyholders receive email prompts to electronically sign documents to ensure swift document handling.
- Signature Flexibility: Agents can choose between wet signatures and e-signatures for policy-related forms.
- Request Management: Agents can switch between signature types or void e-signature requests as needed.
- Pre-populated Information: Agents can select e-signature with pre-filled email addresses and names based on information added during quoting.
- Policy Update Restrictions: Agents cannot update quotes until e-signatures are completed, ensuring data integrity.
The DocuSign eSignature integration streamlines policy completion, enhances user experience, and provides valuable metrics and analytics. For implementation details and technical documentation, refer to the help site. (BC-6714, BC-6722, BC-11738)
Underwriter Name Missing on Custom Documents
An issue has been identified and resolved regarding Custom Deliverables (ex. Quote Summary and Policy Application). The problem is related to the absence of the Underwriter Name in certain copies of these deliverables. Specifically, the Underwriter Name was missing on the Quote Summary when viewed by the Agency, and it is not present on any copies of the Policy Application. BriteCore has corrected this issue moving forward; previously generated documents will not be automatically updated. (TS-1060)
Unable to copy a Line Effective Date (LED) to a future LED
This release resolves an issue related to copying a Line Effective Date (LED) to a future LED. Previously, the system failed to copy the LED to a future LED when users closed the page without saving or canceling changes. As a result, the new item's record remained in the database but was unusable. To address this, BriteCore has implemented a fix that ensures LED copying functions correctly, thereby maintaining data integrity and accuracy (BC-11261).
Error with Policies loaded by Data Conversion
This release addresses a defect in the data conversion process, ensuring a smoother user experience. The builder tab now loads successfully with the Rate and Save button when loading a policy imported through a data conversion for the first time. BriteCore has also addressed errors occurring in the front-end due to poor data entries during the data conversion process. A small template change has been implemented to handle null values more effectively, reducing potential errors (BC-11487).
PDFs not available when uploading to Ivans eDocs Service
During the usage of the Ivans API for generating downloads, an error was encountered. Certain files did not have the expected URL format but instead had partial paths. Due to this discrepancy, BriteCore was unable to identify alternative file paths, leading to issues with accessing and processing these files as intended. In response to this challenge, BriteCore has made improvements to the utility, enabling it to handle alternative paths for PDF documents if the URL does not match the expected format. With these enhancements, BriteCore aims to provide a more reliable and seamless experience when working with files through the Ivans API.
Policy Fee Deletion on Policy Type Change
A defect was discovered wherein the policy fee line item associated with a policy type was not removed from the database when a new policy type was selected. To address this issue, BriteCore has updated the method responsible for deleting all associated line items. As a result, when a policy type is changed, all relevant line items associated with that policy will now be correctly removed from the backend, ensuring accurate data management and preventing any residual line items from affecting the new policy type selection (BC-10141).
Property CLUE Ordering: Streamlined Integration and Error Handling
The Property CLUE vendor offers two integrations: Property CLUE ordering and Property CLUE contribution. BriteCore has now ensured that the (1) request for CLUE ordering does not require validation against the settings for (2) contribution, preventing the display of an error on the UI. The Property CLUE ordering now functions seamlessly with only the relevant settings configured (BC-10022).
Correct Agent/Agency Display on A/R Page
A defect occurred recently, resulting in agencies being notified of policies that were not associated with them. As both agencies were categorized as such, there was no need to retrieve any "Agency behind an Agent" information. This indicated a policy-to-go=agency relationship, and on the A/R (Accounts Receivable) page, only the correct Agency assigned to a specific policy should be displayed. To address this issue, BriteCore has refined the data retrieval process to consider only the agency when the policy-to-go setting is equal to agency. This modification ensures that the correct agency information is displayed on the A/R page and notifications are sent to the correct agency (BC-10019).
Property CLUE validation
During the Property CLUE validation process, BriteCore learned from LexisNexis that there was an issue with extended legal description addresses (Acre, Quarter, Section, Township, Range). BriteCore implemented a change to improve the parsing of addresses (BC-11729).
The “Invoices Coming Due, Premiums Receivable Aging, and Premium Written Earned Unearned” reports were released a few months ago and the word “New” was added to the title of those reports. To better clarify the status of reports, in this release, BriteCore removed the word “New” from those report titles. Instead, the correct naming method was implemented where BriteCore added the word, “Old” to the older prior version of the report. This same naming approach will be used for all older reports that are rewritten by BriteCore to use the new and improved report approach (BC-110980).