An account is the workspace everything else belongs to. Setting one up means working through a series of steps, each of which has to be complete before the account counts as valid.
A new account starts as a draft. While it is a draft you can edit everything freely. Only a draft account can have its domain and alias changed, so it is worth getting those right before you move on.
Work through the account steps
Identity
Set the Account ID, the Name and a Description. The name is what your team sees; the description explains what the account is for.
Presentation
Add an Image, your Links and the Default Language for the account. The default language is the language used when a message has no other language set.
Business details
Set the Business Name, Business Address, Company Type, Business Type, Business Industry and Business Registration ID. The business address has to be a real physical address and includes street, city, state or province, postal code and country.
Regions and volume
Choose the Business Regions of Operations and the Estimated Volume per Day. These describe where you send and how much, which is what compliance review looks at.
Authorized representative
Name the authorized representative or representatives for the account, with their role. A second representative can be added.
Use cases
Describe your Use Cases and give a Use Case Description and a Use Case Description CTA. The use cases you choose determine which additional fields the form asks for.
Sample messages
Provide sample messages. The first two are required and up to three more are optional. Samples are what reviewers read to understand what you will send.
Alias and domain
Set an Alias and a Domain. The alias has to be unique and may contain only lowercase letters, numbers and hyphens. Both can only be edited while the account is a draft.
Checking the account is valid
The account tracks which of its steps are complete. Each step reports whether it is satisfied, and the account as a whole reports whether it is valid. An incomplete step is the reason an account cannot move forward, so if something will not progress, the step list is the first place to look.
Why samples and use cases matter
The use cases you declare decide which additional details the form requires, and the sample messages are what a reviewer reads. Both exist so that messaging from the account can be reviewed before it goes out.
A broken domain is reported, not hidden
If the domain has problems, the account shows it directly and asks you to remove and re-add the domain to see what is wrong. Fixing it before leaving the draft stage is much easier than afterwards.