2. People
Everything in CRM City hangs off a contact. Deals, invoices, bookings, tickets, enrolments, donations — all of them point back at a person. Get this chapter right and the rest of the product has something to stand on.
2.1 Contacts
A contact is a person. Name, email, phone, addresses, date of birth, where they came from, plus whatever custom fields you have defined.
Addresses have no limit. A person with five houses gets five, a supplier gets its office, its factories and the one address you post to. Each has a type (Home, Work / business, Postal / correspondence, Billing, Delivery, Other), an optional name of your own ("Factory 2", "Head office, post only"), the standard lines (address line 1 and 2, town or city, county or region, postcode, country) and a free-text note for anything that does not fit the lines. On the contact's page each address sits in its own card. Add or change them with Edit, using "Add another address". Like email and phone, an address is part of the contact's identity: an owner who hides identity from a role hides the addresses too.
Three fields do more work than they look like they do.
Source records where the person came from — an import, a web form, a booking,
Telegram, the API. CRM City fills it in when the contact arrives, and you can correct it
or fill it in on the contact's Edit page. It shows under Details on the contact. Your
preset may give it another name: "Lead source" on Sales, "How we met" on Personal. Six
months later this is how you find out which channel actually brings you people worth
having.
Last contacted updates itself. You never set it. Every activity logged against
the contact pushes it forward automatically, at the database level, regardless of
whether the activity came from you typing a note or from an email captured by BCC.
It only ever counts what has already happened: a meeting you log ahead of time, for
tomorrow or next week, moves it on the morning after the meeting takes place, not on
the day you wrote it down. A booking made through your booking page counts the same
way, and a booking that is cancelled never counts. An activity dated years back never
pulls it backwards. The time you pick when logging is read in your own time zone.
Lead score is a running total, not a snapshot. Behaviour adds and subtracts
points, and crossing a threshold emits an event of its own. Covered in chapter 6.
The timeline
The contact page merges activities, reminders and emails into one chronological timeline. This is the answer to "what is going on with this person" and it is the reason to log things: the value is not in any single entry, it is in being able to read two years in thirty seconds.
At the top of the page, under the name, a Last time line shows where you left off: what the latest entry was, how long ago, and the start of what was written. If a message in a conversation came later, the line shows that message instead. Something booked for later does not count, because it has not happened yet. See activity takes you down to the full timeline. If nothing has been written yet, there is no line.
Reminders can repeat: yearly on the calendar date (name days, anniversaries — the date never drifts, leap years included) or every N days, from daily upward (a visit you make three times a month is "every 10 days"). Ticking a repeating reminder does not close it — it schedules the next occurrence, computed from the planned date, and skipped cycles are jumped over rather than piling up as overdue copies.
Deleting
Two levels, deliberately different.
Delete is recoverable. The contact disappears from lists but the row survives, and it can be brought back.
Erase is permanent and irreversible — the GDPR right to be forgotten. Because it cannot be undone, it makes you type a confirmation phrase by hand, including the person's name. That friction is intentional. If you can erase someone by clicking twice without thinking, eventually you will.
What erasure clears, and what it deliberately does not. Erase removes the person from the live database: their record, their timeline (notes, calls, meetings), orders, donations, event places, course enrolments and certificates, the messages they wrote, and every copy a connected platform or webhook carried. Your business record stays, with the person unlinked: invoices, deals, quotes and tickets, and the notes written on them — those are your bookkeeping, the same category as the invoice. Their address stays on your do-not-email list, so a later import can never email them again. Export first if you need the donation or order history for your books.
A connected platform can ask for the same erasure. When someone leaves a platform that
brought them into your CRM and asks to be forgotten, the platform can erase them here
through the API with its secret key (DELETE /api/crm/contacts/:id). It is exactly the
erasure above, not the recycle bin, and it reaches only your organisation's contacts. A
person you moved to the recycle bin is found and erased too: the platform's search can ask
to include the bin, so binning someone does not keep them here after they asked to leave. The
audit log records it as an erasure by "system"; the name of the key that asked for it is
kept with the entry and comes out in the full export.
Which leads to the one habit worth adopting on day one: write about the work on the deal, the invoice or the ticket, not on the person's timeline. Those notes survive an erasure; timeline notes go with the person. And keep identifiers out of them: "email her at maria@…, sister of the landlord at 12 Elm St" plants personal data in a field no automated erasure will ever find. The product clears every structured field for you — free text is the one place where minimisation is your job, not ours.
2.2 Companies
A company is an organisation, and the link between contacts and companies is many-to-many. One person can belong to several organisations, and one of those links can be marked primary.
This matters more than it sounds. Many CRMs make a contact belong to exactly one company, which forces you to duplicate a person who sits on two boards, or consults for three clients, or is both a member of your church and a supplier to it. Here you do not duplicate — you attach them twice.
Adding a company to a person is one field, Company, on the contact form and on the contact's page. Start typing: your existing companies are suggested, so you pick the same "Acme Ltd" rather than create a second one, but any name is accepted, and a new one is created when you save. A role ("Director", "Buyer") is optional. Each company then sits in its own row below the field, with a star to make it primary, a pencil to edit it and a bin to remove it from the person; hover over a symbol to see what it does. Removing a company from a person never deletes the company itself.
The company page lists its people. Focus mode (chapter 3) can narrow the entire dashboard to a single company.
2.3 Activities
An activity is a thing that happened with a person: a call, an email, a meeting, a message, or a note.
That last one is different from the other four in a way that matters. A note is something you write about someone; the other four are contacts they actually experienced. The product knows the difference and uses it — over-contact is counted from calls, emails, meetings and messages only. Otherwise the most conscientious note-taker in your team would look like the biggest pest, which would be exactly backwards.
Quick catch-up
On the dashboard and on contact pages there is a one-line box. You spoke to someone, you write one line, you press enter. That counts as a touch, refreshes their health immediately, and takes them off the neglected list.
It exists because the alternative — a form with a type dropdown, a date picker, a subject and a body — is the reason people stop logging things after two weeks.
What fills in by itself
Inbound email captured by BCC, Telegram messages in and out, public bookings, and events pushed in through the API or a connector all land on the timeline as activities without you doing anything.
What you have to log by hand is everything that happened offline. That is the honest cost of using this product properly, and it is small.
2.4 Tags
Free-form labels on contacts and companies. Create them in Settings → Tags, then
attach them anywhere.
Tags are not decoration — they are the segmentation mechanism the rest of the product
reads. A tag can be a campaign audience, an automation condition, an automation
action ("when a deal is won, tag them customer"), an API segment filter, or a focus
lens.
Practical advice: keep them few and mean something. Thirty tags with four contacts each is a filing system nobody uses, including you.
2.5 Custom fields
Settings → Custom fields. Define your own fields on contacts or companies — text,
number, date, select, and so on. They appear on the forms and are editable inline on
the record.
Tick Required and the field has to be filled in whenever someone types into a form: on the record, and when they create a contact or a company. Leave it empty and the form will not save, and it tells you which field is missing. Contacts that arrive another way, through an import, an agent or your booking page, are still saved without it.
This is how the product moulds itself to your work without a developer. An estate agent needs "budget" and "preferred area". A pastor needs "small group" and "baptism date". A coach needs "goal" and "sessions remaining". None of those belong in a general CRM's schema, and all of them are the reason people abandon general CRMs.
Presets pre-create a small set at onboarding so you start with something rather than an empty page.
2.6 Duplicates
Two mechanisms, at different moments.
At creation, the form warns you if what you are typing looks like someone already in the database: the same email or phone, or the same person written differently, using the same rules as the Duplicates page below. The warning names the contact and says why ("Similar name: Jose Perez, José Pérez"), so you can open it instead. It never stops you: "Create anyway" creates the new contact. The candidate form under Recruitment warns only on the same email or phone, because it has no "Create anyway" button.
Afterwards, Settings → Duplicates lists candidates and lets you merge. You pick
which record survives; every related row — activities, deals, tags, files, enrolments,
company links — is re-pointed at the survivor, and the losing record is soft-deleted.
Nothing is lost. The merge is written to the audit log.
It finds records that are the same, and records that are written differently but are probably the same: a name with or without accents or in another order ("Smith, John" and "John Smith"), a Gmail address with or without dots or a "+" tag, a phone number written the national or the international way ("07700 900123" and "+44 7700 900123"), a company with or without "Ltd" or "Limited", and a first name one letter apart when the surname is the same ("Jonathan" and "Johnathan"). Each group says why it was found: "Same …" when the records match exactly, "Similar …" when they only look alike. A similar match is only a suggestion, so check it before you merge.
2.7 Getting people in
Import (Import) for a spreadsheet or a migration from another CRM. It reads CSV
files and Excel workbooks (.xlsx, first sheet only), up to 10 MB and 50,000 contacts per
file. Formulas are never run: a formula cell imports the result saved in the file. Google
Sheets and Airtable export CSV. For JSON, use the API (chapter 11).
A large file is sent in parts of at most 5,000 contacts or 2 MB each, one after another; you do not split it yourself. Your plan's contact limit is checked against the whole file first, so a file that does not fit is stopped before anything is imported. If a part cannot go in (the connection drops, the plan filled up in the meantime), the parts before it stay imported and the button continues from that part.
Run automations and webhooks for these contacts is off by default, so an import only adds the contacts. Tick it when you want each imported contact to count as a new one: your automations, lead scoring and webhooks then react to each of them as if you had added it by hand (chapter 6), so an automation that creates a task for each new contact creates one for every row in the file, and the file goes in smaller parts, of at most 200 contacts each. The box can be changed only before the first part is sent. If some imported contacts did not reach your automations and webhooks, the message after the import says how many. They are in your contacts, but importing them again would add them a second time.
The file is checked as soon as you choose it, and again when you press Import. Each
field has a length limit: 200 characters for a name or a company, 50 for a phone
number, 32,767 for notes. The message names the contact to fix. An email that is not a
real address ("n/a", "ana@gmail") does not stop the import: that contact comes in
without an email, and a task on your Home page names the contacts to fix, with what the
file said. When two columns mean the same thing (email and mail), the first one
with a value in it is used.
The company column links each contact to a company. A name that differs only in
capital letters is the same company ("Acme", "ACME" and "acme"); anything else is
another company ("Acme" and "Acme Ltd"). An existing company keeps its name as it is;
a new one is created with the name as first written in the file.
Scan card (Contacts → Scan card) photographs a business card and creates the
contact from it, with a greeting drafted automatically. Limited by plan and monthly
quota, because unlike everything else in this chapter it costs us money per use.
Settings → Billing shows how many you have used this month.
My network imports contacts between organisations you own — if you run more than one organisation in CRM City, you do not have to type the same person twice.
The API and connectors create contacts from your website, your shop, or anything else you connect. Chapter 11.
2.8 Files
Contacts and companies can hold files. Uploads are stored privately and served through time-limited signed links, not public URLs.
Telegram media and inbound email attachments land here automatically — if someone sends you a photo on Telegram, it ends up on their record without you saving anything.
2.9 Finding people
Global search sits in the top bar everywhere and searches contacts and companies in one pass. Two keystrokes to any record.
Focus mode is a different thing and is covered in chapter 3 — it narrows the whole dashboard rather than jumping to one record.
2.10 Sending identities (business cards)
Account. A business card is a sending identity: a label, a context and a display
name. One person can have several — "Personal", "Pastor", "Marketing" — and pick which
one an email goes out as.
They are also printable, as actual digital business cards.
You need at least one before the email composer can be used, because the composer asks who is writing, not just what. A personal note does not send yet: it waits for your own mailbox, which can't be connected yet; see Chapter 5 — Email.
What to read next
Chapter 3 — Attention. That is where the records in this chapter start doing something for you rather than sitting there.
