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

# Notifications and Email Alerts

> Understand the notifications and emails FieldKo sends, and build your own custom notifications and email alerts with Flow.

FieldKo already sends several notifications and emails, such as alerts for missed check-ins and visit summary PDFs, and you can add your own with Salesforce Flow. Use this page to see what FieldKo sends, what turns each one on, and how to build your own custom notifications and email alerts without overloading reps or managers.

## User Permissions Needed

| To do this | You need |
| - | - |
| Change FieldKo custom settings | Customize Application permission |
| Create custom notification types and email alerts | Customize Application permission |
| Create flows | Manage Flow permission |

## What FieldKo Sends

The packages don't send any of these until you turn them on. Most of them need a scheduled job. See [Scheduled Jobs](/admin/installation#scheduled-jobs).

| Notification | Who Gets It | What Turns It On |
| - | - | - |
| Missed check-in and check-out alerts in Salesforce | The visit's owner, which is the rep | **Enable Visit Reminders On Backend** and **Enable Visit Checkin Checkout Reminders**, and the `MissedVisitCheckInScheduler` job |
| Visit reminders in the FieldKo Atlas app | The rep, on their device | **Enable Visit Checkin Checkout Reminders** and **Enable Visit Reminders On Mobile** |
| Visit summary PDF emails | The rep and the account owner | The `VisitSummaryPdfSchedular` job and an email template |
| Order PDF emails | The order's contact | The `SendOrderMailsSchedular` job |
| Chatter posts on check-in and check-out | Followers of the account's Chatter feed | **Post Checkin - Checkout Feed On Account** (on after install) |
| Field campaign visit emails | Reps who get campaign visits | **Notify Rep on Visit Planning using Field Campaign** on the **FieldKo Configuration** tab |

### Missed Check-In and Check-Out Alerts

FieldKo includes the **Visit Check in Checkout notification** custom notification type, with the desktop and mobile channels turned on. When `MissedVisitCheckInScheduler` runs, every 15 minutes if you use its helper method, FieldKo looks at today's visits:

* **Check-in missed:** The visit is still **Not Started** after its planned start plus the reminder delay.
* **Check-out missed:** The visit is still **In Progress** after its planned end plus the reminder delay.

The notification shows the visit name with its planned start and end, and opens the visit. FieldKo sends each type of alert only once per visit.

Set these fields in the **Visit Configurations** custom setting:

* **Visit Reminder Delay Minutes:** The minutes after the planned start or end before a visit counts as missed. It's 30 if blank.
* **Missed Visit Notification Type Name:** Optional. The API name of your own custom notification type, if you want to use one instead of FieldKo's.

These alerts appear in Salesforce, in the notification bell and in the Salesforce mobile app if a rep uses it. They don't appear in the FieldKo Atlas app, which schedules its own reminders on the device. See [Get Visit Reminders](/visits/reminders).

### Visit Summary PDF Emails

FieldKo creates a PDF for each completed visit, saves it to the visit and the account, and emails it to the rep and the account owner. It needs an email template with the developer name `Visit_Summary_Template`. To limit which visits get PDFs, set **Summary PDF Start Date** and **Summary PDF End Date** in the **Visit Configurations** custom setting. See [Get Visit Summary PDFs](/managers/monitor-your-team#get-visit-summary-pdfs).

### Order PDF Emails

`SendOrderMailsSchedular` emails each FieldKo order's PDF to the order's **Ship To Contact**, once the order's PO date has arrived and all its order lines have synced. Salesforce limits single emails to 1,000 per day, so on busy days some order emails wait for a later run. See [Emailing Orders](/admin/products-ordering-ranging#emailing-orders).

### Chatter Posts

When **Post Checkin - Checkout Feed On Account** is on in the **Visit Configurations** custom setting, FieldKo posts each check-in and check-out to the account's Chatter feed. Turn it off if the posts are noise for your team. See [Visit Configurations](/admin/configuration-reference#visit-configurations).

## Build Your Own Notifications

When FieldKo's built-in notifications don't cover what you need, such as a manager alert for a failed compliance check, send your own from a flow. For examples, see [Flow Recipes for Field Teams](/platform/automate/flow-recipes).

| Option | Best For | Notes |
| - | - | - |
| Custom notification | Short, timely alerts to managers or account owners in Salesforce | Appears in the notification bell and the Salesforce mobile app. Doesn't use email limits. |
| Email alert | Messages to people outside Salesforce, or that need a formatted template | Uses an email template. Counts toward your org's email limits. |
| Chatter post | Updates the whole team should see on a record | Use the **Post to Chatter** action. |

### Send a Custom Notification

Create a notification type once, and then use it in any flow:

1. From Setup, in the Quick Find box, enter `Custom Notifications`, and then select **Custom Notifications**.
2. Click **New**, enter a name, and select the **Desktop** and **Mobile** channels.
3. In your flow, add a **Send Custom Notification** action. Select the notification type, and set the recipients, title, body, and target record.

For more, see [Custom Notifications](https://help.salesforce.com/s/articleView?id=sf.notif_builder_custom.htm\&type=5) in Salesforce Help.

### Send an Email Alert

Create an email template and an email alert on the object, and then call the alert from your flow with its action. For more, see [Email Alerts](https://help.salesforce.com/s/articleView?id=sf.customize_wfalerts.htm\&type=5) in Salesforce Help.

### Keep Notifications Useful

Reps sync many records at once, so a flow that notifies on every record can send a burst of alerts after one sync:

* **Notify on exceptions only,** such as a failed compliance answer or an out-of-stock on a must-stock product, not on every survey answer or order.
* **Send from an asynchronous path,** so a notification that fails can't block the rep's record. See [Keep a Failing Flow from Failing a Rep's Sync](/platform/automate/design-automation#keep-a-failing-flow-from-failing-a-reps-sync).
* **Summarize on a schedule** when managers need an overview, for example a daily scheduled flow or a report subscription, instead of one alert per record. See [Share, Schedule, and Subscribe to Reports](/managers/platform/share-and-schedule).

<Note>
  Email alerts and emails sent from flows count toward your org's daily email limits, together with FieldKo's order and visit summary emails. For your org's limits, check your Salesforce contract or ask your Salesforce account executive.
</Note>

## See Also

* [Get Visit Reminders](/visits/reminders)
* [Install and Set Up FieldKo](/admin/installation#scheduled-jobs)
* [Flow Recipes for Field Teams](/platform/automate/flow-recipes)
* [Design Automation for FieldKo](/platform/automate/design-automation)
* [Track Your Team's Performance](/managers/monitor-your-team)


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