Overview
Field Pro v2 includes reports that turn recordings into coaching decisions. Instead of listening to calls one at a time to find a pattern, you read the pattern first, then open only the recordings that prove it.
Field Pro v2 has five reports, under Field Pro > Reports:
Objections: which objections your team hears most, how often, and how often the team still closes.
Recording Health: what happened to each completed Appointment, from recording to score.
Tech Engagement: how your technicians use Field Pro after a Call: listening, commenting, and asking Atlas.
Manager Engagement: the same view for managers and other office users.
Recording Usage: your recording rate, and the reasons appointments weren't recorded.
Objections tells you what to coach. The engagement reports tell you whether people are using the coaching. Recording Health and Recording Usage tell you how complete your data is.
Where Field Pro v2 reports live
On the ServiceTitan desktop, go to Field Pro, then select a report under Reports.
Field Pro data in ServiceTitan's standard reports
Field Pro data also appears in ServiceTitan's standard reports: Field Pro: Job Recordings and Field Pro: Technician Recording Performance. To see jobs that weren't recorded, build a report on the Jobs dataset and add Field Pro: Job Recordings.
Who can see the reports
Managers need the View Field Pro permission to open the reports. If a manager can't see a report, check their role's permissions.
Team access shapes what you see
Every report shows only the teams you have access to. All Teams means all of your teams. Team access is set in Field Pro settings; see Field Pro v2 Settings, Permissions, and Teams.
Filters
Every report has a Team filter and a Lookback filter. Lookback offers the last 7, 14, 30, 60 or 90 days, month to date, or a custom range of up to 90 days. The default is the last 30 days. Totals show the change from the previous period of the same length.
Each report also has Ask Atlas, which already knows the report, team and period you're looking at.
Objections report
What the report shows
Top Objections lists your eight most common objections for the period, with:
Count: how many recordings it came up in.
% of Rec.: that count as a share of all your completed recordings.
Read both. A count tells you volume; a percentage tells you whether that volume is actually common or just a reflection of how much your team recorded that period.
What the report depends on
The report counts signals tagged Objection. An objection is only counted on a recording if that signal is on the recording profile the recording used. New recording profiles start with the objection signals selected, but they can be removed, and changing which signals start selected only affects profiles created afterward.
If the report is empty, or an objection is missing, check your recording profiles before assuming the objection never came up.
Trend lines
Objection Trend shows how often each objection comes up, as a share of recordings, by day (for periods of 14 days or less) or by week. It starts with all objections; use the picker to focus on the ones you care about.
A rising objection usually means something changed, such as pricing, the market, a script or a new hire, and your current handling may need work.
Close Rate by Objection
Close Rate by Objection shows the close rate on jobs where each objection came up, lowest first, so the objections your team struggles to overcome are at the top. Jobs that are still open aren't counted. It shows outcomes, not causes.
Reading frequency and close rate together
Read the two together. An objection your team hears often but still closes is one they handle well; save examples for training. An objection that comes up often and rarely closes is your best coaching target.
Open the recordings behind an objection
Select an objection name in Top Objections. Recordings opens in a new tab, filtered to that objection, with the same dates and team.
The Objections report filters by team, not by technician. To see one technician's objections, open the objection's recordings and filter by user.
Turn examples into a coaching playlist
In a recording, select the transcript text you want and choose Add to playlist. Two or three examples of the same objection, one handled well and one not, make a good one-on-one or team meeting. Playlists are private until you share them with Team Visibility. See Manage Team Performance in Field Pro v2: Dashboards, Recordings, and Coaching for how to build and share playlists.
Related: watch a specific objection over time
To keep an eye on one objection between report reviews, set up a signal watch on the signal that detects it. Your watch flags matching recordings and adds Signal actions to your own Manager Console. See Set Up and Use Signal Watch in Field Pro v2.
Tech Engagement report
Why engagement matters more than recording volume
Recording volume tells you that calls are being captured. It tells you nothing about whether anyone learned from them.
The Tech Engagement report tracks what technicians do after a recording exists: listening to their own and others' calls, commenting, and asking Atlas. Teams get the most from Field Pro when managers and technicians both use the recordings regularly.
Metrics tracked
The report shows:
Recordings Listened To: different recordings listened to.
Minutes Listened.
Comments Posted.
Atlas Chat Coaching Interactions: messages technicians sent to Atlas.
Day In Review: how often technicians viewed their Day in Review.
The table also shows Recordings Viewed: how many times technicians opened a recording.
Engagement by Tech
Below the summary cards, a table breaks every metric down by technician. This is where you find the technician who has not listened to a single recording this period, or the one whose minutes listened dropped sharply after a strong stretch.
Scan for two things: zeros, and direction changes. A zero is a conversation about expectations. A drop is a conversation about what changed.
The table includes every technician on the selected teams who has Field Pro, including those with no activity.
Follow one engagement area over time
Engagement Trend plots one metric at a time. Use its picker to choose which one, such as Minutes Listened or Comments Posted.
This is the right view when you have made an ask of the team and want to know whether it stuck.
Recording Health report
Recording Health shows what happened to your completed appointments, from recording through scoring. Use it when technicians aren't recording or recordings aren't getting scored.
The top shows completed Appointments, Scored appointments, and Unknown. The Funnel follows appointments step by step, from the app and microphone access through consent, recording, upload and processing, to a scored recording. It shows where appointments drop off along the way, for example when consent wasn't given or the appointment was canceled.
Unknown counts appointments where Field Pro saw part of the recording process but not how it ended. For example, ST Field reported that a recording started or finished, but nothing after that, or processing began without a result. Field Pro can't tell whether those appointments ended up recorded, so it doesn't count them as scored or as a drop-off.
Filter by team, technician and lookback. Days are counted in UTC, so totals can differ slightly from other ServiceTitan reports.
Recording Usage report
Recording Usage shows how much your team records.
Recording Rate: the share of completed appointments that were recorded.
Recordings: recordings that can be scored.
Total Appointments and Total Recording Minutes.
Each total shows the change from the previous period. Below them:
Recording Rate by Team.
Recordings by Team, or by technician. Turn on Include techs with 0 recordings to find technicians who aren't recording at all.
Reasons for Not Recording, such as completed but not scored, consent declined, canceled, manually stopped, or not linked to an appointment.
Manager Engagement report
Manager Engagement works like Tech Engagement, for managers and other office users. It shows Recordings Viewed, Recordings Listened To, Minutes Listened, Comments Posted, Atlas Chat Interactions, Suggested Actions Completed and Suggested Actions Dismissed, with a breakdown by person.
Decide what to coach first
A practical weekly or monthly rhythm using these reports:
Open the Objections report. Find the objection with a high count and a low close rate in Close Rate by Objection. That is your coaching target.
Click through to the filtered recordings. Listen to two or three. Confirm the pattern is what the data suggests.
Build a playlist of the clearest examples.
Coach it in a one-on-one, a team meeting, or a comment on a specific recording.
Open Tech Engagement the next period. Check whether the technicians you coached listened, commented or asked Atlas. If they didn't, follow up with them directly.
Recheck the Objections report trend line for that objection. Falling frequency or a rising close rate is your evidence that it worked.