User Permissions Needed
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:- 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
VisitsFilters
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:- In the report builder, click the arrow next to Columns, and then click Add Row-Level Formula.
-
Name the column
Completed (%), and set the output type to Number with 0 decimal places. -
Enter the formula, inserting Status from the field list:
- Click Apply. On the Completed (%) column, click the arrow, click Summarize, and then select Average.
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
VisitsFilters
Group By
- Reason For Incompletion
- 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.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”.
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 OrdersFilters
Group By
Sales RepresentativeColumns and Summary Formulas
Add Subject, Account, FieldKo Order Name, and Order Amount. Then add a row-level formula namedHas Order, with output type Number:
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.
- 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.