ServiceDesk 4.5.72 Update 02/26/12

Technically, this is a CyberOffice feature -- but, as with a few other CyberOffice features, its implementation is only practical within the context of using SD-Mobile. 

What is the feature?

Quite simply, as the tech indicates he's completed one job, an automated telephone call can immediately go out to the next stop, informing their tech is on his way.  This is a further implementation of the "robo-calling" function we added a few weeks back (see entry here accompanying Rel 4.5.58) for use when confirming/reminding on appointments (as typically done the day prior to the actual appointment date). 

To use this new implementation, you need to be subscribed to both SD-CyberOffice and SD-Mobile (if you are not, call, and we'll get you setup).  In the CyberLink program (you'll need Ver. 4.5.12 or later), you'll need to "check" a new box to "turn-on" the feature:

Once that is checked (and assuming your technicians are updated to SD-Mobile Ver. 1.4.86 or later), they'll see a new popup appear whenever they click, in the Mobile interface, on a job's "I've Finished" button (at least assuming there are more jobs following the one involved):

As you can see, it's very fast and easy for the tech.  Within seconds of his consent, a telephone call will go to that next stop.  When the call is answered, an electronic voice will identify the call as being from your company, and inform of the tech's soon-to-be-expected arrival.  Specifically, if your tech has picked the first-provided option, it will (after identifying your company) state: "Your technician, [insert technician's name], is just finishing his prior job, and then will be on his way.  Please have your machine accessible and ready to be serviced.  We will see you soon." If he picks the second option, it will speak similarly, but state the number of minutes within which the tech is expected to arrive. 

Very simple, we think, and very effective. 

We added the option to include barcodes within PartsLabels over three years ago.  On recent review, it was realized the method as then created to allow the user to specify whether with-BarCode labels were preferred (as opposed to standard, text-only labels) was less than optimum.  With this release that awkwardness is corrected.  There is a new Settings option in the PartsProcess form's CheatSheet (from the F8 form, click in any otherwise non-operative space):

Just click on this CheatSheet item, and you can then pick yea or nea for use of BarCodes (the default is nea).  (Incidental to adding this new Settings option, we realized the dialog on the three items above it were not as optimum as they could be; so those have each been independently improved). 

About a month ago (see entry accompanying Rel. 4.5.67) we introduced a new report designed to specifically show percentages and quantities of dispatches that ended in completes, ordering parts, no-shows and other, broken down by techs and other criteria.  When creating that new report, we suspected there would be desire for a corresponding option we've prior provided in connection with several reports. 

What happens is sometimes folks run these reports and do not feel the results are credible.  Our solution is to provide what we call a "Check-Data" export.  The idea is, as the code churns through your data to produce the final tallied figures, it simultaneously compiles an item-by-item table that contains the specific data it relied on for the tally.  This allows you, if you feel in way any skeptical about the tallied result, to open that table (exported data) and review the items one-by-one, to see if there is any discrepancy in how the reporting mechanism handled and judged your data. 

Other reports, that already had this "Check-Data" function, were the TechsTimeOnJob report, TechsCompletionAnalysisreport, TechsRevenue report, both Recall-Rate reports, the QualityOfService report, MarginAnalysis report, Profitabilityreport and PayForPerformance report.  The simple idea is, after the report displays, there's an added button toward the lower-right corner of the Reports form:

If you want to review the "Check-Data" export as applicable to the report, just click on that button. 

Anyhow, that's all background for stating that, sure enough, some folks soon requested that our new "Result-on-Dispatches" report be equipped, same as these others, with its own "Check-Data" export.  That is now added, with this release.