Route first, resolve faster

Describe your request clearly and send it to the right queue

Email us about configuration, bulk deployment, or partnerships. For existing orders, machine status, or connection issues, submit a console ticket so our team can link it directly to your order and timeline.

Console ticket
4 business hours for first response
Support email
1 business day for first response
SOARMAC / REQUEST ROUTING Request intake checklist
Ready to submit
PRE
Configuration & bulk deployment Describe your workload, concurrency, term, and preferred node
Email
ORD
Existing orders & billing Provide your order number, model, term, and items to verify
Ticket
TEC
Connection & runtime issues Include the node, time, reproduction steps, and redacted logs
Ticket
ENT
Enterprise & partnership needs Describe machine count, rollout pace, and internal process constraints
Email
One support email support@soarmac.com
Four request types

Include the information that moves the decision forward

A problem name alone is rarely enough to begin. Add configuration, timing, and expected results for your situation to reduce back-and-forth.

Support email

Pre-sales configuration

For teams without an order that are comparing SoarMac M4 Air, M4 Plus, and M4 Pro.

  • Projects, toolchains, and workload types you plan to run
  • Expected concurrent tasks and runtime per task
  • Memory, storage, term, and preferred node
  • Whether you need multiple machines or Thunderbolt 5 interconnects
Complete the pre-sales email
Console ticket

Existing order

For checking delivery, term, renewals, add-ons, payment records, or details of machines you already ordered.

  • Order number and current machine tier
  • Singapore, Tokyo, Seoul, or Hong Kong node
  • Billing items to verify and their applicable term
  • Desired resolution and deadline
Submit an order ticket
Console ticket

Technical support

For remote sessions, networking, development environments, CI runners, storage, and runtime issues.

  • Affected node and macOS version
  • Incident time with time zone and duration
  • Minimal reproduction steps and expected result
  • Logs with credentials, keys, and business data removed
Submit a technical ticket
Support email

Enterprise needs

For bulk nodes, phased rollouts, procurement workflows, billing materials, and long-term workflow evaluations.

  • Planned machine tiers and quantity range
  • Deployment phases, term, and node preferences
  • Internal approval, settlement, and delivery requirements
  • Technical boundaries and acceptance criteria to validate
Complete the enterprise email
Email draft generator

Organize the required details once, then send them from your system email

This form does not submit content to the website backend. After you click Generate, a draft addressed to the support team will open in your system email for your review and sending.

Complete the required fields to generate a structured email draft.
Have an existing order?

Create a ticket in the console first

Tickets are linked to your account and order timeline, making them ideal for delivery, machine status, connection, billing, and renewal issues. Include the node and main symptom in the title.

Recommended entry point
Ticket area in the console
First-response target
4 business hours
Sign in to the console
No order yet?

Discuss configuration and deployment by email

Email is best when you need to confirm machine tier, node, quantity, term, and internal processes first. Include “pre-sales” or “enterprise needs” in the subject for faster routing.

Support email
support@soarmac.com
First-response target
1 business day
Create a support email
Technical issue checklist

Make the issue diagnosable, not merely describable

“I can’t connect” may be caused by the address, account, network path, client settings, or credential status. Provide context in the same order so our team can identify where the issue stops.

Never send sensitive credentials

Remove passwords, private keys, session credentials, access tokens, signing materials, and identifiable business data from logs and screenshots first. Support does not need these original secrets.

  1. 01

    Node & environment

    Specify the Singapore, Tokyo, Seoul, or Hong Kong node, along with the macOS version, client version, and relevant tool versions.

  2. 02

    Incident time

    Provide the exact time with time zone, duration, whether the issue is ongoing, and whether other tasks on the same node are working normally.

  3. 03

    Minimal reproduction steps

    Starting from a known-good state, list each action, input, observed result, and expected result. Avoid pasting only the final error.

  4. 04

    Redacted evidence

    Include necessary error codes, command output, and log excerpts, and note any reconnection, network-switching, or environment-cleanup steps already tried.

  5. 05

    Impact & priority

    Describe the number of affected tasks, whether delivery is blocked, whether a workaround exists, and the state you need restored.

Ordering & billing

Use clear paths for orders, machine management, and support requests

For a new order, choose the model, term, node, and add-ons in the configuration flow. Manage existing machines and orders in the console. Actual availability and supported payment gateways are shown in real time by the console.

Configure & order

Three dedicated physical machine tiers

Choose SoarMac M4 Air, SoarMac M4 Plus, or SoarMac M4 Pro, with daily, weekly, monthly, or quarterly terms.

View full plans
Order management

Keep delivery and billing on one timeline

View orders, machine status, renewals, and support tickets together in the console. For existing-order issues, submit a ticket from the relevant account.

Manage existing orders
USD billing

Two payment methods supported

Pay with USDT-TRC20 or Visa / Mastercard / Amex (via Stripe). Machine, term, and add-on amounts are shown before you confirm the order.

Choose a plan and order now
Privacy & response boundaries

Submit only the information needed for the current request

Contact details help identify the requester, answer questions, link necessary order records, and maintain the support timeline. Access is limited according to the request, with information retained only as needed for account, order, security, and support records.

If your issue can be explained with an order number, node, error code, and redacted logs, do not attach complete project files or unrelated data. If more material is needed, support will specify the scope in a ticket or email reply.

Review data handling before submitting

The Privacy Policy explains how account, order, support content, security logs, and website visit data are handled, including their purposes and retention principles.

View Privacy Policy

Confirm service and responsibility boundaries

The Terms of Service explain the rules for ordering, terms, delivery, availability, data export, suspension, and termination.

View Terms of Service

Ready to configure your cloud Mac?

Compare three machine tiers and four terms, then configure a node in Singapore, Tokyo, Seoul, or Hong Kong.