Benefits

A benefits field renders the positive outcomes of the recommended advice as a rich content block. It is one of the five rich content types and is generated by a Stage 5 LLM step that mirrors the structure of things to consider, but framed around the upside of each recommendation.

How to write the placeholder

Use a regular {{ field_name }}. As with all rich content types, the classifier reads the field description — the name is just a label.

Benefits placeholders

{{ benefits }}
{{ portfolio_benefits }}
{{ benefits_of_advice }}

What the classifier looks for

Descriptions like “Outline the benefits of the advice,” “Describe how the client will benefit,” or “Positive outcomes of the recommended approach” reliably classify a field as benefits.

What renders at fill time

The placeholder is replaced with a structured list of blocks (typically a bulleted list, but headings and paragraphs can also appear when the example document uses them). The Stage 5 LLM:

Reads each recommendation on the template.
Generates per-recommendation benefits framed in plain English.
Adapts the bullets to the client’s data (e.g. amounts, time frames, member numbers).
Styles the output to match the linked example document.

Configuration after upload

Open the template-level generation settings (gear icon next to the template name) and point the benefits example document slot at a Setting whose “Benefits of Our Advice” section matches the tone you want. There is no per-field modal — all benefits fields on the template share the same example.

Common pitfalls

Don't write a single-line description

A field named benefits with no description (or a one-word description like “benefits”) is too thin for the classifier. Spell out what benefits should be described and how.

Benefits depend on recommendations

Benefits are derived from the template’s recommendations. If no recommendation fields exist, or none have been generated, the benefits placeholder renders empty.

Manual override is supported

Use the field configuration UI to set the type explicitly when the classifier hesitates between benefits and content.

Syntax to copy

Generic benefits

{{ benefits }}

Topic-specific benefits

{{ portfolio_benefits }}
{{ insurance_benefits }}
{{ super_benefits }}

As part of a loop

{% for rec in recommendations %}
{{ rec.benefits }}
{% endfor %}