A credit cooperative has a structural advantage over banks: the member is the owner, service is close, and decisions happen near the requester. It also has an operational disadvantage that cancels much of this: a credit proposal requires documents, analysis, guarantees, and signatures, and each of these steps is a point where someone needs to communicate with the member — and where, in practice, no one does.
In this article
- Where the proposal stalls
- The document pending that no one follows up on
- The follow-up process that supports the proposal
- A cooperative channel, not the manager's
- One quarter in numbers
- The member who does not use the cooperative
- Financial data and compliance on the channel
- The scam using the cooperative's name
- Five mistakes that cost operations
- The numbers to monitor
- Frequently Asked Questions
Where the proposal stalls
A credit operation is not a sale; it is a process with stages, and the real funnel of a cooperative usually looks like this:
- Interest — the member inquires about a credit line
- Simulation — receives amount, term, and installment
- Documentation — needs to gather and submit papers
- Analysis — goes through credit, committee, or approval level
- Guarantee — guarantor, lien, joint guarantor
- Signature and release
When measuring the drop between each stage, the result surprises almost every board: the biggest loss is not in analysis, but between simulation and documentation. In other words, the member heard the proposal, liked it, and gave up on gathering the documents.
This is not lack of interest. It is lack of follow-up at a moment when the person is alone with a list of requirements they do not fully understand, not knowing how long it will take or what happens if an item is missing.
A useful analogy is a stalled construction: it wasn’t lack of money or will, it was lack of someone saying what the next step is.
An approval rate of 71% seems good and hides that only 44% of simulations reached analysis. The important number is how many left simulation and submitted the first document within five days — that’s where most cooperative operations get lost.
The document pending that no one follows up on
On the cooperative side, the document list is routine. On the member’s side, it is an obstacle with four simultaneous problems:
- They don’t understand some items. Proof of income for self-employed, revenue for small legal entities, guarantee documentation — each raises doubts and doubt causes delay.
- They don’t know the deadline. Without a date, the task competes with everything else and loses.
- They don’t know what they already submitted. Sent three photos by message and don’t know if they were accepted.
- They don’t know if it’s still valid. Two weeks passed and they assume the proposal expired.
The fix is operational and inexpensive. The list is sent in a single message, numbered, with a one-line explanation per item, with a deadline and information that the simulation is valid until a certain date. Each submitted item receives confirmation — “received item 3, missing 1 and 5” — which simultaneously resolves insecurity and the need for follow-up.
Cooperatives that started confirming item by item usually see the average documentation time cut in half without hiring anyone.
The follow-up process that supports the proposal
Five scheduled contacts cover the entire path from simulation to release. None of them is a demand for payment.
- On the day of simulation: a written summary with amount, term, installment, total cost, and proposal validity.
- Within 48 hours: the numbered document list, with explanation and deadline.
- On the fifth day, if nothing has arrived: a human, not automated, contact with a useful question — which document is difficult to obtain.
- During analysis: a notice stating it is under analysis and when to expect feedback. Silence during analysis is where anxiety turns into abandonment.
- At decision: clear communication, including when negative, with what can be done to enable approval later.
Contact 5 deserves special attention. A refusal communicated respectfully with an alternative path keeps the member; a refusal communicated by silence or a curt message produces a member who does not return and who tells others — which in a cooperative, where the base is community, has a multiplied effect.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we are writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
A cooperative channel, not the manager's
In most cooperatives, the member has the personal number of a manager or assistant. This is great for the relationship and terrible for the institution, for three reasons.
Information is not recorded. Agreements, simulations, and deadlines remain on a device the cooperative does not control, which is a management and compliance problem, since service in a financial institution must be traceable.
When the person leaves, the relationship goes with them. In community-based cooperatives, the manager is usually the real bond, and their departure takes members.
Service is hostage to vacations and absences. A member with a proposal in progress cannot wait two weeks because the person is away.
The fix maintains closeness and transfers ownership: the member continues to be served by a named person, but within an institutional channel, with visible history for whoever needs to continue. This allows another employee to resume a proposal without asking the member to retell everything — the gesture that most destroys trust in any financial service.
One quarter in numbers
A single cooperative with 4,100 members and 3 service points.
Before. Service via managers’ cell phones, document list sent by email, no scheduled follow-up.
- Simulations performed in the quarter: 612
- Proposals that reached complete documentation: 373
- Loss between simulation and documentation: 39%
- Approved: 264
- Average time from simulation to release: 23 days
After, with written summary on the day of simulation, numbered list with deadline, item-by-item confirmation, human contact on the fifth day, and notice during analysis:
- Simulations: 605
- Complete documentation: 492
- Loss between simulation and documentation: 19%
- Approved: 351
- Average time until release: 14 days
There are 87 more operations in the quarter, without a new simulation or credit policy change. The cooperative did not approve more — it stopped losing in the middle those who had already been effectively approved.
There is a relevant side effect: the drop from 23 to 14 days freed up credit team capacity, which previously spent part of the time reopening stalled processes and restarting analyses with expired documents.
The member who does not use the cooperative
Every cooperative has a large portion of members who are on the social register but barely transact. They do not generate revenue, generate account maintenance costs, and represent a risk rarely discussed: they are the first to leave when an alternative arises, and the least likely to defend the cooperative when needed.
It is worth separating this group into three, because each requires a different action:
- Those who joined for a specific reason and resolved it. Took a credit, paid it off, and stopped. They need a new reason — and that reason is rarely a new credit line, usually a day-to-day service.
- Those who were never activated. Joined by referral and never used anything. They need a welcome contact that never happened, even two years later.
- Those who partially migrated. Remain members but transact elsewhere. They are the most valuable and easiest to recover because they already know the cooperative and did not leave — they just found it more practical to use another channel.
The action that works for all three is the same in form and different in content: a human, individual contact with a question instead of an offer. Cooperatives that conduct outreach campaigns to inactive members usually discover that most did not leave due to dissatisfaction — they left due to lack of reason to stay.
Participation in assemblies is low in almost every cooperative, and the reason is rarely disinterest — it is communication in the wrong format, on the wrong channel, with the wrong timing. An individual, brief invitation on the channel the member uses daily, stating what will be decided and why it affects their life changes attendance in ways that newspaper notices do not.
Financial data and compliance on the channel
Service in financial institutions via messaging involves personal data and confidentiality, and there are non-optional precautions.
- Identity confirmation before any account information. Phone number does not identify a person — devices are changed, numbers recycled, chips cloned.
- No passwords, access codes, or tokens via the channel, under any circumstances, not even for verification. The institution must frequently remind members of this because it is exactly the loophole used in fraud.
- Traceability. Service must be recorded with date, time, who served, and what was said, which does not happen on personal devices.
- Access control. Who can see a member’s history must be defined, and employee termination must revoke access the same day.
- Consent for commercial communication, separate from operational relationship, with simple and recorded opt-out.
- Retention and disposal. Documents sent by message must go into the system and leave the channel, with a defined retention period.
A practical language rule is also worth noting: never promise approval, rates, or terms before analysis. In credit, an expectation created in writing guarantees future complaints, and in cooperatives it circulates in the community.
The scam using the cooperative's name
Small financial institutions with close relationships are preferred fraud targets precisely because members trust them. The typical scam uses an unknown number, the cooperative’s name, a real manager’s name, and some urgency.
Four measures greatly reduce damage:
An official, published, and verifiable number, with verified commercial account identification, communicated constantly — on statements, app, service points, and the channel itself.
A fixed and repeated rule: the cooperative never asks for passwords, codes, transfers to third-party accounts, or advance fees to release credit. Repeating this is tedious but effective.
A simple channel for members to verify if a contact is genuine, with quick response. Most frauds are avoided by a timely question.
Immediate communication when a scam is circulating, with the exact format of the approach. Generic alerts protect no one; alerts describing the circulating message protect.
Five mistakes that cost operations
- Sending the document list without explanation or deadline. This is where 39% of proposals are lost.
- Disappearing during analysis. Silence is read as refusal and the member looks elsewhere.
- Communicating refusal without alternatives. In community-based cooperatives, a poorly handled refusal costs more than the denied operation.
- Leaving service on the manager’s cell phone. A management, compliance, and continuity problem all at once.
- Treating inactive members as statistics. They are the first to leave and the least likely to defend the cooperative.
The numbers to monitor
- Conversion between each funnel stage, with special attention to the transition from simulation to documentation.
- Average documentation time, from list sent to last item received.
- Total time from simulation to release.
- Proposals stalled for more than 10 days, as a nominal list, not percentage.
- Members without transactions in 6 months, segmented into three profiles.
- Reactivation contacts made and how many resumed transactions.
- Reported fraud attempts, with recorded approach format.
The cooperative sells closeness, and closeness is not an abstract value — it is someone who responds, explains what is missing, and notifies when analysis is delayed. When this follow-up exists, the competitive advantage over banks is real. When it does not, the cooperative delivers the same experience as a large bank with less structure, which is the worst possible position.
Frequently Asked Questions
Where do credit proposals in a cooperative get lost the most?
Between simulation and documentation, not in analysis as almost every board assumes. In a real cooperative with 4,100 members, 39% of simulated proposals never reached complete documentation — the member heard the proposal, liked it, and gave up gathering the papers. This is not lack of interest: it is lack of follow-up at a moment when the person is alone with a list of requirements they do not fully understand, not knowing how long it will take or what happens if an item is missing. Therefore, the important indicator is not the final approval rate, which may seem excellent, but how many left simulation and submitted the first document within five days.
How to reduce documentation time in a credit operation?
By sending the list differently and confirming receipt item by item. The list should be sent in a single, numbered message, with a one-line explanation per item, a deadline, and the simulation’s validity date — because the member does not understand some items, does not know the deadline, does not know what has already been submitted, and assumes the proposal expired after two weeks. Each received document generates explicit confirmation, such as “received item 3, missing 1 and 5”, which simultaneously resolves insecurity and the need for follow-up. Cooperatives adopting this practice usually see average documentation time cut in half without hiring anyone, and in a real operation the total time to release dropped from 23 to 14 days.
What precautions must a financial institution take on WhatsApp?
Six, and none are optional. Confirm identity before giving any account information, because phone number does not identify a person — devices are changed, numbers recycled, chips cloned. Never ask for passwords, access codes, or tokens via the channel, under any circumstances, not even for verification, as this is exactly the loophole used in fraud. Maintain traceability, with date, time, who served, and what was said, which does not happen on personal devices. Control access, defining who can see history and revoking access the same day an employee leaves. Obtain consent for commercial communication separate from operational relationship. And define retention and disposal, with documents sent going into the system and leaving the channel.
How to protect members from scams using the cooperative’s name?
With four measures, because institutions with close relationships are preferred targets precisely due to the trust they inspire. Have an official, published, and verifiable number, with verified commercial account identification, communicated constantly on statements, app, service points, and the channel itself. Always repeat a fixed rule: the cooperative never asks for passwords, codes, transfers to third-party accounts, or advance fees to release credit. Offer a simple and quick channel for members to verify if a contact is genuine, since most frauds are avoided by a timely question. And communicate immediately when a scam is circulating, describing the exact format of the approach — generic alerts protect no one.
How to reactivate members who do not transact?
By separating them into three profiles, because each requires a different action. Those who joined for a specific reason and resolved it — took a credit, paid it off, and stopped — need a new reason, which is rarely another credit line and usually a day-to-day service. Those who were never activated, joined by referral and never used anything, need a welcome contact that never happened, even two years later. And those who partially migrated, remaining members but transacting elsewhere, are the most valuable and easiest to recover because they did not leave due to dissatisfaction and just found another channel more practical. For all three, the effective format is the same: a human, individual contact with a question instead of an offer.
The operation is not lost in analysis — it is lost waiting for documents
VeyloCRM records each proposal with its current stage, confirms documents received item by item, alerts the team when a proposal stalls, and keeps all service in a cooperative channel, with traceable history and controlled access.