Concepts

What staff see on a contact's or organization's Relationships tab, what current, past, and future mean there, and why relationships are a Console feature with no equivalent for members on the Portal.

Explains when Rhythm gives a contact roles at an organization without staff choosing them, why the Roles field on the contact form clears when you move a contact to a new organization, and why an integration move keeps the contact's old roles instead.

How Rhythm rechecks whether an organization has the contact roles its type requires, what the resulting compliance status and violations mean, and why changing an organization's type does not recheck it by itself.

How a custom address type or phone number type becomes a field on contact and organization records, how a preferred value is chosen when a contact has several, and where else those values can be used, from query columns to letter and email templates.

How Rhythm uses an organization's web domain to find its record and match it to a new member signing up on the Portal, and where the company details that fill in a new organization come from.

How changing an organization's main address or main phone number automatically copies down to the work address and work phone of contacts who linked those fields to their organization, and how to turn it off for one organization.

Why Rhythm refuses to delete a contact or organization that still has recorded activities, what a merge carries over to the surviving record, and who Rhythm records as having created or last changed an activity or relationship.

How Rhythm decides which region a contact or organization belongs to, from your account's ordered address rules, what happens when no rule matches, and where a record's current region is shown.

How Rhythm decides two contacts might be the same person, what raises or lowers a match, why a pair below a certain strength is never shown, and why an imported contact might not be checked at all.

How Rhythm turns the metrics in an engagement scoring model into a monthly score, a percentile rank, and an engagement category for a contact or organization.

The contact roles, web forms, and settings Rhythm creates automatically the moment a new Rhythm account is set up, and when that automatic setup is skipped.

How the rating shown on an organization's directory listing is kept current as visitors leave rated comments, which comments count toward it, and why a comment brought in by an import does not change it.

How the Portal recognizes a signed-in member as a particular contact by matching your sign-in email, what happens when more than one contact matches, and why signing in with an inactive contact's email does not get you in.

What appears on a contact's or organization's activity timeline, in what order, and where administrators can place it on a record page.