ServiceDesk 4.8.126 Update 10/29/19
Assistance in Reconciling/Proving Whirlpool OOW Referral Fees
For many of you, this feature will not mean very much.
For those of you who accept COD referrals from Whirlpool in exchange for paying Whirlpool a $15 referral fee, you'll like it very much.
Whirlpool is now providing reports in an Excel spreadsheet detailing the items for which it is charging a referral fee.
This new feature will open that report for you, examine each line-item, find the matching JobRecord within ServiceDesk, and add five columns into Whirlpool's report that give you a bunch of information in regard to each item -- including the ServiceDesk JobRecord Number, start and end dates, who was the paying party (i.e., Whirlpool or the consumer), what was the total sold, and whether the historical notes indicate you've already prior paid the referral fee.
The new report can be accessed from here:
Please be aware of two caveats:
Above we italicized the expression "whether historical notes indicate . . ." The reason is because, at this point, ServiceDesk has no mechanism by which to explicitly-and-directly keep track of whether you've paid the referral fee on any item. In absence of this, many users have made it a practice, when paying WP referral fees, to add a little note into each applicable JobRecord with text such as "Paid WP referral fee" or "Paid $15 fee." This is the type of text that this reporting mechanism is looking for. Specifically, it is looking within each applicable JobRecord narrative for the text strings "Paid WP" or "Paid "$15". If it sees either such textual string, it will, in that fifth added field, indicate that, "Yes," it found the indication. Otherwise it will indicate "No."
This report depends on some added data that is newly compiled during the overnight archiving process, based on additional mechanisms that are contained only in this release and forward. Thus, if you try to run the report prior to an overnight archiving process that is done via a version of ServiceDesk that is either this release or forward, you are no likely to get a good result.