Purchasing Additional Domain-Based Business Email Accounts: Setup & Implementation Guide

Purchasing Additional Domain-Based Business Email Accounts: Setup & Implementation Guide

When your team grows, your email system must scale with it. Purchasing additional domain-based business email accounts is a common requirement for enterprises, foreign trade teams, and cross-border operators. This guide focuses on the practical steps to evaluate, purchase, and implement extra accounts under your existing custom domain, helping IT administrators and decision-makers avoid common pitfalls and ensure a smooth rollout.

1. Prerequisites: What You Need Before Buying

Before purchasing additional accounts, ensure the following conditions are met:

• Domain Ownership & Management: Enterprise email accounts use your own domain as the @ suffix (e.g., name@yourcompany.com). You must own and manage the domain. If you do not have a domain, you must register one first. The service provider can assist with registration, but domain pricing, ownership, and renewal terms should be confirmed before purchase.
• Business Verification: Enterprise purchases typically require a business license and a purchase contract. Individual users may also purchase accounts, but identity verification is required. Confirm the specific documentation and compliance requirements with the official service team.
• Existing Account Audit: Review your current account structure. Determine if you need to add departmental admins, standard users, or shared mailboxes. Ensure your current plan supports the desired number of accounts.

2. Purchasing & Activation Process

The purchasing process is designed to be straightforward, with officially direct-operated support to minimize delays:

1. Select Account Quantity: The service supports a minimum of 1 account, with no upper limit. For large-scale deployments, consult the official team for tiered solutions and management hierarchy recommendations.
2. Submit Documentation: Provide the required business license and contract. Ensure all details match your domain registration information.
3. Activation Timeline: If you already have a domain and all documentation is complete, activation typically occurs within 1 business day. If domain registration is required, allow 1–2 business days. Note that this timeline depends on documentation accuracy, DNS resolution, and review status.
4. Payment & Confirmation: Complete the purchase through the official service portal. You will receive confirmation and access credentials for the administrator console.

3. Implementation: Creating & Configuring Accounts

Once activated, the administrator can proceed with account creation and configuration:

• Create Sub-Accounts: Log in to the administrator console, navigate to "Organization & Users" > "User Management" > "New Mailbox User." Enter the account name (recommended in lowercase) and initial password. Save to create the account.
• Set Initial Passwords: Assign initial passwords to users. Users will log in via the web interface or configure their mobile/PC clients using the full email address.
• Client Configuration: The service supports web, mobile apps, PC clients, and standard protocol clients (e.g., Outlook, Foxmail). Supported protocols include SMTP, IMAP, and POP, with standard ports (25/465, 143/993, 110/995). Specific server addresses and encryption settings should be verified in the admin console or via customer support.
• Client Login Troubleshooting: If users experience login failures, check the following in order: network connectivity, full email username, password or client-specific password, server address, port, SSL/TLS settings, SMTP authentication, and any IP restrictions set by the administrator. If issues persist, provide the error message, client version, and timestamp to customer support.

4. Security & Compliance Checkpoints

Adding accounts increases your attack surface. Implement these security measures immediately:

• Sender Authentication: Ensure SPF, DKIM, and DMARC records are configured for your domain. This prevents spoofing and improves deliverability.
• Spoofed Email Identification: The service provides alerts for unknown senders and spoofed email identification. Enable these features in the admin console.
• Administrator Roles: Follow the principle of least privilege. The service supports standard users, department admins, and organization admins. Avoid setting multiple organization admins unless necessary, and regularly review admin accounts.
• Anti-Spam & Anti-Virus: The service includes built-in anti-spam and anti-virus protection. Review spam filtering settings and adjust black/white lists as needed, but do not rely on white lists as a substitute for root cause fixes.

5. Suitability & Decision Checklist

This solution is suitable for:

• Enterprises & Small Teams: Needing unified domain identity and centralized account management.
• Foreign Trade & Cross-Border Teams: Requiring global multi-node delivery and stable international communication.
• Security-Conscious Organizations: Such as law firms or financial institutions, where evidence chains, confidentiality, and compliance are critical. Decision Checklist:
• Domain is registered and under your control.
• Business license and contract are prepared.
• Account quantity and hierarchy are defined.
• Client compatibility (web, mobile, PC, third-party) is verified.
• Security settings (SPF, DKIM, DMARC, admin roles) are planned.

6. Next Steps & Support

For official activation, migration, and daily operation support, use the official service portal. The service is officially direct-operated with no agents, ensuring consistent support and configuration. If you need assistance with account creation, client configuration, or security policy updates, contact the official support team. For detailed guidance on defending against business email compromise, refer to the enterprise email operation guide. For information on single-user plans, visit the single user enterprise email help page.

This guide is based on current product capabilities and official documentation. Specific configurations, pricing, and timelines should be confirmed with the official service team before implementation.