Contacts

Contacts is Clatri's unified directory. One single entry per contact across the whole app: the same contact you assign as the responsible party for a task appears as a counterparty on an expense in Money without duplication.

This solves one of the most annoying problems of having several modules: having to maintain "your mom" in three different places and reconcile manually. In Clatri, Mom is a single entry and everything else references that same entry.

Contact types

Each contact has a type that defines what it is:

Type	What it is
Person	A human being (family, friend, partner, acquaintance, professional).
Company	An organization: business, brand, institution, service provider.

The role a contact plays (client, vendor, lender, borrower, friend, neighbor, etc.) is not part of the type — it's described in the free-text relation field ("sister", "neighbor", "my bank", "key client") and inferred from usage. For example, a company can be a vendor of a recurring payment and at the same time a lender on an account payable; a person can be your sister and at the same time a borrower of a loan. You don't have to classify them upfront.

Fields

Any contact can have:

• Name — required
• Emoji — quick visual icon in the list
• Photo — avatar uploaded to storage (encrypted at rest like the rest). You upload it from the contact's card or ask Clatri for it in the chat: it can use a photo you attach or look for that person's public professional photo (their company's website, LinkedIn, press). If it doesn't find one that's clearly of that person, it doesn't set any and tells you so. Companies don't need one: they show their logo on their own.
• Email, phone, address — contact info
• Notes — free text for whatever you need to remember
• Relation — free text describing the bond or role ("sister", "my bank", "coffee vendor")
• Favorite — flag to make it appear first on the dashboard
• Link to a Clatri user — if this contact also has a Clatri account and shares an entity with you

Sensitive fields (name, email, phone, address, notes) are encrypted at rest using the user-derived key — see Security and privacy.

Automatic integrations

The contact directory is referenced from almost every domain:

Money: transaction counterparties

Each expense and income can have a counterparty — the contact involved. "Loan to Camila", "Payment from Carlos for lunch", "Birthday dinner with Andrés". It's a single source of truth: the same contact directory feeds the counterparty picker in Money.

A contact's detail in Money isn't a static card: it's a small report. It brings a summary —how many expenses and how many incomes are associated, their totals and the primary currency—, a "Where your money went" breakdown that splits what you spent with that person by account in the chart of accounts, and the transaction history, with See all to open the full list.

And from chat you can ask things like "how much did I spend on mom this month?" and the agent queries those grouped transactions.

Money: link transactions

The real problem isn't creating the contact — it's that you have hundreds of old movements that should point to it and don't. That's what Link transactions is for.

Clatri reviews your movements without a counterparty, scores them and proposes the ones that probably belong to that contact, with the reason for each suggestion in view: name match, previous payment. The Suggested ones go first; the rest stay below in case you want to search by hand. You check the ones that apply and confirm them all at once.

It's a proposal, never a decision: Clatri doesn't link anything on its own. A name match is a clue, not proof.

Money: projects

Projects group the income and expenses of a one-off activity that ends — a trip, an event, a side venture — and show you the net, not just what you spent. That's the difference that matters: a project answers "did I come out ahead?", not just "how much went out?".

A project can be linked to contacts from the directory, so the movements of a shared trip and the people you shared it with stay in the same story.

If the activity doesn't end —a running business, a service line— it isn't a project: it's a business inside your entity. See My businesses.

Administration: task assignee

Each task in Spaces can have an assignee. It's a contact from your directory. The picker reads directly from the same directory, so the list is always synced.

Calendar: invitees (future)

Calendar events in a future iteration will allow inviting contacts. They'll link to the same directory.

Via chat

The agent can create, edit, list and delete contacts. Examples:

• "add my sister Ana as a contact"
• "create a contact for Carlos, type vendor, email carlos@example.com"
• "rename the Pedro contact to Pedro García"
• "who are my favorite contacts?"
• "delete the duplicate John contact"

How it looks on the dashboard

In the Administration tab the Contacts section first shows favorites with their avatars. Tap See all opens the full list; tap directly on a contact from the dashboard opens its detail / editor.

What's NOT here

• Deep financial analytics on a contact (how much you owe them, what they owe you, detailed payment history, charts) → lives in Money. The Administration agent automatically redirects you when you ask about that.