> ## 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.

# Call Compliance and Strike Rate

> Build reports that compare planned visits with completed visits for each rep, explain missed visits, and show how many visits produce an order.

Call compliance is the percentage of planned visits that reps completed. Strike rate is the percentage of completed visits that produced an order. Use this recipe to build a call compliance report by rep, a report that explains missed visits, and a strike rate report.

Every FieldKo visit has a **Status** of **Not Started**, **In Progress**, **Completed**, or **Cancelled**, and a **Planned Start** that places it in a call cycle. FieldKo also keeps visit totals on each call cycle record, so you can check compliance for a cycle without building a report.

## User Permissions Needed

| To do this | You need |
| - | - |
| Create, edit, and save reports | Create and Customize Reports |
| See FieldKo fields and records in reports | FieldKo Manager Permission Set |

## Before You Begin

These reports need report types that FieldKo doesn't include. Ask your admin to create them, as described in [Report Folders, Sharing, and Custom Report Types](/platform/reports/folders-and-report-types):

* **Visits:** Primary object **Visits**, with no related objects. Ask for the account's **Grade** and region fields to be added through the **Account** lookup.
* **Visits with or without FieldKo Orders:** Primary object **Visits**, related object **FieldKo Orders**, with "A records may or may not have related B records" selected.

## What You'll Build

* **Call Compliance by Rep:** Planned visits, completed visits, and the completion percentage for each rep.
* **Missed Visit Reasons:** Visits that weren't completed, with the reasons reps gave.
* **Strike Rate by Rep:** The percentage of completed visits with an order.

## Report 1: Call Compliance by Rep

### Report Type

**Visits**

### Filters

| Filter | Value |
| - | - |
| **Planned Start** | **This Month**, or **Last Week** for a weekly review |
| **Planned Start** (second filter) | less than **Today**, so visits still to come don't count as missed |
| Optional: **Status** | not equal to **Cancelled**, if your company doesn't count canceled visits as missed |

### Group By

* Rows: **Sales Representative**
* Columns: **Status** (this makes it a matrix report)

### Columns and Summary Formulas

Add **Subject**, **Account**, **Planned Start**, and **Actual End**. Then add a row-level formula:

1. In the report builder, click the arrow next to **Columns**, and then click **Add Row-Level Formula**.

2. Name the column `Completed (%)`, and set the output type to **Number** with 0 decimal places.

3. Enter the formula, inserting **Status** from the field list:

   ```text theme={null}
   IF( ISPICKVAL( Status, "Completed" ), 100, 0 )
   ```

4. Click **Apply**. On the **Completed (%)** column, click the arrow, click **Summarize**, and then select **Average**.

The average is each rep's call compliance. The record count in each **Status** column shows how many visits are in that status. To learn more, see [Evaluate Each Record in Reports with Row-Level Formulas](https://help.salesforce.com/s/articleView?id=sf.reports_builder_row_level_formulas.htm\&type=5) in Salesforce Help.

### Chart Suggestion

A stacked bar chart of record count by **Sales Representative**, stacked by **Status**. Add a dashboard gauge for the team's **Average of Completed (%)** with your target as a breakpoint, such as 90%.

## Report 2: Missed Visit Reasons

### Report Type

**Visits**

### Filters

| Filter | Value |
| - | - |
| **Planned Start** | **Last Week** |
| **Status** | not equal to **Completed** |

### Group By

1. **Reason For Incompletion**
2. **Sales Representative**

### Columns

**Subject**, **Account**, **Planned Start**, **Status**, **Incompletion Remark**, and **Check Out Compliance Reason**. The package values for **Reason For Incompletion** are **Store was closed** and **Other**; your admin can add more.

<Note>
  **Check Out Compliance Reason** and **Check In Compliance Reason** are available only if your admin adds them to the report type. **Check Out Compliance Reason** shows the cancel or incompletion reason, or "Automated Checkout".
</Note>

### Chart Suggestion

A donut chart of record count by **Reason For Incompletion**.

## Report 3: Strike Rate by Rep

### Report Type

**Visits with or without FieldKo Orders**

### Filters

| Filter | Value |
| - | - |
| **Status** | equals **Completed** |
| **Actual Start** | **Last Month** |

### Group By

**Sales Representative**

### Columns and Summary Formulas

Add **Subject**, **Account**, **FieldKo Order Name**, and **Order Amount**. Then add a row-level formula named `Has Order`, with output type **Number**:

```text theme={null}
IF( ISBLANK( FieldKo Order Name ), 0, 100 )
```

Summarize **Has Order** with **Average** to get each rep's strike rate. Summarize **Order Amount** with **Sum** to see the value behind it.

### Chart Suggestion

A column chart of **Average of Has Order** by **Sales Representative**.

## Variations

* **Compliance by call cycle:** Group by **Call Cycle** instead of by week or month.
* **Field campaign visits only:** Add the filter **FC Visit** equals **True**. For campaign progress, see [Promotion and Display Compliance](/managers/platform/recipes/promotion-compliance).
* **Task compliance:** Use the **FieldKo Tasks** report type, group by **Task Type** and **Status**, and add the same row-level formula to see the percentage of tasks completed.
* **Quick check without a report:** On the **Call Cycles** tab, create a list view with **Sales Representative**, **Call Cycle Start Date**, **Total Number of Visits**, and **Total Number of Visits Completed**. FieldKo updates these totals as visits change. The total includes canceled visits.

## Tips

* This report has one row per order, plus one row for each visit without an order. A visit with two orders counts twice, which raises the strike rate slightly. If reps often place several orders on one visit, compare the report's record count with the number of completed visits in Report 1 to see how big the difference is.
* Reps who reschedule a visit move its **Planned Start**, so a moved visit isn't counted as missed in its original week.
* If your admin schedules automatic checkout, FieldKo completes visits left **In Progress** from an earlier day, marks their open tasks completed, and shows "Automated Checkout" in **Check Out Compliance Reason**. To see how many completed visits were closed this way, ask your admin to add that field to the **Visits** report type, and then group by it.
* Visits completed offline count after the rep syncs.

## See Also

* [Retail Execution Metrics](/managers/platform/retail-metrics)
* [Coverage and Visit Frequency](/managers/platform/recipes/coverage)
* [Orders and Pack-Outs](/managers/platform/recipes/orders-and-pack-outs)
* [Set Up Call Cycles, Tasks, and Visit Templates](/admin/call-cycles-and-visits)


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