Consent-first CRM workflows for mortgage brokers

Mortgage follow-up isn't a sprint. A homebuyer may start asking questions long before they find a property, a refinance lead may wait for rates to move, and a referral partner may send someone who is months from applying. Meanwhile the conversation touches some of the most sensitive data a person has, and messages to borrowers are often subject to consent and marketing requirements that your compliance adviser can confirm for your market.

So the goal of automation here is modest and specific: remember every borrower, remind at the right time, keep sensitive data out of the wrong channels, and leave every judgment to the broker. This page explains how we approach that design. We haven't built for a mortgage business yet, and the page is written that way.

• Timing is set by the borrower. Pre-approval, house hunting, offer, application and closing each move at their own pace. Generic "day 1, day 3, day 7" sequences don't fit.
• Several people care about one file. The borrower, a co-borrower, a real estate agent who referred them, and sometimes a processor all need different updates.
• Messages need review. Consent, opt-outs, approved wording and record keeping are considerations to review with your compliance adviser, and they matter as much as speed.
• Sensitive data tempts shortcuts. A borrower will happily send a pay stub by text if nobody tells them not to.

The first form should collect only what a broker needs to call: name, contact details, preferred channel, purpose (purchase or refinance), rough timeline and location. It doesn't need income, account numbers or identity documents, so it doesn't ask for them.

Documents belong in the secure borrower portal or loan system you already use. Automated messages can remind a borrower that their document checklist is waiting there, but they never request or carry the documents themselves. Inside the CRM, access follows roles: assistants see what they need to schedule, not everything in the file. Retention is decided up front, so old leads don't keep data nobody is using.

We separate the questions automation can ask from the decisions only a person can make. A short pre-screen (purchase or refinance, timeline, property type, first-time buyer or not) helps route the lead to the right broker and pick the right follow-up track. It doesn't produce a verdict.

The broker reviews each new lead and chooses what happens next: book a consultation, send approved educational material, refer out, or close the record. Nothing in the workflow tells a borrower they qualify, suggests a product or mentions a rate. If you want a message that references rates or terms, it goes through your approved-template process first.

The loan system stays the record for the loan itself. The CRM tracks the relationship and the conversations around it.

Consultations book into each broker's real calendar with confirmation and reminder messages, plus simple reschedule links. Follow-up for borrowers who aren't ready is educational and infrequent: explainers on the process, what documents usually come up, how a pre-approval works. Content is written or approved by the broker, not generated for each person.

Referral partners get updates only when the borrower has agreed to it, and only the milestone, never the numbers.

We build every consequential step with a gate in front of it:

1. Template approval. New or changed message templates are reviewed by the broker or compliance lead before they go live.
2. Change control. Workflow edits are drafted, tested with a test contact and published deliberately, with a record of who changed what.
3. Kill switch. One control pauses all outbound sequences, for example when rules or products change.
4. Audit trail. Consent, opt-outs, messages and stage changes are logged on the contact, so you can answer "why did this person get this message?"

The same pattern runs through builds we've shown in public: the model or workflow proposes, deterministic rules check, and a person approves before anything is sent.

We don't interpret regulations or decide which ones apply to you. We build to the requirements you and your compliance adviser confirm. As a starting list for that conversation, these are examples of rules brokers often raise with their adviser, by market:

• United States: the TCPA for calls and texts, CAN-SPAM for email, the GLBA Safeguards Rule for borrowers' personal information, Regulation Z's mortgage advertising rules, and any state requirements.
• United Kingdom: FCA rules on mortgage financial promotions and the Consumer Duty, PECR for electronic marketing and calls, and UK GDPR for personal data.
• Australia: ASIC's guidance on advertising credit, the Spam Act for electronic messages, the Privacy Act for personal information, and the Do Not Call Register for telemarketing calls.

Whatever your adviser confirms, two design habits usually help: record the consent and its source before the first message, and keep financial details out of chat, SMS, email and ad platforms. Conversion tracking reports that a consultation was booked, never anything about the loan.

Source and campaign are captured once at first contact, and referral partners are tracked as sources so you can see which relationships send ready borrowers. Reporting uses stages and counts, not personal financial details, and it's built on data you control.

We build in GoHighLevel or connect the CRM you already use when it has an API. The handoff to a loan origination system is designed field by field: which status changes come back to the CRM, and which data stays in the loan file. Webhooks are verified, duplicates are handled, and every sync writes a log.

Teqprotech works remotely from Karachi, Pakistan, with clients in the United States, the United Kingdom and Australia. We start with a review of your current process, and we never need real borrower data to design a workflow.