Records
A record is one row — one wedding, one task, one contact.
Difficulty 1/5
Plain English
A record is one complete thing in your system: one wedding, one lead, one message thread. It is the unit you create, edit, or delete. Users think in records ('add a task'), not in tables.
Analogy
One index card in the filing cabinet — all the lines on that card belong to the same thing.
Jessica's wedding portal
The wedding 'Ana & Luis — March 2026' is one record with its own id.
Agentify CRM
One contact with name + phone is one record.
Go deeper
One item: one task, one contact, one order.
Common mistakes
- Treating a list UI as the source of truth instead of the records behind it.
- Creating duplicate records instead of updating the same id.
AI-agent trap
Agents sometimes insert a second record instead of patching. Say: 'update record X'.
Summary
Records have a stable id so you can link to them, update them, and show them in lists. Lists are many records; detail pages are one record.
Confidence: