Using Cleats
Knowledge Base
Guides to connect your CRM and understand how Cleats keeps your team's follow-up standards visible and actionable.
Cleats Docs
The accountability layer for your CRM. Learn how to connect your sales data and turn your team's follow-up standards into consistent action.
Connect. Set the standard. Follow through.
Using Cleats
Guides to connect your CRM and understand how Cleats keeps your team's follow-up standards visible and actionable.
Connect the tools your team uses to Cleats. Close CRM is the supported CRM integration.
Connect Close to Cleats to see which leads and opportunities are worked to your team's standard—and take action when they need attention.
You need a Cleats account with access to your organization. An organization owner or manager can manage the integration. Use a Close account authorized to approve the requested access for the correct Close organization.
The first import runs in the background. Completion time depends on your Close organization's size and activity history. A successful authorization confirms the connection; it does not mean the data import has finished.
Close remains the place where your sales team works its CRM records. Cleats keeps an organization-scoped copy of supported data to evaluate accountability rules and calculate KPIs.
| Close data | How Cleats uses it |
|---|---|
| Leads, contacts, and opportunities | Account and deal context, record relationships, pipeline stages, and statuses. |
| Activities | Supported calls, emails, SMS, notes, and meetings used to evaluate follow-up. |
| Lead tasks | Follow-up task state. Close system reminders such as missed-call and opportunity-due reminders are excluded from lead-task sync. |
| Users and groups | Rep identities, team membership, and accountability reporting. Syncing a Close user does not automatically grant that user access to Cleats. |
| Custom fields and ownership | Custom values used in filters and the ownership roles your team selects. |
| CRM configuration | Lead statuses, pipelines, opportunity statuses, custom field definitions, and lead Smart Views. |
After the initial import, supported Close webhook events update Cleats in the background. Processing is asynchronous, so a change in Close may take time to appear. Use a targeted refresh when you need to check recent data or update CRM configuration.
Aida lists define which accounts or opportunities to evaluate and what good follow-up looks like. Audits classify records as Compliant, At Risk, or Neglected. Scorecards and KPIs help managers inspect results and the records behind them.
When your team enables and configures actions, Cleats can write back to Close:
Cleats also supports email alerts. Connecting Close does not define your team's rules or enable every action. Review the organization and list action settings before turning on automation. Use the Actions Log to inspect recorded action outcomes.
Cleats requests Close's all.full_access and
offline_access OAuth scopes. Full access supports both importing data and
configured CRM actions. Offline access lets the integration refresh its authorization
and run background syncs without requiring you to sign in to Close for every request.
Authorization takes place in Close. Cleats stores the integration credentials encrypted and refreshes access tokens as needed. Your Close connection is associated with your Cleats organization; reconnect using the same Close organization.
For information about data handling, see the Cleats Privacy Policy and Terms of Service.
Open Settings → Integrations → Close and use the sync panel to select the records and time window to refresh. Use CRM Configuration for users, statuses, pipelines, Smart Views, and custom field definitions. Watch the progress panel for completion or errors.
Select Manage connection → Reconnect Close and authorize again in Close. Use this if authorization expires or is revoked. Reconnect to the same Close organization already linked to Cleats.
Select Manage connection → Disconnect. Cleats removes its Close webhook, revokes OAuth access, and clears the stored credentials. Previously synced records stay in Cleats; disconnecting does not delete them. The disconnected integration cannot receive new Close updates or execute new Close actions.
Ask a Cleats organization owner or manager to connect, reconnect, or disconnect Close. If you cannot authorize in Close, ask your Close administrator to review your access.
Check that ownership fields are saved and the initial sync has started. Review the progress and record counts. Confirm that you selected the correct Cleats organization and connected the expected Close organization. For subsequent changes, run a targeted refresh for the relevant records or CRM configuration.
Refresh CRM Configuration, then revisit the ownership fields panel. Lead and contact ownership uses supported single-value Close user custom fields. Save changes to the promoted ownership fields and allow the background ownership update to finish.
Try Reconnect Close for an authorization error. For a stalled or failed sync, review the progress panel and use the available recovery controls. If the error continues, contact support with your organization name, the affected sync step, approximate time, and the visible error message. Do not send passwords, API keys, or OAuth tokens.