Leads

Leads are the fruit of your labor. Literally everything in Juiced exists to get leads from point A (your sources) to point B (your customers) while making sure you get paid along the way. A lead is a person who’s expressed interest in something—a quote, a service, a product. Your job is to connect that person with a customer who can help them. Juiced handles the messy middle: validation, routing, bidding, delivery, and the occasional dispute.

​

Lead statuses

Every lead has a status that tells you where it is in its journey. Here’s what each one means: A lead is considered “sold” if it’s Assigned, Posted, or Returned. Yes, even returned leads count as sold—you delivered them, and the customer chose to return them afterward.

​

Viewing leads

Tenants can view leads assigned to any customer. The lead detail page shows:

• Public ID — The unique identifier for the lead (e.g., lead_01arz3ndektsv4rrffq69g5fav)
• Basic contact information — Name, email, phone, etc.
• Metadata — Source, timestamps, assignment info, charged amount
• Details — Custom fields defined by the lead category or source
• Enriched Data — Property and owner information from third-party enrichment services (when configured)

​

Enriched data

If your distribution plan includes a Real Estate API enrichment stage, successfully enriched leads display an “Enriched Data” section below the property details. This section shows:

• Property Information:
  • Value, type, bedrooms, bathrooms
  • Square footage, lot size, year built
  • Sale history, assessed value, and annual tax
• Owner Information:
  • Name, phone, and email
  • Owner-occupied status and age
  • Mailing address

Only fields with values appear—empty fields are hidden. If no enrichment data exists for a lead (e.g., it was submitted before enrichment was configured, or the API returned no results), the section won’t appear at all.

​

Field visibility

Not all fields are visible to everyone:

• Tenants see all fields on a lead
• Customers only see fields marked as “deliverable” in the lead category configuration

This lets you collect data for your own purposes (like tracking or analytics) without exposing it to buyers.

​

Related records

If the lead was generated through ping-post, you’ll see links to view:

• The ping — The initial request that triggered the auction
• The post — The follow-up request that delivered the full lead data

These links only appear when the related records exist.

​

Lead actions

​

Returning leads

Tenants can return leads on behalf of customers. When a lead is returned:

• The customer’s wallet is credited with the charged amount
• The lead no longer counts against bidding limits
• The customer retains access to the lead data
• The lead status changes to “Returned”

​

Editing leads

Tenants can edit unassigned leads to correct data or add missing information. When editing:

• Lead data can be changed (contact info, custom fields)
• Metadata cannot be changed (source, timestamps, etc.)
• Details can be added if needed

When you save an edited lead, it gets reclassified into the appropriate lead category and lead type based on the updated data.

​

Reclassifying leads

This is useful when:

• A lead type’s conditions have changed
• You’re troubleshooting classification rules and want to test against real lead data

To reclassify a lead, open it for editing and select Reclassify from the More Actions menu. If the lead type changes, you’ll see a notification with the old and new classifications. If the lead is already correctly classified, you’ll be notified that no change was needed.

​

Reprocessing leads

Tenants can reprocess leads to run them back through the distribution engine. This is useful when:

• A lead failed to assign due to temporary issues (distribution errors, no available bids)
• Lead data was corrected and needs to be re-evaluated
• You want to retry distribution from a specific stage

​

Single lead reprocessing

After editing a lead, you can choose to reprocess it immediately. Select which stage of the distribution plan to start from—useful if you want to skip steps that have already been attempted or start fresh from the beginning.

​

Bulk reprocessing

Select multiple leads from the leads table and use the Process bulk action to requeue them all at once. You’ll see a breakdown of which leads are eligible and which aren’t before confirming. Only leads with certain statuses can be reprocessed: When bulk reprocessing, you can choose where to start:

• Bidding — Run leads through the full distribution process from the beginning
• Trigger Ping/Post — Start at the ping/post stage
• Marketplace — Send leads directly to the marketplace
• Trigger Post Marketplace Direct Post — Execute direct post delivery

​

Deleting leads

Tenants can delete leads entirely. This removes the lead from the system. Use this for test data or leads that should never have entered the system in the first place. When you delete a lead, any associated distribution flows are preserved for historical reference. The distribution flow’s timeline will show when the lead was deleted, and the Lead column will display “Deleted” instead of the lead’s name.

​

Exporting leads

Tenants can export leads from a customer’s lead list. This generates a downloadable file of the lead data—useful for reporting, backups, or moving data to external systems. Tenant exports include all custom fields from the lead, regardless of whether they’re marked as deliverable. This gives you full access to any data you’ve collected—including internal tracking fields not visible to customers.

​

Importing leads

Tenants can import leads on behalf of a customer. Imported leads create reverse auctions on the marketplace, where sources can bid to fulfill them. This flips the typical flow—instead of leads coming in and customers bidding on them, the customer is saying “I want leads matching these criteria” and sources compete to provide them. When importing, you’ll select a lead category. The import form automatically shows all fields from that category—both standard fields (name, email, phone, address) and any custom fields you’ve configured. Map your CSV columns to the appropriate fields. Validation rules are pulled from your lead category configuration. Fields marked as required in the lead category will be required during import. This keeps your imported leads consistent with leads that come in through the API.

​

Enriching leads

If you have a Real Estate API integration configured, you can enrich leads with additional property and owner data. The Enrich with Real Estate API button appears in the lead edit page header. When enriching:

1. Select which data endpoints to query (property details, skip-trace, etc.)
2. Choose whether to only fill empty fields or overwrite existing data
3. The lead is updated with any new information returned by the API

Enrichment requires the lead to have complete address information—street address, city, state, and ZIP code. If any of these are missing, you’ll see an error explaining which fields need to be populated first.

​

Test leads

Leads submitted through a source with test mode enabled are marked as test data. These leads:

• Are hidden from lead lists by default
• Can be viewed using the Test Mode filter toggle
• Display a “Test Mode” badge on the lead detail page

Deterministic test zips produce specific statuses depending on the zip code used. Leads submitted with any other zip code are forced to Audit status to prevent distribution. Test leads let vendors verify their integration works correctly without affecting production data or customer billing.