😂 So, we just went into a small restaurant that only has about eight tables.
-
So, we just went into a small restaurant that only has about eight tables. Something seemed a bit off. The host came up to us and said they had a momentary power outage, and even though the power had come back on, the Wifi didn't, which means their ordering/payment system was off line, so they couldn't seat anyone.I said, "What if I paid in cash?"
"We can't open the cash drawer."
"What if I paid the exact amount?"
"We still can't place orders. We can't communicate with the kitchen."
1/2
-
So, we just went into a small restaurant that only has about eight tables. Something seemed a bit off. The host came up to us and said they had a momentary power outage, and even though the power had come back on, the Wifi didn't, which means their ordering/payment system was off line, so they couldn't seat anyone.I said, "What if I paid in cash?"
"We can't open the cash drawer."
"What if I paid the exact amount?"
"We still can't place orders. We can't communicate with the kitchen."
1/2
@ColesStreetPothole
I sell memberships at our zoo. When our manager faced the new computer-based system, she immediately asked 'what if it crashes?', and she assembled a box labelled "crash kit" for us. There are blank paper forms to fill out for membership sales, the info to be entered later when the tech is back online. We can accept cash and issue paper receipts, or use the portable charge, payments to be processed later. There are paper temporary member cards, and tally sheets to keep count of member attendance. In the several years since then, we have only needed the crash kit a couple of times, both times for only a part of the day while techies scrambled in to fix the issue. But when it's suddenly needed, it's good to know the backup plan is in that box, all ready to just grab and use. Every business should have something similar in the way of a tech crash plan, and make sure everyone knows where it is, and knows that they should just go ahead and use it. -
J jwcph@helvede.net shared this topic