The short answer
Create the new key, deploy it, confirm traffic is flowing, then delete the old one. There is no downtime if you do it in that order.
Help centre · Restaurants
Bookings that never turn up on a busy night. How do I replace a key safely? Create the new key, deploy it, confirm traffic is flowing, then delete the old one. There is no downtime if you do it in that order.
Create the new key, deploy it, confirm traffic is flowing, then delete the old one. There is no downtime if you do it in that order.
Bookings that never turn up on a busy night. It usually surfaces the first time a real list goes out, when table confirmations, waitlist calls and quiet night offers stop being a plan and become a send.
Get this right and the outcome is covers protected and last minute tables filled. Get it wrong and the cost shows up quietly, in messages nobody read and money already spent.
The compose screen shows the segment count, the cost and the sender name before anything leaves, so the decision is made before the money moves.
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
Create the new key, deploy it, confirm traffic is flowing, then delete the old one. There is no downtime if you do it in that order.
The mechanics are the same. What changes is the volume and the timing, because restaurants mostly send table confirmations, waitlist calls and quiet night offers.
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
Support on Telegram at @exerioco sets you up in under five minutes.