§ 01 · Support
Help from the person who built it
Stuck?
Email us anytime.
Real answers from the person who built this. Email support — no tickets, no queues, no script-reading. If the FAQ and docs don't cover it, you hear back from a human, not a form letter.
Channels
Email
Real answer from a human, not a template.
FAQ & Docs
Most common questions answered before you ask.
Human fallback
Built by one person. You get that person.
No tickets · No queues
§ 02 · FAQ
Common questions
Four questions
every shop asks in week one.
The fastest way is to scan the supplier's barcode on receipt — the item, quantity, and unit (lengths, each, weight) pre-fill, you confirm the count, and it drops into inventory with a receive-date stamp. If you don't scan, add a SKU manually under Materials → Inventory. Low-stock thresholds you set per-SKU trigger an alert the moment you dip below, so nobody gets to the cut list before a reorder.
§ 03 · Docs
Documentation
Every answer, indexed.
Search
Getting Started / Account Setup
Full guide →
Install as App
Full guide →
Team & Roles
Full guide →
Projects & Scheduling (GANTT)
Full guide →
Resource Library
Full guide →
Time Tracking & QR Clock-In
Full guide →
Estimates & Change Orders
Full guide →
Inventory & Purchase Orders
Full guide →
Photos & Documentation
Full guide →
Exports & Reports
Full guide →
Billing & Subscription
Full guide →
Voice & Text Messaging
Full guide →
Settings
Full guide →
§ 04 · Videos
Watch, don't read
Short loops
of the exact workflow.
Most questions resolve themselves once you see the workflow in motion. These six cover the screens asked about most often.
How to reach us
Email first.
Tell us if it's on fire.
We read every message and reply as soon as we can. When the FAQ and docs don't have a clean answer, a real person steps in.
Email support
Support@fabricationplan.com
Best for most questions — real answer, not a template.
Primary
FAQ & Docs
Right here on this page
Written by the person who built the feature. Updated as the product grows.
Self-serve
Human escalation
Same person, same thread
One founder. If it needs a human, it gets the one who wrote the code.
Fallback