> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Set client message rules, review pending messages, and manage team alerts in Labs.

## Enable the new workspace

In **Settings → Labs**, turn on **Notifications overhaul** for your Location. Your agency controls which Labs features are available. The feature starts off, so existing Locations keep their current Notifications experience and send settings.

Open **Settings → Notifications**. The new workspace has four tabs: **Client messages**, **Team alerts**, **Review queue**, and **Activity**. The Operator Alerts settings link opens the same workspace on Team alerts.

## Client messages

Opening Notifications prepares one set of saved notifications for your Location. Existing saved message text, sender, channel choices, and automatic-send preferences carry forward. There is no separate activation or adoption step. **Application received** starts **Off** unless you already configured it. Messages previously configured for manual drafts remain Off for automatic sending and stay available in the client email composer.

Select a message to see **Currently saved**, its delivery policy, and the status of each channel. These saved settings control future events. Opening the page never sends a message or resumes paused automations.

| Message | Trigger |
| - | - |
| Application received | An application has been recorded and no results email has sent |
| Qualified | Underwriting identifies a qualifying path |
| Follow up later | An Operator parks the application |
| Additional review | Underwriting identifies a need for Operator attention |
| Credit improvement referral | An Operator confirms the referral outcome |
| No current funding fit | An Operator confirms there is no current funding path |

Qualified covers card funding, term loans, Revenue Based funding, and paths with paydowns or inquiry removal. If your saved messages or delivery preferences differ by funding path, a **Funding path** selector keeps each choice available within Qualified. Edit each path separately. Qualified sends at most once per Contact and channel, even across multiple applications or qualifying paths. Previously sent Qualified messages count toward that limit.

## Edit and save

Changes stay in draft until you choose **Save changes**. The sticky save bar shows the effect after saving; **Discard** restores the current saved settings. Unsaved drafts stay with each message when you switch messages or workspace tabs. The page warns before a reload, close, or following a link away with unsaved edits. If another Operator changes the same notification, saving your stale draft is blocked so their changes are preserved.

Email and SMS switches show their effective status. A selected channel can still be paused by the notification's policy, the master client-automation switch, or a shared channel pause. Use **Manage automation and channel pauses** to open those controls. Saving a message does not resume paused automations.

Under **Include in this message**, each option has its own labeled switch and explanation. **Estimated amount**, **Qualifying products**, and **Scheduling link** apply to email and SMS. Missing amounts and products are omitted. Turning Estimated amount off also suppresses the system's amount personalization field, including in the subject. Text you type yourself is not automatically removed. Underwriting remains the source of the result; a message does not change eligibility.

The scheduling switch stays off and disabled until a valid HTTP or HTTPS booking URL is saved. **Add scheduling link** opens a focused link editor. The URL is shared across your Location and saves immediately, separately from your message draft. After saving the URL, turn on Scheduling link and save the notification. Removing the saved URL turns inclusion off; re-adding a URL does not automatically turn it back on.

The editor shows readable personalization fields and an example client preview. Choose **Missing optional details** to check fallback copy. Previews never send a message. **Reset message text** restores the supplied subject and bodies in the draft without changing the send policy, channels, included details, or acknowledgment delay. Save to apply it.

## Application acknowledgment

The delay can be set from 1 to 60 minutes. The acknowledgment is skipped if an automated results email has already been sent for the Contact. A result awaiting Operator review does not suppress it. An in-progress results send takes precedence; its outcome is checked before the acknowledgment proceeds.

The acknowledgment is neutral. It never tells the Applicant about the Operator’s wallet or billing problem. Review any separate CRM workflows before enabling it, because this workspace cannot detect messages sent by external CRM automations.

## Review before sending

A rule set to **Review before sending** creates a message in **Review queue**. Open it to inspect the actual recipient and rendered message, then **Approve and send** or **Dismiss message**.

Approval preserves the displayed message. Before sending, the app checks the current rule, channel pauses, client opt-outs, recipient, and underwriting result again. A changed recipient or result stops the approved message; Activity explains the reason. Review the client’s current record before sending a replacement from their workflow.

## Shared settings and team alerts

Shared settings holds client automation and channel switches, scheduling and referral links, and an optional Operator CC address. A CC is a copy of the client email; it is separate from a team alert.

**Team alerts** controls document-upload notifications. Uploads in a batch are grouped. The intended recipient is the teammate who created the link, with a selectable fallback teammate, email, and mobile number. In-app alerts and CRM notes start on; tasks, email, and SMS start off. A CRM note records activity but does not notify a person. Team email is anchored to the client’s CRM conversation.

Wallet issues appear in the app’s billing alerts and Applicant card. The Operator is responsible for resolving them. No new wallet email is sent. Existing credit-pull recovery remains available when returning to the Applicant after adding funds.

Changing the fallback teammate replaces the saved fallback email and mobile with that teammate’s available details. Missing details are cleared so alerts cannot go to the previous recipient. Review these fields before saving.

**Processing complete** has its own email toggle in Team alerts. It starts on when the Notifications overhaul is enabled in Labs. The email goes to the submitting Operator, using the existing fallback recipient when needed. You can preview the Funding Machine template in Team alerts. It confirms that processing is finished and directs the Operator to the client’s file; it does not confirm lender approval or receipt of funds.

Turn the toggle off and choose **Save team alerts** to stop these emails. Queued emails check the saved setting again before sending. Turning it back on allows future processing-complete emails; skipped emails are not replayed. This toggle is independent of document-upload channels and client-email settings. Disabling the Labs feature restores the existing processing-complete template and behavior.

## Messages sent from a workflow

Document requests, application links, and funding plans remain explicit workflow actions. Global client automation pauses do not replace these manual actions.

* **Document requests:** both upload-link email buttons use the shared checklist, actual expiration time, and reply-for-help template while Labs is enabled. Generating a link alone never sends email. See [Request documents](/operators/funding/document-upload-links).
* **Application links:** the message asks the Applicant to check the prefilled details, complete missing fields, review the disclosures, and submit. It does not promise an offer.
* **Funding plans:** the message lists the plan options, amounts, statuses, and selected next steps. Edits in the funding-plan email composer are reflected in the HTML sent to the client.
* **Freeform texts:** the Text Client action remains a message you compose explicitly.
* **Message Client emails:** when you send from your own Location, the email goes out as you. The `{{user.email_signature}}` line at the end becomes your CRM profile signature, with its formatting; edit or remove it before sending. When you start from a template this way, your signature replaces the template's business-name sign-off. Automatic notifications keep the business-name sign-off.

## Activity and delivery problems

Activity respects your assigned-contact access and shows up to the latest 100 automated client messages, including queued, awaiting review, sent, skipped, and failed messages. **Sent to CRM** means the CRM accepted the message. It does not confirm delivery to the recipient. Manual messages remain in the client’s CRM conversation.

Skipped messages explain conditions such as a paused channel, missing address, opt-out, or a changed result. If a provider response is uncertain, automatic replay is blocked to avoid duplicate messages. Check the CRM conversation before deciding whether to send manually.

## Turn the feature off

Turn off **Notifications overhaul** in Labs to restore the original settings pages and result rules. New-workspace sends that have not started dispatch are stopped when Labs is disabled. A message already accepted by the CRM cannot be recalled.

New rules, review items, and history are retained. Turning Labs back on restores those settings. Pending review items can be reviewed after re-enabling; skipped automatic messages are not replayed just because the feature was re-enabled. Shared client settings and document-upload team preferences are the same underlying settings in both experiences, so changes to those preferences persist.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.