A borrower submits your contact form and sees a success message. Your loan officer never receives the notification. A week later, someone discovers the inquiry while checking the website.
The form may have accepted the submission while a different part of the process failed. Email delivery, recipient rules, CRM assignment, and staff visibility are separate steps. Treating them as one event makes the problem harder to diagnose.
This guide focuses on finding missing notifications after a website is already operating. It complements an initial integration setup by asking a narrower question: where did this specific inquiry stop moving?
Separate the Submission From the Alert
Start by identifying what the success message actually proves. It may indicate that the form accepted a request, not that an email reached a person or that the CRM assigned an owner.
WordPress’s official wp_mail documentation specifically warns that a successful return does not establish that the recipient received the email. A send attempt and inbox delivery are different pieces of evidence.
Write down the stages your actual setup uses:
- The browser submits the form.
- The form service accepts or rejects the request.
- An entry is retained, if the system is configured to retain one.
- The email service processes an alert.
- The CRM receives or updates a record, if connected.
- A team member sees an assigned task or notification.
Not every form uses every stage. Confirm the architecture before changing settings.
Use One Controlled Test Inquiry
Create a clearly labeled test using an email address and phone number controlled by your team. Record the form URL, test time, device, and expected recipient.
Do not use a real borrower’s information to investigate the system. Avoid entering Social Security numbers, account information, or financial documents into a general contact form.
Let the relevant staff know that the record is a test. If the inquiry could trigger automated email or text follow-up, coordinate the test so it does not create unwanted communication or distort production reporting.
Use the same test identifier while checking each stage. That makes it easier to distinguish one failure from several unrelated records.
Check Whether an Entry Exists
Look in the form platform’s permitted entry storage or submission log. Do not assume WordPress or the form plugin automatically keeps a copy.
If no entry exists, investigate whether the request was accepted, blocked, or rejected. Possible areas to inspect include validation, spam controls, an expired connection, or a recent form change. Use the actual error evidence rather than switching multiple settings at once.
If the entry exists, retain its identifier and timestamp. The investigation can now move downstream without assuming the borrower failed to submit.
Access to submission records should be limited to appropriate staff. If logging is enabled for troubleshooting, confirm that it does not retain unnecessary sensitive information and follows the company’s retention practices.
Trace the Email Service’s Result
Ask the website or email administrator to inspect the notification’s message record. Useful evidence can include a provider message ID, recipient, timestamp, and an accepted, deferred, bounced, or suppressed status.
Those statuses require interpretation. A receiving server accepting a message is not the same as a loan officer reading it in the inbox.
If the provider reports rejection, use the specific response to guide the fix. If the message was accepted, check the recipient mailbox’s junk folder, quarantine, rules, forwarding, and shared-mailbox access.
Do not solve the problem by broadly disabling spam protection. Identify the failing path and make a targeted change that the mail administrator can verify.
Review the Sending Identity
A form notification should use a sending arrangement authorized for the domain and mail service. Ask the administrator to review the From address, reply handling, and authentication configuration.
Google’s email sender guidelines describe authentication and delivery expectations for mail sent to personal Gmail accounts. The applicable requirements vary by sender category; they should not be copied into a universal rule for every mailbox provider.
Have an administrator check the relevant SPF, DKIM, and DMARC setup against the actual sending service. Avoid making DNS changes without understanding the other systems that send email for the company.
Using the borrower’s address as the message’s From identity can create a misleading sending arrangement. Ask the form provider how to configure an appropriate sender and a separate Reply-To field.
Check the CRM Independently
A notification problem and a CRM problem can occur separately. An inquiry might exist in the CRM even when the email fails, or arrive by email without creating the expected CRM record.
Search for the controlled test using permitted identifiers. Check whether the record was created, merged into an existing contact, filtered, assigned to another owner, or placed in a queue.
Then review the assignment rule. An empty state field, an inactive team member, or a conditional rule can change where a lead goes even when the integration itself is functioning.
LoanSites’ mortgage CRM integration guide covers connecting the systems. For a missing inquiry, focus on the evidence for this submission and its routing rather than rebuilding the whole connection immediately.
Assign a Reliable Place to Check for New Inquiries
Decide which permitted system staff should use to confirm new inquiries. A mailbox alone may not provide the visibility needed to manage assignments and follow-up.
Where supported, define an owner, an unassigned queue, and a backup process for absences. Keep responsibility explicit: someone should know who checks the queue and what happens when an inquiry remains unassigned.
This is an operational decision as much as a website setting. Sending five alerts to five people does not establish that any one person is responsible for responding.
Use only approved contact and follow-up processes. A website inquiry should not be treated as permission for every possible marketing channel without the company’s appropriate review.
A Practical Failure Example
A mortgage team changes the notification recipient after a loan officer leaves. The form still shows success, and entries continue to appear in the approved form system. The mail service accepts the alerts, but the new recipient is a distribution group that rejects mail from that sender.
Changing the form’s design would not address this issue. The evidence points to the receiving arrangement. After the administrator corrects the group configuration, the team repeats the test and verifies both receipt and the CRM assignment.
This is a hypothetical example, not a diagnosis of a particular website. It illustrates why checking each stage is more useful than treating all missing emails as a broken form.
Retest After Changes That Affect the Path
Include a controlled inquiry after relevant changes to forms, plugins, email providers, domains, CRM connections, or recipient assignments.
Record the result in a small operational log: test date, form, expected destination, observed outcome, and responsible person. A technical success should be paired with confirmation that staff can actually see the result.
The testing frequency should reflect inquiry volume and the importance of the form. A periodic check is useful; a recent unexplained gap in notifications deserves immediate investigation.
LoanSites’ website support and design service includes requested website updates. Describe the issue precisely when requesting help, including the form URL, test time, and observed failure, without sharing borrower information through an unsuitable support channel.
Frequently Asked Questions
Does a success message prove an email arrived?
No. Confirm form acceptance, sending, receiving, and staff visibility separately.
Should we retain every form entry forever?
No universal retention period fits every company. Use an approved storage and retention process and limit the information collected.
Will an SMTP plugin fix every missing alert?
No. A sending connection cannot by itself correct an invalid recipient, mailbox rule, CRM routing problem, or failure before the email stage.
Should we count the test as a marketing lead?
Label it clearly and exclude it from reporting where appropriate. Keep test records from inflating your assessment of inquiry volume.
Make the Lead Path Verifiable
A working contact form needs a path that can be checked from submission through staff visibility. The goal is to locate the failed stage and verify the correction with a controlled test.
Schedule a call with LoanSites to discuss your mortgage website’s forms, notification setup, and support needs. Bring the observed symptoms so the discussion can focus on the part of the process that needs attention.
