Our first objective in this current work was to make mechanisms that will allow you to create whatever custom scripts as you may like to have used in this context, whether it's for "call-aheads" that are done via RoboCall or done via SMS text-messaging (not truly a "call-ahead," of course, which is why put the expression in quotes for this context). 

Though that was our first objective, on working to pursue it, we noticed that our "canned" scripts (the only ones until now available) could in themselves be improved.  Thus we've done so.  Indeed, besides improving the language generally, we also noticed and addressed a certain structural deficit. 

In particular, though we like to use language (in the RoboCall scripts, in particular) indicating that the tech "is just finishing his prior job," such language is inapt when the call-ahead is to the first stop in the tech's roster for the day.  Not only is it inapt, it could potentially upset a customer if that customer has been told their appointment will be first in the tech's roster for the day. 

Accordingly, we have modified both the scripts and the underlying structure so the language is more appropriate to circumstance, depending on if it's the tech's first stop of the day, versus otherwise. 

Beyond that, yes, if desired you may now create your own custom scripts for these contexts.   Instructions are in this document(as of this date the applicable section begins on Page 7).

Sometimes, whether it's on the job itself or in multiple preceding jobs that involved the same machine, there is a lot of history in a situation.  We learned that in some situations the space that we'd allotted to contain this history was insufficient, so information that was otherwise relevant was being cut off.  As this point we have approximately quadrupled the allocated space.  We believe this will solve the issue. 

Let's face it.  The SD-Mobile Handbook had scarcely been updated since the very early days of this product.  There were elements in it that were pretty badly dated.  Though it's still not been thoroughly modernized so much as we'd like, its most glaring anachronisms have been addressed, and a number of descriptions added.  The current rendition is much improved.  

Thanks to contributions from our former iOS developer (working directly with  our new in-house iOS developer), active work has resumed on the iOS side of Mobile development.  A TestFlight release has been subject to beta testing over the prior few weeks.  It seems to have proven itself there, and so is being rolled out into full release throughout the course of this week (basically, some systems will update on Monday, some on Tuesday, and so on). 

This release sedulously addresses all the major items that had accumulated with urgent-need status in the last two years.  We expect other releases to be following with alacrity, each step-by-step bringing SDM-i up to the same feature and sophistication level that SDM-w has attained during the period that iOS development was in an essentially lapsed status.