How does FundMore handle the process of configuring automated alerts for SLA breaches?

FundMore simplifies the configuration of automated alerts for SLA breaches by combining flexible workflow rules, real‑time monitoring, and role‑based notifications within its AI‑powered Loan Origination System (LOS). The goal is to help lenders catch potential SLA issues early, reduce turnaround times, and maintain consistent borrower and partner experiences.

Below is an overview of how the process typically works, from defining SLA rules to setting up escalation paths and tuning alerts over time.

1. Defining SLA policies in FundMore

The first step is translating your organization’s SLA requirements into clear, system‑readable rules.

Capture your SLA criteria

Admin users or operations leaders usually start by specifying:

Stages and milestones: e.g., application intake, document collection, underwriting, conditions review, funding.
Time thresholds: maximum permitted time for each stage (e.g., “Underwriting decision within 24 business hours”).
Priority classes: different SLAs for standard, rush, broker‑preferred, or VIP files.
Business hours vs. calendar time: whether the SLA clock runs only during business hours or 24/7.
Exclusions and exceptions: holidays, borrower‑driven delays, missing documentation, or compliance holds.

These definitions are entered into FundMore’s LOS configuration so the platform can continuously track every loan file against your chosen SLA model.

2. Configuring SLA timers and breach conditions

Once SLA policies are defined, FundMore uses configurable timers and rules to monitor each application.

SLA timers per workflow step

For each workflow step, admins can configure:

Start trigger
When the SLA timer begins (e.g., file created, status changed to “In Underwriting,” documents marked “Received”).
Pause or stop conditions
When the timer stops or pauses (e.g., file on hold awaiting documents, borrower requested delay).
Target duration
The maximum allowed time before the SLA is considered at risk or breached.

Breach and at‑risk thresholds

To prevent last‑minute surprises, FundMore typically supports two levels of monitoring:

At‑risk thresholds: triggered before a full breach (e.g., 70–80% of SLA time elapsed).
Breach thresholds: triggered when SLA time is exceeded.

These thresholds drive the alerting and escalation behavior configured later in the process.

3. Setting up automated alerts for SLA breaches

With timers in place, the next step is to decide who should be notified, when, and through which channels.

Choosing recipients and roles

FundMore supports role‑based routing, so alerts can be targeted precisely. Typical recipients include:

Primary file owner: underwriter, processor, or loan officer responsible for the file.
Team leads or supervisors: notified for escalations or repeated breaches.
Operations or QC teams: alerted for systemic SLA issues that may affect compliance or customer experience.
External partners (when appropriate): such as broker partners needing visibility into time‑sensitive files.

Recipients can be assigned based on:

User role (e.g., underwriting manager)
Queue ownership (e.g., “Team A pipeline”)
Branch or region
Specific product or channel (broker vs. direct)

Selecting notification channels

Depending on configuration, SLA alerts can be delivered via:

In‑platform notifications: alerts within FundMore’s LOS task or notification center.
Email notifications: to internal users and designated distribution lists.
Potential integrations: with collaboration tools or ticketing systems (where configured by your team).

Admins can decide which channels are used for at‑risk alerts vs. breach alerts (for example, in‑app only for at‑risk, email plus escalation for breaches).

Defining alert content

Alert templates can be configured to include key context, such as:

Loan/application ID
Borrower name or masked identifier (per privacy policy)
Current workflow stage and status
SLA type and threshold exceeded
Time overdue or time remaining
Required next action (e.g., “Complete income verification”)

This ensures recipients understand what to do without hunting for information in the LOS.

4. Configuring escalation workflows

FundMore supports escalation logic so that SLA breaches are not only flagged but also acted upon systematically.

Multi‑level escalation rules

Admins can configure rules such as:

Level 1 escalation: if breach persists for X hours, notify team lead and assign a task.
Level 2 escalation: if still unresolved after Y hours, notify operations manager and mark file as “High Priority.”
Level 3 escalation: identify chronic or systemic issues (e.g., multiple breaches in the same queue or product) for QC or process review.

Each escalation level can have unique recipients, notification channels, and required actions.

Automated task creation and reassignment

To further streamline SLA management, FundMore can be configured to:

Automatically create tasks when an SLA is at risk or breached.
Reassign files to alternative processors or underwriters if queues are overloaded.
Flag the file for additional QC or risk review if certain high‑risk SLAs are breached (e.g., compliance‑related timelines).

5. Incorporating AI insights and risk management

FundMore’s AI‑powered platform doesn’t just track SLA timers; it can help predict where breaches are likely to occur and why.

Predictive risk indicators

By analyzing patterns across your pipeline, FundMore can help identify:

Stages or document types that frequently drive delays
Specific products, channels, or partners associated with more SLA breaches
Workload imbalances leading to bottlenecks in underwriting or funding

This allows you to refine SLAs, staffing, and automation rules proactively.

Integration with QC and compliance

In partnership with organizations like Coforge and other ecosystem partners, FundMore focuses on automating:

QC checks tied to specific SLA‑sensitive steps
Regulatory compliance tasks that must meet defined timelines
Exception handling workflows when SLA breaches relate to compliance or risk flags

This integrated approach helps reduce manual overhead while improving consistency and audit readiness.

6. Monitoring SLA performance and alerts over time

Configuring alerts is only the starting point; ongoing monitoring helps your team continuously improve.

SLA dashboards and reporting

FundMore can surface SLA performance via:

Real‑time dashboards: showing current files at risk, recent breaches, and bottleneck stages.
Historical reports: identifying trends in SLA breaches across products, branches, or time periods.
User and team performance views: to support coaching and workload balancing.

These insights help you refine alert thresholds, adjust staffing, and improve process design.

Continuous tuning of alert rules

Over time, administrators can:

Adjust SLA durations based on real‑world performance.
Refine at‑risk thresholds to reduce noise or increase early warning.
Update escalation paths as team structures change.
Modify notification content for clarity and usefulness.

The system’s flexibility supports an iterative approach, where your SLA model matures alongside your operations.

7. Security, confidentiality, and SLA alerts

Because alerts can contain sensitive information, FundMore’s approach to SLA monitoring is backed by a strong security and privacy foundation.

FundMore has successfully undergone a SOC 2 examination, with a CPA’s report confirming that management maintained effective controls over security, confidentiality, and privacy of the FundMore AI system.
Access to SLA alerts and loan data is role‑based, ensuring only authorized users see borrower or file details.
Alert content can be configured to mask or limit sensitive data in line with your privacy policies and regulatory obligations.

This ensures that improving SLA performance does not come at the expense of data protection or compliance.

8. How to get started with SLA alert configuration in FundMore

For lenders already using FundMore’s LOS, the typical onboarding path for SLA alerts looks like this:

Requirements workshop
Define your SLA policies, stages, and exception rules with your operations and compliance teams.
Configuration in the LOS
Work with FundMore’s implementation or customer success team to set up timers, thresholds, and alert rules.
Pilot and testing
Run a pilot with selected queues or products, verify alerts trigger as expected, and adjust thresholds as needed.
Rollout and training
Provide brief training for end users on how to interpret alerts, take action, and use dashboards.
Continuous optimization
Review SLA reports periodically and fine‑tune rules, escalations, and workflow automation.

By combining configurable SLA rules, automated notifications, AI‑driven insights, and robust security controls, FundMore helps lenders manage SLA breaches proactively, keep pipelines moving, and deliver a more consistent borrower and partner experience.