The client card carries the files.
Manage type, identifier and contact data on a client record. Linked cases, notes and other actions need their own grants and company/branch/case scope; not all data appears on one screen or simultaneously. The cards and appointment flow below are illustrative.
Clients
Client A
IndividualTCKN Format example2 cases
0532 000 00 00
Example Logistics Inc.
CorporateVKN Format example5 cases
0212 000 00 00
Client A
- Cases
- Notes
- Custom fields (with permission)
Linked cases
- 2026/42 E.Receivables casePending
- 2025/318 E.Eviction caseClosed
Power of attorney to be renewedAlarm: 20 November
01/04Client record sheet
Every client has a record sheet.
Enter a name/Turkish identity number for an individual or company name/tax number for a corporate client, plus email/phone and applicable fields. Authorized workflows may select the record; invoicing or document creation does not promise every field stays automatically linked or never needs re-entry.
- Type
- Individual or corporate.
- ID
- Type-specific format/checksum checks; not official person/company verification.Format check
- Phone
- Enter 10 digits in the interface; a leading 0 produces the stored 11-digit number. Invalid formats are rejected.
- Email and address
- On the same card, in the same place.
- Cases
- Only permitted accessible linked cases; the list is paged.
- Notes
- Note text and optional future alarm date; no guarantee of automatic notification delivery.
- Appointments
- Separate appointment workflow; availability is limited to checked appointments.
- Intake
- Intake conversion is optional; direct client creation is also available.
The card and linked workflows use separate permissions.
- 01/04
Identifier format and checksum checks
Identity/tax-number length/checksum rules apply before saving. Passing does not mean an official population/tax-service lookup, ownership of the number or verified legal identity. Invalid input must be corrected before saving.
- TCKN
- Must be 11 digits, the first digit cannot be zero, and the last two digits are check digits calculated from the previous ones.Rejected example: A 10-digit number
- VKN
- Must be 10 digits, and the last digit is the check digit.Rejected example: A 9-digit number
- Phone
- 10 digits in the interface; 11 stored with the leading 0.Rejected example: A number with letters or an invalid length
- 02/04
Cases and notes
The web card has an information summary, Cases and Notes, plus custom fields when permitted. Cases are server-filtered by client ID and require full/assigned case reading and current company/branch/case scope. Web pages contain 50 rows; not every case is loaded simultaneously. Details open in case management.
Notes have separate read/create/update/delete grants. An optional alarm date is stored on the note; it does not legally calculate mandate expiry, complete a task or guarantee a phone notification. The sample date is not an actual reminder.
Power of attorney to be renewedAlarm: 20 November - 03/04
Appointments
Suggested times for a selected active company member/day use appointments checked by the system. This does not mean every hearing, external calendar or work schedule is searched. A meeting kind does not automatically create a meeting/call link.
Saving rechecks appointments and rejects detected overlaps. Creation needs its own grant and writable company/branch. The web calendar reads a separate source; export depends on a configured/authorized connection, target, plan and queue conditions.
- Office
- The client comes to the firm.Lawyer, start and end time, subject.
- Online
- The meeting is held remotely.The same fields; if the client is not registered, the name and email of the person who asked.
- Phone
- The lawyer or the firm calls the client.The same fields; the record goes through the same calendar conflict check.
Illustrative appointment flow; performs no real save, availability query or export
Lawyer ExampleMon 12Tue 13Wed 14Thu 15Fri 1609:30Example busy Example busy11:00 Example busyExample busy Example busy14:00Example busy Example busy16:30 Example busySubject
File assessment meeting
Meeting type
- Office
- Online
- Phone
Sample record; not an actual appointment
Checked appointment overlaps are revalidated
Illustrative calendar view
Tue 14:00, meeting with Client A
Appointment screen
- 1/6
Appointment screen
Open the separate appointment screen with permission; do not assume the same form is embedded in the client card.
- 2/6
Lawyer and day
Pick the lawyer who will hold the meeting and the day.
- 3/6
Available slots
Suggestions use checked appointments; not guaranteed complete availability across hearings or external calendars.
- 4/6
Slot, subject and type
Choose the time, write the subject and mark office, online or phone.
- 5/6
Save and conflict check
A real save rechecks overlaps; this illustration saves no record and reserves no time.
- 6/6
Visible in the agenda
Calendar reads the appointment through its own permissions/query. Google/Microsoft export has separate setup/plan/access/queue conditions; instant delivery is not promised.
- 04/04
Mobile and import
Mobile supports client create/edit/delete with their respective grants; it is not read-only. Linked cases use clientId-filtered pages of 20 with full/assigned case reading. Notes, contact consent, privacy requests and custom fields have their own authorized surfaces. Showing phone/email text does not promise one-tap calling/email; real-device acceptance is separate.
Prepare CSV/XLSX for the target template, map columns and review the preview. Data transfer processes approved rows in the background with import/target-create grants and a writable branch; every row succeeding or complete automatic migration from an old system is not guaranteed. Review results; the migration guide supports preparation.
03/04From intake to client
Direct creation or intake conversion
Create a client directly or convert an unconverted Active Client intake through a type/identifier/address form. A writable branch and relevant grants are required; a stored conflict check is not a technical prerequisite. Identifier checking is format/checksum only; legal review is separate. The intake guide and office solution describe the general process.
What do people ask about client management?
- 01/06
What happens if a TCKN or VKN is entered wrong?
Invalid identity/tax-number format/checksum is rejected. Valid format is not official identity verification or confirmation that the number belongs to the person.
- 02/06
Where do I see all of a client's cases?
Only authorized accessible linked cases are shown: pages of 50 on web and 20 on mobile. Client reading needs separate full/assigned case reading. Do not assume all company cases arrive in a single complete load.
- 03/06
Can the client book an appointment themselves?
In this workflow an authorized staff member uses the separate appointment screen. Booker name/email may be entered for an unregistered person; this is not a public self-booking service or client portal.
- 04/06
How does a note alarm work?
An optional future alarm date is stored with the note. This record data guarantees neither automatic every-channel delivery, reading nor legal deadline calculation.
- 05/06
Can I import my old client list?
Prepare CSV/XLSX for the target template; mapping/preview/approval/background results are separate steps. Required grants, writable branch and row rules apply. The guide supports preparation; complete automatic migration is not guaranteed.
- 06/06
Is consent needed before sending a client an SMS or WhatsApp message?
Yes. On the client card, SMS and WhatsApp consent are recorded separately for the registered phone number. An evidence reference is entered for each permitted channel, and who recorded it and when is kept. Messages to the client are not sent unless the consent record matches the current phone number and the channel is permitted. The record does not show that consent is legally valid; obtaining and proving consent remains the office's responsibility.