In Jestor, the open card lets you add more than one form in different side panels, each customized for a specific purpose within the same record. Why split information across several panels Putting all of a process's information into one long form makes the card confusing and hard
Yes. For Jestor's fleet management template to work fully with Omie, a low-code integration needs to be set up, done by request via email to Jestor's team. Why this extra step exists The connection between Jestor and Omie for automatic accounts-payable generation depends on
Yes. Although Jestor's fleet management template was originally designed for the towing vertical, it works for any type of fleet, since the layout and indicator placement can be freely changed after installation. Why the base works for other industries The template's structure — vehicles, maintenance, and fuel-
In Jestor's fleet management template, every expense logged for maintenance or fuel automatically generates a matching accounts-payable entry in Omie, without needing to log the amount twice. Why this automation prevents rework Without this integration, the team would log fleet expenses in a spreadsheet or tracking system,
In Jestor's task management template, the dashboard shows a dedicated chart displaying the count of tasks at each priority level — critical, high, medium, and low — separately and visually. Why viewing priority separately helps Without this split, the team would need to open every task to understand what'
Yes. Jestor's task management template is available in the template store both in the standard version and a dark mode version, both working exactly the same way. Why offer both versions Teams have different interface preferences, and some users spend hours a day looking at the task Kanban.
In Jestor, each contact in the sales template has its own chat, where the team logs internal conversations about that specific customer, separate from the contact's data and the external communication channel. Why separate internal chat from contact data Internal discussions about a deal — like "this customer
In Jestor's sales template, if the team tries to move a sale to the next phase without any product added as a line item, the system blocks the action and shows the error "sale with empty sale items." Why this validation exists A sale with no
In Jestor's sales force template, contacts, companies, and products live in independent registries, each with their own filters and form, connecting only when it's time to log a sale. Why separate these registries Mixing contact, company, and product into the same table makes maintenance harder: a
Yes. In Jestor, if there's more than one document attached in the configured field, the form automatically displays every PDF in sequence, one below the other. Why this is useful Some processes require checking more than one document at the same time, like a contract and its attachments,
Yes. In Jestor, the PDF viewer embedded in the form lets you flip through pages, zoom in, and use other reading tools without leaving the card or opening a new browser tab. Why this improves the workflow Before, viewing an attached PDF meant downloading the file or opening it in
Yes. In Jestor, you can use an existing app or table as a base and ask the AI to create a new version with specific adjustments, instead of building everything again from the start. Why this option saves time Often the team already has a similar process running, but needs