Why it matters
Variables make messages and workflows personal at scale. When variables are tied to the right contact fields and object associations, Whippy can insert accurate data without manual copying.
Key Concepts
Variable: A placeholder that resolves to stored data when a message, template, agent instruction, or automation runs.
Contact variable: A variable that pulls from standard contact data such as name, phone, email, language, external ID, or another contact field.
Object variable: A variable that pulls from a structured object record associated with the contact.
Association: The relationship that tells Whippy which object record belongs with which contact or related record.
Fallback review: The process of checking what happens when the expected field or object value is blank.
Step-by-Step: Use contact and object variables safely
Identify the data you want to insert.
Confirm whether the value lives on the contact record or on a related object record.
Check that the field or property is populated for the contacts who will receive the message.
Confirm the object association if the variable comes from object data.
Insert the variable in the template, message, agent instruction, or automation step.
Preview or test the output with a contact that has complete data.
Review fallback behavior for contacts that may be missing the value.
Tips and Best Practices
Use contact variables for stable person-level details.
Use object variables when the value depends on a related record such as an appointment, job, order, or application.
Keep field names clear so users can choose the correct variable.
Test with more than one contact when object associations or repeated records are involved.
Troubleshooting
Issue | Possible Cause | Fix |
A variable appears blank | The contact field or object property is empty | Open the contact or object record and confirm the value is populated |
The wrong object value appears | The association, filter, or selected related record is not the one intended | Review the object association in Settings > Objects and test with a known contact |
Users cannot find the expected variable | The field or property is not configured or visible in the relevant variable picker | Confirm the field exists in the contact or object setup and that the user has access |