Being ready for this may require you to improve the robustness of your service.
Support - have someone monitor it
General office phone - employ an answering service. A human should answer phones for business image reasons.
Infrastructure - design it right. Assume that fiber to your datacenter can get cut any second. Now what? Provision remote storage in case local drive dies. Boot the OS into RAM so if the local drive dies it won't affect your server. I am going a step further and configuring everything to boot from PXE using iPXE. The goal should be that a monitoring script that hasn't received a heartbeat can reset your infrastructure.
Payments - have multiple payment methods defined for your critical services, prepayment may help.
As long as the infrastructure can reset itself and your phones are answered and support is handled, enjoy yourself.
This is how my processes are setup, but my product is relatively simple so support is usually not an issue. However, I rely on so many APIs that getting all that robust enough for me to be confident to take a break was a significant challenge.