Open a record and you will see a timeline. That feed is the full picture, not only the notes someone typed. It can include synced emails from Gmail or Outlook, WhatsApp chats and WhatsApp groups, audit changes when a field moves, files, to-dos, and the notes, calls, and meetings your team logs.

Two surfaces matter, and they are easy to mix up. The timeline is what you read when you ask, “What is the history with this person?” Logging an activity is what you do when something happened offline and Frontline could not see it. Synced mail and WhatsApp are already on the timeline. You do not need to paste them in as a note.

Your chats with Max are not logged on the record. Max can read the timeline and write activities when you ask, but the conversation you have with him stays in that chat. It does not become a line on James’s record.

People and Companies get the richest version of this. When email or WhatsApp is connected, those messages attach to the person. That includes one-to-one WhatsApp chats and WhatsApp groups. If James is in a family group with other Harringtons, that group thread can land on his timeline, and on the other participants who are in the CRM, with the group name on the activity. The company timeline picks up communication from the people linked to it, so Harrington Family Office shows James’s emails and WhatsApp without anyone copying them over. Last interaction stays current on both records.

Meetings can write themselves too. If the notetaker is on and people-sync is enabled, a recorded meeting lands as a meeting activity on each matched person. Check the timeline before you log the same call twice.

Log the moments Frontline cannot see. A phone call from the car. A lunch. A hallway conversation after a review. A short note that is not a meeting, just context the next advisor will need. Pick the type that matches the moment: note, phone call, meeting, or a manually logged email or WhatsApp thread if it never hit a connected channel.

You do not have to type that in the CRM yourself. You can tell Max, in a message or an audio note, and he can log it on the record. After a walk-out from a review, send Max a voice note: “Log a call with James Harrington from this morning. He wants the IPS updated before funding.” Max writes the activity on James, with the right type and the date, the same way you would from the record. A Slack or WhatsApp message to Max works the same way. The point is to get the moment onto the timeline while it is still fresh, not to make logging a second job.

Use a note for commentary, not as a junk drawer for every interaction. If it was a call, log a call. If it was a meeting, log a meeting. The type is what lets the timeline and reporting tell the difference between “we talked” and “someone left a reminder.”

You can backdate an activity when you are catching up. You can tag the people who were on the call. You can also point the activity at a related record, so a call logged on James can reference the $12 million mandate on Deals. The history stays on the person, and the deal still knows the conversation happened.

Workflows can log activities the same way. When a form is submitted, or a deal stage moves, Studio can write a note or a call summary onto the record. That is useful for a consistent paper trail. It is not a substitute for the sync Frontline already does. Do not build a workflow that copies every inbound email into a note. The email is already there.

Not every activity is visible to every person in the workspace. Emails and WhatsApp, including group threads, follow sharing permissions. If you do not have access to a teammate’s mailbox or WhatsApp, you will still see that something happened on the timeline, but the content is hidden.

That rule is the same everywhere you look. In the app, the timeline redacts the body visually. If you ask Max what James said last week, Max only sees what you are allowed to see. If you query the timeline from the CLI, or from an agent you bring yourself, the server applies the same permissions before anything is returned. There is not a side door. A teammate without access does not get the email or the WhatsApp transcript by asking a different client.

Admins and owners can still work across the account. Everyone else sees the history they have been granted, plus the notes, calls, and meetings the team logged in the open. Set sharing when you connect Gmail, Outlook, or WhatsApp, and treat the timeline as a shared record of work, not a copy of every private inbox.

James starts as a Lead. An inbound email about a first conversation attaches to him automatically, and Harrington Family Office shows it too. After a discovery call, an advisor sends Max an audio note and Max logs the phone call on James, with a short summary and the date it happened. The notetaker joins the portfolio review, and a meeting activity appears on James without anyone typing it.

Later a WhatsApp group with James and two family members lights up about a beneficiary change. That group thread is on his timeline, and on the other people in the CRM who were in the group. The team opens a Ticket so operations can finish the work. When the mandate is signed, James converts from Lead to Contact. The emails, the WhatsApp group, the call, and the meeting do not move to a new record. They were always his. Conversion changes the type. It does not reset the story.

That is why you should not build an “Emails” table, a “Calls” object, or a custom “Last emailed” field. Emails are activities. WhatsApp chats and groups are activities. Calls are activities. Last interaction is already maintained. A parallel structure splits the history, and nobody, including Max, will know which side to trust.

A healthy timeline is specific and light. Offline moments are logged with the right type, by you or by Max from a message or a voice note. Synced email and WhatsApp, including groups, are left alone. Notes add judgment, not a second copy of a thread. Related deals and tickets are one click away from the same conversation. People only see the private channels they are allowed to see, whether they are in the app, talking to Max, or using the CLI with their own agent.

To-dos and files live next to this history, and they get their own lesson later in this course. For now, treat activities as the record’s memory. Fields describe the person. Activities explain the relationship.

Next we will look at tables: when a spreadsheet-like list is the right home, and when you should stay on an object.