3. Attention

This is the chapter that explains what CRM City is for. Everything in chapters 1 and 2 is bookkeeping; this is the part that does something you cannot do yourself.


3.1 Relationship health

Every contact carries a health colour. There are three, and they are not a warm-to-cold scale with one bad end.

Meaning When
🔵 Blue You are neglecting them No contact for longer than their rhythm (30 days unless you set one). Never contacted: blue that long after you added them
🟢 Green Healthy In touch, without crowding them
🔴 Red You are crowding them More touchpoints in 14 days than their rhythm allows (5 unless you set one)

Green is a target between two errors, not the top of a ladder. That is the whole idea.

A contact you have never been in touch with is not blue straight away: someone you added this week has not been neglected, they have not had time to be. Until the gap since you added them reaches the line, they carry no dot at all, and they do not appear in the neglected list. After that the silence is counted from the day you added them. If you set a contact's rhythm (below), its line replaces the 30 days, here as everywhere else.

Blue is not one shade. The longer the silence runs past the contact's rhythm, the darker the dot gets, without steps, until it is almost black at six times their rhythm: six months for someone on the usual 30 days, less for someone you speak to often, more for someone you see a few times a year. A week past the line and a year past it no longer look the same.

Why the second half exists

Neglect is easy to see once someone points at it. Crowding is invisible from the inside, because the person doing it never feels it — only the person receiving it does, and they do not complain, they just go quiet.

That is why CRM City counts every kind of touch, calls, meetings, messages and emails, against a rhythm you can set for each person, and turns a contact red when you cross it.

What counts as a touch

Calls, emails, meetings and messages. Notes do not count. A note is something you write about a person, not something they experienced; if notes counted, the most disciplined record-keeper on your team would show up as the biggest nuisance.

Everything counts regardless of where it came from — an email you typed by hand, a campaign send, a sequence step, a booking, anything pushed in from a connected system. This is deliberate: it is the only way the number reflects what your organisation is actually doing to someone, rather than what you personally remember doing. A campaign lands on the same counter as a phone call, because from the other side it is the same thing — you contacted them again.

Telegram messages and logged conversations count too, with two rules worth knowing.

A message they sent you keeps the relationship alive but never makes you red. They contacted you; you did not crowd them. Inbound moves the clock, nothing more.

Group conversations do not count towards crowding. In a one-to-one thread, what you write is aimed at that person. In a group, they joined a shared space, and the traffic there is not directed at them. Otherwise a small-group leader posting daily would turn twelve people red in a week, and the warning would become noise for exactly the people it was built for. Group messages still count as contact for the quiet side: if you are talking in the same room, the relationship is alive.

Red beats blue

If someone has been silent for six months and then receives five things in a fortnight, they are red, not blue. Excess is an error in its own right, no matter how recent the last contact was. In practice this catches the most common failure in the product: you notice a neglected list, you enthusiastically re-engage everyone at once, and you turn neglect into crowding in a single afternoon.

Where you see it

On the dashboard, on contact lists, and on individual records. The dashboard surfaces the people you have neglected longest, oldest first — which is the right order, because the longest silence is the hardest to recover.


3.2 Variety — the second axis

Colour answers how often. It does not answer how same.

A person can sit comfortably in green and still be receiving nothing but broadcasts: the monthly newsletter, the campaign, the sequence step. Correct tempo, identical content. That is still the song you switch off — however well-spaced it is.

So there is a second, independent signal. When someone has had three or more bulk sends in 90 days and nothing personal at all, the contact page says so.

It is deliberately independent of the colour, because you can be green and monotone at the same time, and that combination is the easiest one to miss. The numbers look fine. The relationship is still going flat.

Two windows, on purpose: intensity is judged over two weeks, sameness needs three months. If they matched, the two signals would be saying the same thing in different words.

The warning is not asking you to send more. It is asking for one line written for that person alone, which is worth more than another well-timed broadcast.


3.3 Reminders

A reminder is a dated follow-up attached to a contact. Create one when you promise something, and it appears on your dashboard the day it is due.

Automations can create them too, which is where they become useful at scale: "when a deal is won, remind me in thirty days", "when someone submits feedback below three stars, remind me tomorrow". Chapter 6.

In the product, reminders and tasks are one thing, listed under Tasks: a dated follow-up, about a person or a piece of work (3.4).

A contact's Next contact date works the same way without a separate reminder. On the day it arrives, the person appears on your dashboard under the day's tasks, and stays there, marked overdue, until you change the date on their page.


3.4 Tasks

A task is a dated follow-up, about a person or a piece of work. Give it to yourself or to anyone on your team; it appears on their dashboard the day it is due and stays there, overdue, until it is ticked off. Tasks can repeat, every year or every few days.


3.5 The calendar

A single monthly view that merges everything with a date on it: bookings, tasks and events. Rather than checking three separate lists to find out what next Tuesday looks like, you look once.


3.6 Birthdays

If a contact has a date of birth, the product runs a daily check at 07:00 and creates a task for the owner on the day. It also emits a contact.birthday event, which means an automation can act on it — add a tag, create a reminder, notify the team, and send the greeting through your organisation's own email account, once it is connected (chapter 5).

Birthdays are a native field on the contact, not a custom field, and the daily check reads it. Importing a spreadsheet does not bring dates of birth in yet: add them on the contact.


3.7 Focus mode

A lens over the dashboard. Set it to a group, a company or a tag, and every list on the dashboard (tasks, follow-ups, neglected contacts, contact count) narrows to that slice.

The use case is having one CRM that behaves like several. A pastor with six small groups focuses on one and sees only those members. A consultant focuses on one client account. Nothing is hidden permanently and nothing is duplicated; you are looking through a lens and you can take it off.

Focus is remembered between sessions, which is worth knowing when the dashboard looks emptier than you expected. Check the focus selector before concluding something is broken.


3.8 How to actually use this

The honest workflow, once your people are in:

Look at the dashboard first thing. It tells you who has gone quiet and what is due. That is the whole ritual; it takes a minute.

Deal with the longest silence, not the whole list. The list is ordered oldest-first for a reason. Two people properly re-engaged beats thirty generic messages, and the thirty generic messages will turn a chunk of your list red.

Log the offline stuff. The phone call, the corridor conversation, the coffee. If it does not get logged, the product will keep telling you that you are neglecting someone you spoke to yesterday, and you will stop trusting it — which is the real failure mode.

Watch for red. Red is not a badge of effort. It means someone is being crowded and is probably about to stop replying. The correct response to red is to stop, not to try harder.


3.9 Away mode

Going on holiday? Open Settings → Away mode, choose the day you are back and turn it on. Until the start of that day (UTC), the reminders and notifications you choose stay quiet: Email and Telegram, both on by default. Phone notifications (3.10) always stay quiet while you are away. Security alerts and billing emails still reach you, because those are the ones you would want on a beach. Telegram notifications go to your organisation's chat, so the Telegram switch only works when you are the only member; with a team, the chat keeps coming.

Everything else keeps running as usual. Sequences, automations, campaigns, review requests and booking confirmations go to your contacts exactly as they would if you were at your desk, and your teammates still get everything meant for them. Away mode is yours alone: it does not pause your organisation.

When you are back, you get one summary instead of a pile of alarms: the tasks that came due, the approval requests that were answered and the notifications that came in for you while you were away. It arrives by email, and in the notification bell when something came in, within the hour after your return date. Back early? Press I'm back and the summary follows within the hour.

3.10 CRM City on your phone

CRM City can sit on your phone's home screen like any other app, with no app store involved. Open Settings → Phone app on your phone and follow the steps it shows for that phone:

  • Android: open crmcity.app in Chrome, sign in, then tap the menu (three dots) and Install app or Add to Home screen. When Chrome offers the install itself, the page shows an Install CRM City button.
  • iPhone and iPad: open crmcity.app in Safari, sign in, tap Share, then Add to Home Screen. Open CRM City from its new icon and sign in there once: on an iPhone the home-screen app keeps its own sign-in.

It is the same product at the same address, with the same sign-in and the same two-step check. Nothing from your organisation is kept on the phone: the app keeps only its icon and a "You're offline" card, so without a connection it tells you so instead of showing an old page. Signing out clears what it keeps.

Your day's list, on your phone

On the same page, under Notifications, tap Turn on notifications here and allow them when your phone asks. On an iPhone this works only in CRM City opened from the home screen, with iOS 16.4 or later. Then choose how the list reaches you; the settings are yours alone and apply to every device where you turned notifications on:

  • Send it at: the hour, in your phone's time zone. The list holds what is due today and what is overdue: your own tasks, and unassigned ones in an organisation you own. On a day with nothing to do, nothing is sent.
  • If I don't open it: nothing more, or a reminder every 5, 10, 15, 30 or 60 minutes, up to six more times. Opening the notification, or tapping Got it, stops them for the day.
  • Snooze for: how long Snooze puts it off before it comes back.
  • Keep it on screen until I deal with it: a longer vibration, and it stays until you tap it. Android phones and computers honour this; an iPhone shows it the usual way, and does not show the Snooze and Got it buttons.
  • Quiet hours: nothing arrives between the two hours you choose; a list due then waits until they end.
  • Show the first task's name: off by default, so the lock screen shows only the numbers.

Send a test shows you what a notification looks like on each of your devices. Signing out turns notifications off on that device; signing out everywhere turns them off on all of them. Your phone's own settings (Focus, Do Not Disturb) still decide whether it rings.


What to read next

You now know what the product is for. The remaining chapters are modules — switch on what your work needs and ignore the rest.

Chapter 5 (Email) is the natural next one if you send anything at all, because it is where most of your activity log will come from without you typing it.