Skip to content

Logging meetings and activity

A meeting nobody records is a meeting the firm cannot learn from. It does not appear on the relationship, does not update Last Contacted Date, and does not tell the next person that a conversation already happened.

This page covers how to log activity, the purpose-built capture actions ClientVerse adds, and — just as usefully — which objects not to use.

Everything here is Core.

1. The Activity panel

Every ClientVerse record page carries the standard Salesforce Activity panel in the sidebar. It is the primary way to log anything:

Action Creates Use for
Log a Call A completed Task A conversation that has happened — call, meeting, corridor chat
New Event A calendar Event Something scheduled, past or future
New Task An open Task Something to do — a follow-up you owe

Log a Call is the workhorse, and its name is misleading: use it for any completed interaction, not only telephone calls.

2. The ClientVerse capture actions

Beyond the standard actions, the package adds several purpose-built ones:

Action Where What it does
Post Meeting Capture Global A guided capture screen for writing up a meeting
New Engagement Activity Global Creates an Event
Upcoming Meeting Contact Creates an Event for a meeting ahead
New Meeting Recap Reminder Contact Creates a Task to remind you to write the meeting up
Capture Visit Outcome Trip Target Records what happened at a trip meeting

New Meeting Recap Reminder is the one to adopt. The realistic failure mode is not refusing to write up a meeting — it is intending to, then landing, then a week passing. A reminder created at the moment the meeting is booked survives the journey home.

Capture Visit Outcome is the trip equivalent; see Planning a trip.

3. What logging actually updates

Recording activity feeds the relationship picture:

  • Last Contacted Date on the Contact — the fastest read on whether a relationship is live
  • Engagement Score and Engagement Level, and therefore Previous Engagement Level, which is how a cooling relationship becomes visible

See Finding people.

This is the argument for logging even when it feels like paperwork: it is what stops a colleague cold-emailing someone you spoke to last week.

4. Touchpoint Summary — the automatic picture

Touchpoint Summary records are not something you create. They are generated from your firm's relationship-intelligence (ERM) system, summarising contact frequency over a period. Each carries a Contact, a Company, a Connection, a Summary Date, a Summary Period, and a Summary Type.

Read them to see the automatic picture of how often the firm is in touch with someone — the counterpart to manually logged activity, and useful precisely because nobody had to remember to create it.

5. Do not use Touchpoint

The Touchpoint object exists in this release but is not usable, and it is easy to mistake for the meeting-logging object because of its name.

It has five custom fields, all internal plumbing — record-naming helpers and legacy identifiers. There is no date, no type, no contact link, and no notes field. Its record page shows only Name, Owner, Created By, and Last Modified By.

Log meetings as Tasks and Events through the Activity panel, or with the capture actions above. If someone at your firm has started entering Touchpoint records, raise it — the data will not connect to anything.

Touchpoint and Touchpoint Summary are different objects despite the names. Touchpoint Summary is real, populated, and useful. Touchpoint is a shell.

Troubleshooting

"I logged a call but Last Contacted Date hasn't moved." The field is maintained by configured automation. If it never updates, the relevant rollup may not be switched on — an admin question.

"I need to log the same activity against a whole list." Open the List record and use Bulk Activity Logger in the sidebar's CRM Tools panel — see Building a list. Logging a seminar against two hundred contacts one at a time is not work anyone should do.

"Should I log internal discussions about a client?" Firm policy, not a system question. Activity records are visible to anyone with access to the record, so treat them as you would any note that a colleague may read.

"Post Meeting Capture isn't in my action menu." It is a global action; its availability depends on the publisher layout and your permission sets. Ask your admin.

"What about meetings the ERM system already saw?" It captures email and calendar traffic automatically, which is what feeds Connections and Touchpoint Summaries. Logging adds the thing it cannot see: what was said and what happens next.