Jotform Notification Emails Not Received

If a customer says they submitted a service request but your office received no Jotform email, check the stored submission before asking them to fill out the form again. A missing alert is not proof that the request was lost.

For an owner or office administrator, the useful sequence is: locate the request, identify which notification should have been sent, inspect the email log, then reconcile the intended mailbox. Keep customer confirmation, internal notification and job assignment as separate outcomes.

Start with the missing step

Do not delete a working notification template, change every recipient or submit the same customer request repeatedly to diagnose one missing alert. If the request is already stored, assign a staff member to handle that existing record while the email issue is investigated.

Locate the request in the correct form

Open the affected form's Inbox from Jotform Workspace. You can also select Inbox from the app picker when a related form asset is open. Jotform's Inbox displays stored submissions and supports searching and filtering them. Access Jotform Inbox.

Match a request using its reference and approximate submission time. Check whether an active filter or the wrong form could explain why it is not visible. Keep any private identifiers in your authorized workspace.

If you cannot locate the record, mark its existence as unconfirmed. Do not tell the customer their request was received simply because a browser displayed a confirmation or because a different test succeeded. Reconcile the original form with the account owner before choosing a retry.

Check which email should reach the office

In Form Builder, open Settings, then Emails, and inspect the relevant Notification Email. Verify the saved delivery address, including spelling and whether it is a former employee's mailbox. Jotform initially uses the account email as the notification recipient; changing that form's recipient is separate from changing the account address. Change the notification recipient.

Notification Emails go to configured recipients, whereas Autoresponder Emails go to the selected email field from the form. Reply-To controls where replies go; it is not the notification's delivery address. Also inspect whether the relevant automatic-send event is enabled: receiving a new submission and editing an existing submission are separate events. Notification and autoresponder settings.

For example, a customer confirmation reaching a homeowner does not demonstrate that the office alert reached your estimator. Record those as two different messages. If the message comes from a separate approval workflow, identify that workflow and its trigger rather than assuming the form's notification controls govern it.

Do not confuse Test Email with a recipient test

Jotform documents an important limitation: the notification editor's Test Email button sends to the email address associated with the account, even after the notification recipient changes. Receiving that sample is not proof that the new office mailbox receives submission alerts.

The documented recipient test uses Preview Form and a submitted test entry. Preview submissions count toward the submission allowance, so do not treat preview as an isolated sandbox. Test a notification recipient correctly.

Before submitting anything, have the form owner check whether that action could start a payment, dispatch request, customer message or integration. Use an authorized safe test flow, an address you control and clearly labeled fictional information. Stop if the side effects are unknown. A successful test of a copied form does not establish that the original live form is configured identically.

Trace conditional routing before changing delivery settings

Open Settings and Conditions if email routing depends on service type, location or another answer. Jotform's Change Email Recipient condition selects a template and recipient when its rule matches. Multiple rules can use Any or All matching, so record the actual submitted values and the intended branch. Conditional email recipients.

Compare the selected template and destination with the alert you are missing. Do not remove all conditions to force a message through: that can send requests to the wrong team. Use a case that should match the affected route and, when safely authorized, a second case that should not match it.

Avoid adding unrelated recipients as a troubleshooting shortcut. Jotform warns that recipients entered together in this conditional setup can see one another's addresses. Keep the intended audience and the form's existing privacy boundary intact.

Read the email log and the mailbox together

From the account settings, open History, select Emails in the action filter and choose a date range covering the request. Open the relevant email entry and its Details. Jotform documents recipient, sending time and delivery status information in this view. View form email logs.

Record the exact status shown instead of translating every entry into "received." Match the form, recipient and timestamp, noting time zones where the two systems differ. A log entry and a message visible in the recipient mailbox answer different questions; neither proves that a staff member acted on the lead.

If no matching entry appears, verify the filters and routing before concluding that Jotform never generated an email. If an entry exists, follow its status and any available error. Check the recipient's spam or junk folders, then ask the mailbox administrator about rules and quarantine if the message is still absent. Jotform's troubleshooting guide also recommends email-log review and provider escalation for unresolved delivery cases. Missing notification troubleshooting.

Handle bounce suppression and sender changes carefully

Jotform stops sending to addresses on its bounce list. Its documentation names causes such as inactive or full mailboxes, server trouble and spam rejection. Account Settings provides a bounce check, but self-service removal applies only to the account's own email address. Other recipient addresses require Jotform Support. Bounce-list guidance.

Resolve the underlying mailbox problem before an authorized removal and retest. Repeatedly clearing suppression does not establish that delivery is fixed.

If the provider identifies filtering as the cause, give the authorized mail administrator Jotform's maintained sender information. Ask for a narrowly justified correction, not disabled spam protection or an indiscriminate allowlist. Jotform sender domains and IP guidance.

Custom SMTP is a separate sending configuration, not a universal repair. Jotform requires both configuring the sender and selecting it for the relevant form email. If SMTP is already in use, confirm that selection with its owner. New SMTP credentials belong only in the official configuration flow, never in this worksheet or a public support message. Custom SMTP setup.

Copy the Submission to Inbox Trace

Use one record for one intended alert. This worksheet keeps a missing message from becoming a duplicate service request. Record only references, not customer message bodies or credentials.

For a fictional cleaning estimate, the office might find the saved request but discover that its notification still targets a former scheduling mailbox. The next step is to verify the intended recipient with the owner, not ask the homeowner to resubmit. This is an illustrative diagnosis, not a result from a tested customer account.

After a correction, reconcile the test submission, intended recipient, log and received message. Confirm separately who owns the existing customer request. Record "not checked" for anything unverified; one successful email does not establish a delivery-rate guarantee.

Escalate the specific gap

If the cause remains unclear, send official support the affected form reference, intended recipient, time range, exact log status and a redacted description of the failed step through an approved private channel. Jotform's troubleshooting guidance explains that support can provide server-log information for the mail provider to trace. Do not publish private submission links, SMTP credentials or customer details.

If the email arrives but its uploaded-file link fails, use our Jotform file-access guide. For the broader intake design and our earlier bounded observations, see the Jotform service-intake test. Our Jotform review covers product fit and buying considerations.

Evidence and scope

Official documentation checked on October 16, 2026. This diagnostic sequence and worksheet are proposed checks, not a new delivery test. No form was submitted, email sent, bounce entry removed or live configuration changed for this article.