This is a tenant-wide technical configuration screen. It stores a display label, external CRM location ID, and the name of a server-side secret; it must never contain the raw token. Save CRM sync currently enables the supported calls, SMS, chats, and emails sync flags together—there are no individual sync toggles on this page. Each CentriPOS business needs its own correct location mapping and credential reference; never reuse another customer’s fixed-location connection.

Before you beginUse an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.

Step by step

  1. Confirm the active CentriPOS business and the exact CRM/HighLevel sub-account that belongs to it. Obtain the external Location ID from an approved administrator and independently verify the business name/address or account ownership. A syntactically valid location ID can still point customer data to the wrong account.
  2. Have an authorized platform administrator create a uniquely named server secret containing this business’s approved LeadConnector private-integration token with the required scopes. The raw token belongs in the secure server secret store, never in CentriPOS fields, screenshots, chat, email, tickets, or documentation.
  3. Go to Admin → Integrations → CRM Connect. Before editing, read the status badge and summary cards: Contact location, Credential, and Secret present. Not connected, Configured/another status, Connected, Missing, or Not checked describe configuration evidence—not proof that customer records are synchronizing correctly.
  4. Enter a clear Display name, usually CRM Connect or a business-specific administrative label. This label identifies the connection in CentriPOS; it does not rename the external CRM location.
  5. Enter the exact CRM Connect location ID for this CentriPOS tenant. Do not use the current POS location/register ID: this field expects the external CRM sub-account/location identifier. Remove copied spaces and verify every character.
  6. Enter only the Token environment variable name created for this tenant, such as a uniquely named CENTRICRM_…_TOKEN reference. Do not paste the token value. Treat even the environment-variable name as internal configuration and omit it from public screenshots.
  7. Choose Save CRM sync once and wait. CentriPOS upserts the tenant connection with the display name, trimmed external location ID, secret-name reference, and calls/SMS/chats/emails sync flags enabled. Success shows CRM Connect integration saved and refreshes the status summary.
  8. Re-read Contact location, Credential, Secret present, and the status badge after save. Secret present must be Yes before expecting authentication to work. If it says Missing, correct the server secret deployment/reference rather than pasting a token into the field.
  9. Choose Test connection only after a connection record exists; the control is disabled otherwise. Wait for CRM Connect connection verified. This tests server authentication against the saved mapping, then refreshes status. It does not prove that every contact field, receipt, note, message, owner, tag, or custom field maps correctly.
  10. Run a controlled, privacy-safe data test in a designated demo/test customer such as the approved Harbor & Hearth demo—not a real customer. Create or update one distinctive non-sensitive field and verify it lands in the intended external CRM location without creating a duplicate. Record which system is authoritative for each tested field.
  11. Test the customer timeline separately. Add a controlled note or refresh CRM Connect activity where supported and verify direction, timestamp, author/owner, body, external identity, and deduplication. CentriPOS can warn Note saved, but CRM Connect sync needs review: that means the local note succeeded while external sync needs reconciliation, not that the whole save failed.
  12. Test communication sender behavior only when assigned CRM Connect lines exist. In the customer communication card, confirm the sender provider label and number before SMS. CRM Connect sender availability is user-assignment dependent; it does not make the Dialpad-only Call button available.
  13. Verify broader supported outcomes deliberately: contact identity/type, phone/email/address, customer-since, assigned owner, tags/custom-field mapping, receipts, notes, interactions, CRM activity, Dialpad calls/SMS, and smart-list/contact-search behavior. The page describes future email conversations, so do not represent future/placeholder coverage as proven production sync.
  14. If data reaches the wrong CRM location, stop synchronization immediately and escalate as a cross-tenant incident. Preserve the CentriPOS tenant, external location ID, connection label/status, affected demo/contact identifiers, operation/time, and direction. Never include raw tokens. Correct the mapping and assess already-sent records before resuming.
  15. If Test connection fails, check the saved location ID, exact environment-variable reference, Secret present state, token scopes/expiration/revocation, server deployment, and external service status. Do not swap in another tenant’s token as a shortcut.

Screen and contract reference

Control or areaWhat it means
Status badgeChecking, Connected, Not connected, Configured/another stored status; connection state is not field-level sync proof.
Contact locationSaved external LeadConnector/HighLevel Location ID, not the CentriPOS store/location selector.
CredentialName of the server environment secret referenced by the connection; it is not the raw token and should remain internal.
Secret presentServer-reported Yes/Missing/Not checked signal for whether the referenced secret exists. It does not reveal or validate the token by itself.
Display nameFriendly administrative label stored for this tenant connection.
CRM Connect location IDRequired external CRM sub-account/location destination for this CentriPOS business.
Token environment variableRequired server-secret name. Raw secret values never belong in this field.
Save CRM syncUpserts the connection and currently submits calls, SMS, chats, and emails sync flags as true together.
CRM Connect integration savedConfiguration write succeeded and status is refetched; follow with Test connection and controlled data verification.
Test connectionAvailable only after a saved connection exists; tests authentication/mapping against the server service.
CRM Connect connection verifiedConnection test succeeded; it is not proof of every object/field/timeline workflow.
Contacts cardDescribes identity, type, customer since, owner, tags, and custom-field mapping intent.
Timeline cardDescribes receipts, notes, interactions, Dialpad calls/SMS, and CRM activity in one customer journey.
Smart lists cardDescribes CRM-style contact filters and LeadConnector contact-search synchronization.
Partial-success note warningA local note saved while CRM Connect sync failed or needs review; reconcile rather than duplicating the note.
Assigned CRM Connect senderUser-available line for supported SMS; sender assignment and provider must be confirmed in the customer profile.
No exact screenshotThe approved Amelia Grant Harbor & Hearth manifest contains a safe Integrations overview but no exact CRM Connect configuration page. This guide intentionally does not expose or invent a location ID or secret reference.

Expected result

The intended CentriPOS contact and activity fields map to the authorized CentriCRM location, and one controlled record syncs once in the configured direction.

Troubleshooting

  • Confirm you are changing the intended business and location before saving.
  • Record the previous setting when a change affects live selling, payments, tax, or integrations.
  • Use a controlled test record after saving before rolling the setting out broadly.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.