CRM

Everything registered · Published by Legra

Bring customer-facing work together around people and organizations. Keep relationship records connected to relevant activities and business context so the next action has an explanation.

For example, a lead becomes a qualified opportunity after a conversation and assessment. Keep the participants, supporting documents, and recorded changes connected to that relationship.

Other apps contribute their own experiences. A conversation belongs in Messaging; CRM provides the customer context. Shared knowledge does not require duplicating the record into a separate app database.

CRM uses the selected workspace's permissions and applicable contact data. Review the prerequisites shown during activation, including any required apps. A CRM view does not grant access to an otherwise restricted workspace.

Select CRM for a workspace that manages customer relationships. Review the proposed setup before using it with shared knowledge. Workspace activation explains enablement and dependencies; Branching explains reviewing changes.