Pre-sales evaluations, existing orders, technical issues, and partnership discussions require different information. Organize your use case, node, order number, or diagnostic output using the checklist, then choose support email or a console ticket so the team can move straight to confirmation or troubleshooting.
Your information is not submitted to the website. After you complete the form, your local mail app opens with the fields organized into a subject and message. If the issue relates to an order, submit a console ticket instead.
Describe the actual workload, not just “I need a Mac.” The number of parallel builds, dependency cache size, frequency of remote interaction, and node location all affect how you should use the host and whether you need additional storage.
Order issues should preferably be submitted through a console ticket. If you cannot access the console, you can generate an email draft; include the order number, term, node, and time the issue occurred.
Submit technical issues through a console ticket so you can add logs over time. Before sending, remove passwords, access tokens, private keys, certificate passphrases, and other private credentials.
Partnership inquiries also use support@runamac.com. Avoid sending only a high-level introduction; describe the participating teams, technical scope, expected timeline, and the specific work each side will complete.
Clear catalog boundaries reduce unnecessary clarification. RunAMac M4 is currently the only configuration offered and is normally available in five nodes; real-time availability and payment gateways are returned by the console.
The available scope is Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and US West. When contacting us, also include your team location, code repository location, artifact destination, and remote interaction frequency.
We support USDT-TRC20 and Visa, Mastercard, and Amex processed through Stripe. Gateway availability is determined by the console; for billing questions, include the order number, rental term, base host, and add-ons.
Email is best for initial pre-sales and partnership discussions. Console tickets are best for order-related issues, multi-round log collection, or cases requiring ongoing status tracking. Continue replying in the same thread for either channel.
The team first checks for the use case or order number, node, time of occurrence, and desired result. With complete information, we move directly to plan confirmation or technical troubleshooting.
If we cannot locate the record or reproduce the behavior, our reply will list the missing fields. Add them to the original email thread or ticket instead of splitting the issue across multiple messages.
Pre-sales questions receive configuration, node, and add-on guidance; order questions are checked against delivery and billing records; technical issues receive validation steps or requests for further diagnostics.
Once the work is complete, confirm whether the issue is resolved, the billing is consistent, or the plan meets the task boundaries. You can continue viewing the ticket status after signing in to the console.
Best for pre-sales evaluations, partnership discussions, or order details when you cannot access the console. Put the issue type in the subject and organize the message using this page’s field checklist.
Send to support@runamac.comBest for existing orders, delivery, renewals, billing, and technical issues. Sign in and submit from the ticket area, then add logs, screenshots, and reproduction results to the same ticket.
Sign in to submit a ticketThe console centralizes order and service information. For technical troubleshooting, organize the node, timestamps, error output, and reproduction steps from the relevant order before submitting a ticket.