Buying field service software is the easy part. The harder part is the two weeks that follow, when the team has to actually learn the system, hook it into the existing accounting setup, get the schedule loaded, and adjust the daily workflow around the new tool. That transition goes either well or it goes the way most software rollouts go in the field service trades, with three months of half-use followed by quiet abandonment. The Smart Service onboarding sequence is built around the bet that the rollout goes well only when the implementation team handles the technical setup, runs the training against the customer's actual data, and stays available through the first ninety days of real use. The walkthrough below covers what happens at each stage of that sequence, the role the implementation team plays, and the role the customer plays on the same call. The pattern that runs across every section is the split: there is a Smart Service role and there is a customer role, and the onboarding works because both are clear up front.
The Installation Call
Your role: pick a time. Our role: remote in, install Smart Service on the office computer, and connect it to your existing QuickBooks setup.
The installation call is the first contact after the purchase, usually inside the first business day. The implementation team reaches out to schedule a thirty- to sixty-minute remote connection to the office computer (or computers, for a multi-seat setup). During the session, the technician installs Smart Service, configures the QuickBooks Desktop or QuickBooks Online connection, and verifies that the two systems are talking to each other before the call ends. The customer's job during this window is to be at the keyboard, approve the remote-connection prompt, and confirm that the QuickBooks credentials work. Nothing more. The installation does not require a network engineer or an IT consultant; the implementation technician handles every technical step on the call, and the customer's first hands-on experience with the software happens after the install is verified rather than during it. For business owners worried about the technical lift of switching systems, this is the moment the worry resolves. The system is installed and connected by the time the call ends, and the customer is set up to start clicking around the software the same afternoon.
The First Training Session
Your role: show up, take notes, ask questions as they come up. Our role: walk through the core software using your schedule and your customer list, not a generic demo set.
Two to three business days after installation, the implementation team follows up to schedule the first of two training sessions. The brief gap between install and training is intentional. It gives the customer a chance to click around the software on their own and arrive at the training session with the questions that come from actual hands-on time rather than from imagined scenarios. The first session covers the foundational pieces of the software: the setup tab, the home screen, employee setup and permissions, the scheduler, contact search and filtering, and the Smart Service job process from creation through completion. The session runs against the customer's own data wherever possible: the dispatcher loaded into the system as a real employee, the first ten customers loaded as real contacts, the actual service categories the business runs. The training is taught against real material because the muscle memory has to form on the customer's actual workflow, not on a hypothetical one. Sessions typically run sixty to ninety minutes depending on the number of people in the room and the depth of questions, and the customer leaves the call with the basic operating pattern of the software in hand.
The Second Training Session
Your role: bring a list of questions specific to your business. Our role: tailor the software to those questions and walk through the mobile app and any add-ons.
The second training session typically falls inside a week of the first. By that point the customer has run the software against a few real jobs and has the kind of specific questions that the first session could not have anticipated. The second session is structured around those questions. It covers the mobile app (iFleet) so the techs in the field can sync with the office in real time, and it covers any add-ons the business has purchased (Routing, ServiceCard, the email or text reminder modules, the integrations beyond QuickBooks). The session is the moment when the generic software bends to the specific business. The work-order template gets customized to the trade, the equipment categories get loaded against the actual fixtures the contractor services, the recurring service contracts get set up against the customers who actually carry them. The goal by the end of session two is a working Smart Service configuration that fits the way the specific business operates, not a generic install that the customer would then have to customize alone over the next month.
After session two, the customer receives access to recordings of both training sessions, so anyone hired into the office later (a new dispatcher, a new office manager, a relief tech coordinator) can watch through the original team's training without rebooking a session. The recordings also give the original team a reference to revisit any specific configuration step weeks or months later without having to call the implementation team back in.
Help Desk Support
Your role: call when you are stuck. Our role: answer the phone, get on a screen-share if needed, and resolve the issue inside the same business day.
The Help Desk is the support channel that runs from the close of the second training session through the entire life of the account. The line is staffed by Smart Service technicians who know the software at the configuration level and can step into any customer's setup in seconds. The hours are 8:30 a.m. to 5:30 p.m. Eastern, Monday through Friday. The contact options are a phone call to 1-888-518-0818 or an email to [email protected]. The Help Desk handles three categories of issue. The immediate technical problem (the QuickBooks sync stopped working, the scheduler is showing an error). The how-do-I question (the dispatcher needs to set up a new recurring service contract and is not sure where the field lives). And the workflow refinement (the office wants to add a new step to the job process and needs help configuring it). The first call typically resolves the issue on the call; the more complex configuration questions sometimes get scheduled into a brief follow-up screen-share inside the same day. The pattern that holds across the support relationship is the same one that holds in the original training. The Smart Service technician steps into the customer's actual setup and works the problem in context, rather than describing the fix over abstract instructions.
Wiki and Video Library
Your role: search the resource first when you need a quick answer. Our role: maintain a searchable reference library you can use without picking up the phone.
Not every question is worth a phone call, and the self-service reference layer exists for the questions a customer wants to answer at 9 p.m. on a Tuesday without waiting until the morning. The searchable Smart Service Wiki covers every feature of the software in written-instruction form, organized by topic so the dispatcher who needs to look up "how do I set up a new equipment type" can find the article in two clicks. The Smart Service YouTube channel carries a library of short tutorial videos that walk through specific features step by step, from basic scheduling through advanced inventory management. The wiki and the video library are the resources customers reach for between training sessions and after the Help Desk closes for the day; the Help Desk is the resource they reach for when the wiki article does not match the situation in front of them. The pairing of self-service reference and human-staffed support is the structure that keeps the office productive without making the customer wait on a single channel for every question. For office workflows specifically, the broader SOP framework the business runs sits naturally on top of the Smart Service configuration as the source of truth.
The First Ninety Days
Your role: run the software against real work and feed back what is working and what needs adjustment. Our role: stay reachable, fold the feedback into the configuration, and check in proactively at the thirty-day mark.
The first ninety days are when the software becomes a habit. Most customers see meaningful changes inside the first two weeks. The dispatcher stops keeping the schedule on paper. The techs start running their day off the iFleet mobile app. The office starts billing from the completed work orders rather than reconstructing the day on Friday. The compound benefits accrue more slowly. The field-captured time tracking habit takes the techs a pay period to adopt cleanly, and the equipment tracking layer only delivers its full value once the asset list is populated against the customer base, which is a tagging exercise that happens during the natural rhythm of the next round of service calls. The thirty-day check-in from the implementation team catches the configuration questions that did not surface during the training sessions, and the sixty- and ninety-day touchpoints catch the questions that only emerge once the software has been in production use long enough to expose them. The pairing of the dispatch management discipline with the mobile invoicing layer typically reduces the office reconciliation hours by the end of month two; the broader monthly financial review the office runs against the books gets cleaner inside the same window because the data flowing into QuickBooks is now structured rather than retroactively reconstructed.
The bet behind the whole onboarding sequence is that the team that runs the install, both training sessions, and the first ninety days proactively is the team that captures the full operational lift the software is built to deliver. The customer who treats the install as the finish line gets a software license; the customer who runs the entire ninety-day sequence with the implementation team gets the operational shift the software is built around. Both outcomes are common, and the difference between them is mostly about whether the customer engaged with the structured handholding the team is providing across the first three months. The handholding is built into the price; the customer who skips it is the one who pays for it twice, once at the purchase and once again at the abandonment.
Smart Service for Field Service
If you are running a field service business and want a software stack that handles scheduling, dispatch, customer history, mobile invoicing, equipment tracking, and the implementation handholding that gets your team into production use inside two weeks, Smart Service integrates with QuickBooks Desktop and QuickBooks Online and iFleet keeps techs in the field synced with the office. Try a free demo to see how it fits!
