Log an interaction

  1. Open Communications → Log.
  2. Select Log communication.
  3. Choose the type: call, email, meeting, SMS, or another available channel.
  4. Connect at least one contact or deal so the activity has useful context.
  5. Set the direction and when the interaction occurred.
  6. Add the channel-specific details and a concise summary.
  7. For calls, record the outcome and optional duration and phone number.
  8. Create a follow-up task in the same dialog when the interaction produced a next action.
  9. Save and confirm the row appears in the hub and related record timeline.

Who can do this

  • Required access: an access level that includes Contacts - Standard Access or Contacts - Full Access.
  • Default access levels that include it: Team Member, Accountant, and System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Call outcomes

OutcomeUse it when
ConnectedYou reached the intended person and had a conversation.
No answer / BusyThe attempt did not connect.
VoicemailYou left a voicemail.
Wrong numberThe saved number does not reach the intended contact.
Callback requestedThe contact asked for another call at a later time.
Meeting bookedThe call produced a scheduled next meeting.

Use the weekly metrics

The Log shows calls this week, connect rate, meetings booked, and talk time. Use filters to compare the work behind those totals, not only the totals themselves. A high call count with a weak connect rate may point to data quality or timing; a healthy connect rate with few meetings may point to qualification or messaging.

Correct the record

Edit a call when its direction, outcome, duration, notes, phone number, or occurrence time was entered incorrectly. Delete a communication only when it should not exist; deletion removes it from the shared history and cannot be undone.

Follow-up habit: If the summary contains a future-tense action, create the task before saving. This keeps promises out of prose and inside the work queue where they can be assigned and completed.