Skip to content

CRM

This module is not about sales but about people and the work around them. The rest of the system keeps documents: the invoice is issued, the goods are shipped, the repair is closed. CRM keeps what documents never hold: who to call back, who is responsible, when you promised to arrive and whose time is booked for it.

It stands on three things. Contacts — the single reference of everyone the company deals with, and at the same time the source of the terms documents inherit. Actions (tasks) — the shared to-do list that both people and the system itself write into. Resources — whatever is occupied while the work runs: a technician, a bay, a lift.

Video walkthrough: CRM in ERPJS step by step — the customer card, a task, the process board and the next step by itself.

The route: from a contact to a closed job

Contact (customer, supplier, contact person)
        ↓
Task: type · group · executors · deadline · resource
        ↓
Process board — columns are task types, dragging moves the work
        ↓
Action consequences: close one → the system creates the next
        ↓
Reports: customer dossier · change history of the card
  1. Contact — the card of a customer or supplier. Not a form for tidiness but a set of terms: where the price comes from, how many days until payment is due, which currency to invoice in.
  2. Task — an obligation with an owner and a deadline. The type says what we are doing, the group says which line of business it belongs to, the executors group says who is on it.
  3. Company workflow — the board: a column equals a task type, and dragging a card changes that type. The work moves visually instead of through field editing.
  4. Action consequences — the "what next" rule: when a task is closed with a given outcome, the following one is created automatically.
  5. Resources with their types and accounting lists answer the question "whose time are we booking" — and feed the resource manager and online booking.

What is worth understanding

A task is not a note but an obligation. It has an owner, a deadline, a "done" state and, where needed, the booked time of a particular technician. That is why other modules write into this list: a service order creates a task on a status change, telephony on a call from a contact or service order card, online booking on a reservation from the website. The shared list is the point of the module: one work queue for the whole company.

The chain is held by the setup, not by a manager's memory. Action consequences turn separate errands into a route — diagnosis → approval → repair → handover. A step is not lost because somebody forgot to set a reminder.

The board does not display the process, it drives it. Dragging a card to another column changes the task's type, not a "status flag". So columns are worth defining as real stages of work rather than as moods.

Type, group and executor are three different questions. The type says WHAT we do (call, site visit), the group says WHICH line of business it belongs to (tool repair, implementation), the executors say WHO. Mixing them into one reference makes every filter useless.

A resource is not a job title but an occupancy. A resource type is a team of interchangeable ones (three technicians, two bays), and it is what lets a service avoid being tied to one person. Hire equipment creates resources too — that is how rental reaches the booking calendar.

The contact card is the source of the numbers in documents. So the contact change history is not a log for tidiness but an investigation tool: "why does this customer now have 30 days' credit instead of 10?"

Where to start in a new database

  1. Action types — they are also the columns of the future board.
  2. Action groups and executors groups — lines of work and teams.
  3. Resources, resource types, accounting lists — if you book technicians' or workplaces' time.
  4. Company workflow — assemble the board out of the types.
  5. Actions setting and consequences — so that work is handed out by itself.

Common tasks

You need Where to go
add a customer or supplier Contacts
assign somebody a job Actions
see the company's work as a board Company workflow
turn separate errands into a chain Action consequences
hand out work automatically Actions setting
book a technician's or a bay's time Resources · resource type
build a picture of the workload Resource accounting list
see everything about a customer before calling Customer Information Report
find out who changed a customer's terms Contact change history
export the contact base Contacts report · XLSX export

Everything in the module

Documents: actions

References: contacts · action types · action groups · action consequences · executors groups · resources · resource type · resource accounting list

Settings: actions setting · company workflow

Reports: contacts report · customer information report · contact change history

Maintenance: XLSX import · XLSX export

Where to look next