Online Credit Prequalification for Dealer Websites

Three different products get sold under this one word. Knowing which one you are shopping for saves you a quarter of wasted demos.

Search for prequalification software and you will be shown at least three different things, described in almost identical language. Sort them before you sit through a demo, because the price and the compliance weight of each is different.

Soft pull prequalification. The shopper enters name, address and date of birth, and the tool runs a soft inquiry with a credit bureau. The store sees a score band or a set of program eligibilities without a hard inquiry hitting the consumer's file. This is the version most people mean, it requires a bureau relationship and a permissible purpose framework, and it is a genuinely separate product category.

Payment estimation. The shopper picks a vehicle, moves a down payment slider and a term, and sees an estimated payment. No credit data is involved at all. It reads to the customer as prequalification because it answers the same emotional question, which is whether this car is possible for them.

Full credit application intake. The customer completes a real application with income, employment, residence history and identifiers, which the store then works with its lenders. This is not prequalification in the strict sense, but for a large share of stores it is the step the website is actually failing to produce.

Most vendor pages blur all three. A store that buys the second while believing it bought the first ends up with a payment widget and no applications, which is a frustrating and expensive discovery.

We would rather be direct about scope now than have you find out during onboarding.

We do not run soft credit pulls. SecureWebX has no bureau integration, does not return score bands, does not do automated decisioning and does not submit anything to lender portals. If a soft pull result on your website is the requirement, you need a dedicated prequalification vendor and you should evaluate one on its own merits. Our page on soft pull credit prequalification covers what to ask those vendors.

What SecureWebX does cover is the application front door and the record keeping around it: secure online credit applications, shareable apply links, an application inbox tied to the company rather than to one person's email, document collection, identity verification at intake, a compliance module, and a terms and consent gate with versioning. On the CRM side there is desking with a fifty state tax matrix, which is where credible payment estimation comes from.

That combination solves the same business problem for a lot of stores, just by a different route. Instead of telling a shopper what band they fall in, you give them a private way to apply and a real payment they can look at. Whether that is enough depends on your traffic and your finance department, and it is worth deciding on purpose rather than by accident.

Ask a finance manager where deals die and you hear about structure and approvals. Ask where applications die and the answer is quieter: most of them die before anyone submits them.

A customer sitting at a desk, in a showroom, with a salesperson watching, is being asked to hand over income, employment history, residence history and a social security number at the least private moment of their day. Plenty of people will do it. A meaningful number say they want to think about it, leave, and get recorded as a lost sale rather than as a process failure.

The same person will complete the same form at their kitchen table in about twelve minutes. Nothing about the information changed. What changed is that nobody was watching them type it.

The effect is sharpest exactly where it costs most. A buyer rebuilding after a repossession or a bankruptcy carries real embarrassment into that conversation, and handing them a private path is not a convenience feature. Our page on subprime auto leads covers how those customers behave across the rest of the process.

An apply link is a shareable secure application URL. You text it, put it on a landing page, drop it in an email signature, or print it on a card. The customer completes the application wherever they are, and it lands in your application inbox.

That single mechanism changes several things at once. The application can be started before the customer ever visits, so the showroom conversation opens with structure rather than paperwork. A shopper who is not ready to come in can still enter your pipeline instead of disappearing. And a salesperson working a lead by text finally has something concrete to send that is not another request to come down to the store.

Because the CRM includes SMS and MMS with real threading, plus RCS with SMS fallback on supported handsets, sending that link is one action inside the conversation the customer is already having. No second system, no second login. Texting stays consent based with opt outs honored, which matters a great deal here, since an application request is precisely the kind of message that has to be clean.

The operational detail most stores miss: decide by name who owns the application inbox and what the response expectation is. An unowned inbox is where applications go to age.

If you cannot show a shopper a credit band, you can still answer the question underneath it, which is what the payment looks like.

The desking engine behind the platform handles loan and lease, a fifty state tax matrix, semimonthly payment frequency, trade credit caps and three lease tax methods. Multi state stores get consistent tax treatment instead of a spreadsheet built years ago for one state and quietly wrong on the other. Semimonthly exists because a lot of real payment schedules track pay periods rather than calendar months, and a calculator that only knows monthly produces numbers that will not hold at signing.

From there a deal can be sent to a customer facing page the shopper opens on their own phone, with e-signature available. They leave with real figures rather than a photograph of a worksheet, and the numbers your desk is using are the numbers they are looking at.

Two cautions. State any estimate as an estimate and label the assumptions, because a payment shown without a rate assumption is a complaint waiting to happen. And nothing here predicts approval. We cannot guarantee credit outcomes and no vendor honestly can. More on the mechanics on the desking tool page.

The reason to care about the intake layer is not only conversion. It is that this is where your compliance record gets created, and a weak record is a problem you discover at the worst possible moment.

SecureWebX includes a compliance module and a terms and consent gate with versioning. Versioning matters more than it sounds. When your disclosure language changes, you need to know which version a specific customer accepted and on what date, not simply that they accepted something at some point. A system that overwrites its own terms cannot answer that question, and that is the question you will be asked.

Document collection sits in the same flow, so proof of income, proof of residence and identification arrive attached to the application rather than as photographs scattered through a text thread. Document reading assists capture, so a licence or an insurance card can be handled from a phone camera instead of a copier in the back office.

Identity verification is supported at intake. Being precise about what that is: verification and record keeping at the application stage. It does not replace your own Red Flags Rule program, your OFAC screening or your obligations under the FTC Safeguards Rule. Those remain yours to build and document.

Anything that markets financing sits under fair lending rules, and it is worth stating bluntly because it comes up in vendor conversations more often than it should.

Campaigns for financing cannot narrow an audience by age, gender, income, marital status, household size, education, language or ZIP. Those are not house preferences we invented. They are the rules, and they exist for good reasons.

If a vendor offers to help you target around them, or presents that capability as a competitive edge, they are handing you liability with a bow on it. Treat that as disqualifying information about the vendor rather than as cleverness. We will not do it, and we would rather lose the business than pretend otherwise.

Inside those lines there is plenty of legitimate room. Geographic service area, vehicle type, the shopper's own stated situation, and where they are in your own pipeline are all fair game. The honest version performs perfectly well, which is the part nobody says out loud.

A sequence that avoids the usual failure, which is buying the tool and then never changing the process around it.

1. Put the apply link in your text templates first. If sending it depends on someone remembering, it will not happen. Build it into the messages your team already sends every day.
2. Give it to the internet department before the floor. They already work customers remotely and will use it immediately, which produces internal proof faster than a showroom rollout ever will.
3. Build a dedicated page for it. The lead pages builder creates a landing page with its own URL settings, so a financing page can carry its own consent language, its own tracking and its own follow up rather than sharing a generic contact form.
4. Wire the follow up before you drive traffic. Automations and follow up processes should already be running when the first application lands, not built afterward.
5. Then bring it to the desk as the default path rather than the exception, once the team has seen it work on real customers.

Expect someone to argue that customers will not complete a form on a phone. In our experience the resistance comes from the store, not the customer. Test it on your own traffic for three weeks and let the numbers settle the argument.

To close without ambiguity. Provided: secure online credit applications, shareable apply links, an application inbox, document collection with camera capture, identity verification at intake, a compliance module, a versioned terms and consent gate, worksheets and desking with a fifty state tax engine, customer facing deal pages with e-signature, lead pages with per page URL settings, a free live chat widget for your site, role based permissions, reporting, and eFax on the admin side.

Alongside it sits the full CRM: SMS, MMS and RCS with SMS fallback, a VoIP softphone with click to call, call recording with transcription, voicemail drop, an email inbox and composer with bulk email, an email validator and a phone validator, automations, follow up processes, drip campaigns, appointments and reminders, and three layers of reporting.

Not provided: soft pull credit prequalification, bureau integration, lender portal submission, automated decisioning, menu selling with product rating, eContracting of retail installment contracts, and anything in the dealer management system category. We do not sell a dealer management system, and no DMS integration or inventory feed is required to run any of this.

Pricing is month to month with no long term contract, from $199 on CRM Only and from $799 for programs that include exclusive local leads. Detail on the pricing page. If you are unsure whether the intake layer alone solves what is broken, tell us what happens today and we will tell you straight whether we are the right fix.

Does this run a soft credit pull?

No. There is no bureau integration, no score bands returned and no automated decisioning. SecureWebX covers application intake, apply links, document collection, identity verification at intake and consent records. A soft pull requires a dedicated prequalification vendor.

What is an apply link?

A shareable secure application URL. Text it, email it, put it on a landing page or print it. The customer completes the application privately on their own device and it arrives in an application inbox tied to your company rather than one person's email.

Can we show payments on the website without a credit pull?

Yes, as clearly labeled estimates. The desking engine covers loan and lease with a fifty state tax matrix, and a deal can be sent to a customer facing page the shopper opens on their phone. Always show your rate and term assumptions.

How is consent recorded?

Through a terms and consent gate with versioning, so you can show which version of your disclosure language a specific customer accepted and when. Texting consent is honored platform wide, and opt outs apply everywhere rather than per campaign.

Will this make us compliant?

No single tool does that. It produces intake records, identity verification at application and versioned consent, which support your program. Your Red Flags, OFAC and FTC Safeguards obligations stay yours to build, run and document.

Do we need a DMS integration or an inventory feed?

Neither is required. That is deliberate, and it is why independents, brokers and individual salespeople can run on the platform. If you do have an inventory feed, Inventory Link can ingest it and advertise your actual vehicles.

See an apply link go out by text and come back as a worked application with documents attached. Month to month, no long term contract.