Skip to content
  • There are no suggestions because the search field is empty.

LeadPerfection Configuration and Synchronization

Technical reference for settings, data movement, scheduled synchronization, document return, and known limitations.

1. Configuration Settings

Configuration settings control how LeadPerfection data synchronizes with One Click Contractor (OCC), including appointment time zones, document attachments, and filtering rules.

Timezone

Set the LeadPerfection organization time zone. The legacy default is Eastern Time unless changed. This setting controls the time zone used when OCC creates appointments.

Document Attachment Preferences

Control which OCC documents and job images are returned to the LeadPerfection lead, and assign the corresponding LeadPerfection Document Type IDs.

Filters

Filters can selectively pull jobs based on the following LeadPerfection fields:

Filter Category Available Fields
Sales Representative SalesRepName
Location City, State, zip
Lead Source Source, SubSource
Disposition Disposition, DispositionComments
Products ProductID1, ProductID2, ProductID3, ProductID4, ProductID5

2. User and Assignment Behavior

Active LeadPerfection employees synchronize with OCC. The current authorization update is authoritative for employee linking. OCC automatically links an employee to an existing OCC user when email addresses match.

Legacy User Mapping

OCC Field LeadPerfection Source
crm_id User.key
name User.value

Primary Sales Representative

An appointment can create or update an OCC job only when its LeadPerfection sales representative is actively mapped to an OCC user.

The appointment field slr_id identifies the assigned representative.

Additional Assignments

A secondary LeadPerfection representative becomes an OCC Additional Assignment only when a primary representative is also present and both users are mapped.

Assignment Changes

A change to an appointment representative is evaluated on the next 15-minute synchronization cycle when the replacement representative remains actively mapped and the appointment falls within the synchronization window.

3. Synchronization Schedule and Sync Action

Scheduled Synchronization

Scheduled job updates are pulled every 15 minutes, at the following minutes after each hour:

:05   :20   :35   :50

Manual Sync

The Sync button starts the initial synchronization and can be used to expedite job creation instead of waiting for the next scheduled run.

Data Retrieved During Sync

Data Type Endpoint / Mapping
Dispositions api/SalesApi/GetSalesApptDispProd
Event Result ID disposition.key
Event Result Name disposition.value
User CRM ID rep.key
User Name rep.value
Appointments api/SalesApi/GetSalesApptDetailDateRange

Appointment Retrieval Window

2 Days Before Through 30 Days Ahead

Sync retrieves appointments within this range, but only for users actively mapped between LeadPerfection and OCC.

4. Inbound Data Mapping from LeadPerfection

The following tables identify how LeadPerfection appointment data is mapped into OCC.

Job and Customer Data

OCC Field LeadPerfection Source / Behavior
customer_name Appointment.CustName
name Appointment.CustName and Appointment.ProductId
email Appointment.email and Appointment.email2. Both addresses are stored as a comma-separated value when present.
lead_source Appointment.Source and Appointment.SubSource
LeadPerfection Appointment ID Metadata Appointment.id
lead_perfection_salesperson metadata Appointment.SalesRepName
Metadata Naming Warning

Legacy documentation spells the appointment metadata key as metadata.lead_perferction_id. Validate the actual tenant key before custom development. Do not automatically correct or rename it without verifying the integration.

Address and Phone Data

OCC Field LeadPerfection Source / Behavior
address.line_1 Appointment.Address1
address.line_2 Not used
address.city
address.state
address.postal_code
Appointment.CSZ. OCC splits the comma-separated City, State ZIP value into city, state, and postal code.
Job Phone Name and Number Appointment.Phone. Primary-phone label: Phone.
Alternate Phone 1 Appointment.AltPhone1Type
Appointment.AltPhone1
Alternate Phone 2 Appointment.AltPhone2Type
Appointment.AltPhone2

Appointments and Notes

OCC Field LeadPerfection Source / Behavior
Appointment Summary Not used
Appointment Notes Appointment.Notes
start_time Appointment.ApptDate
end_time Start time plus two hours, converted using the organization time zone.
Appointment LeadPerfection ID Metadata Appointment.id
Note Text Appointment.notes
Note LeadPerfection ID Metadata Appointment.id
Appointment Duration

OCC calculates the appointment end time as two hours after the start time, using the configured organization time zone.

5. Data Sent Back to LeadPerfection

OCC returns documents according to organization settings and configured LeadPerfection Document Type IDs.

Returned files attach to the LeadPerfection lead associated with the appointment and are available in the lead or prospect Documents tab.

Document Return Configuration

Document Type Required Configuration / Behavior
Agreement / Proposal Agreement / Proposal Document Type ID. If a specific type is not entered, the configured default document type can be used.
Cost CSV Cost CSV Document Type ID and Attach Cost CSV on Fully Executed Agreement.
Job Image Job Image Document Type ID and Attach Job Image on Upload.
Labor Summary CSV Labor Summary CSV Document Type ID, Labor Summary CSV Pattern, and Attach Labor Summary CSV on Fully Executed Agreement.
Labor Summary PDF Labor Summary PDF Document Type ID, Labor Summary PDF Pattern, and Attach Labor Summary PDF on Fully Executed Agreement.
Important: Job Image Updates

Images are sent immediately after upload when enabled. Later changes made in OCC do not update the image already sent to LeadPerfection.

Notes Synchronization

OCC Notes content maps to LeadPerfection presnotes.

Returned notes are grouped with the newest first and include:

  • Creation date and time
  • OCC user name
  • Note text

Appointment Result and Result Reason

When a LeadPerfection appointment is resulted in OCC and saved, the result becomes available in LeadPerfection in the appointment Disp disposition field.

Outbound Synchronization Limitation

OCC does not send general job-status changes or general job-record updates back to LeadPerfection.

Supported outbound behavior includes configured documents and images, job notes, and appointment result or result-reason updates.

6. Known Behavior and Troubleshooting

Multiple Jobs from the Same Lead

LeadPerfection can create one OCC job for each appointment attached to a lead.

Multiple appointments can therefore appear as duplicate jobs in OCC. This is an API limitation and does not necessarily indicate a duplicate synchronization error.

Deleted Leads and Appointments

Deleting a LeadPerfection lead or appointment does not delete the related OCC job or appointment.

The relationship becomes orphaned, and no later updates are pulled for that deleted source record.

Appointments Not Appearing in OCC

  1. Verify the assigned representative is active.
  2. Confirm the representative is mapped to an OCC user.
  3. Check that the appointment falls within the two-days-before to 30-days-ahead window.
  4. Verify the appointment passes configured filters.
  5. Run Sync and review the result.

Employees Not Synchronizing

  1. Verify the LeadPerfection credentials.
  2. Confirm OCC has access to the GetEmployees API Security endpoint.
  3. Verify the employees are active in LeadPerfection.
  4. Review matching email addresses for automatic linking.

Only active employees are expected in the employee synchronization result.

Documents Not Returning to LeadPerfection

  1. Review organization Document Attachment Preferences.
  2. Verify the corresponding Document Type ID.
  3. Confirm the relevant attach condition is enabled.
  4. Check the LeadPerfection user permission for the document type.

7. Final Technician Checklist

  1. LeadPerfection authorization and credentials verified
  2. Organization time zone confirmed
  3. Active employees synchronized
  4. OCC user email matching verified
  5. Primary representative actively mapped
  6. Additional Assignment requirements reviewed
  7. Appointment date range verified
  8. Job filters checked
  9. Initial or manual Sync completed
  10. Inbound customer and job mappings reviewed
  11. Address and phone fields validated
  12. Appointment and note metadata reviewed
  13. Document Attachment Preferences configured
  14. Document Type IDs and attach conditions verified
  15. Outbound appointment results tested where applicable
  16. Known duplicate-job and deletion behavior reviewed
Remember

What you see can differ depending on your organization's settings and your permission level. Tab names, headers, and available options are configurable. If you cannot see or perform something described here, ask your manager first. They can contact support.