Co-Buyer Credit Applications Done Right

Two applicants, one application, one customer record and one signature page: how a co-buyer deal moves through SecureWebX and LeadLocate CRM without anyone retyping a name.

A co-buyer shows up in three familiar ways. A couple buys together and both incomes carry the payment. A parent signs with a young buyer who has income but no file. Or a lender comes back on a thin file and asks for a second applicant before it will look again. In every case the store now has two people, two sets of personal information, two consents and one deal, and the paperwork goes wrong at the seams: the co-buyer's address typed differently on the application than on the worksheet, a consent captured for one applicant and assumed for the other, a second application started on a separate link that never gets joined to the first, and an adverse action notice that names one person when the file had two.

This page is the product side of that problem: how the SecureWebX application and the LeadLocate CRM customer record are built so that both applicants stay on one file from the first text to the signature. The dealership CRM with credit application page explains why the application belongs inside the CRM at all, and the bad credit car buyer leads page covers the leads that most often need a co-buyer in the first place. Here we walk the deal.

The salesperson opens the lead in LeadLocate CRM, presses Send a Text, and sends the store's SecureWebX apply link. Apply links are branded to the dealership and customizable with extra sections, custom fields, document uploads and disclosures, and the same link serves a single applicant and a pair, because the co-applicant section is part of the five step application itself: personal, residence, employment, income and review. There is no second link to start and no second file to join later.

The application accepts an ITIN as well as a Social Security number, which matters on co-buyer deals more often than a prime desk expects. Income, down payment and trade-in details are collected in the same pass, so the file the desk receives already shows what both people bring to the deal. Consent and the e-signature are captured against versioned terms, so the record shows exactly which language the applicants agreed to and when. Bot protection guards the public form, and if the pair starts at the kitchen table and stops at the employment step, the abandoned application feeds back to the CRM for follow up, which is usually a text asking whether the co-buyer needs help with their part.

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.

On the CRM side both applicants live on the Customer Profile, one shared buyer record for the customer and the co-buyer with personal information encrypted at rest and a driver license and insurance card slot for each person. It opens from the lead and from the deal, so the salesperson, the desk and DealTracker read the same two names, numbers and addresses rather than retyping them at each step. The driver license scanner reads each license from a phone camera into that record, from the deal view on the desktop or from the LeadLocate mobile app, which is how the co-buyer's address ends up spelled the same way on every document.

Two people also means two phones and two email addresses, and the CRM treats them as the contact points they are. Texts and emails to either person land in the same communications log on the lead, with delivery status on every message, and the Phone Validator and Email Validator show validity dots next to each contact. When the co-buyer had inquired separately weeks earlier and already exists as a lead, merge duplicates joins the two records rather than leaving a second file that a different salesperson works by mistake.

The desk structures the payment on a SecureWebX worksheet, a cash, finance or lease pencil that attaches directly to the application carrying both applicants. Worksheets run on the same math as LeadLocate CRM desking, with a 50 state tax matrix, semimonthly payment frequency, trade credit caps, three lease tax methods and the store's centralized deal defaults, and a worksheet already penciled in the CRM's EZ Desking pushes into SecureWebX instead of being rekeyed. The desking tool page covers the engine.

The deal vehicle on the worksheet decodes from the VIN or looks up a stock number against your inventory through Inventory Link, a manager confirms the build and options, and Kelley Blue Book QuickValues book-outs run inside the worksheet. Worksheets duplicate, which is how a desk holds one structure with the co-buyer and one without, on the same application, while the lender is deciding what it wants. The deal recap PDF prints from whichever worksheet wins.

Press Send to Lender and SecureWebX creates a code gated, expiring, revocable, watermarked share of the application for a lender your store chooses. Because the co-applicant section is part of the application, the lender sees both applicants in one view, reads the file in the lender response portal and records a decision, and the decision lands back on the application. Lenders that want a file in a set format get an export as STAR XML, fixed width, CSV or JSON, delivered by SFTP, SOAP, REST API, PGP encrypted email, structured email or the secure portal. eFax covers the lender that still works by fax, and the Mailbox keeps dealer to lender email on the file.

Co-buyer deals collect more stipulations than single applicant deals, because the lender wants proof of income and residence for both. The stipulations workflow tracks each stip on the application, marks it required, and fulfills it by uploading the document against it, with an upload for a lender shared into that lender's secure view. Uploads are virus scanned, and supporting documents stay per submission, so the co-buyer's pay stub is on the file and only the file. When the documents have to come from home, the Deal Jacket in the CRM shows a QR code either applicant scans to send a photo straight to the deal record.

The buyer sees a text from the salesperson with a link that opens a branded application on their phone. The co-buyer sees the co-applicant section of that same application, completes it, and both consent at the review step. Neither person sees the other's credit file, the lender share, the stip list or the notes on the pipeline; those belong to the store. When the deal is structured they see one customer deal page branded to the dealership, opened with a PIN, with an e-signature, a revision view when the numbers change, and deal chat with the salesperson where questions from either of them land in one thread with photos and link previews. A PencilRecap sheet gives them the recap to take home, and the print packet with payment ranges and a finance breakdown is there for the pair who want it on paper.

Getting the co-buyer's experience right is mostly about not making them feel like an afterthought. One link, one page and one signature flow does that better than a second application emailed as a form.

The checks run on the application, and the application carries both people. OFAC screening checks the applicants against the sanctions list. Consent and e-signature are captured against versioned terms. State specific disclosures are entered and edited per store, and the privacy notice and terms editor keep the applicant facing language the store's own; the disclosures page shows where those live. Every user on the console has accepted the store's terms before working a file, signs in with two factor authentication, and leaves a trail in the audit log.

When a co-buyer deal declines, or closes on terms other than the ones applied for, the adverse action notice generates from the application record, so the applicants, dates and details on the notice are the ones on the file rather than the ones someone remembered. Application data is encrypted at rest, the PDF viewer is watermarked and gated for print and download, and archiving retains every record, share and decision rather than deleting it. On the CRM side, the DNC Blacklist blocks a number in both directions with a live do not call lookup, which applies to the co-buyer's phone as much as the buyer's.

The manager works the SecureWebX pipeline, where every application carries its status, assignee, amount and notes, and the console's reports and analytics export to PDF. The application inbox page shows that view. On the CRM side the Reports dashboard on the dock carries activity, company and management reporting, so the manager sees which leads were sent the apply link, which came back with a co-applicant, and which were desked. Every call to either applicant is recorded with a transcript, and every call, text, MMS, email and voicemail sits in one communications log on the lead.

User Management sets who is a User, a Manager or a Master Administrator, so a desk can work the pipeline without touching the compliance settings, and the security log in SecureWebX shows every share and revocation. If your store's co-buyer process 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 opens with the same login from the SecureWebX button on the CRM dock. Users created in User Management sync across, and the store's tracking phone numbers carry with them. Setup is the apply link customized with the sections your lenders expect on a two applicant file, state disclosures and the privacy notice entered, deal defaults set for the worksheet, and your lenders added for Send to Lender and eFax.

Plans are month to month with no long term contract and are listed on the pricing page. The recorded demo shows the application and the inbox before you commit, and the contact page reaches a person who will 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 the co-buyer fill out a separate application?

No. The SecureWebX application has a co-applicant section inside the same five step form, so both applicants are on one application, one file and one lender share. Consent is captured against versioned terms at the review step.

Can a co-buyer apply with an ITIN?

Yes. The application accepts an ITIN as well as a Social Security number for applicants, and collects income, down payment and trade-in details in the same pass.

Where do the buyer and co-buyer live in the CRM?

On one Customer Profile, a shared buyer record with the co-buyer on it, personal information encrypted at rest, and a driver license and insurance card slot for each person. The driver license scanner fills each slot from a phone camera.

Does the lender see both applicants?

Yes. Send to Lender shares the application, and the co-applicant section is part of it, as a code gated, expiring, revocable, watermarked view with a lender response portal where the lender records a decision. Exports to a lender or DMS carry the same application.

What happens to the adverse action notice on a two applicant deal?

It generates from the application record, which carries both applicants, so the notice reflects the file rather than a retyped version of it. The application, shares and decision are archived, never deleted.

Is there an extra charge for co-buyer applications?

No. SecureWebX and its application are part of the LeadLocate platform under one login. Plans are month to month and listed on the pricing page.

Watch the recorded demo or book a walkthrough on a real co-buyer deal. 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.