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, like a quote, a service, or a product. Your job is to connect that person with a customer who can help them. Juiced handles the messy middle, including 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.

​

Browsing leads

Open Leads under Entries in the sidebar to see every lead in your workspace, newest first, 50 to a page.

​

Status tabs

The tabs across the top slice the list by status (All, Assigned, Unassigned, Duplicates, Returned, Withheld, Pending, Marketplace, Club, Audit, and Uncategorized). Each tab shows a count that respects your current search and filters, so the number tells you exactly how many rows you’ll get when you click it. Tabs with nothing in them slide to the end of the row so the statuses that matter stay in view. Hover a tab for a one-line description of what it holds.

​

Searching and filtering

The Search leads box matches names, lead IDs, emails, phone numbers, addresses, customers, states, postal codes, and statuses. Click Filters to narrow things down further. You can filter by any of these.

• Lead types, States, and Counties (multi-country workspaces see their regional labels instead)
• Sources, Customers, and Partners
• Assigned scope (County, State, Nationwide, Marketplace, or Posted)
• Test mode (real leads by default, or test leads only)
• Value range and Created date range

​

Choosing columns

Name is always shown. Use Columns to show or hide Status, Address, Assigned To, Deliveries, Sold For, Source, and Date. Your choice is remembered in this browser. You can sort by Name, Sold For, and Date. When a customer won a lead at a discount, Sold For shows an “off” badge with the discount amount.

​

Viewing a lead

Click any row to open the lead. The header shows the lead’s name (or “No name provided”), its status, and a Test Mode badge for test leads.

• Contact shows phone, email, and address with one-click call, email, copy, and Open in Maps buttons. A map preview appears next to the address when your workspace has maps configured.
• Lead Details lists every custom field collected for the lead.
• Details (sidebar) shows the lead type, source, when it was received, and the lead ID (e.g., lead_01arz3ndektsv4rrffq69g5fav).
• Deliveries (sidebar) lists each customer or partner who received the lead, with the amount charged, the delivery’s status, the scope it was won at (County, State, and so on), and the payout owed to the source. Returned deliveries show the amount struck through. If nobody has received it yet, you’ll see “This lead hasn’t been delivered to anyone yet.”

​

Field visibility

Not all fields are visible to everyone.

• You 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.

​

Lead actions

Everything you can do with a lead lives in the More actions (⋯) menu in the lead’s header, plus an Edit button when the lead can still be edited. You’ll only see the actions your role allows and that make sense for the lead.

​

Viewing history

History opens a side panel with the lead’s activity log, newest first, including field-level changes and who made them. Long histories load in pages with a Load older button.

​

Returning leads

You can return a lead on a customer’s behalf. When you confirm the Return lead dialog, four things happen.

• The customer is refunded the charged amount
• The lead no longer counts against the customer’s lead cap
• The customer retains access to the lead data
• The lead status changes to “Returned”

Returns your customers request themselves follow your return tiers.

​

Triggering the customer’s webhook

If a customer’s system missed a lead (their endpoint was down, say), Trigger Webhook resends the lead to the customer’s webhook endpoints. It’s only available on assigned leads, and you can trigger it once per minute per lead.

​

Editing leads

You can edit a lead that hasn’t been assigned yet to correct data or fill in missing information. Click Edit in the lead’s header. The edit page has three sections.

• Contact Information covers name, email, and phone.
• Address covers street, city, state, and postal code.
• Details holds the lead’s custom field values.

Metadata like the source and timestamps can’t be changed. Save with the bar that appears at the bottom of the page. When you save, Juiced reclassifies the lead into the right lead type based on the updated data.

​

Reclassifying leads

Reclassifying re-runs lead type matching against the lead’s current data. It’s useful when a lead type’s conditions have changed, or when you’re troubleshooting classification rules and want to test against real lead data. Open the lead’s edit page and click Reclassify, then confirm the Re-run Classification dialog. If the lead type changes, you’ll see the old and new lead types. If it’s already correctly classified, you’ll be told no change was needed.

​

Reprocessing leads

Reprocessing runs leads back through your distribution stages. This is useful in situations like these.

• A lead failed to assign due to temporary issues (distribution errors, no available bids)
• Lead data was corrected and needs to be re-evaluated
• A lead is being held by an Audit stage and you’ve reviewed it
• You want to retry distribution from a specific stage

Every reprocess asks for a Starting stage. The list shows your own stages by name, in order. The lead runs that stage and continues through every stage after it.

​

Single lead

Choose Process from a lead’s More actions menu. This works for a lead in any status, including one flagged as a duplicate at intake. The one exception is a lead that’s already been delivered. It must be returned first, so the recipient is refunded before the lead goes anywhere else.

​

Bulk reprocessing

Select leads in the list and click Process in the bar that appears. Pick a starting stage and confirm. Bulk reprocessing only picks up leads in these statuses, and skips any that have been delivered. When it’s done, you’ll see how many leads were queued.

​

Deleting leads

Delete removes a lead entirely. Use this for test data or leads that should never have entered the system in the first place. Deleting can’t be undone. The lead’s incoming log is preserved for historical reference. In the logs, the lead column shows a Deleted badge instead of the lead’s name.

​

Exporting leads

Click Export in the Leads header to download leads as a CSV. You can choose between two options.

• Export filtered leads uses your current status tab, search, and filters. It’s disabled until you’ve applied at least one.
• Export all leads ignores the table filters and exports everything.

You can also select rows in the list and click Export in the bulk actions bar to export just those leads. Exports include at most the 10,000 most recent matching leads. The file is built in the background; when it’s ready, a Lead export ready notification lands in the notification bell with a download link. Exports include all of your custom fields, regardless of whether they’re marked as deliverable. That gives you full access to any data you’ve collected, including internal tracking fields customers never see.

​

Test leads

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

• They’re hidden from the Leads list by default.
• You can view them by setting the Test mode filter to test leads only.
• They display a Test Mode badge on the lead 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.