The reply-with-a-status workflow
Reporting where a deal stands by email, the Hub, or the API.
The fastest way to keep a deal moving is to report where it stands. The client, and our matching, read what you report.
The stages
- In review: you have it and are working on it. Finer stages are there when you want them: contacted, documents requested, in underwriting.
- Offer made: you have put figures in front of the client, see The Lender Hub for submitting the offer itself. Approved, offer accepted, contracts sent and contracts signed sit in the same group.
- Funded: the deal completed. The funded amount is required, it is used for commission reconciliation.
- Closed: the deal ended without funding. Pick the reason from the list: your credit decision (for example revenue too low, not trading long enough, industry not funded), the client did not proceed or did not respond, or the business is already known to you. Other needs a short note.
The reason matters twice. It feeds the matching that keeps deals outside your criteria from reaching you again, and it decides what happens next for the client: after a credit decision the request can go to other funding partners, after the client walks away it does not.
Three ways to report it
- Email: reply to the referral email. One line is enough, and these are read automatically: "Received", "In review", "Docs requested", "Approved", "Offer made" with the figures, "Funded £85,000", and "Declined:" followed by the reason, for example "Declined: turnover below our minimum", "Declined: existing customer" or "Declined: client did not respond". Anything else is read by a person on our team, who records it for you.
- The Lender Hub: move the deal on the board, or open it and pick the stage. Funded asks for the amount, Closed asks for the reason.
- The API: the status endpoint, or your personal status URL under Integration in the Hub, from your own systems.
All three update the same deal, and the Hub board always shows its latest status, whichever channel it came from.
Why it matters
Lanes that respond quickly and report accurately receive materially more flow. A quiet lane, or one that never reports back, naturally sees less over time.
Full field-level detail for the API route is on docs.capvant.com.
Related articles
Was this article helpful?
Not covered here? Write to support@capvant.com and say which page you were on.