Always open. Tracked by ticket.
support@fabrixa.com — a ticketed inbox. Auto-acknowledged within minutes; first human response within 4 business hours. Every issue gets a ticket and a paper trail.
The customer-support inbox. For order-specific issues, account help, returns, quality concerns and billing questions. Different from commercial questions — volume, pricing and contracts — and from solutions engineering, which handles API integration. One ticketed channel with a published SLA, and a priority path when production is on the line.
Routing the question to the right team upfront cuts the back-and-forth dramatically. A quick reference for who handles what:
Everything runs through the ticketed inbox, so nothing gets lost and every issue has a paper trail. Production-blocking issues jump the queue; Enterprise accounts have their own escalation paths.
Always open. Tracked by ticket.
support@fabrixa.com — a ticketed inbox. Auto-acknowledged within minutes; first human response within 4 business hours. Every issue gets a ticket and a paper trail.
For production-blocking issues.
Mark the email subject [CRITICAL] when an active production order or a live customer-facing flow is affected. Critical tickets get a first response within 1 business hour and a same-day resolution path.
Contracted, tighter SLAs.
Enterprise customers get tighter SLAs in their Master Supply Agreement — a dedicated support manager and priority escalation paths. If you’re on an MSA, use the contacts in your agreement first.
Not sure whether your issue is support, commercial or engineering? Route it with the table above — or talk to our team and we’ll get it to the right person.
Standard-tier published SLAs. Enterprise-tier customers get tighter SLAs in their MSA — including a dedicated support manager and priority escalation paths.
First response within 1 business hour, with a same-day resolution path. Reserved for issues affecting an active production order or a live customer-facing failure.
First response within 4 business hours; resolution within 1 business day. Examples: a damaged shipment, order tracking lost, a billing error on an active invoice.
First response within 1 business day; resolution within 2–3 business days. Most account questions, refund processing and knowledge-base gaps.
For genuine production-blocking emergencies, mark the email subject [CRITICAL]. The escalation path is reserved for actual emergencies — abuse blunts the channel for the customers who need it.
Every Fabrixa unit goes through QC before dispatch. If something arrives with a defect — print misalignment, a finishing flaw, fabric damage, the wrong size cut — contact support within 30 days of delivery with photos and the order_id. We reproduce the affected units at no charge or refund the unit cost, whichever your customer prefers.
Carrier-damaged shipments are handled separately — we file the carrier claim and bridge the customer experience while the claim resolves. You don’t deal with the carrier directly.
Including these details upfront moves the response from “can you tell us more” to “here’s what’s wrong” in one fewer email cycle.
The Fabrixa order_id (it starts with ord_) or your internal order_ref. Lets us pull the order record without back-and-forth.
For quality, defect or damage issues: clear photos of the affected unit, plus the shipping label visible on the parcel for damage claims. JPEG or PNG is fine.
What you expected versus what arrived. Helps us scope the issue — production defect, file-prep issue, carrier damage or a mis-spec at the order stage.
The support team is staffed during business hours. Tickets opened outside business hours are queued for the next morning’s first triage. Critical-severity tickets get same-day attention regardless of hour.
Portuguese, Spanish and Dutch public holidays affect production-hub availability, and standard EU bank holidays affect support availability. Major holiday windows — Christmas and New Year, Easter, mid-August — are announced 30 days ahead via email and a dashboard banner.
Still looking for an answer? The knowledge base and FAQs resolve most questions without a ticket — and the Platform Guide walks through every screen in the dashboard.
One inbox, real humans, published SLAs. Commercial questions go to /contact/. Technical and API questions go to solutions engineering.
Every screen of the platform explained — from signup to dispatch. Setup, designs, channels, orders, billing — in plain English.