Managing your Jump waitlists

Some partners have asked for advice about managing their waitlists. We understand many are having difficulty contacting customers who have been added to the waitlist and the question then is how much effort do you put into following up with people who are difficult to contact.

The Auckland Library team discussed this at a recent Jump Community of Practice and agreed to set aside modems for up to 7 days; some felt it didn’t even need to be as long as this, as we are continuing to face up to six week delays in the supply chain.

We support the idea of a definite timeframe being communicated to customers and agree it should be no longer than 7 days. We find many people are reluctant to answer calls from unknown numbers but can be responsive to text messages when they know it is about Jump.

I know some partners try time and time again to contact these customers, but my advice is that one call is all that is necessary – leave a message if possible (voice or text). The ‘reserved’ modem should then be released for distribution after 7 days. This practice should be explained to customers at the time they are added to the waitlist. They should also be encouraged to take responsibility for checking in with you from time to time as well.

Partners are welcome to leave unresponsive names in the Waitlist section of their Jump registers but they eventually ‘expire’ (currently after 6 weeks) when it comes to influencing modem re-order quantities.

You are also welcome to add your own notes in column H of the register and contact details in columns I to N.

More on Jump Waiting Lists

Many partners are now actively using the waiting list process to signal unmet demand for Jump modems, and we are continuously monitoring these lists to adjust delivery quantities for partners as well as priorities. We currently have 102 modem orders for partners in the pipeline, with total requests for over 1200 modems. This might seem like a lot, but the good news is that waiting times are trending down, and with Christmas coming, we expect this trend to continue at least until February. We have adjusted the re-supply trigger quantity down from 8 weeks to 5. This means that whenever you receive a new supply of modems, you should have enough to last 5 weeks (based on the number issued during the previous five weeks). We do factor in customers on waiting lists, so a couple of reminders about this process.

(1) When you add someone to the waitlist towards the bottom of your Jump Register please include their first and last name and the date they have applied for Jump. The most important field is the date – it must be in the following format: “22-Nov-2022”. Other date formats may not be recognised and this directly affects re-supply quantities.

(2) Do not add people living at locations that fail the Jump coverage test to your waitlists. You should complete an online application for them, so that we get ongoing data about demand that can not currently be met. We do double check coverage for every online application and send an email to applicants at locations where there is no Jump service.

(3) We have noticed some situations where applicants get the green light for Jump coverage when they initially apply, but by the time new modem supplies arrive the situation has changed. This is regrettable, but it is not something we can control. In these situations, please transfer the applicant from your waiting list to an online application.

(4) Some partners are confused about the address verification process and have reported that by the time they discover their customer’s address is not in coverage, they have already set up a Skinny account. The address coverage check MUST come first, and certainly before you start to set up a Skinny Jump account.

(5) And before you add anyone to your waitlist, we do strongly encourage you to use the 6 C’s checklist with your customer to make sure Jump is the right product for them. Failing to do this is likely to lead to further frustration when modem supplies become available and the customer only then discovering that the data cap is not going to work for their household, for example.