The entities that purchase your leads—wallets, contacts, and configuration.
Customers are the businesses buying leads from you. They’re the reason this whole operation exists—they want leads, you have them, and Juiced connects the two while making sure money changes hands appropriately.
Before diving in, let’s clear up a common point of confusion: customers are not users.
Concept
What it represents
Example
Customer
A business entity
”Acme Insurance Co.”
User
A person who logs in
”Jane Smith, Account Manager”
A single user can access multiple customers (useful for agencies managing several accounts), and a single customer can have multiple users (the whole team can log in). Users authenticate. Customers purchase leads.
Click Create Customer to add a new buyer. This is the same as what happens when a customer registers through your portal—you’re just doing it on their behalf.You’ll need to provide:
Business name and email (required)
Phone and address (optional, but helpful for records)
Lead caps and budgets if you want to limit their activity
Customers have several statuses that reflect different aspects of their account health. Understanding these helps you quickly diagnose why a customer might not be receiving leads.
Rather than showing all four statuses everywhere, Juiced computes a display status that summarizes the customer’s situation:
Display status
Shown when
Active
Operational and has available funding
Paused
Manually paused
Inactive
Wallet funding is exhausted (no bid can cover its minimum)
Archived
Account archived
This is what you’ll see in most places throughout the app.
Display status only reflects operational and funding state. Cap and budget exhaustion show up on the customer’s individual bids (as Capped or Exhausted) rather than changing the customer’s own display status. A customer with every bid capped will still show as Active if their wallet is funded—they just won’t be receiving leads.
Customers have a wallet balance that funds their lead purchases. You can add or remove funds without processing an actual payment—useful for credits, adjustments, or corrections.
When a customer’s bids are active, funds may be “reserved” to cover potential purchases. The displayed wallet balance accounts for these holds—what you see is what’s actually available to spend.
Return tiers let you incentivize good behavior. Customers with low return rates can earn discounts, while serial returners face penalties.If a customer is assigned to a return tier, you’ll see it displayed on their overview with a colored badge. Tiers can include:
Discounts — Reduced pricing on bids (they compete at full price but pay less)
Penalties — Surcharges based on their return rate
The Disable Return Tiers toggle exempts a customer from this system entirely.
A record of every change to the customer’s wallet balance. Each transaction shows:
Timestamp — When the transaction occurred
Amount — How much was deposited or withdrawn
Event — What triggered the transaction, with a link to the related record (lead, dispute, etc.)
Transaction ID — Unique identifier for the transaction
These are wallet transactions, not necessarily real currency movements. Adding credits, adjusting balances, or processing returns all create transactions here even though no money changed hands externally.
Contacts are phone numbers or email addresses used to send notifications. Each contact can optionally have a name attached for easier identification.
You can only add contact types for integrations you’ve configured. No email integration means no email contacts. No texting integration means no phone contacts.
From this page you can:
Add contacts — Enter a phone number or email address
Test contacts — Send a test notification to verify delivery
Edit notification preferences — Click edit to see a list of available notifications that can be enabled or disabled for that specific contact
Available notification categories include:
Lead notifications — Lead assigned, dispute approved
