Subprime Deal Desk Workflow With SecureWebX

From the first text to the lender decision: the apply link, the application inbox, the worksheet, Send to Lender, stipulations and the adverse action notice, in the order a special finance desk actually uses them.

Three things start it. A financing lead arrives from a LeadLocate campaign, the kind described on the bad credit car buyer leads page, and lands in the Leads menu of LeadLocate CRM with its source attached. A customer on the lot tells the salesperson that credit is going to be the conversation, not the car. Or a shopper on your website taps the apply link on their own and the application shows up before anyone has spoken to them. In all three cases the desk needs the same sequence: get the application, structure the deal, get it in front of a lender, collect what the lender asks for, and close or decline with the paperwork right.

What makes subprime different from a prime desk is that the order matters more and the paper matters more. The structure has to be built around what a lender will buy before the customer falls in love with a unit, and every disclosure, consent and decision has to be on the file when someone asks for it later. That is why this workflow lives in SecureWebX, the credit application system on the LeadLocate platform, rather than in a texting app and a folder. The SecureWebX product page covers the system as a whole; this page walks one deal through it.

One thing to say plainly before the steps: financing campaigns run under fair lending rules, so the audience for a subprime campaign is never narrowed by age, gender, income, marital status, household size, education, language or ZIP. Every lead that submits in your zone is delivered, and the workflow below is how you work all of them.

Open the lead in LeadLocate CRM, press Send a Text in the top bar, and drop in the store's SecureWebX apply link. Apply links are branded to your dealership and each one can be customized with extra sections, custom fields, document uploads and disclosures, so the link a special finance desk sends can ask for the things a subprime lender will want up front rather than in a second round. Trackable short links in the text tell you whether the customer opened it. The same link goes on your website, on a personal salesperson website and in an Automated Templates response for the financing feed, so a lead that arrives at midnight has the link before the desk opens.

On the customer's phone the application runs in five steps: personal, residence, employment, income and review. It accepts an ITIN as well as a Social Security number, has a co-applicant section, and collects income, down payment and trade-in details in the same pass. Consent and the e-signature are captured against versioned terms, so the file records exactly which terms the applicant agreed to. Bot protection guards the public form. When a customer starts and stops, the abandoned application feeds back to the CRM for follow up, which on a subprime desk is often the most valuable list of the day, because the people who stopped at the income step are the people who need a phone call.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

The finished application arrives in the SecureWebX application inbox. The dealer console dashboard carries live badges, and the pipeline view shows each application with its status, assignee, amount and notes, with email from the record. The special finance manager assigns it to a desk or takes it, and the status moves as the deal moves, so nobody has to ask where a file is.

Two checks run before anyone structures anything. OFAC screening checks the applicant against the sanctions list, and the application data is encrypted at rest from the moment it is stored. Every user signs in with two factor authentication, every user has accepted the store's terms before they can work a file, and every open, edit and share is written to the audit log. On a subprime desk, where files move between more hands and more lenders than a prime deal, that log is what answers the question months later about who saw what.

The customer record on the CRM side is the Customer Profile, one shared buyer record with the co-buyer on it and personal information encrypted. The driver license scanner reads a license or insurance card from a phone camera straight into that record, so the names and addresses on the application, the worksheet and the deal page are the same names and addresses.

A subprime deal is structured to what a lender will buy, which means the worksheet comes before the test drive more often than not. SecureWebX worksheets are cash, finance and lease pencils that attach directly to the application, running on the same math as LeadLocate CRM desking: a 50 state tax matrix, semimonthly payment frequency, trade credit caps, three lease tax methods and centralized deal defaults set by the store. A desk that already penciled the deal in the CRM's EZ Desking pushes that worksheet into SecureWebX rather than rekeying it. The desking tool page walks the engine itself.

The vehicle side of the worksheet is where subprime deals are won or lost on advance. The deal vehicle decodes from the VIN or looks up a stock number against the store's own inventory through Inventory Link, holds a wish list when the unit is still open, and lets a manager confirm the build and options. Kelley Blue Book QuickValues book-outs run inside the worksheet, and title, stolen, sales, auction and warranty checks run from the same screen. When the structure is right, the deal recap PDF prints from the worksheet, and that recap is what goes with the file to the lender.

Worksheets duplicate, so the desk can hold two structures against two lenders on the same application, and a worksheet can be attached to or detached from an application as the deal changes units. That is the multi pencil habit of a good special finance desk, kept on the file instead of on a legal pad.

Press Send to Lender. Send to Lender creates a code gated, expiring, revocable, watermarked share of the application for any lender the store chooses. The lender opens a lender response portal, reviews the file and records a decision, and that decision lands back on the application through a decision webhook. It is a secure share to the lender your store already works with, chosen by you, and the share can be revoked the moment the deal goes elsewhere.

Lenders that want a file in a particular format get it that way. SecureWebX exports an application as STAR XML, fixed width, CSV or JSON, delivered by SFTP, SOAP, REST API, PGP encrypted email, structured email or the secure portal, with mapping templates saved per destination. A lender that still works by fax is covered by eFax, with fax numbers per company and partner and inbound status on the console. The Mailbox handles dealer to lender email in the same console with inbound handling, so the back and forth with a buyer at the lender stays on the file rather than in a personal inbox.

Nothing in this step is a lender portal integration or an automated decision. The store picks the lender, the lender reads the file and decides, and SecureWebX keeps the record of both. Credit pulls run on the store's own bureau account, with the store's bureau keys stored in SecureWebX under Settings.

A subprime approval comes back with stips, and the stipulations workflow tracks each one on the application: add a stip from the common list or type a custom one, mark it required, and fulfill it by uploading the document against it. Proof of income, proof of residence, references and the rest stop being a sticky note on the file. Supporting documents live per submission, uploads are virus scanned, and an upload for a lender shares into that lender's secure view so the buyer at the lender sees it without another email.

When the customer needs to send something from home, the CRM's Deal Jacket shows a QR code any phone scans, and the photo lands on the deal record within seconds. The same QR intake runs from the trade in form for the registration, title and payoff on the trade.

When a deal declines, or closes on terms other than the ones applied for, the adverse action notice generates from the application record itself, so the names, dates and application details on the notice match the file. State specific disclosures are added and edited per store in the compliance settings, the privacy notice and terms editor keep the applicant facing language current, and nothing is ever deleted: archiving retains every record, application, share and decision, for as long as compliance needs it.

The customer sees a text from a salesperson with a link that opens a branded application on their phone, five steps, with their consent captured at the end. If they stop partway, they get a call or a text from the person who sent the link, because the abandoned application came back to the CRM. When the deal is structured, they see a customer deal page branded to the store, opened with a PIN, with e-signature, a revision view when the numbers change, and deal chat with the salesperson where photos and links drop into the thread. A PencilRecap sheet gives them a clean recap to take home, and the print packet, with payment ranges and a finance breakdown, is there for the customer who wants paper.

What the customer never sees is the lender share, the stip list, the audit log or the notes on the pipeline. Those are the store's. The customer experience is a link, a page and a signature, which is exactly as much software as a subprime buyer wants to deal with.

The manager works from the SecureWebX pipeline, where every application in the store carries its status, assignee and amount, and from the console's reports and analytics, which export to PDF. On the CRM side, the Reports dashboard on the dock shows activity, company and management reporting, so the manager sees how many financing leads arrived, who was texted the apply link, and which deals were desked. Every call to a subprime customer is recorded with a transcript, and every call, text, MMS, email and voicemail sits in one communications log on the lead, which is the record to open when a customer says they were told something different.

User Management sets who is a User, a Manager or a Master Administrator, so a desk can be given the pipeline without being given the compliance settings. The security log and audit log in SecureWebX show every share and revocation. Support tickets and feature requests file from the console with reference numbers, and if your desk needs a step this page does not describe, it is available on request, our team puts it in production for your dealership.

SecureWebX is part of the LeadLocate platform, and one login opens both. Users created in User Management sync into SecureWebX, the SecureWebX button on the CRM dock opens the console, and the store's tracking phone numbers carry across. Setup is the apply links customized for the financing feed, the store's state disclosures and privacy notice entered, deal defaults set for the worksheet, and the lenders the store works with entered as partners for Send to Lender and eFax. The security page lists what protects the file at each step.

Every plan is month to month with no long term contract, and current plans are on the pricing page. Watch the recorded demo to see the inbox and worksheet before you commit, or use the contact page to have a person set the desk up with you. Your DMS stays where it is: the deal is contracted and posted there, and SecureWebX exports the application in the format it expects.

Does SecureWebX submit the application to a lender portal?

Send to Lender is a secure share: a code gated, expiring, revocable, watermarked view of the application for a lender your store chooses, with a lender response portal where the lender records a decision. Applications also export as STAR XML, fixed width, CSV or JSON in the format a lender or DMS expects. It is a share and an export, not a lender portal integration.

Who pulls the credit report?

Your store does, on its own bureau account. SecureWebX stores the store's bureau keys under Settings and offers a referral request for a store that needs an account. Decisions are made by the lender in the lender response portal, and the decision lands back on the application.

Can a co-buyer be on the same application?

Yes. The five step application has a co-applicant section, accepts an ITIN as well as a Social Security number, and the CRM's Customer Profile carries the buyer and co-buyer on one shared record with personal information encrypted.

What happens when a deal is declined?

The adverse action notice generates from the application record, so the details on the notice match the file. The application, the lender shares and the decision are archived rather than deleted, and the audit log shows who touched the file and when.

Do I need to rekey the deal from the CRM into SecureWebX?

No. A worksheet penciled in the CRM's EZ Desking pushes into SecureWebX, where the worksheet engine runs on the same math, and the worksheet attaches to the application. The deal recap PDF prints from there for the lender.

Is SecureWebX an extra charge?

SecureWebX is part of the LeadLocate platform, opened with the same login from the CRM dock. Plans are month to month and listed on the pricing page.

Watch the recorded demo or book a walkthrough with your own lenders in mind. Month to month, no long term contract, and your DMS stays exactly where it is.

Prefer to talk right now? Call or text 844-376-2274.