A Gmail CRM setup for a mortgage brokerage keeps client conversations in Gmail and puts the client, the loan and the next action in a CRM record. Assistants get delegated access or their own CRM login, never the broker’s password.
The handoff is where follow-ups get lost: a reply that nobody owns, or an email that never reaches the loan file before an assistant leaves.
Choose Between an Inbox and a CRM Connection
Gmail organises conversations, but it cannot show who owns the next step on a loan. Labels group threads by client, lender or stage. A thread keeps every reply to one enquiry together. Stars, snoozes and filters remind only the person who set them.
A CRM record holds what the team must share, such as the client’s details, each loan and the assigned follow-up with its due date. Once two people answer the same clients, or a follow-up must survive someone’s leave, that work belongs in a CRM. Gmail stays the place where the conversation happens.
Delegation, CRM Connections and Gmail Add-Ons Compared
| Option | How it works | Who sees the messages | Where the client record lives | What to watch |
|---|---|---|---|---|
| Mailbox delegation | The broker lets an assistant open the broker’s Gmail account | Every delegate sees the whole mailbox | Gmail labels only | No assigned owner, so two people can answer one client |
| Documented CRM connection | Each user connects their inbox through the CRM’s own published Gmail integration | CRM users see logged emails on the client record | The CRM client and loan | Logging rules and what stays after disconnection differ by CRM |
| Specialist Gmail CRM add-on | A browser extension adds pipelines and record fields inside Gmail | Add-on users who share a pipeline | The add-on vendor’s storage, beside Gmail | A second record system that the loan file still needs copies from |
Choose delegation when one broker needs help answering their own mail. Choose the CRM’s documented connection when clients and loans already sit in your mortgage broker CRM, because each logged email lands beside the loan it concerns. Treat a specialist add-on as an extra system that must still hand important correspondence to the loan file. The three options grant different permissions and keep messages for different periods, so set those rules before anyone connects.
Set Shared Access and Message Ownership
Before an assistant starts, decide who replies to clients from each mailbox and who owns each follow-up. Then give access through Gmail delegation or the CRM, never by sharing the broker’s password. A shared password hides who sent each reply and opens the broker’s whole Google account, including Drive.
A Gmail delegate can read, send and delete messages in the broker’s account. The delegate cannot change the password or the account settings. Messages a delegate sends show the delegate’s address, unless a Workspace administrator sets them to show only the account owner.
Give every client conversation one owner. In a CRM, the owner is the user assigned to the follow-up task on that loan. In Gmail alone, a Google Groups collaborative inbox covers part of this job: members assign a conversation to a colleague, then mark it complete, a duplicate or needing no action. It still holds no loan record.
Check the Account Type and Administrator Controls
Confirm the account type before you plan delegation. A personal Gmail account allows up to 10 delegates, while Google Workspace allows up to 1,000 from the same organisation.
In Google Workspace, the administrator must turn on mail delegation first, and the change can take up to 24 hours. The same setting decides whether a delegate’s emails show both names or only the broker’s. Showing both names keeps a record of which assistant answered.
The administrator also controls which outside apps reach Gmail. Each app can be trusted, limited to specific Google data, limited to unrestricted services or blocked. When Gmail access is restricted, untrusted apps that staff already connected stop working.
Read the Google permissions screen before anyone connects a CRM. HubSpot’s inbox connection, for example, can send and receive Gmail messages and read headers, subject lines and bodies. Approve a connector only for the access its documented email logging needs. The HubSpot CRM integration guide covers those connection settings in detail.
Log the Right Conversation to the Right File
Log each email to a specific client and loan, and send any message that matches no client, or more than one, to a review step first. A hypothetical brokerage shows the flow: broker Priya, assistant Tom and new joint applicants Sam and Alex.
- New enquiry: Sam writes from an address the CRM has never seen. Tom creates Sam’s contact and the loan before logging, then logs the thread to that loan and assigns himself the first follow-up.
- Joint-applicant reply: Alex replies from a household address that Alex’s parent also uses for their own loan with Priya. The address matches two contacts, so the message waits under a Gmail label such as “To match”. Tom reads it, logs it to the joint loan and records Alex’s address on Alex’s own contact.
- Document follow-up: the lender asks for two recent payslips. Tom sends the request from the loan record and sets a follow-up task due in three business days. Sam replies with the payslips attached, and Tom closes the task once the documents are filed.
Match by email address only when that address belongs to one client. A shared household address, a work address used by two applicants or an accountant’s address used for several clients needs a person to decide where the message goes.
Record each client’s permission to be contacted on their CRM contact, where the authorised broker can see it. Correspondence that records a client instruction, advice given or a lender condition goes to the loan file in the aggregator’s system. A Gmail label or add-on holds a working copy. The loan file is the record the licensee relies on, and Gmail is not a lodgement platform.
Keep identity documents, payslips and bank statements in the brokerage’s approved document location, then log the email text to the loan. Nobody forwards them to a personal address or leaves them only in an assistant’s mailbox. Confirm any emailed change to bank details by phone on a number you already hold, because business email compromise usually arrives as a believable email from a known sender.
Keep Records When Mailboxes or Staff Change
A client email can exist in Gmail, in the CRM connector’s storage and in the loan file, and each keeps it on its own terms. Name one person, usually the principal broker or office manager, who copies required correspondence into the loan file before a mailbox or role changes.
Gmail keeps a message until someone deletes it. Deleted messages stay in Trash for 30 days, and a Workspace administrator then has 25 more days to restore them. If your Workspace edition includes Google Vault, an administrator can also set Gmail retention rules and holds. Google states that Vault is not an archive, and that a deleted user’s data might be purged and no longer available to Vault.
The CRM keeps its own copy. HubSpot states that disconnecting an inbox does not delete email activity already logged, and that new email stops syncing from that account. Read your CRM’s equivalent article before relying on logged emails as the only copy.
The loan file holds the evidence your licensee’s record-keeping policy requires. Under Australian Privacy Principle 11.2, a business must take reasonable steps to destroy or de-identify personal information it no longer needs. The exception is information an Australian law requires it to keep. Copies scattered across mailboxes make that harder. The records retention guide covers how long to keep each type of record.
When an Assistant Leaves
Remove the assistant as a delegate, close their CRM seat, revoke any connector they authorised and reassign their open follow-ups. Deleting a Workspace user transfers Drive and Calendar data but not Gmail. Unless an administrator migrates the mail first or keeps the account under an Archived User licence, the mail goes with the account. A deleted account can be restored for up to 20 days.
What Breaks Continuity
- An alias is not a separate Google Account, so it cannot have delegates. Mail sent to a broker’s alias reaches only the broker’s mailbox.
- A forwarded copy starts a new thread in the assistant’s mailbox, so the client’s next reply splits the conversation across two inboxes.
- Deleting a thread in Gmail leaves any copy already logged in the CRM, and removing a CRM activity leaves the Gmail thread.
- When a connection expires or a seat is removed, logging stops from that point. In HubSpot, earlier activity stays on the records it was logged to.
Verify the Shared Client Workflow
Test the setup with fictional clients and a test assistant account before real correspondence relies on it. Each check below names the result you need to see.
Four Test Cases With Expected Results
| Test case | What to do | Expected assignee | Who can see it | File history to retrieve |
|---|---|---|---|---|
| New enquiry | Send an email from an unknown test address | Assistant who creates the contact and loan | Broker and assistant on the loan record | The first email, logged to the new loan |
| Existing joint application | Reply as the second applicant from a new address | Owner of the existing loan’s follow-up | Everyone with access to that loan | Both applicants’ emails on one loan |
| Mislinked email | Log a test email to the wrong client, then move it | Assistant who corrects the link | Only users of the correct client record | The email on the correct loan and none left on the other |
| Removed assistant | Remove the test assistant’s delegation, seat and connector | Broker or office manager, after reassignment | Nobody under the removed account | Every email the assistant logged, still on its loans |
Diagnose Missing Logs and Duplicate Replies
When an email never reaches the CRM, check these causes in order:
- Open the CRM’s email settings and confirm the sender’s inbox still shows as connected. An expired or disabled connection stops new logging, while Gmail keeps receiving mail as normal.
- Check whether the Workspace administrator restricted Gmail access for the CRM’s app. Restricting an untrusted app revokes its access.
- Confirm the sender’s address belongs to exactly one contact. An unknown or shared address belongs in the review step.
- Check which mailbox sent the reply. A delegate replying from the broker’s mailbox is logged only when the broker’s inbox is connected to the CRM.
Duplicate replies usually mean nobody owned the thread. Two people answered because neither could see that the other had taken it. Assign an owner when each email arrives, and show both names on delegated messages, so the team sees who replied.
Fix permissions, matching and connection status before you plan a CRM migration. If the four test cases pass, keep the current tools and use CRM training so every assistant logs, matches and hands over email the same way.
