Docs

Interactions

Interactions represent touchpoints with a relationship.

Interactions represent touchpoints with a relationship. They are the primary way SecondTouch learns, builds context, and generates meaningful follow-up and prioritization.

Every insight, signal, and recommendation in your daily brief is driven by the interactions you log.

Overview

An interaction is any meaningful engagement with a person or account, including:

  • Meetings
  • Calls
  • Emails
  • Messages
  • Informal check-ins

You do not need to capture everything. The goal is to log enough signal for the system to understand:

  • What is happening
  • When it happened
  • What matters next

Interactions should be fast to log and lightweight.

Capabilities

  • Create an interaction
  • Edit an interaction
  • Delete an interaction
  • View interaction history across accounts

Logging Methods

SecondTouch supports multiple ways to log interactions. Use whichever method fits your workflow in the moment.

Manual Entry

Use manual entry when you want full control over the interaction.

Best for:

  • After meetings or calls
  • When capturing structured notes
  • When adding context intentionally

How to use:

  1. Open the relevant account
  2. Click “Log Interaction”
  3. Enter a short summary (1-2 sentences)
  4. Save

Example:

  • “Discovery call, exploring integration options next quarter”
  • “Reviewed proposal, follow-up scheduled for Friday”

Quick Interaction

Quick interactions are designed for speed.

Best for:

  • Logging activity immediately after it happens
  • Capturing lightweight updates
  • High-frequency workflows

How to use:

  1. Use the quick interaction input (where available)
  2. Type a short note
  3. Submit instantly

No formatting or structure required.

Example:

  • “Quick check-in, no updates”
  • “Sent follow-up email”

Log Meeting

Use this when recording a completed meeting.

Best for:

  • Scheduled calls
  • Sales or client meetings
  • Internal syncs

How to use:

  1. Open the account or meeting context
  2. Select “Log Meeting”
  3. Add a short summary of the discussion
  4. Capture key outcomes or next steps

Focus on:

  • What was discussed
  • Any decisions made
  • What should happen next

Example:

  • “Demo completed, strong interest, pricing discussion next step”

Email CTA (Manual Email Logging)

Use the email CTA when you want to explicitly log an email interaction.

Best for:

  • Important outbound emails
  • Follow-ups that should be tracked
  • High-signal communication

How to use:

  1. Send your email
  2. Use the logging CTA (e.g., BCC or trigger)
  3. The system creates an interaction tied to the account

This ensures important communication is captured without additional manual entry.

Example:

  • “Sent pricing follow-up and included implementation timeline options”

Email Ingestion (Automatic Logging)

Email ingestion automatically converts emails into interactions.

Best for:

  • Passive capture of communication
  • Reducing manual logging effort
  • Ensuring no important interaction is missed

How it works:

  • Emails sent to the ingestion address are processed
  • Interactions are created automatically
  • Records are associated with the correct account when possible

What to expect:

  • Automatic interaction creation
  • Basic summaries generated from email content
  • Continuous background capture of activity

Example:

  • “Ingested email: confirmed renewal review on Tuesday and requested stakeholder list”

Interaction Data

Each interaction includes:

  • Summary / Notes - a short description of what happened
  • Timestamp - when the interaction occurred
  • Account association - the relationship this interaction belongs to

The system uses this data to:

  • Identify patterns
  • Surface follow-ups
  • Generate signals in your daily brief

How to Write Good Interactions

Keep interactions:

  • Short (1-2 sentences)
  • Focused on outcomes
  • Action-oriented when possible

Good:

  • “Client asked for revised pricing, follow-up next week”
  • “Intro call complete, interested but timing unclear”

Avoid:

  • Long transcripts
  • Overly detailed notes
  • Irrelevant information

Clarity is more valuable than completeness.

Usage Guidelines

  • Log interactions as close to real-time as possible
  • Prioritize consistency over detail
  • Capture meaningful changes, not every minor touchpoint
  • Use quick logging for speed, manual entry for clarity when needed

How Interactions Drive the System

Interactions are the core input to SecondTouch.

As you log more interactions, the system will:

  • Detect momentum and risk in relationships
  • Surface timely follow-ups
  • Improve prioritization in your daily brief
  • Provide more contextual and actionable insights

The quality and consistency of your interactions directly determine the quality of the system’s output.