Understanding AI Suggestion Cards
When AI Dispatcher analyzes unassigned jobs and generates recommendations, each suggestion appears as a detailed card on your calendar. These cards aren't simple notifications β they're decision-support tools packed with context to help you quickly evaluate whether to accept, reject, or modify each assignment.
In this guide:
How to read suggestion cards and confidence scores
What each decision factor means in practice
When to accept, reject, or explore alternatives
Real-world scenarios from HVAC, plumbing, and electrical dispatching
Anatomy of a Suggestion Card
When you hover over an AI suggestion block on the calendar, the detail card reveals multiple layers of information organized into distinct sections:
Header Section
The card header displays:
Job number and customer name β Quick identification
Blue "AI Suggestion" badge β Distinguishes from manual assignments
"PENDING CONFIRMATION" status (orange) β Requires your action
Accepted suggestions show a green "ACCEPTED" status instead.
Time Information
Every suggestion displays two critical time windows:
π€ AI Scheduled Time
When the AI recommends scheduling based on optimal routing, technician availability, and workload balancing. You'll see:
Suggested start and end times
Total duration
Estimated travel time from previous job
π€ Customer Preferred Time
The original time window requested when booking. The AI may suggest scheduling outside this window if it detects conflicts or identifies a more efficient alternative β but the customer's preference is always visible so you can make informed decisions.
β οΈ Key Signal: Large gaps between AI scheduled time and customer preferred time (e.g., scheduling at 2 PM when customer requested 9 AM) usually indicate the AI detected constraints. These warrant closer review and often require a customer callback.
Technician Assignment
The "Assigned To" row displays the technician the AI selected (with profile avatar and name). This technician was chosen based on:
Skills match for the job type
Proximity to the job site
Current workload and capacity
Route efficiency
To understand why this specific technician was selected, expand the reasoning panel (covered below).
Location Details
The location row shows the job site address. This is particularly important when reviewing travel time estimates β you can quickly verify whether the suggested routing makes geographic sense.
Understanding Confidence Scores
Every AI suggestion includes a confidence score β a percentage from 0-100% that represents how optimal the assignment is. This isn't a guess β it's a weighted calculation across multiple decision factors.
Click the "Why this assignment?" panel to expand the detailed confidence breakdown.
The Five Decision Factors
The confidence score is built from five weighted factors:
1. Skills Match (35% weight) π§
Does the technician have all required certifications and skills for this job type?
Perfect match: 100% β All required skills present
Partial match: 60-80% β Most skills present, minor gaps
Poor match: Below 50% β Critical skills missing
Example: Emergency furnace repair requires EPA 608 certification and HVAC diagnostics experience. A technician with both scores 100%. One with EPA 608 but limited furnace experience might score 75%.
2. Proximity (25% weight) π
How far is the technician from the job site? This considers actual driving time, not straight-line distance.
Very close: 0-15 minutes travel time
Moderate: 16-30 minutes
Far: 31+ minutes
Example: If your electrical tech is wrapping up a panel upgrade in Downtown and the next job is a circuit breaker replacement 8 minutes away in the same neighborhood, proximity scores 95%+.
3. Availability (20% weight) β°
Does the suggested time slot align with both technician availability and customer preferred time?
Perfect alignment: 100% β Both conditions met
Partial match: 70% β Technician available but customer preference missed
Conflict: Below 50% β Scheduling compromises required
Example: Customer requested 9-11 AM for a water heater installation. Technician is available 9-11 AM with no conflicts = 100%. If the only available slot is 2-4 PM, score drops to ~65%.
4. Workload (10% weight) π
How busy is the technician already? Displays current job count and total hours scheduled for the day.
Light load: Below 60% capacity
Moderate: 60-80% capacity
Heavy: 80%+ capacity (scores lower to prevent overloading)
Example: Technician has 4 jobs totaling 6 hours in an 8-hour shift = 75% utilization. Adding a 2-hour job would push them to 100%, so workload scores around 60%.
5. Route Efficiency (10% weight) πΊοΈ
Does this job fit logically into the technician's daily route, or does it force backtracking?
Optimal: 90%+ β Job flows naturally in sequence
Moderate: 70-89% β Minor detour required
Poor: Below 70% β Significant backtracking
Example: Your plumber's route goes: North End (8 AM) β Midtown (10 AM) β South Side (1 PM). A new drain cleaning job on the South Side at 2:30 PM scores high. A job back in the North End at 2:30 PM scores low (forces backtracking).
π‘ Pro Tip: Each factor displays a color-coded status (excellent/good/moderate/poor) and a progress bar. The overall confidence is the weighted sum of all factors.
Interpreting Confidence Levels
Confidence Range | Indicator | What It Means | Recommended Action |
85-100% | π’ Green | Excellent match. Skills align perfectly, minimal travel, no conflicts, efficient routing. | Accept with confidence. Minimal review needed. |
70-84% | π΅ Blue | Good match. Minor trade-offs (slightly longer travel or moderate workload). | Review specific factors to understand compromises. |
50-69% | π Orange | Acceptable with caveats. Notable compromises present. | Inspect closely. Consider alternatives. |
Below 50% | π΄ Red | Suboptimal assignment. Significant concerns exist. | Always review reasoning. Check alternatives before accepting. |
Reading the AI Reasoning Panel
Below the confidence score breakdown, the reasoning panel displays two critical sections:
β Key Strengths
This section lists the primary reasons why this assignment is recommended. You'll see statements like:
"Technician has all required HVAC certifications"
"Only 12 minutes from previous job location"
"Available during customer preferred time window"
"Creates efficient route with minimal backtracking"
Each strength is marked with a green checkmark. These are the positive factors that drove the AI's decision.
β οΈ Considerations (Concerns)
If the AI detected any potential issues or trade-offs, they appear here with orange warning icons. Common concerns include:
"Technician workload approaching 85% capacity today"
"Scheduled outside customer preferred time window by 2 hours"
"Travel time higher than average for this service area"
"Skills match but technician less experienced with this job type"
Important: Concerns don't necessarily mean the assignment is bad β they're flags for you to review with your operational context. For example, scheduling outside the customer preference might be necessary if all technicians are booked during the requested window, but you'll want to call the customer for approval.
Real-World Example: HVAC Emergency Call
Scenario: Emergency AC repair during a heatwave. Customer requested 2-4 PM, but all certified HVAC techs are booked.
AI Suggestion:
Assigned: Mike (HVAC certified, EPA 608)
Confidence: 72% (Blue - Good)
Scheduled: 5-7 PM (3 hours after customer preference)
Key Strengths:
β Perfect skills match (EPA 608, 5 years AC experience)
β Only 18 minutes from previous job
β Fits route efficiently (final job of the day)
Considerations:
β οΈ Scheduled 3 hours outside customer preferred window
β οΈ Mike already at 80% workload for the day
Your Decision: Accept the suggestion but call the customer immediately to explain the delay. Emergency AC during heatwave = they'll likely accept same-day service even if it's evening.
Detecting and Understanding Conflicts
Some AI suggestions may display a conflict indicator in the footer. When conflicts are detected, the system shows detailed breakdowns:
Types of Conflicts
π΄ Time Overlap (CRITICAL)
The suggested job overlaps with an existing appointment.
Shows: Exact overlap start/end times and duration in minutes
Action: Must be resolved before accepting
Example: AI suggests scheduling a 2-hour drain cleaning from 10 AM - 12 PM, but technician already has a pipe repair from 11 AM - 1 PM. Conflict: 1-hour overlap (11 AM - 12 PM).
π Impossible Travel (WARNING)
The technician cannot physically travel from their previous job to this one in the available time.
Shows: Required travel time vs. available time, distance, estimated late arrival
Action: Adjust schedule or reassign
Example: Previous job ends at 2 PM in North County. Next job starts at 2:15 PM in South County. Actual drive time: 35 minutes. Technician would arrive 20 minutes late.
π΅ Outside Time Window (INFO)
The suggested schedule falls outside the customer's preferred window.
Shows: Customer's requested time range, actual scheduled time, deviation in hours/minutes
Action: Review and decide if customer callback is needed
Example: Customer requested 9-11 AM. AI scheduled 1-3 PM. Deviation: 4 hours. Call customer for approval.
π¨ Critical Rule: Never accept CRITICAL (red) conflicts without resolving the underlying issue. These indicate scheduling impossibilities that will cause real problems in the field.
Exploring Alternative Assignments
Not confident about the suggested assignment? Click the "Reassign" button to see alternative technician options ranked by confidence score.
Each alternative displays:
Technician name and avatar
Alternative confidence score
Current utilization percentage (workload)
Suggested start time for this technician
Trade-offs β specific compromises compared to the primary suggestion
The top alternative is marked "Recommended" and represents the second-best option.
Example: Comparing Alternatives
Job: Pool pump installation requiring electrical and plumbing skills
Primary Suggestion:
Tech: Sarah (electrician + basic plumbing)
Confidence: 78%
Start: 10 AM
Travel: 12 minutes
Alternative #1 (Recommended):
Tech: Carlos (master plumber + electrical certified)
Confidence: 82%
Start: 1 PM
Travel: 25 minutes
Trade-off: "15 minutes farther travel, but higher skill level for pool systems"
Alternative #2:
Tech: Mike (electrician only)
Confidence: 62%
Start: 11 AM
Travel: 8 minutes
Trade-off: "Closer but lacks plumbing certification β would need partner tech for water connections"
Best Choice: Carlos (Alternative #1) β Higher confidence due to perfect skill match, even though travel is longer. Pool pump installations are complex and benefit from dual expertise.
π‘ Remember: Alternatives are ranked by weighted confidence, not just proximity. A technician 20 minutes away with perfect skills often ranks higher than one 5 minutes away without required certification.
Taking Action on Suggestions
After reviewing a suggestion card, you have three primary actions:
β Accept
Confirms the AI assignment and schedules the job with the suggested technician at the suggested time. The job moves from "AI Suggestion" status to "Accepted" and syncs to FieldCamp on the next batch operation.
When to accept:
Confidence score 85%+ with no critical concerns
All decision factors show green/blue status
No customer callback needed
Technician workload is reasonable
β Reject
Dismisses this specific assignment suggestion. The system prompts for a rejection reason:
Skills mismatch
Time conflict
Technician preference (customer-requested specific tech)
Workload concerns
Route inefficiency
Other (custom reason)
Why feedback matters: Your rejection reasons train the AI to avoid similar mistakes in future suggestions.
π Reassign
Opens the alternatives dialog where you can select a different technician from the ranked list. Choosing an alternative updates the assignment while keeping the job in your active schedule.
When to reassign:
Confidence score below 70%
Better alternative available with higher confidence
Customer specifically requested a different technician
Primary suggestion has workload concerns but alternative has capacity
Reviewing Multiple Suggestions Efficiently
When AI Dispatcher processes multiple unassigned jobs, you'll see multiple suggestion cards. Use the selection checkboxes to review in bulk:
Bulk Review Workflow
Sort by confidence β Highest to lowest
Select all 85%+ suggestions β Review quickly for obvious issues
Bulk accept high-confidence β If they align with operational requirements
Filter for conflicts/warnings β Show only suggestions below 70% or with flags
Review individually β Deep dive on flagged items
Sort by technician β See all suggestions for each team member
Evaluate daily workload β Ensure no single tech is overloaded
Example: Monday Morning Rush
Scenario: 15 new jobs came in over the weekend. AI Dispatcher generated suggestions for all.
Efficient Review Process:
Filter: 90%+ confidence β 8 suggestions β Bulk accept (2 minutes)
Filter: 70-89% confidence β 5 suggestions β Quick review, accept 4, reassign 1 (5 minutes)
Filter: Below 70% β 2 suggestions β Deep review, both have skill gaps β Reject with feedback, manually assign later (3 minutes)
Sort by technician β Check Sarah has 6 jobs (reasonable), Mike has 8 (heavy but acceptable), Carlos has 1 (light) β Manually add one more to Carlos from backlog (2 minutes)
Total time: 12 minutes to process 15 jobs. Without AI: 45+ minutes of manual scheduling.
π‘ Pro Tip: Bulk actions are particularly useful during peak scheduling periods when you need to process dozens of assignments quickly while maintaining quality control.
Best Practices for Review
To maximize the value of AI suggestions while maintaining dispatch quality:
1. Start with Confidence Scores
Review the overall percentage before diving into details. High-confidence suggestions (85%+) rarely need deep inspection.
2. Always Check Concerns
If the "Considerations" section lists items, read them carefully. These flags often surface issues that aren't obvious from the confidence score alone.
3. Verify Customer Time Preferences
When AI scheduled time differs significantly from customer preferred time, this usually requires a customer callback for approval.
Quick rule:
Deviation < 1 hour β Usually acceptable, monitor
Deviation 1-3 hours β Call customer for approval
Deviation 3+ hours β Always call customer, explain reason
4. Review Workload Context
Before accepting, check the technician's daily schedule to ensure the new job doesn't push them into overtime or create unrealistic back-to-back commitments.
Healthy workload distribution:
60-75% utilization: Optimal (allows buffer for delays)
75-85% utilization: Acceptable (monitor for issues)
85%+ utilization: High risk (delays cascade, overtime likely)
5. Provide Rejection Feedback
When rejecting suggestions, choose accurate rejection reasons. This data trains the AI to avoid similar mistakes in future assignments.
Good rejection feedback example:
Reason: "Skills mismatch"
Note: "Job requires commercial refrigeration certification, not standard HVAC"
This teaches the AI to distinguish between residential HVAC and commercial refrigeration in future suggestions.
6. Trust but Verify Critical Jobs
For high-value customers, emergency calls, or complex jobs, always review suggestions carefully even if confidence is 90%+.
Extra scrutiny for:
VIP/contract customers
Jobs over $5,000 value
Emergency/same-day requests
Multi-trade requirements (electrical + plumbing)
First-time customers (sets the relationship tone)
Key Takeaways
Confidence scores combine 5 weighted factors β Skills (35%), Proximity (25%), Availability (20%), Workload (10%), Route Efficiency (10%)
85%+ suggestions are usually safe to accept β Minimal review needed
Below 70% requires close inspection β Check reasoning and alternatives
Large time deviations need customer callbacks β Don't schedule 3+ hours outside preference without approval
Red conflicts are critical β Never accept without resolving
Rejection feedback trains the AI β Always provide accurate reasons
Alternatives are ranked by weighted confidence β Not just proximity
You have the final authority β AI suggests, you decide
π― Remember: AI suggestions are decision-support tools, not mandates. The AI handles the computational heavy lifting β analyzing hundreds of factors per second β but your operational judgment and customer relationships remain irreplaceable.
Related Articles
Understanding the AI Dispatcher β How the AI engine analyzes jobs and generates suggestions
Configuring AI Rules and Preferences β Customize how AI prioritizes different factors
Managing Technician Skills and Certifications β Ensure accurate skills matching
Batch Operations and Bulk Actions β Process multiple suggestions efficiently
Training the AI with Feedback β Improve suggestion quality over time
Need help? Contact support or check the FieldCamp AI Dispatcher documentation.
Related Articles