Getting help
How to reach a person at X3D, what to put in the first message so the first reply is useful, how long a reply takes, and what support covers.
Four ways to reach a person, all of them reaching the same team in Austin. Email is the one to use for anything with a file or a photo attached; the ticket form is better when it concerns an order on your account, because it arrives with your account attached and gets a reference number.
How to reach us#
| Channel | Where | Sign-in | Reply |
|---|---|---|---|
| [email protected] | No | Within 24 hours | |
| Support ticket | The form at /contact | Yes | Within 24 hours, with a TKT- reference |
| Contact form | /contact | No | Within 24 hours, to the address you type |
| Phone | +1 (512) 850-4703 | No | 8AM–7:30PM daily |
A ticket asks you to pick a type — general enquiry, order issue, return or refund, print quality issue, technical support, or billing issue. Pick the closest one; it travels in the ticket's subject line, which is what it gets triaged on. You get a confirmation email straight away carrying the ticket reference, and replying to that email adds to the same thread.
What to include#
The first reply is only as good as the first message. Almost every slow support thread is slow because the first message was missing one of these four things.
- The order code. Orders placed through the API look like X3D-K7M2QP; a store or cart order code starts with STORE- or CART-. An API order's code is in the URL of its status page; a store or cart order shows its code at the top of the order on /orders.
- The file, or the model link. Attach the exact file you uploaded, not a re-export of it — the difference between the two is often the answer.
- What you expected. One sentence. "The holes should be 5mm and they measure 4.6" tells us more than a paragraph about the part's purpose.
- Photos, if it is a physical problem. Photograph the part on a plain surface with the layer lines visible, and include a ruler or calipers if the complaint is dimensional.
For an API problem, send the endpoint, the HTTP status code and the exact error string in the response body. Those three identify the failing check precisely, because every error the print API returns is a fixed sentence tied to one branch in the code.
What support covers#
| Support handles this | This is separate work |
|---|---|
| An order that arrived damaged, wrong, or not at all | Designing a model from scratch |
| A print quality problem — layer separation, warping, dimensions off | Repairing or remodelling a file so it prints |
| A file that will not upload, or an error you cannot interpret | Converting a drawing or a photo into CAD |
| Billing, refunds and returns | Engineering advice on whether a part will survive its load case |
| API errors, key problems, and integration questions | Writing your integration for you |
The line is roughly this: if it is about something we made or something our software did, it is support and it is free. If it is about making something new, it is design work and it gets quoted. There is no published rate card for design work — it is scoped per job. Use the Schedule a call link on /design to start that conversation.
Returns are 15 days from delivery, no questions asked. Shipping inside the US is $7 flat and free at $50 and above; international is $30 flat and free at $500 and above.
Before you write#
Three problems account for most of the mail, and all three have an answer here already.