Salesforce FSC Benefits renewal intake

Benefits Renewal Intake loads carrier renewal and quote workbooks into Salesforce Financial Services Cloud in about a minute. AI proposes how the columns map, and a person approves every load.

Each carrier sends its benefits renewal as a large Excel workbook with many tabs, and no two carriers use the same layout. Account managers can spend days retyping census, rates and quotes before a producer can start marketing the renewal. Changes in the renewal often aren't found until the data has already been keyed in.

Benefits Renewal Intake removes that retyping. The producer attaches the carrier's workbook to the renewal opportunity. Prompt Builder proposes which column maps to which FSC field, and nothing loads until a reviewer clicks Accept. Census data goes into the FSC Group Census objects, and the offer by line appears on the deal. The producer gets an alert on what changed, for example "medical +11.8%".

The AI never retypes data. It only proposes the mapping, and Apex applies that mapping to every row against an approved list of fields. Once a reviewer approves a carrier's layout, the next workbook from that carrier maps without calling the model. Census, carrier quotes, review and alerts all stay in Financial Services Cloud.

Apex can't read Excel natively, and large carrier workbooks go past its memory and file-size limits. A small parser handles that step. It runs on Azure today, can be hosted in the brokerage's own Azure or AWS, and never runs macros. Producers who work in Microsoft Teams can drop a workbook into Copilot, ask "what changed?", and get the answer there.

With renewals, quotes and census data structured in FSC, a brokerage can build on the same data for quote comparison, renewal negotiation support, contribution modeling and finding new opportunities across its book.