Quote Insurance Products

Learning Objectives

After completing this unit, you’ll be able to:

• Explain why quoting is foundational to policy administration.
  
• Describe how Digital Insurance executes quoting through shared services.
  
• Use the Insurance Quote Configurator and explain how it reflects product modeling and pricing setup.
  
• Describe how quote data is structured to support issuance and downstream policy changes.
  

Ground Policy Administration in the Quote

Quoting is the stage when an insurer evaluates a customer request and produces a priced offer under defined product and underwriting logic.

A well-formed quote is more than a snapshot of premium. It captures what the customer asked for, what was selected, what was configured, and what rules and calculations produced the result.

This information matters because policy administration depends on continuity. Issuance, endorsements, renewals, and cancellations all rely on the same underlying product structure, eligibility outcomes, and rating results. When the quote stores those inputs and outputs in a structured way, downstream work can reuse them directly. When the quote is incomplete or inconsistent, teams reinterpret decisions that were already made, which adds rework, breaks alignment between quoting and policy administration, and increases risk.

Digital Insurance treats quoting and policy administration as connected stages in one governed lifecycle. Shared services evaluate eligibility, calculate premiums, and return traceable results each time a quote is created or updated. Those results can then be carried forward into the insurance policy so the policy remains aligned with the logic that produced it.

In this unit, you learn how a structured quote captures product selections, rule outcomes, and rating results in a way that supports downstream policy issuance and servicing.

Power Quoting with Shared Services

Insurance Quoting APIs and invocable actions sit at the center of the quoting solution. These services apply product structure, underwriting rules, pricing logic, and surcharges to customer inputs, then return structured results that later processes can use directly.

A single quoting request can validate product eligibility, execute qualification and configuration rules, and run pricing procedures. The request can also apply clauses, exclusions, taxes, and surcharges.

Here’s the service pattern behind a typical quote-to-issue flow.

Each step builds on the output of the one before it. Context flows forward so nothing is recalculated from scratch or reinterpreted between steps.

This logic runs through services, so it stays independent of any particular interface. The same sequence powers internal desktop workflows, guided portal experiences for brokers or policyholders, automated pipelines, and direct API integrations. Admins compose guided quoting journeys from these building blocks using Salesforce Flows and Omniscripts without reimplementing business logic in each channel.

For the full set of quoting APIs and additional details, read Insurance Quoting APIs and Invocable Actions in Salesforce Help.

A prebuilt experience, the Insurance Quote Configurator, brings this execution model together for internal users. Here's how it works in practice.

Explore Quote Creation

The Insurance Quote Configurator is a guided internal experience that orchestrates calls to quoting services while enforcing the product structure, rules, and pricing logic defined during Product Administration. It walks users through building a structured, policy-ready quote that issuance and servicing can use without reinterpretation.

To see the configurator in action, follow a personal auto quote at Cumulus Insurance.

Establish Quote Context

Riley Zhang, a captive agent at Cumulus Insurance, starts a new quote from a returning customer’s opportunity record. Riley captures the customer, policy type, effective dates, and sales opportunity. After it’s saved, this quote record becomes the container for every product selection, pricing outcome, and decision that follows.

The record also tracks progression through defined stages, such as Draft, Submitted, and Approved. These stages reflect Cumulus’s quoting workflow and govern when approvals, checks, and transitions occur.

Every product selection and pricing decision later on evaluates against this context.

Select Eligible Products

Riley opens the product catalog and navigates to the Auto Insurance category.

The catalog includes the products created during product administration. Qualification rules and quote context dynamically filter the display so only eligible products appear. Riley chooses Auto Gold because the customer meets that product’s qualification criteria.

A single quote can include one or more root products. In multi-root scenarios, for example auto and home sold together, each root product is configured independently while pricing rolls up at the quote level.

When Riley adds Auto Gold, the system creates a root-level Quote Line Item representing the base policy bundle.

Behind the scenes, this triggers the same product rating and context generation you learned about in the service pattern.

Configure the Product Hierarchy

Insurance products are typically modeled as hierarchies: A root product contains component groups, child products, insured items, and configurable attributes. The configurator mirrors that hierarchy directly, guiding agents through configuration one level at a time.

For Auto Gold, Riley notices policy-level coverages alongside vehicle-level components. She can add multiple vehicles, each with its own coverages and assigned driver.

Two types of attributes shape the configuration. Standard attributes capture modeled selections such deductibles, limits, and coverage options using the inputs defined during product modeling. Extended attributes pull values from related records such as the customer's Contact or Account automatically populating fields such as age or address to reduce manual entry.

Apply Rules and Pricing in Real Time

As Riley updates inputs, the system evaluates rules and pricing.

Configuration rules govern assembly, such as which coverages are required or excluded, which options are available, and how components relate within the hierarchy. Clauses and exclusions can conditionally override coverage behavior or attach policy-specific terms—reflecting underwriting exceptions without altering the product model itself.

When Riley changes a value, the configurator calls the same pricing services available through the API. Premium totals update on screen. Riley notices the financial impact of each choice as she makes it, and every recalculation is consistent with what a direct API call returns.

Review the Complete Structure

Before presenting the quote, Riley reviews the Quote Line Items view. It displays the full hierarchy: root product, nested coverages, insured vehicles, and assigned drivers.

This visibility makes the quote explainable to the customer and verifiable for the broker.

Trace the Quote’s Record Structure

Every choice Riley made in the configurator persists as a discrete record. Together, those records form a hierarchy that mirrors the product model, preserving what was selected, how it was configured, and how it was priced.

Here’s a breakdown of the key objects.

This architecture is what makes the transition to policy administration clean. An accepted quote becomes a policy without rework. An endorsed policy references the original configuration without guessing at intent. A renewal reevaluates pricing against the same structured baseline. The quote's record hierarchy travels intact through every lifecycle stage.

What’s Next

In this unit, you learned how structured quoting translates product configuration into a governed, decision-complete offer. Product logic, underwriting rules, and rating services execute through shared services, producing a quote that preserves coverage structure, eligibility outcomes, and pricing drivers in explicit records.

That structure is retained, so the policy issuance team doesn’t need to reinterpret or rebuild the offer.

In the next unit, you explore how an accepted quote becomes an in-force policy, and how that structured baseline supports endorsements, renewals, cancellations, and reinstatements across the full lifecycle.

Resources

• Salesforce Help: Insurance Quoting