A ready-made CRM never matches your business one to one: one company cares about service objects, another about partners or equipment, and the card lacks a couple of fields. So the product can be adjusted to you: create your own fields, your own record kinds and convenient selections. It is all done by commands to the agent — the interface shows the result.
Custom fields
Contacts, companies, deals and other records can get your own fields — for example, “Fleet size”, “Industry code” or “Preferred communication channel”. A field has a name, a description hint and a type: text, number, date, an option list, a yes/no flag and others. A field can be made required and given a default value.
Such fields are not “glued on from the side”: records can be filtered by them in lists, they take part in write-time checks (an option list, for example, cannot be given a value that is not on the list — the attempt is rejected with a clear explanation), and they are described in the reference the agent uses. A created field works immediately — no restart needed.
There is also protection from losing the meaning of data: if a field is already filled on several records, it cannot be silently deleted or renamed — the product refuses and names how many records hold values. First the values are cleared, then the field is changed. This way numbers in the base never stay without an explanation of what they meant.
Custom objects
When the ready record kinds are not enough, you can create your own — for your industry. For example, “Service objects”, “Partners”, “Sites”, “Equipment”. A custom object has its set of fields and behaves like a full record: it links to contacts and companies, goes into the trash, has its own timeline, and selections work over it.
The main convenience: as soon as the object is created, its management appears automatically — the agent can create, read and change records of this kind at once, without any development and without a restart. The agent’s reference updates itself: it sees the new description and fields. An object with data cannot be deleted — first the records must be cleared or the object archived (then the data is kept, while the work with it pauses).
Import and export understand custom objects too: a spreadsheet of records of your own kind can be uploaded and exported like any other, and the columns map by the field names.
Labels
Labels are quick marks for any record: “important client”, “we work on prepayment”, “call mornings only”. A label is one per base, so it cannot be named almost like another one. If a label is renamed, it updates everywhere at once — the attachments are not lost. If two labels turned out to be about the same thing, they are merged: all the marked records move under the surviving label. Deleting a label removes it from all records but does not touch the records themselves. Labels are convenient for filtering records and seeing counters — how many records with each label are in the current list.
Saved views
If you regularly look at the same thing from a certain angle — “hot leads”, “deals without movement”, “clients without an owner” — that selection is worth saving. A saved view remembers the conditions and the column set and then opens with one choice. Views come as personal (yours only), shared (for everyone), hidden (visible only by link) and system (ready out of the box; they cannot be spoiled — only saved as a copy). Every user can have their own default view, so you see your convenient picture and your colleague sees theirs.
If a view “rots” over time — it referred to a deleted custom field, for example — it does not break: the failed condition is simply skipped with a warning, and the rest keep working.
Segments
A segment is a named group of clients assembled by conditions. It is needed everywhere you work with many people at once: for a mailing, for an export, for a bulk edit. Segments come in three kinds:
- By list — the membership is fixed: whoever was added is inside. This is convenient for “clients from the trade show” — a group that is not derived from the data but known to you.
- By conditions — the membership is computed by a rule, for example “no activity for 90 days” or “active clients in Munich”. A person gets into the segment or leaves it automatically when they stop matching the condition.
- Excluding — not a separate group but a subtraction from another: “send to everyone except these”. This makes it convenient to remove from an audience those who should not be written to.
Every segment shows how many members it has and how the membership changed at the last recount. And every question “why is this person here?” has an answer: by which condition they got in, and by which they dropped out.
Where this is configured
All of it is data, and the agent changes it by your request: “add a field”, “create an object”, “save this view”, “make a segment from these conditions”. The interface shows the result: the Model section displays the structure — which records exist, which fields they have and how they are linked. So you see what came out without going into the code and without studying complex forms.
Next → Leads