In Jestor, every WhatsApp conversation becomes a card with data visible directly on the panel — including the exact number of messages and time spent at each stage — also consolidated in a complete operational dashboard. Why does seeing this outside the card save time? Instead of opening each conversation individually to
In Jestor, the practical rule for deciding required fields is simple: information essential for the process to move forward — like a supplier's name, email, and phone — tends to be required, while internal control data, like a description, can be optional. Why doesn't every field need to
In Jestor, a single-select field — like a supplier or stage status — can enable log metrics that show how long each record stays stalled in a stage and the movement time between stages on the Kanban. Why do these metrics depend on a single-select field? Since a single-select
In Jestor, the checklist field lets you choose between different visual styles — like green/red, yes/no, happy/sad faces, or custom emojis — to represent whether an internal audit item has been validated. Why is a checklist different from a simple checkbox? Besides marking item by item, Jestor's
For payment deadlines in Jestor, a plain date field is usually more suitable than a date-and-time field — since payment can happen at any time on that day — while a date-range field is used to represent a period during which the payment can be made. Why can date-
In Jestor, a currency-type field lets formulas and reports sum values automatically, something a plain text field doesn't support, since text can't be used in math operations. Why not just use a text field with the value? Typing "$100" as text might look
Yes. In Jestor, when filling out a linked-record field — like the supplier on an accounts payable entry — you can create a new supplier on the spot, without leaving the form you're filling out. Why does this avoid interrupting the entry? Without this option, the person would need
In Jestor, AI credits and processed pages (OCR) are separate metrics: credits cover general AI use on the platform, while processed pages specifically count the document reader's usage, in a more predictable way. Why does separating these two metrics make tracking easier? Before, reading images counted as variable
When building a cost center table in Jestor, using a sequential ID field together with a name field lets you keep code-based organization — common in companies that number their cost centers — without losing the name's readability during allocation. Why doesn't the ID or the name
Before deciding to switch ERPs, it's worth evaluating whether what's missing isn't the accounting or financial module itself, but rather a complementary operational layer — like approvals, AI, and more process flexibility — that the ERP wasn't designed to cover. Why doesn't
In Jestor, the Random ID field lets you build friendly codes, combining a fixed process-related prefix (like "AG" for appointment) with a sequential or random part, in a format the customer will actually recognize. Why does a friendly code matter in customer communication? An identifier like "
In Jestor, the Random ID field can be used in the subject line of automatic ticket emails, giving the customer a unique, recognizable identifier without relying on a sequential ID that exposes the total volume of records. Why can a sequential ID be a problem? With sequential IDs like 1,