Manage contact, company and lead lifecycle profiles
Find existing CRM records and maintain Hub lifecycle, score and health without creating a second customer database.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Where to start
Hub → CRM → Contacts / Companies / Leads → record
PermissionNative record access; Manage lifecycle and segments to update Hub profile values
Before you begin
Decide whether you are working with a person, company or lead. A similarly named record of another type is not automatically the same identity.
Follow these steps
- Choose Contacts, Companies or Leads, search the existing records and open the intended result.
- Read the authoritative name, company and contact details before making a change. Use the native record link for changes owned by the CRM.
- In the Hub profile controls, choose the lifecycle stage and review score and health.
- Save the Hub profile. If a conflict is reported, reload the current record and repeat only the intended change.
- Review the record’s Hub activities, permission status and history, or open Client workspace for permitted information from connected native features.
Fields and options
- Lifecycle
- Subscriber, Lead, Marketing qualified, Sales qualified, Opportunity, Customer, Evangelist or Other.
- Score
- A manually maintained Hub score between −1,000 and 1,000. It is not automatically a probability of purchase.
- Health
- A supplemental value from 0 to 100. New Hub profiles begin with lifecycle Lead, score 0 and health 50.
Rules and limits
- Search shows 40 authorised native records per page. Native customer and lead access is checked again when opening a result.
- Hub profile changes do not convert a lead, create a customer or overwrite the original CRM identity.
- Marketing permission is recorded against a contact or lead’s current email address; a company profile is not itself an email recipient.
Check the result
- Reload the record and confirm the lifecycle, score and health are saved.
- Check the native record identity is unchanged and the profile update appears in history.
If something does not look right
- If a record is absent, check its type, current search and native permissions.
- An email address changed in the CRM needs fresh verification of permission for that address; an earlier consent record is not silently transferred.
Common questions
Does setting lifecycle to Customer convert a lead?
No. It updates the Hub’s supplemental lifecycle value; native lead conversion remains a separate CRM operation.
Why are contact and company results different?
The Hub keeps their native identities and access rules separate.