The merchant opened the application off your text, filled in their name, business, revenue and how much they want, reached the questions about positions and bank statements, and closed the tab. On most floors that record is either invisible or filed as incomplete. On the best ones it is a task on a rep’s desk within minutes.
![Whiteboard diagram. The application: name, business, revenue and requesting ticked; positions and statements blank; closed the tab at 10:19. An arrow to “Saved — 6 of 11 fields, on the record”, which splits into “rep gets pinged — he stopped at positions” and a text: “10:25 — hey Marcus, your app’s saved where you left off. two more questions and it’s in: [link]”. Below: partial apps are more common than you think — and the CRM already caught them. In GHL: forms save partial submissions on their own. Build the workflow off them: partial → task to the rep → text to the merchant with the resume link.](/_next/image?url=%2Fvideos%2Fcrm-features-top-mca-brokerages%2Fpartial-application-chase.png&w=3840&q=75)
What the CRM should do
| Step | What happens | On the board |
|---|---|---|
| Save | Every field entered so far stays on the record | 6 of 11 fields, on the record |
| Ping the rep | A task that says where the merchant stopped | “He stopped at positions” |
| Text the merchant | A link that resumes the application where they left off | “Two more questions and it’s in” |
Where they stopped matters as much as that they stopped. A merchant who quits at the positions question may have more open advances than they want to admit; one who quits at the upload hit the step where Alex watched good merchants leave until he took it off the form. The rep calls differently for each.
What the rep says
Alex’s version is short: I saw you took a break from your application, I have everything saved, let’s finish it over a call. It tells the merchant you are paying attention and that you are trying to get them an offer for their specific situation, which is most of what separates the broker who funds the deal from the four who called the same morning.
Setting it up
In GoHighLevel, forms save partial submissions on their own; the workflow is built off them — partial submission, then a task to the rep, then a text to the merchant with the resume link. In another CRM the form has to post each step as it is completed rather than only on submit, which most form tools can do.
The text only works if the phone number was one of the fields they filled. If it was not, the merchant is still reachable, just not by you directly: retargeting the merchants who did not submit is how that audience gets a second look. And a merchant who abandoned twice and then went quiet belongs on a come-back date rather than in the bin.
Questions brokers ask
What should I do with incomplete MCA applications?
Save what the merchant entered, ping the rep with where they stopped, and text the merchant a link that resumes the application where they left off. Then call.
Does GoHighLevel save partial form submissions?
Yes, its forms save partial submissions on their own. Build a workflow off them: partial submission, task to the rep, text to the merchant with the resume link.
What do I say to a merchant who abandoned the funding application?
That you saw they took a break, you have everything saved, and you can finish it together on a call. It shows you are paying attention without repeating the pitch.
Are partial applications worth following up?
Yes. They are more common than most brokers think, the merchant already started asking for funding, and you have already paid for the click or the lead.
Where do merchants usually abandon a funding application?
At the questions that feel exposing — open positions and bank statements. The field they stopped at is worth putting in the rep’s task, because it changes how the call should open.
Reference
Watch: six things the top MCA brokerages have in their CRMPartial applications are number three, with the GoHighLevel workflow on the board.
