Contacts
The people behind the client
Every client comes down to a handful of people. schakl records them as contacts, attaches them to the right clients, and keeps track of who is the point of contact for what.
People, not accounts
Contacts are the people at your client: the signatory, the marketer, the technical administrator. They are kept separate from your own team, who are users with a role. Every contact carries a name, email, phone, job title and notes, plus any custom fields your organisation has defined.
One person, many clients
A contact isn't locked to a single client. The same person can be the point of contact at one client and the technical contact at another — that role lives on the link, not on the person. So you never enter anyone twice, and a contact's own page shows exactly which clients they belong to.
- Each link carries its own contact type and its own primary marking.
- Delete a client and the person remains; only the link falls away.
- The client page shows the contacts, the contact page shows the clients.
The primary contact
Each client has exactly one primary contact; the rest sit alongside as the others. You recognise the primary by the brand colour of its chip and nothing else — no star, no glyph. Click another chip to promote it to primary; the store allows only one primary per client, and because colour alone can't be read, a screen reader gets its own text label.
Add where you work
You create a contact from the client page itself. Type a name that doesn't exist yet and “+ add” appears — it opens the full create dialog (real fields plus your own custom fields), prefills what you typed, and attaches the new person to this client in one step. You never leave the screen, and you return with the chip already selected.
Types you define
What a contact actually is — client contact, technical contact, billing — is yours to define under Settings → Contact types. Types carry a label in every language and are set per client, because someone can be the point of contact at one client and the technical administrator at another. Every change to a contact lands in the activity trail with who and when, so you can always see how a value came to be.
Want to know more?
The documentation describes every module in detail, from installation to permissions.