Use a structured email for pre-sales and partnership requests. For existing orders, technical issues, and billing reviews, submit a console ticket first. Include the model, region, timing, and reproduction details to reduce follow-up.
This form does not send data to the site backend. After you click the button, it creates a draft email in your system email client addressed to support@macminilab.com. Review and send it yourself.
Both models are available in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Actual availability is confirmed in real time by the console.
For existing orders, a console ticket automatically links your account and order context, making it the preferred entry point for troubleshooting. If you cannot access the console, use the tool below to generate a redacted email.
After signing in, open the support area, create a ticket, and select the relevant order. Status updates, follow-up questions, and resolution notes stay together in the ticket, making it suitable for technical or billing issues that require ongoing tracking.
Open the ticket portalEnterprise discussions do not start with “how many machines?” They start with team responsibilities, build queues, environment replication, and ownership of issues.
Specify which of Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong you plan to use, along with normal and peak concurrency.
Explain whether you plan to use the service daily, weekly, monthly, or quarterly, and whether you need centralized review of orders, charges, and renewal arrangements.
List who handles orders, maintains build environments, manages tickets, and hands off node-use information within the team.
Provide the repository count, build frequency, cache size, toolchain version strategy, and escalation path for failed tasks.
Send a structured email if the project is still under evaluation, you do not have an order number, or you need to discuss multi-node deployment, centralized procurement, or role separation.
Send an enterprise inquiryDescribe the partner, expected outcome, Cloud Mac workloads involved, each party’s contribution, and the stage you want to reach. Broad proposals without a defined scope will first receive a request for more context.
Send a partnership inquiryDifferent issues require different context. The response process focuses on acknowledging receipt, checking the information, classifying the request, asking for missing details, and updating the conclusion. Completion time depends on reproducibility, scope, and any required user confirmation.
We first verify the use case, model, region, term, concurrency, and storage, then identify missing details or recommend the ordering process.
We first classify the issue by connection, system, network, disk, or build layer, then investigate using the reproduction steps and log summary.
Provide the order number, payment method category, payment time, and displayed status. Do not send complete payment credentials by email.
Once the project context is clear, we can discuss node scale, role separation, procurement terms, and continuous build workflows.
| Issue type | Recommended channel | Prepare before submitting | Where status updates appear |
|---|---|---|---|
| Pre-sales selection | Support email | Use case, region, term, concurrency, storage | Email thread |
| Enterprise solution and partnerships | Support email | Project context, node scale, role separation | Email thread |
| Technical issue with an existing order | Console ticket | Order number, time, reproduction steps, redacted logs | Ticket record |
| Billing and payment status | Console ticket | Order number, payment category, time, displayed status | Ticket record |
For technical issues, retain the order number, node region, time of occurrence, error code, and reproduction steps. Remove access tokens, repository secrets, complete environment variables, and business data. For existing orders, submit a console ticket first; send pre-sales and partnership requests to support@macminilab.com.