Two jobs in one guide. The internal deploy SOP that gets EZ Check live for a merchant inside the first hour, and the merchant run-a-lead guide that gets them reading the portal and hitting their 300 leads. EZ Check is the engine that feeds every application, so this is the stage the whole first 30 days leans on.
Live in the first hourTest lead before go-liveData + Pixel connected300 leads, month one
Two audiences, one guide. Sections 02 and 03 are internal, for Gian and the deploy. Sections 04 to 06 are written for the merchant, so they can be handed over directly. Where a portal screen or exact field is not yet confirmed, it is marked [confirm] rather than guessed.
Start here01
What EZ Check is
The lead engine. EZ Check is the soft-pull tool the merchant runs to find financeable customers. Every application downstream starts as an EZ Check lead, so getting this live and flowing is the highest-leverage thing in week one.
A soft-pull lead tool. It checks a customer's options without affecting their credit score, so the merchant can see who is financeable.
The 300-a-month engine. The month-one floor of 300 leads runs entirely through EZ Check, roughly 10 to 12 a day.
Connected to their funnel. Their lead source feeds EZ Check, and the data flows back so each lead makes the next one easier to find.
The input to everything. Leads become applications become funded deals. If EZ Check is not flowing, nothing downstream is either.
Confirm the platform specifics. The deploy and portal steps below are the structure. [Confirm the exact EZ Check platform, login, API-key location, and the fields a test lead returns with Gian, so every step is exact and any installer can run it.]
Deploy (internal)02
The deploy SOP
Internal, for the installer. Run this from the SOP, never from memory. The client is only told EZ Check is live after the test lead passes.
Book the deploy in-window8 to 5 PST onlyThe self-serve booking link offers only in-window slots. Aim for inside the first hour of the welcome where possible. [Confirm the booking link.]
Install EZ Check for the merchantFrom the deploy SOPSet up the merchant's EZ Check account and dashboard. [Confirm the exact install steps and where the account is created.]
Connect the API keyThe integrationConnect the API key so EZ Check is wired behind the merchant's funnel. [Confirm where the key lives and how it is connected.]
Run a test leadVerify, do not assumeRun one test lead and confirm it returns the expected results before doing anything else. [Confirm the exact fields a test lead returns, the four numbers.]
Connect data and the Meta PixelSee section 03Wire the merchant's lead data and Pixel so conversions flow back, this is what makes leads compound.
Only now, tell the merchant it is liveAfter the test passesConfirm the test lead returned and data is flowing, then walk the merchant through the portal (section 04) and hand them this guide.
The rule. A merchant is never told EZ Check is live until a test lead has actually returned. That single check prevents a merchant running real leads into a broken setup.
Deploy (internal)03
Connecting data & the Pixel
The single highest-leverage part of the deploy. When lead and conversion data flows back, every lead sharpens the next. Do this on the deploy call, with the merchant, not later by message.
Confirm the funnel feeds EZ CheckTheir lead sourceCheck where the merchant's leads come from (their lead source) and confirm that source is wired into EZ Check so leads actually arrive.
If they run Meta, connect the PixelConversions flow backConnect the merchant's Meta Pixel so conversion events flow back to their ad system. This lowers their cost per lead over time. [Confirm the exact Pixel connection steps.]
Confirm data is flowing both waysIn, and backVerify leads are arriving and conversion data is posting back. The merchant's health board should show data connected.
Why it matters. Connected data is the difference between a merchant whose leads get cheaper and better every week and one whose system never improves. Treat this as part of go-live, not an optional extra.
Run it (merchant)04
Reading the portal
For the merchant. Once you are live, here is how to read your EZ Check dashboard, so you always know where your leads are and what to do next.
Your leads. Every lead you run appears here, with their status. [Confirm where the leads list sits in the portal.]
Lead status. Each lead shows where it is in the process, so you can see who is ready to move forward. [Confirm the statuses.]
Your numbers. Your running lead count and activity, so you can see your pace toward the 300 a month. [Confirm the dashboard view.]
Where to act. The leads worth following up are the ones that prequalify, work those first. [Confirm how a prequalified lead is shown.]
If anything looks unclear, ask in your channel and we will jump on a quick screen-share and walk it with you. You should never be guessing what a screen means.
Run it (merchant)05
Running a lead
For the merchant. The core action, the one you will do many times a day. We will run your first one together on the deploy call, then it takes seconds.
Start a new leadFrom your dashboardOpen a new lead in EZ Check. [Confirm the exact button and screen.]
Enter the customer's basic detailsA short formEnter the customer's information. Keep it quick, fewer fields means more completed leads. [Confirm the required fields.]
Run the soft checkNo impact to their scoreThe soft pull checks their options without affecting their credit score. [Confirm the submit step.]
Read the resultWho prequalifiesSee whether the customer prequalifies and for what. Work the ones who prequalify first. [Confirm how the result displays.]
Move a good lead forwardInto an applicationFor a prequalified customer, move them into a finance application. Your point of contact will help you with the first few.
"Soft check, no impact to your score, let's see what you qualify for." That is the only language to use with a customer. Never say no credit check or guaranteed approval.
Run it (merchant)06
Hitting 300 leads
For the merchant. 300 leads in your first month sounds like a lot until you break it down. It is a simple daily rhythm, and we help you build it.
Daily target
10 to 12 leads
Weekly
~75 leads
Month one
300 leads
Make it a daily habit. 10 to 12 leads a day, run as you go, gets you to 300 without a scramble.
Point your funnel at it. Every enquiry you already get can become an EZ Check lead, so you are not starting from zero.
Use the list-upload play. If you have an existing contact list, we can run it through in one go to get you moving fast.
Watch your board. Your health board shows your pace, so you always know where you stand.
We do this with you. Your point of contact helps you build the daily rhythm and removes anything slowing it down. You are never left to hit the number alone.
Support07
Scenarios
What comes up with EZ Check, and what to do.
The test lead doesn't return on deploy
Do not tell the merchant it is live. Stop and check the API-key connection and the install steps. Re-run the test lead. Only proceed once it returns the expected result. Escalate to Gian if it persists.
Leads aren't flowing into EZ Check
Check the funnel-to-EZ-Check connection and the merchant's lead source. If they have an existing list, run the list-upload play to get immediate volume while the funnel connection is fixed. Get on a screen-share rather than trading messages.
Data or the Pixel isn't connected
This is the highest-leverage fix, so prioritize it. Get on a screen-share and connect it with the merchant. If they run Meta, set up the Pixel; if not, confirm the funnel is feeding EZ Check. Confirm data flows both ways before closing it out.
The merchant is confused by the portal
Reset to one thing at a time on a screen-share. Find the single screen they are stuck on and walk it, then point them to this guide so they can self-serve next time. Confusion never gets fixed over text.
Lead volume is low after week one
It is a flow problem, not a willpower problem. Diagnose where leads come from, connect that source properly, and run the list-upload play for immediate volume. Help them build the daily rhythm, do not push them to do more.
Support08
Definition of done & SLA
EZ Check enablement is done when all of this is true.
EZ Check live with the API key connected.
Test lead returned the expected result before go-live.
Data and Pixel connected, flowing both ways.
Merchant can run a lead and read the portal, confirmed on the call.
Daily rhythm set, the merchant knows their 10-to-12-a-day target.
SLA. Deploy within the first hour of the welcome where in-window, 48 hours at most. The merchant is told it is live only after the test lead passes. [Confirm the exact deploy SLA with Chai and Gian.]
Support09
Who to contact
Owners for EZ Check.
G
Gian
Deploy & systems
Owns the install, the API key, and the data connection. Escalate any deploy issue here.
H
Harvey
Lead Broker
Helps the merchant turn prequalified leads into funded deals.
S
Shara
Point of contact
Helps the merchant build the daily rhythm and read the portal.
Live in the first hour. Flowing all month.
Deploy from the SOP, connect the data, prove it with a test lead, then help the merchant build the daily rhythm to 300.