Manage contact lists, segments, and profiles
Find and maintain customer profiles while using lists and segments for clear operational follow-up Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Find and maintain customer profiles while using lists and segments for clear operational follow-up This guide keeps the work focused on Contacts and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
Contacts brings customer identity and conversation context together. Appointments add schedulable work with availability, timezone, duration, and location settings. Accurate records and clear ownership help a team follow up consistently, while booking rules prevent customers from seeing times that the business cannot honor.
Before you begin
Access: Contacts read access is required. Editing records, lists, or segments requires Contacts write access.
- Define the customer or operational group you need.
- Know which identifiers are approved for matching contacts.
- Follow company rules for personal data handling.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Open Contacts and search by a reliable identifier before creating, editing, or associating a profile.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Review conversation context, attributes, list membership, and any duplicate-looking records without assuming similar names are the same person.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
Create or update a list for explicit membership, or a segment for repeatable criteria when those options are available in the workspace.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Open representative profiles from the resulting group and verify that operators can understand why each contact belongs there.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in Contacts separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The intended contacts are findable by approved identifiers.
- Profile fields and conversation context belong to the correct person.
- List or segment membership matches its documented rule.
- No personal data was copied into unrelated notes or Knowledge.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
A customer appears in more than one profile
Compare stable identifiers and conversation history before changing anything. Follow the available merge or administrative process rather than deleting a record based on name alone.
A segment excludes an expected contact
Inspect the contact's current field values and every segment criterion. Remember that live segments can change as profile data changes.