Helpdesk — A ticket is a record

When somebody writes in, RowFold creates a row on one of your tables. Not an object inside a separate support product that you later reconcile against your real data. A record, on a table you chose, with columns you chose. Everything else follows from that. A ticket is in your reports because it is a record. It sits in a filtered view, fires an automation, respects your per-field permissions, appears in the audit trail, exports to CSV, comes back through the API, and can be asked about in plain English. None of that had to be built for support. It works because a ticket is not special. What is special is where it sits. Your Tickets table is one relation from Customers, and Customers is one relation from Orders, Bookings and Invoices. So the answer to “where is Tuesday’s delivery?” is not in another tab — it is on the record already open. Plain English: the customer asking the question and the customer in your orders table are the same row. There is nothing to sync. The ticket is an ordinary record. Its status, who it is assigned to and the customer it links to are columns on a table you chose.