Opta Lead Filtering Integration

Overview

Heavyset can route leads through Opta before they reach your CRM. Opta filters out duplicate, invalid, and low-value leads in real time—ensuring that only qualified leads are written to your CRM and counted against your appointment capacity.

---

How It Works

When an Opta submission URL is configured, Heavyset adjusts how leads are routed based on your CRM type.

LeadPerfection

• Leads are initially submitted to LeadPerfection at the time of form submission.
• When a prospect books an appointment:
  • Heavyset sends the lead to Opta instead of posting it directly to LeadPerfection.
• If no appointment is booked:
  • A deferred lead task (triggered after your configured threshold) sends the lead to Opta as a fallback.
• In both scenarios, Opta determines whether the lead is ultimately written to LeadPerfection.

All Other CRMs

• Leads are sent to Opta immediately upon form submission.
• The CRM API call is only made if Opta approves the lead.
• Your CRM receives only leads that pass Opta’s filtering.

---

Data Sent to Opta

The payload sent to Opta includes a complete lead record, such as:

• Contact information
• Lead source
• Product details
• Appointment date and time (if applicable)
• CRM-specific identifiers

---

Configuration

1. Navigate to Settings → CRM → Behavior Settings
2. Enter your Opta submission URL in the Opta Lead Submission URL field
3. Click Okay to save

Note: The URL must be a valid https:// endpoint provided by Opta.

---

Payload

Heavyset sends a JSON payload to your Opta submission URL. This base payload is included for all CRM types and contains the following fields:

Field	Type	Description
name	string	Full name
email	string	Email address
phone	string	Phone number (significant digits only)
address1	string	Street address
city	string	City
state	string	Full state name
stateAlpha2	string	Two-letter state code
zip	string	Postal code
country	string	Full country name
countryAlpha2	string	Two-letter country code
source	string	Lead source
sourceType	string	Lead source type
product	string	Product of interest
appointmentStart	ISO 8601 date string	Appointment start date/time in UTC (e.g. 2025-04-10T14:00:00.000Z) — only present when an appointment is booked
appointmentStartAMPM	string	Appointment start time in 12-hour local format (e.g. 10:00 AM) — only present when an appointment is booked

---

LeadPerfection Payload Details

For LeadPerfection integrations, Heavyset enriches the Opta payload with the following fields:

Field	Description
srs_id	Resolved source/sub-source ID
pro_id	Promoter ID from common settings
adate	Appointment date (MM/DD/YYYY)
atime	Appointment time (e.g., 9:00 AM)
productid	Resolved product ID

---

Notes

• If Opta is unreachable or returns an error:
  • The lead is not written to your CRM
  • For LeadPerfection only, the submission will be retried during the next deferred task cycle
• Demo mode is unaffected:
  • Leads in demo mode are skipped before any Opta call
• Removing the Opta submission URL:
  • Immediately disables the integration
  • No additional changes are required