Custom Values

How Lead360 helps

Lead360 Custom Values stores reusable sub-account content that templates and supported experiences can reference from one controlled location. Updating a shared value can keep repeated business details consistent, but every downstream use must be understood before changing it.

When to use this area

Use Custom Values for stable reusable text or configuration values such as approved contact details, short disclosures, or destination information.

Before you begin

• Search for an existing value with the same purpose.
• Choose a clear name and non-sensitive content.
• Find templates, pages, automations, and messages that reference the value.

Create a shared value

1. Choose a durable key with one purpose.
2. Enter an approved value such as a support contact, booking link, policy URL, or standard wording.
3. Use the supported token in templates and workflows.
4. Preview the resolved value in a controlled test.

Change it safely

1. Find every email, SMS, campaign, page, and automation that uses the key.
2. Confirm the new value is valid for every use.
3. Avoid storing passwords, access tokens, payment details, or contact-specific information.

When to use a custom field instead

Use a Custom Value for one shared sub-account value. Use a Custom Field when the value differs by contact, opportunity, or another record.

Use Ask360 here

Ask360 can list authorized keys, explain where a value is used, and prepare one reviewed key or value change when supported. It never stores a password or secret, silently changes every dependent message, or edits contact-specific data from this Help flow.

Confirm the result

A completed Custom Values workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Preview representative references before and after the change.
• Check missing-value fallback behavior.
• Confirm the value does not expose credentials, private data, or environment-specific secrets.

Troubleshooting

A template shows the token instead of the value

Check the reference syntax, publication context, sub-account, and whether the value exists and is permitted there.

A shared update changed unrelated content

Restore the prior value if needed, then split uses into purpose-specific custom values.