Skip to main content

Contacts and Data in Whippy

Understand how Contacts, lists, segments, objects, and related settings fit together in Whippy.

Written by Maria Cairns

Why it matters

Contacts is now the main place to manage people and contact-linked data in Whippy. A clear mental model helps teams decide whether to use a contact field, tag, static list, segment, object, or setting for the job in front of them.

Key Concepts

Contacts: The primary sidebar area for people who can receive messages. Contacts contain standard fields, tags, list membership, communication preferences, and links to related data.

All contacts: The main table for viewing, searching, filtering, adding, importing, exporting, editing, and bulk updating contacts.

Static lists: Fixed groups of contacts that change when a user imports, adds, or removes contacts.

Segments: Dynamic contact audiences built from saved filters. Contacts enter or leave automatically as their data changes.

Objects: Structured records linked to contacts, such as orders, appointments, candidates, jobs, or other integration data.

Related settings: Settings for Objects, Tags, Messaging, Channel mappings, and Roles affect how contact data is structured, labelled, messaged, and permissioned.

Step-by-Step: Navigate the Contacts and Data area

  1. Open Contacts from the main sidebar.

  2. Select All contacts to work with contact records.

  3. Select Objects to view object types and the records linked to them.

  4. Open Lists, then choose Segments for dynamic audiences or Static lists for fixed audiences.

  5. Open Settings > Objects to manage object definitions and properties.

  6. Open Settings > Tags to create or manage contact tags.

  7. Open Settings > Messaging to review organization opt-out behavior.

Tips and Best Practices

  • Use Contacts as the starting point for people, messaging eligibility, and contact-level updates.

  • Use static lists for fixed audiences such as imported event lists or one-time campaign groups.

  • Use segments when an audience should update automatically from contact or object data.

  • Use objects when operational data needs to support filtering, personalization, routing, or automation.

  • Use Settings when the structure or permission model needs to change, not when you only need to view records.

Troubleshooting

Issue

Possible Cause

Fix

A contact is missing from an audience

The contact is not on the static list or does not match the segment filters

Check the contact fields, tags, list membership, and saved segment filters

Object data is not available on a contact

The object is not configured, synced, or associated with the contact

Review Data > Objects and Settings > Objects, then confirm the association or integration source

A user can view Contacts but cannot edit them

Their role does not include the required Contacts permissions

Review the user's role in Settings > Users > Roles

Did this answer your question?