Conditional Logic on Custom Fields

Conditional logic lets you set rules that automatically reshape custom fields on an opportunity — hiding fields until they're relevant, and auto-filling default values when conditions match. You describe the rule once, and TrustPager applies it every time an opportunity is created or updated, in-app or via any back-end process.

When you'd use this

• Mortgage broker — settlement date by application type. When Application Type is "Refinance", set Settlement Date to today + 1 month. When Application Type is "Purchase" and Purchase Date is filled in, set Settlement Date to Purchase Date + 6 weeks. Brokers stop calculating dates by hand.
• Mortgage broker — hide irrelevant fields. Show Purchase Date only when Application Type is "Purchase". For Refinance opportunities, the field stays out of the way.
• Fitness studio — follow-up timing by class type. When Class Type is "PT Session", set First Follow-Up Date to today + 3 days. When it's "Group Class", set it to today + 7 days.
• Agency — kickoff date by project type. When Project Type is "Brand Identity", set Kickoff Date to today + 14 days. When it's "Website Build", set it to today + 21 days.
• Any team — protect weekend dates. If a calculated date falls on a Saturday or Sunday, the rule can shift it to the following Monday automatically.

The two kinds of rules

1. Visibility rules — show or hide a field based on another field's value

A visibility rule controls whether a custom field appears on the opportunity detail view at all. The rule reads another field's value and decides whether to display the target field.

Example: "Show Purchase Date only when Application Type is set to Purchase." On a Refinance opportunity, Purchase Date never appears — the broker isn't distracted by it. The moment they switch Application Type to Purchase, the field appears for them to fill in.

Visibility rules support the same operators as default-value rules — is, is not, is set, is empty — and combine multiple conditions with AND.

2. Default-value rules — auto-fill a field's value when conditions match

A default-value rule writes a value into a target field whenever its conditions match. Three actions are supported:

• Today plus N — fills the field with today's date plus a number of days, weeks, or months. Example: today + 1 month for a refinance settlement.
• Another field plus N — fills the field relative to a different date field on the same opportunity. Example: Purchase Date + 6 weeks for a settlement date.
• A fixed value — fills the field with a specific constant.

You can list several rules on the same field. They're evaluated in order — the first matching rule wins, the rest are skipped. This lets you cover several scenarios on one field (one rule for Refinance, another for Purchase, etc).

Weekend skipping for date rules

For date defaults, you can request that calculated dates never land on a Saturday or Sunday. When weekend skipping is on and the result falls on a weekend, TrustPager shifts it to the following Monday automatically.

Where rules run

• The opportunity detail view — when your team edits an opportunity at https://app.trustpager.com/dashboard/deals, rules fire when the user saves a triggering field. Visibility rules show or hide fields immediately. Default-value rules fill the target field in the same save round-trip — no extra action needed.
• Any back-end path — TrustPager API calls, MCP tool calls, automations, and internal forms that create or update opportunities all run the same logic. You get consistent values regardless of how the opportunity was created.

Rules apply when an opportunity is created or saved. Existing opportunities fill in the next time any field on them is edited — they're not retroactively backfilled. Send a service request at https://app.trustpager.com/settings/service-requests if you want a one-shot backfill across an existing pipeline.

Conditional logic does not run on public client-facing forms (intake or contact forms sent to your customers). Those use a separate field system, and conditional logic for them is a separate feature on the roadmap.

Manual edits are protected

This is the most important thing to understand: once a team member types a value directly into a rule-managed field, the rule will never overwrite it again.

The rule fires when a field is empty or still at its rule-calculated default. The moment someone manually changes it, TrustPager treats that value as intentional and leaves it alone — even when the trigger field changes later. Your team can always override the default, and the system will respect that override permanently.

If a manual override needs to go back to being rule-managed, clearing the field's value and re-saving lets the rule re-fire on the next trigger change.

How to set this up

1. Open https://app.trustpager.com/settings/crm and scroll to the Custom Fields section.
2. Click the pencil (edit) icon on the field you want to add logic to.
3. Click the Conditional logic button — it sits next to the Hidden and Fill with AI checkboxes in the field editor.
4. Configure your visibility rule (Always show / Only show when…) and add any default-value rules you need.
5. Click Save Changes on the field row to persist the rules.

Rules take effect immediately for new and updated opportunities. Existing opportunities fill on their next field edit.

What's not supported yet

• Public client-facing forms — conditional logic doesn't run on intake or contact forms sent to your customers.
• OR conditions — conditions within a single rule are AND only. If you need "A or B", create two separate rules with the same action.
• Complex date arithmetic — calculations like "business days only" (other than weekend skipping) or "add 2 weeks then subtract 3 days" aren't supported in v1.
• Custom fields on contacts and companies — v1 supports rules on opportunity custom fields. Contact and company custom fields will follow.