No ticket number, no chatbot, no queue. One address, read by the people who built this. Tell us what went wrong, or what you wish it did instead — both are useful.
We are a small team, so that target is honest rather than contractual. If something is broken and stopping you working, say so in the subject line and it goes to the front.
None of it is required. But with these we can usually look at the actual run rather than writing back to ask which pack you meant.
Every pack has one, printed at the top of the PDF and in the header of every page — something like CJ-001. It is the fastest way for us to find the exact run.
“The back elevation” or “the measurement chart” rather than “the drawings”. A pack has twelve views and seven sections, and the fix is usually specific to one.
This matters more than it sounds. Often nothing is broken — the brief was read differently from how you meant it, and knowing what you wanted tells us whether to fix code or fix wording.
Every pack prints its own verdict and the list of anything that blocked it. If yours flagged something, paste that line in. Half the time it already names the problem.
Where the measurements come from, what the rules check, and what a pack does not prove.
Read the FAQ →A pack with a missing view or a blocking problem is held back on purpose, and it tells you which.
What you get →Most edits are a sentence and a re-run. Some are free, some re-run the checks, some need a fresh pack.
The Studio →Feedback is genuinely wanted, not politely tolerated. Seamix is early, and the fastest way it gets better is somebody telling us the drawing was wrong, the wording was confusing, or the thing they needed was not there.
If a pack came back wrong, send it. If a rule fired when it should not have, send that too — those are the ones that turn into real fixes. Same address.