The days right after a service is provisioned are when small omissions turn into problems months later. This checklist takes about twenty minutes and prevents most of them.
1. Confirm the details on your account are the ones you want on invoices
Open Edit Account Details and check the company name, address and tax identifier. These are printed on every invoice, and correcting them later does not retroactively change invoices already issued. Get them right once, now.
2. Add a second contact
If exactly one person receives billing and technical notices, that account has a single point of failure. Add at least one more contact under Contacts and choose which notification types they should receive. A billing contact who receives invoices but not technical alerts is a common and sensible split.
Use a role address such as billing@yourcompany.com rather than one person's mailbox where you can. Role addresses survive staff changes.
3. Turn on two-factor authentication
Under Security Settings. Do it while you are calm and at your desk, not during an incident. Save the recovery codes somewhere that is not the same device as your authenticator app.
4. Whitelist our notification address
Renewal notices, invoices and ticket replies all arrive by email. Add our sending address to your safe senders list, and if your organisation filters aggressively, ask whoever runs your mail to allow it. A suspension caused by an invoice that landed in a junk folder is entirely avoidable.
5. Decide how you want to pay, before the first renewal
Storing a payment method and enabling automatic payment removes an entire class of problem. If your organisation requires manual approval of every payment, that is fine, but then make sure the person who approves payments is on the account as a billing contact.
6. Write down what you actually have
Note which domains are registered where, which nameservers they use, and which of your systems depend on which service. Do this while it is fresh. The single most common cause of a slow incident response is nobody being sure what the affected system is connected to.
7. Open one low-stakes ticket
Before you need us urgently, use the ticket system once for something small. You will learn how it behaves, confirm our replies reach your inbox, and discover any mail filtering issue at a moment when it does not matter.
Keep this list
Every item here is something that costs minutes now and hours later. If you are unsure about any of them for your particular account, open a ticket and ask.
