Blame
|
1 | # Service Call Lifecycle - Role Entry/Exit Points & Deliverables |
||||||
| 2 | ||||||||
| 3 | ## Service Call Phases Overview |
|||||||
| 4 | ||||||||
| 5 | ``` |
|||||||
| 6 | CALL INTAKE → TRIAGE & DISPATCH → TRAVEL → ON-SITE DIAGNOSIS → |
|||||||
| 7 | REPAIR/RESOLUTION → COMPLETION → BILLING & CLOSEOUT |
|||||||
| 8 | ``` |
|||||||
| 9 | ||||||||
| 10 | --- |
|||||||
| 11 | ||||||||
| 12 | ## Phase 1: CALL INTAKE (Customer Contact → Ticket Creation) |
|||||||
| 13 | ||||||||
|
14 | ### **[[training-structure/roles/senior-field-operations-coordinator]]** |
||||||
|
15 | **Entry Point:** Customer call, email, alarm notification, or Service Fusion portal submission |
||||||
| 16 | **Activities:** |
|||||||
| 17 | - Answer incoming service requests via phone, email, or system alarm |
|||||||
| 18 | - Gather critical information from customer: |
|||||||
| 19 | - Location and system affected |
|||||||
| 20 | - Nature of problem (no cooling, alarm condition, comfort complaint, etc.) |
|||||||
| 21 | - Severity and impact on building operations |
|||||||
| 22 | - Preferred service window |
|||||||
| 23 | - Special access requirements or site restrictions |
|||||||
| 24 | - Create service ticket in Service Fusion |
|||||||
| 25 | - Categorize request (Emergency, Urgent, Routine) |
|||||||
| 26 | - Link to appropriate Service Agreement and PO# (verify not expired) |
|||||||
| 27 | - Determine if covered under service contract or billable |
|||||||
| 28 | ||||||||
| 29 | **Deliverables:** |
|||||||
| 30 | - [ ] Service ticket created in Service Fusion with complete information: |
|||||||
| 31 | - Customer (address and contact info) |
|||||||
| 32 | - Service Agreement linked (with project numbers and expiration dates) |
|||||||
| 33 | - Primary Contact (point of contact for this service) |
|||||||
| 34 | - Service Location (if different from customer address) |
|||||||
| 35 | - Job Description (detailed problem description) |
|||||||
| 36 | - PO# assigned (specific project number for this visit) |
|||||||
| 37 | - Job Category assigned |
|||||||
| 38 | - Current Status: "Scheduled" or "Dispatched" |
|||||||
| 39 | - [ ] Customer acknowledgment sent (email/text with ticket number and ETA) |
|||||||
| 40 | - [ ] If Service Agreement expired: Office confirmation obtained before scheduling |
|||||||
| 41 | ||||||||
| 42 | **Exit Point:** Never exits - monitors entire service call lifecycle |
|||||||
| 43 | ||||||||
| 44 | --- |
|||||||
| 45 | ||||||||
| 46 | ## Phase 2: TRIAGE & DISPATCH (Assessment → Technician Assignment) |
|||||||
| 47 | ||||||||
|
48 | ### **[[training-structure/roles/senior-field-operations-coordinator]]** |
||||||
|
49 | **Activities:** |
||||||
| 50 | - Assess technical complexity and required skill level |
|||||||
| 51 | - Check Field Specialist skill matrix for best match: |
|||||||
| 52 | - Technical capability (network, programming, mechanical) |
|||||||
| 53 | - Geographic location (minimize drive time) |
|||||||
| 54 | - Current workload and availability |
|||||||
| 55 | - Customer relationship history |
|||||||
| 56 | - Determine priority based on: |
|||||||
| 57 | - Emergency status (system down, safety issue, critical alarm) |
|||||||
| 58 | - Service Level Agreement (SLA) requirements |
|||||||
| 59 | - Customer importance |
|||||||
| 60 | - Contractual response time commitments |
|||||||
| 61 | - Assign appropriate Field Specialist (or escalate to specialist if needed) |
|||||||
| 62 | - Optimize routing with scheduling software |
|||||||
| 63 | - Update on-call rotation if after-hours emergency |
|||||||
| 64 | - Communicate with customer on technician ETA |
|||||||
| 65 | ||||||||
| 66 | **Deliverables:** |
|||||||
| 67 | - [ ] Field Specialist assigned in Service Fusion |
|||||||
| 68 | - [ ] Start/End Date and Arrival Time Window set |
|||||||
| 69 | - [ ] Estimated Duration calculated |
|||||||
| 70 | - [ ] Project Manager added to notification list (if applicable) |
|||||||
| 71 | - [ ] Notes for Tech added with: |
|||||||
| 72 | - Known system history |
|||||||
| 73 | - Previous issues at this site |
|||||||
| 74 | - Special access instructions |
|||||||
| 75 | - Customer preferences or concerns |
|||||||
| 76 | - Parts likely needed (if known) |
|||||||
| 77 | - [ ] Customer notified of technician assignment and ETA |
|||||||
| 78 | - [ ] Route optimized in scheduling software |
|||||||
| 79 | ||||||||
| 80 | **Technical Escalation Decision Point:** |
|||||||
| 81 | If issue requires specialized expertise: |
|||||||
| 82 | - [ ] Network Specialist assigned for network/IT issues |
|||||||
| 83 | - [ ] Programmer Developer assigned for complex control logic issues |
|||||||
| 84 | - [ ] Graphic Developer assigned for HMI/graphics issues |
|||||||
| 85 | ||||||||
| 86 | **Exit Point:** Continues monitoring through completion |
|||||||
| 87 | ||||||||
| 88 | --- |
|||||||
| 89 | ||||||||
|
90 | ### **[[training-structure/roles/project-manager]]** (if applicable) |
||||||
|
91 | **Entry Point:** Service call related to recent project or warranty work |
||||||
| 92 | **Activities:** |
|||||||
| 93 | - Review service call details |
|||||||
| 94 | - Determine if warranty or billable work |
|||||||
| 95 | - Provide Field Specialist with project history |
|||||||
| 96 | - Coordinate with customer if warranty issue |
|||||||
| 97 | ||||||||
| 98 | **Deliverables:** |
|||||||
| 99 | - [ ] Warranty vs. billable determination documented |
|||||||
| 100 | - [ ] Project history notes added to ticket |
|||||||
| 101 | - [ ] Customer communication if warranty-related |
|||||||
| 102 | ||||||||
| 103 | **Exit Point:** After warranty determination and coordination |
|||||||
| 104 | ||||||||
| 105 | --- |
|||||||
| 106 | ||||||||
|
107 | ### **[[training-structure/roles/warehouse-manager]]** |
||||||
|
108 | **Entry Point:** Dispatch identifies parts likely needed |
||||||
| 109 | **Activities:** |
|||||||
| 110 | - Check inventory for commonly needed parts |
|||||||
| 111 | - Stage parts for potential pickup |
|||||||
| 112 | - Coordinate expedited delivery if critical part needed |
|||||||
| 113 | ||||||||
| 114 | **Deliverables:** |
|||||||
| 115 | - [ ] Parts availability confirmed |
|||||||
| 116 | - [ ] Parts staged for pickup (if known requirement) |
|||||||
| 117 | - [ ] Expedited shipping arranged (if emergency and part not in stock) |
|||||||
| 118 | ||||||||
| 119 | **Exit Point:** Parts issued or availability confirmed |
|||||||
| 120 | ||||||||
| 121 | --- |
|||||||
| 122 | ||||||||
| 123 | ## Phase 3: TRAVEL (En Route to Site) |
|||||||
| 124 | ||||||||
|
125 | ### **[[training-structure/roles/field-specialist]]** |
||||||
|
126 | **Entry Point:** Service call assigned and acknowledged |
||||||
| 127 | **Activities:** |
|||||||
| 128 | - Review service ticket details in Service Fusion |
|||||||
| 129 | - Review Notes for Tech section |
|||||||
| 130 | - Gather necessary tools and test equipment |
|||||||
| 131 | - Pick up parts from warehouse (if pre-identified) |
|||||||
| 132 | - Update Service Fusion status to "On the Way" |
|||||||
| 133 | - Navigate to site using GPS/routing |
|||||||
| 134 | - Contact customer if arrival time changes |
|||||||
| 135 | ||||||||
| 136 | **Deliverables:** |
|||||||
| 137 | - [ ] Service Fusion status: "On the Way" (timestamp recorded) |
|||||||
| 138 | - [ ] Tools and equipment loaded in vehicle |
|||||||
| 139 | - [ ] Parts picked up (if applicable) - documented in Service Fusion |
|||||||
| 140 | - [ ] Customer contact made if delayed |
|||||||
| 141 | ||||||||
| 142 | **Drive Time Calculation:** Automatically tracked between "On the Way" and "On Site" status changes |
|||||||
| 143 | ||||||||
| 144 | **Exit Point:** Continues to next phase upon site arrival |
|||||||
| 145 | ||||||||
| 146 | --- |
|||||||
| 147 | ||||||||
| 148 | ## Phase 4: ON-SITE DIAGNOSIS (Initial Assessment → Problem Identification) |
|||||||
| 149 | ||||||||
|
150 | ### **[[training-structure/roles/field-specialist]]** |
||||||
|
151 | **Entry Point:** Arrival at customer site |
||||||
| 152 | **Activities:** |
|||||||
| 153 | - Update Service Fusion status to "On Site" (timestamp recorded) |
|||||||
| 154 | - Check in with customer contact (Primary Contact) |
|||||||
| 155 | - Gather additional information about the problem: |
|||||||
| 156 | - When did it start? |
|||||||
| 157 | - What symptoms are observed? |
|||||||
| 158 | - Any recent changes to the system? |
|||||||
| 159 | - Review system graphics and historical trends |
|||||||
| 160 | - Perform initial system assessment: |
|||||||
| 161 | - Check network connectivity |
|||||||
| 162 | - Review current alarms and system status |
|||||||
| 163 | - Verify sensor readings |
|||||||
| 164 | - Check control sequences |
|||||||
| 165 | - Update Service Fusion status to "Started" when work begins (timestamp recorded) |
|||||||
| 166 | - Perform detailed diagnostics: |
|||||||
| 167 | - Use multimeter for electrical testing |
|||||||
| 168 | - Check physical components (sensors, actuators, relays) |
|||||||
| 169 | - Review control logic and setpoints |
|||||||
| 170 | - Test mechanical operation (valves, dampers) |
|||||||
| 171 | - Analyze communication issues if network-related |
|||||||
| 172 | - Identify root cause of problem |
|||||||
| 173 | - Determine repair approach and parts needed |
|||||||
| 174 | - Communicate findings to customer |
|||||||
| 175 | - If parts needed: Contact Dispatch for parts coordination |
|||||||
| 176 | ||||||||
| 177 | **Deliverables:** |
|||||||
| 178 | - [ ] Service Fusion status: "On Site" then "Started" (timestamps recorded) |
|||||||
| 179 | - [ ] Problem diagnosis documented in notes |
|||||||
| 180 | - [ ] Root cause identified |
|||||||
| 181 | - [ ] Repair plan communicated to customer |
|||||||
| 182 | - [ ] Parts list (if additional parts needed) |
|||||||
| 183 | - [ ] Customer approval for work (if billable or out-of-scope) |
|||||||
| 184 | ||||||||
| 185 | **Labor Time Calculation:** Begins when status changes to "Started" |
|||||||
| 186 | ||||||||
| 187 | **Escalation Point:** |
|||||||
| 188 | If issue is beyond Field Specialist capability: |
|||||||
| 189 | - [ ] Contact Dispatch for technical escalation |
|||||||
| 190 | - [ ] Specialist (Network/Programmer/Graphic) dispatched or provides remote support |
|||||||
| 191 | ||||||||
| 192 | **Exit Point:** Continues to repair phase (or pauses if awaiting parts) |
|||||||
| 193 | ||||||||
| 194 | --- |
|||||||
| 195 | ||||||||
|
196 | ### **[[training-structure/roles/senior-field-operations-coordinator]]** |
||||||
|
197 | **Activities (if escalation needed):** |
||||||
| 198 | - Provide remote troubleshooting support |
|||||||
| 199 | - Coordinate parts retrieval/delivery |
|||||||
| 200 | - Dispatch specialist if needed |
|||||||
| 201 | - Update customer on status |
|||||||
| 202 | - Coordinate with Warehouse Manager for expedited parts |
|||||||
| 203 | ||||||||
| 204 | **Deliverables:** |
|||||||
| 205 | - [ ] Remote support provided and documented |
|||||||
| 206 | - [ ] Parts expedited (if needed) |
|||||||
| 207 | - [ ] Specialist dispatched (if needed) |
|||||||
| 208 | - [ ] Customer status update provided |
|||||||
| 209 | ||||||||
| 210 | --- |
|||||||
| 211 | ||||||||
|
212 | ### **[[training-structure/roles/warehouse-manager]]** (if parts needed during diagnosis) |
||||||
|
213 | **Entry Point:** Field Specialist identifies parts needed |
||||||
| 214 | **Activities:** |
|||||||
| 215 | - Locate parts in inventory |
|||||||
| 216 | - Prepare for pickup or arrange delivery to job site |
|||||||
| 217 | - Log parts issuance in Service Fusion |
|||||||
| 218 | - If part not available: Source from vendor, coordinate expedited shipping |
|||||||
| 219 | ||||||||
| 220 | **Deliverables:** |
|||||||
| 221 | - [ ] Parts availability confirmed |
|||||||
| 222 | - [ ] Parts ready for pickup or en route to site |
|||||||
| 223 | - [ ] Invoice created in Service Fusion (removes from inventory) |
|||||||
| 224 | - [ ] Estimated arrival time communicated (if delivery) |
|||||||
| 225 | ||||||||
| 226 | **Exit Point:** Parts delivered/picked up |
|||||||
| 227 | ||||||||
| 228 | --- |
|||||||
| 229 | ||||||||
| 230 | ## Phase 5: REPAIR/RESOLUTION (Fix Implementation) |
|||||||
| 231 | ||||||||
|
232 | ### **[[training-structure/roles/field-specialist]]** |
||||||
|
233 | **Activities:** |
||||||
| 234 | - Pick up parts (if local pickup) or receive delivery |
|||||||
| 235 | - Log all parts used in Service Fusion Invoice section |
|||||||
| 236 | - Perform repair work: |
|||||||
| 237 | - Replace faulty sensors, actuators, or devices |
|||||||
| 238 | - Repair or replace wiring/connections |
|||||||
| 239 | - Recalibrate sensors |
|||||||
| 240 | - Adjust control logic or setpoints (if within scope) |
|||||||
| 241 | - Reset alarms |
|||||||
| 242 | - Clear faults |
|||||||
| 243 | - Test repair thoroughly: |
|||||||
| 244 | - Verify sensor readings accurate |
|||||||
| 245 | - Confirm mechanical operation |
|||||||
| 246 | - Test control sequences through full cycle |
|||||||
| 247 | - Monitor system operation for stability |
|||||||
| 248 | - Document all work performed in detail |
|||||||
| 249 | - If issue requires programming changes: Coordinate with Programmer |
|||||||
| 250 | - If issue requires network changes: Coordinate with Network Specialist |
|||||||
| 251 | - Take photos of before/after conditions (if applicable) |
|||||||
| 252 | ||||||||
| 253 | **Deliverables:** |
|||||||
| 254 | - [ ] Repair completed successfully |
|||||||
| 255 | - [ ] All parts used logged in Service Fusion Invoice |
|||||||
| 256 | - [ ] System tested and verified operational |
|||||||
| 257 | - [ ] Control sequences confirmed working correctly |
|||||||
| 258 | - [ ] Alarms cleared |
|||||||
| 259 | - [ ] Before/after photos (if applicable) |
|||||||
| 260 | - [ ] Detailed work description in Completion Notes |
|||||||
| 261 | ||||||||
| 262 | **If Multi-Day Service:** |
|||||||
| 263 | - [ ] Service Fusion status: "Paused" or "Partially Completed" |
|||||||
| 264 | - [ ] Additional Visit created in Service Fusion |
|||||||
| 265 | - [ ] Customer notified of return date |
|||||||
| 266 | - [ ] Progress documented for next visit |
|||||||
| 267 | ||||||||
| 268 | **Exit Point:** Repair complete and verified |
|||||||
| 269 | ||||||||
| 270 | --- |
|||||||
| 271 | ||||||||
|
272 | ### **[[training-structure/roles/network-specialist]]** (if network issue) |
||||||
|
273 | **Entry Point:** Network-related problem identified |
||||||
| 274 | **Activities:** |
|||||||
| 275 | - Remote diagnosis of network issue (if possible) |
|||||||
| 276 | - Dispatch to site (if on-site work required) |
|||||||
| 277 | - Troubleshoot and repair: |
|||||||
| 278 | - Network connectivity issues |
|||||||
| 279 | - Switch configuration problems |
|||||||
| 280 | - IP conflicts |
|||||||
| 281 | - Firewall/security issues |
|||||||
| 282 | - BACnet/Modbus communication failures |
|||||||
| 283 | - Document changes made |
|||||||
| 284 | - Verify all devices back online |
|||||||
| 285 | ||||||||
| 286 | **Deliverables:** |
|||||||
| 287 | - [ ] Network issue diagnosed and resolved |
|||||||
| 288 | - [ ] All devices communicating properly |
|||||||
| 289 | - [ ] Network changes documented |
|||||||
| 290 | - [ ] Time logged in Service Fusion |
|||||||
| 291 | - [ ] Handoff notes to Field Specialist |
|||||||
| 292 | ||||||||
| 293 | **Exit Point:** Network issue resolved |
|||||||
| 294 | ||||||||
| 295 | --- |
|||||||
| 296 | ||||||||
|
297 | ### **[[training-structure/roles/programmer-developer]]** (if programming issue) |
||||||
|
298 | **Entry Point:** Control logic issue identified |
||||||
| 299 | **Activities:** |
|||||||
| 300 | - Remote review of control programs (if possible) |
|||||||
| 301 | - Dispatch to site (if on-site programming required) |
|||||||
| 302 | - Troubleshoot and fix: |
|||||||
| 303 | - Control logic errors |
|||||||
| 304 | - PID loop tuning issues |
|||||||
| 305 | - Sequence of operation problems |
|||||||
| 306 | - Integration issues |
|||||||
| 307 | - Test programming changes thoroughly |
|||||||
| 308 | - Document all changes made |
|||||||
| 309 | - Update program documentation |
|||||||
| 310 | ||||||||
| 311 | **Deliverables:** |
|||||||
| 312 | - [ ] Control logic issue diagnosed and resolved |
|||||||
| 313 | - [ ] Program changes tested and verified |
|||||||
| 314 | - [ ] Program version control updated |
|||||||
| 315 | - [ ] Programming changes documented |
|||||||
| 316 | - [ ] Time logged in Service Fusion |
|||||||
| 317 | - [ ] Handoff notes to Field Specialist |
|||||||
| 318 | ||||||||
| 319 | **Exit Point:** Programming issue resolved |
|||||||
| 320 | ||||||||
| 321 | --- |
|||||||
| 322 | ||||||||
|
323 | ### **[[training-structure/roles/graphic-developer]]** (if graphics issue) |
||||||
|
324 | **Entry Point:** HMI/graphics issue identified |
||||||
| 325 | **Activities:** |
|||||||
| 326 | - Remote review of graphics (if possible) |
|||||||
| 327 | - Fix issues: |
|||||||
| 328 | - Broken data point links |
|||||||
| 329 | - Graphic display errors |
|||||||
| 330 | - Navigation issues |
|||||||
| 331 | - Dashboard problems |
|||||||
| 332 | - Test all fixes |
|||||||
| 333 | - Verify on multiple devices (desktop, tablet, mobile) |
|||||||
| 334 | ||||||||
| 335 | **Deliverables:** |
|||||||
| 336 | - [ ] Graphics issue diagnosed and resolved |
|||||||
| 337 | - [ ] All data links verified functional |
|||||||
| 338 | - [ ] Graphics tested on applicable devices |
|||||||
| 339 | - [ ] Time logged in Service Fusion |
|||||||
| 340 | - [ ] Handoff notes to Field Specialist |
|||||||
| 341 | ||||||||
| 342 | **Exit Point:** Graphics issue resolved |
|||||||
| 343 | ||||||||
| 344 | --- |
|||||||
| 345 | ||||||||
| 346 | ## Phase 6: COMPLETION (Customer Sign-off → Documentation) |
|||||||
| 347 | ||||||||
|
348 | ### **[[training-structure/roles/field-specialist]]** |
||||||
|
349 | **Activities:** |
||||||
| 350 | - Walk through completed work with customer |
|||||||
| 351 | - Demonstrate system operation |
|||||||
| 352 | - Answer any customer questions |
|||||||
| 353 | - Provide recommendations for preventive maintenance or improvements |
|||||||
| 354 | - Complete comprehensive documentation in Service Fusion: |
|||||||
| 355 | - Update Completion Notes with detailed work performed |
|||||||
| 356 | - Reference Task List items completed (if PM created task list) |
|||||||
| 357 | - Document all parts and materials used |
|||||||
| 358 | - Log all expenses (parking, tolls, supplies, travel) |
|||||||
| 359 | - Take final photos if needed |
|||||||
| 360 | - Obtain customer acknowledgment/satisfaction |
|||||||
| 361 | - Update Service Fusion status to "Completed" (timestamp recorded) |
|||||||
| 362 | - Clean up work area |
|||||||
| 363 | - Return to vehicle |
|||||||
| 364 | ||||||||
| 365 | **Deliverables:** |
|||||||
| 366 | - [ ] System fully operational and customer satisfied |
|||||||
| 367 | - [ ] Comprehensive Completion Notes in Service Fusion including: |
|||||||
| 368 | - Problem found |
|||||||
| 369 | - Work performed |
|||||||
| 370 | - Parts used |
|||||||
| 371 | - Test results |
|||||||
| 372 | - System status (operational) |
|||||||
| 373 | - Recommendations (if any) |
|||||||
| 374 | - [ ] Task List marked complete (if applicable) |
|||||||
| 375 | - [ ] All materials logged in Invoice section |
|||||||
| 376 | - [ ] All expenses logged in Expenses section: |
|||||||
| 377 | - Parking (if applicable) |
|||||||
| 378 | - Tolls (if applicable) |
|||||||
| 379 | - Small Tools and Equipment (if purchased) |
|||||||
| 380 | - Supplies (consumables) |
|||||||
| 381 | - Travel expenses (if covered by company) |
|||||||
| 382 | - [ ] Drive Time automatically calculated (On the Way → On Site) |
|||||||
| 383 | - [ ] Labor Time automatically calculated (Started → Completed) |
|||||||
| 384 | - [ ] Customer sign-off obtained (digital or signature) |
|||||||
| 385 | - [ ] Service Fusion status: "Completed" |
|||||||
| 386 | - [ ] Photos attached to ticket (if applicable) |
|||||||
| 387 | ||||||||
| 388 | **Labor Time Calculation:** Ends when status changes to "Completed" |
|||||||
| 389 | ||||||||
| 390 | **Exit Point:** Service call complete, documentation submitted |
|||||||
| 391 | ||||||||
| 392 | --- |
|||||||
| 393 | ||||||||
|
394 | ### **[[training-structure/roles/senior-field-operations-coordinator]]** |
||||||
|
395 | **Activities:** |
||||||
| 396 | - Review completed service ticket for quality and completeness |
|||||||
| 397 | - Verify all time and materials documented |
|||||||
| 398 | - Update customer with completion confirmation |
|||||||
| 399 | - Add service call to weekly reporting |
|||||||
| 400 | - File any follow-up actions needed |
|||||||
| 401 | - Monitor customer satisfaction |
|||||||
| 402 | ||||||||
| 403 | **Deliverables:** |
|||||||
| 404 | - [ ] Service ticket reviewed for completeness |
|||||||
| 405 | - [ ] Customer completion notification sent |
|||||||
| 406 | - [ ] Follow-up service scheduled (if needed) |
|||||||
| 407 | - [ ] Service call added to weekly KPI report |
|||||||
| 408 | ||||||||
| 409 | **Exit Point:** Ticket reviewed and customer updated |
|||||||
| 410 | ||||||||
| 411 | --- |
|||||||
| 412 | ||||||||
| 413 | ## Phase 7: BILLING & CLOSEOUT (Financial Processing → Project Close) |
|||||||
| 414 | ||||||||
|
415 | ### **[[training-structure/roles/project-manager]]** (if project-related or warranty) |
||||||
|
416 | **Entry Point:** Service call completed |
||||||
| 417 | **Activities:** |
|||||||
| 418 | - Review service call against warranty terms |
|||||||
| 419 | - Verify if billable or warranty work |
|||||||
| 420 | - Approve or flag for discussion |
|||||||
| 421 | - Update project tracking if warranty issue affects project status |
|||||||
| 422 | ||||||||
| 423 | **Deliverables:** |
|||||||
| 424 | - [ ] Billability determination confirmed |
|||||||
| 425 | - [ ] Warranty tracking updated (if applicable) |
|||||||
| 426 | - [ ] Approval for billing (if billable) |
|||||||
| 427 | ||||||||
| 428 | **Exit Point:** After billability review |
|||||||
| 429 | ||||||||
| 430 | --- |
|||||||
| 431 | ||||||||
|
432 | ### **[[training-structure/roles/senior-field-operations-coordinator]]** |
||||||
|
433 | **Activities:** |
||||||
| 434 | - Verify all labor time is accurate (Drive + Labor) |
|||||||
| 435 | - Verify all materials are documented |
|||||||
| 436 | - Verify all expenses are documented |
|||||||
| 437 | - Change status to "Ready to Close" |
|||||||
| 438 | - Route to Accountant for invoicing |
|||||||
| 439 | ||||||||
| 440 | **Deliverables:** |
|||||||
| 441 | - [ ] All time verified and approved |
|||||||
| 442 | - [ ] All materials verified and approved |
|||||||
| 443 | - [ ] All expenses verified and approved |
|||||||
| 444 | - [ ] Service Fusion status: "Ready to Close" |
|||||||
| 445 | - [ ] Ticket routed to Accountant |
|||||||
| 446 | ||||||||
| 447 | **Exit Point:** Ticket ready for accounting |
|||||||
| 448 | ||||||||
| 449 | --- |
|||||||
| 450 | ||||||||
|
451 | ### **[[training-structure/roles/accountant]]** |
||||||
|
452 | **Entry Point:** Service ticket marked "Ready to Close" |
||||||
| 453 | **Activities:** |
|||||||
| 454 | - Review service ticket for completeness |
|||||||
| 455 | - Verify all costs are properly coded: |
|||||||
| 456 | - Labor time (drive + on-site) |
|||||||
| 457 | - Materials used (from Invoice section) |
|||||||
| 458 | - Expenses incurred |
|||||||
| 459 | - Verify against Service Agreement terms: |
|||||||
| 460 | - Covered under contract? (no charge) |
|||||||
| 461 | - Billable hours? (T&M rates) |
|||||||
| 462 | - After-hours premium? (if applicable) |
|||||||
| 463 | - Generate invoice in Service Fusion (if billable): |
|||||||
| 464 | - Timesheet Report (labor hours) |
|||||||
| 465 | - Expense Report (expenses incurred) |
|||||||
| 466 | - Materials Report (parts used) |
|||||||
| 467 | - Apply appropriate rates from Service Agreement |
|||||||
| 468 | - Code costs to proper GL accounts: |
|||||||
| 469 | - Service revenue (if billable) |
|||||||
| 470 | - Warranty expense (if warranty) |
|||||||
| 471 | - Project cost (if project-related) |
|||||||
| 472 | - Mark service ticket as "Logged" |
|||||||
| 473 | - Send invoice to customer (if billable) |
|||||||
| 474 | - Track payment in AR system |
|||||||
| 475 | ||||||||
| 476 | **Deliverables:** |
|||||||
| 477 | - [ ] All costs verified and coded correctly |
|||||||
| 478 | - [ ] Invoice generated in Service Fusion (if billable): |
|||||||
| 479 | - Timesheet Report attached |
|||||||
| 480 | - Expense Report attached |
|||||||
| 481 | - Materials list attached |
|||||||
| 482 | - [ ] Invoice sent to customer (if billable) |
|||||||
| 483 | - [ ] Service ticket status: "Logged" |
|||||||
| 484 | - [ ] Costs posted to General Ledger |
|||||||
| 485 | - [ ] AR tracking initiated (if invoice generated) |
|||||||
| 486 | - [ ] Service profitability calculated |
|||||||
| 487 | ||||||||
| 488 | **Exit Point:** Invoice sent and payment tracking initiated (or warranty cost recorded) |
|||||||
| 489 | ||||||||
| 490 | --- |
|||||||
| 491 | ||||||||
|
492 | ### **[[training-structure/roles/warehouse-manager]]** |
||||||
|
493 | **Entry Point:** Service ticket closed, materials used documented |
||||||
| 494 | **Activities:** |
|||||||
| 495 | - Verify inventory adjustment for parts used |
|||||||
| 496 | - Update stock levels |
|||||||
| 497 | - Flag any low-stock items triggered by this service call |
|||||||
| 498 | - Update tool tracking (if tools checked out) |
|||||||
| 499 | ||||||||
| 500 | **Deliverables:** |
|||||||
| 501 | - [ ] Inventory adjusted for parts used |
|||||||
| 502 | - [ ] Stock replenishment flagged (if needed) |
|||||||
| 503 | - [ ] Tool check-in verified |
|||||||
| 504 | - [ ] Monthly procurement report updated |
|||||||
| 505 | ||||||||
| 506 | **Exit Point:** Inventory reconciled |
|||||||
| 507 | ||||||||
| 508 | --- |
|||||||
| 509 | ||||||||
| 510 | ## Service Call Types & Variations |
|||||||
| 511 | ||||||||
| 512 | ### 1. EMERGENCY SERVICE CALL (After-Hours, Critical) |
|||||||
| 513 | **Key Differences:** |
|||||||
| 514 | - Immediate dispatch (response time: 1-4 hours typically) |
|||||||
| 515 | - On-call technician dispatched |
|||||||
| 516 | - Premium rates may apply (per Service Agreement) |
|||||||
| 517 | - Dispatch manages customer expectations closely |
|||||||
| 518 | - May require multiple specialists on-call |
|||||||
| 519 | ||||||||
| 520 | ### 2. ROUTINE SERVICE CALL (Scheduled Maintenance) |
|||||||
| 521 | **Key Differences:** |
|||||||
| 522 | - Scheduled in advance (Status: "Scheduled") |
|||||||
| 523 | - Non-urgent, planned work |
|||||||
| 524 | - May be part of preventive maintenance program |
|||||||
| 525 | - Predictable parts and time requirements |
|||||||
| 526 | - Can be batched with other work at same location |
|||||||
| 527 | ||||||||
| 528 | ### 3. SYSTEM OPTIMIZATION / ENHANCEMENT |
|||||||
| 529 | **Key Differences:** |
|||||||
| 530 | - May involve multiple specialists (Programmer, Graphic Developer) |
|||||||
| 531 | - Longer duration work |
|||||||
| 532 | - May require project-style planning |
|||||||
| 533 | - Often scheduled during off-hours or weekends |
|||||||
| 534 | - Higher complexity documentation |
|||||||
| 535 | ||||||||
| 536 | ### 4. WARRANTY SERVICE CALL |
|||||||
| 537 | **Key Differences:** |
|||||||
| 538 | - Project Manager involved in coordination |
|||||||
| 539 | - No-charge to customer (unless out-of-scope found) |
|||||||
| 540 | - Tracked against project warranty costs |
|||||||
| 541 | - May trigger project punch list completion |
|||||||
| 542 | - Additional documentation for warranty tracking |
|||||||
| 543 | ||||||||
| 544 | ### 5. SERVICE AGREEMENT / PREVENTIVE MAINTENANCE |
|||||||
| 545 | **Key Differences:** |
|||||||
| 546 | - Pre-scheduled, recurring visits |
|||||||
| 547 | - Checklist-driven activities |
|||||||
| 548 | - Predictable scope and duration |
|||||||
| 549 | - May include multiple systems in one visit |
|||||||
| 550 | - Often includes inspection and minor adjustments |
|||||||
| 551 | ||||||||
| 552 | --- |
|||||||
| 553 | ||||||||
| 554 | ## Critical Service Fusion Workflow Summary |
|||||||
| 555 | ||||||||
| 556 | ### Dispatch Creates Ticket: |
|||||||
| 557 | ``` |
|||||||
| 558 | Customer → Service Agreement → Primary Contact → Service Location → |
|||||||
| 559 | Job Description → PO# → Job Category → Status: "Scheduled" or "Dispatched" |
|||||||
| 560 | ``` |
|||||||
| 561 | ||||||||
| 562 | ### Field Specialist Updates Status: |
|||||||
| 563 | ``` |
|||||||
| 564 | Scheduled → Dispatched → On the Way → On Site → Started → |
|||||||
| 565 | Completed (or Paused/Partially Completed) |
|||||||
| 566 | ``` |
|||||||
| 567 | ||||||||
| 568 | ### Time Tracking (Automatic): |
|||||||
| 569 | - **Drive Time:** Timestamp between "On the Way" and "On Site" |
|||||||
| 570 | - **Labor Time:** Timestamp between "Started" and "Completed" |
|||||||
| 571 | ||||||||
| 572 | ### Materials & Expenses: |
|||||||
| 573 | - **Purchase Order:** PM requests materials (if project-related) |
|||||||
| 574 | - **Inventory Order:** Warehouse receives materials |
|||||||
| 575 | - **Invoice:** Field Specialist logs materials used (removes from inventory) |
|||||||
| 576 | - **Expenses:** Field Specialist logs all expenses by category |
|||||||
| 577 | ||||||||
| 578 | ### Closeout: |
|||||||
| 579 | ``` |
|||||||
| 580 | Completed → Logged → Ready to Close → Close |
|||||||
| 581 | ``` |
|||||||
| 582 | ||||||||
| 583 | ### Accounting Generates: |
|||||||
| 584 | - Timesheet Report |
|||||||
| 585 | - Expense Report |
|||||||
| 586 | - Material Report |
|||||||
| 587 | - Customer Invoice (if billable) |
|||||||
| 588 | ||||||||
| 589 | --- |
|||||||
| 590 | ||||||||
| 591 | ## Key Performance Indicators (KPIs) Tracked |
|||||||
| 592 | ||||||||
| 593 | ### Response Time: |
|||||||
| 594 | - Time from call intake to technician "On Site" |
|||||||
| 595 | - Measured against SLA requirements (Emergency: 4 hrs, Urgent: 24 hrs, Routine: 72 hrs) |
|||||||
| 596 | ||||||||
| 597 | ### First-Time Fix Rate: |
|||||||
| 598 | - Percentage of service calls resolved on first visit |
|||||||
| 599 | - Target: 85%+ |
|||||||
| 600 | ||||||||
| 601 | ### Technician Utilization: |
|||||||
| 602 | - Labor Time / (Labor Time + Drive Time + Non-Productive Time) |
|||||||
| 603 | - Target: 70%+ |
|||||||
| 604 | ||||||||
| 605 | ### Customer Satisfaction: |
|||||||
| 606 | - Post-service survey ratings |
|||||||
| 607 | - Target: 4.5/5.0 or higher |
|||||||
| 608 | ||||||||
| 609 | ### Average Response Time: |
|||||||
| 610 | - By customer, by contract, by severity |
|||||||
| 611 | - Tracked weekly for contractual clients |
|||||||
| 612 | ||||||||
| 613 | ### Billable vs. Warranty Ratio: |
|||||||
| 614 | - Tracks profitability of service operations |
|||||||
| 615 | - Identifies warranty issue trends |
|||||||
| 616 | ||||||||
| 617 | --- |
|||||||
| 618 | ||||||||
| 619 | ## Critical Success Factors |
|||||||
| 620 | ||||||||
| 621 | 1. **Accurate and complete ticket creation** by Dispatch |
|||||||
| 622 | 2. **Proper technician skill matching** for first-time fix |
|||||||
| 623 | 3. **Real-time status updates** in Service Fusion |
|||||||
| 624 | 4. **Thorough documentation** of all work performed |
|||||||
| 625 | 5. **Complete materials and expense logging** for accurate billing |
|||||||
| 626 | 6. **Proactive customer communication** throughout service call |
|||||||
| 627 | 7. **Technical escalation when needed** (don't let technicians struggle) |
|||||||
| 628 | 8. **Quality review before closeout** to ensure completeness |
|||||||
| 629 | 9. **Timely invoicing** for billable work (within 48 hours of completion) |
|||||||
| 630 | 10. **KPI monitoring** for continuous improvement |
|||||||
| 631 | ||||||||
| 632 | --- |
|||||||
| 633 | ||||||||
| 634 | ## Common Service Call Pitfalls to Avoid |
|||||||
| 635 | ||||||||
| 636 | 1. ❌ Incomplete ticket information at intake |
|||||||
| 637 | 2. ❌ Wrong technician skill level assigned |
|||||||
| 638 | 3. ❌ Forgetting to update Service Fusion status changes |
|||||||
| 639 | 4. ❌ Incomplete completion notes (poor documentation) |
|||||||
| 640 | 5. ❌ Forgetting to log materials or expenses |
|||||||
| 641 | 6. ❌ Not obtaining customer approval for billable work |
|||||||
| 642 | 7. ❌ Delayed invoicing (reduces cash flow) |
|||||||
| 643 | 8. ❌ Parts not returned to inventory (if unused) |
|||||||
| 644 | 9. ❌ No follow-up on customer satisfaction |
|||||||
| 645 | 10. ❌ Failure to identify recurring issues for system improvements |
|||||||
