ServiceDesk 4.8.278 Update 02/07/23

This is a big one.

We’ve never prior had a purpose-built method by which you can store information, from your customer’s bankcards, for future use.  

More particularly, we’ve never had any method by which you can store this information in a manner that is secure (by “secure” we mean, once collected, no one has any direct access to the sensitive elements of it), and that is PCI-compliant.  

We have it now.  

Initially, we’ve provided mechanisms for you to invite QET clients and regular customers to create stored card information, and for you to then charge against such information (called tokens) whenever you wish to run a charge to be paid by that QET client or regular customer.  

Details are here.  In particular, please go to the section in the above-referenced manual supplement.

Going forward, we plan to add other options whereby you can collect such information in conjunction with online scheduling, on your own accord when a customer calls in and provides you with card information orally, and in conjunction with simply doing a card transaction.

This is a small one.

While working on the project to add stored card info functionality into QETs (QuickEntryTemplates, Shift-F9 in ServiceDesk) we were reminded that, that when you're in one edit interface and wish to move to another, it was awkward. You had to exit the edit interface you were in to get back into the main QET form, select the new QET client whose edit interface you were interested in, then again click on the Edit button.

Well, now, while in the Edit interface, you can simply hit PgUp or PgDn on your keyboard to move among the Edit interfaces for various clients.

The Rossware ecosystem obviously has provision for a great variety of automated and semi-automated communications between you and your customers. Usually, when we first create a new context of such communication, we equip it with language we have written that we feel is typically optimum for the circumstance.

You might call this the "canned" script.

From time to time, clients want some variation in the communication, that is different from the canned script. Where persuaded to do so, we then create a path by which clients can, optionally, substitute their own custom dialog for that canned dialog.

This is such a case.

Emailed and RoboCall-based Appointment-Reminder communications have long had opportunity for customization. The SMS-texted variant of this communication context was more recently developed, and has not prior had a path for customization. Now it does.

Instructions are here.

Auto-Dialing.

If you haven't enjoyed it, you've no idea what you're missing. You're looking in a Callsheet or JobRecord or Rolodex and you want to dial a number there displayed. Just right-click, and, in barely an instant, you're listening to the ringing tone on the dialed number.

It's wonderful, quick and so easy.

Service Company Solutions (SCS) created earlier paths that made auto-dialing via their phone systems very easy and virtually trouble free. But, they've now done it even better. In the ServiceDesk Settings form (Ctrl-F1) there is now just a single method from to which pick for SCS-based auto-dialing (superseding the prior three), and it's the best by far:

If you're not using a SCS phone system, it's something we highly recommend, and your present absence of such use is a very easy thing to remedy. Just talk to SCS, and they'll fix you right up. Here's a link to their website.

Almost eight years ago (as described here), we added an option that allows you to create a list of non-inventory and non-special-order-parts items that you may want to insert in a POS context to a ServiceDesk FinishedForm.

Functionality for these same insertions was soon added into the Windows version of SD-Mobile. It turns, however, we'd somehow failed to activate the insertions in the Android/iOS version of SD-Mobile. That oversight is now corrected.

In conjunction with this, we also realized that we had never added line-item tax-exempt checkboxes in the Mobile instance of ServiceDesk's internal FinishdedForms interface. This was particular important because one of the properties you can specify in your POS-Insertions list is is an item should be treated as tax exempt. Without checkboxes to register this, that specification could not be honored in this context. With those checkboxes now added, that issue is now remedied:

If you're a U.S. based servicer of Samsung products, you may now fully automate reception of Samsung Dispatches via our Samsung DispatchLink utility. Yahoo!!! (Formerly, full automation in this context was limited to Canadian servicers.)

If you're Canada-based servicer of LG products, you may now use the EmailedDispatchReceiver to automate reception of dispatches from LG.

If you're using the SP-DispatchLInk and need to have it configured for multiple different ServicePower accounts, it is now configured to permit that.