View profile

Herald changelog - Applicant- and Agent-Facing Text

Herald changelog - Applicant- and Agent-Facing Text
By The Herald team • Issue #32 • View online
Herald builds digital infrastructure for commercial insurance. Originally published here.

Tailoring question text to your audience
An applicant, or an agent representative, must answer questions about their level of risk and the coverage items they seek in order to get an insurance quote. This week we launched support for alternative versions of the same question text: one oriented towards the applicant and one oriented towards their agent. We now provide applicant- and agent-facing text for every risk and coverage parameter in Herald.
With this feature, our customers can customize which type of question text their user sees based on the experience they’re trying to build. Prior to this release Herald only offered one version of the text for each question that was provided by the relevant carriers. This text was inconsistent across the multiple carriers integrated with Herald. Sometimes this text was written for the applicant, other times for the agent.
These text options appear in the /applications responses, located within the parameter_text object for each risk and coverage parameter. We have also documented the details around applicant- and agent-facing text in the Appendix for every parameter in Herald.
Fixes and Improvements
  • We fixed a bug that was returning quotes without a portal_link for certain Cyber products.
  • We enhanced Cyber products to accept more values for Aggregate Limits.
  • We improved the error messaging around certain malformed requests to our /quotes endpoint.
  • We fixed a bug that was throwing an erroneous 400 error when Content-Type was not set to “application/json.”
Did you enjoy this issue?
The Herald team

Herald changelog and updates

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue