Records
Which record types Blocchi can work with in your workspace, who owns their data, and the lead queue.
Records (/app/records) shows every shared record type (people, organizations, leads, opportunities, agreements, invoices and payments), what Blocchi verifiably supports for each one in your workspace, and the queue of open leads.
Maturity is evidence, not permission
Each record type has a maturity level computed from what your workspace actually has connected and stored:
| Level | Meaning |
|---|---|
| T0 · Defined | Blocchi understands the concept, but nothing is connected yet. |
| T1 · Connected | A source is connected and can be read. |
| T2 · Stored | Records are stored in Blocchi with their source and history. |
| T3 · First-class | You can list, open, search and relate these records in Blocchi and through the API. |
| T4 · Actionable | Governed actions, events and automation work on these records. |
A high level never lets anyone change data by itself. You can lists what you can actually do, after data ownership and your role are applied. Records owned by another system (for example a connected CRM) stay read-only here.
People, organizations and roles
A customer can be a person or an organization. Customer, payer, guardian, supplier and the other roles describe a record's relationship with you; adding a role never creates a second record. Organizations can have contact people, who stay separate people.
Use New customer or New person and type what you know, for example "Gabriela Souza, WhatsApp 19 99876-5432, interested in an appointment". Blocchi prepares the fields, marks what it suggested, says what is missing instead of guessing, checks for existing records with the same email, phone or domain, and shows a summary before saving. Everything in the summary is saved together, or nothing is. Optional AI suggestions only use words you typed, and health or assessment details are never sent to AI.
Leads
A lead is an inquiry linked to a person or organization. Move it to review, qualify it, disqualify it (with a reason) or mark it converted. Each change shows a preview before it is applied. The Lead queue and governed create/transition actions are supported, but dedicated Lead details and scoped search are not available yet; Lead maturity remains T2 until those read surfaces ship.
How customers are presented
Workspace admins can choose Mostly individuals (B2C), Mostly organizations (B2B) or Both. This only changes labels and defaults; people and organizations can always both be customers.
Related
Last updated on