
Pipeline Design
Part of CRM activity management
Avoiding activity logs that obscure the customer history
A busy CRM timeline can hide the very event someone needs: a changed requirement, a missed commitment or an unresolved objection. The cure is a clearer recording …
Start with the customer story, not the activity count
A customer record fills up on its own. HubSpot logs some activities automatically; staff add calls, emails, meetings, notes and messages by hand. The few entries explaining why a customer bought, paused or left end up buried.
Logged activities should display a complete outreach and engagement relationship with a record. When they don't, the cost lands in the next conversation: a colleague rings the customer and asks for details the customer already supplied.
A readable timeline carries context and points to the next action. Control what gets recorded, what stays in tasks, and how the history is filtered and reviewed.
Decide what belongs on a customer record
In HubSpot, the activities you can create or log on a record are calls, emails, meetings, notes, tasks, messages sent through LinkedIn, WhatsApp or SMS, and postal mail. Anything that happened with the customer can belong there; anything else is internal housekeeping.
Tasks can be saved without any associated record. Unassociated tasks don't appear on record timelines, although the assigned user still receives notifications and sees them in their task list. Associating a task is what puts it into the customer history.
A simple test: did the customer see, say or receive it? Log it on the record. Is it something you or a colleague still has to do? Keep it as a task.
What to log on a customer record: a quick guide
- Did the customer see, say or receive it?Yes → Log on the record
- Is it something you or a colleague still has to do?Yes → Keep as a task
- Is it internal housekeeping (e.g. team meeting notes)?Yes → Do not log on the record
Log each interaction once, with enough context to stand alone
Automatic logging covers activity that happens inside the system. Manual logging exists for everything outside it — a meeting with a client that wasn't booked, or a message sent through LinkedIn.
Record these from the record itself, using the log icons for a sent email, a made call, an attended meeting, a LinkedIn, WhatsApp or SMS message, or postal mail. Logging a call the system already captured automatically adds noise rather than history.
An entry with no detail can't stand alone. The companion article on recording useful conversation context covers what to write — the substance of the conversation.
Where interactions arrive in a batch, activities can also be imported and associated with records in bulk.
Customer interaction timeline: best practices for clarity
- Log each interaction onceUse the record’s log icons for calls, emails, meetings, messages (LinkedIn, WhatsApp, SMS), postal mail
- Avoid double loggingDo not manually log activities already captured automatically by HubSpot
- Add context that stands aloneInclude key points from conversations — avoid vague entries like 'discussed pricing'
Keep follow-ups in tasks, not in the history
Follow-ups belong in tasks, not in the history. Separating completed activity from scheduled follow-up, and tracking a next step with an owner and a date, are covered in their own companion articles.
Logging vs. tasks: when to use each
- Pros of keeping follow-ups in tasksClear ownership, due dates, and visibility of next steps; prevents cluttering customer history with pending actions
- Cons of logging follow-ups in historyCreates confusion between completed actions and pending work; obscures the customer's true journey
Filter the timeline before adding more entries
Activity index pages let you review activities in bulk rather than record by record. Click a view tab, apply a property quick filter, or use advanced filters to narrow calls, communications, emails, meetings, notes, postal mail and tasks by specific criteria. On a record, the same activities sit on the default Activities tab and in activity cards.
From an index page, tick the checkboxes beside activities to edit property values in bulk or delete entries outright. That is the practical way to clear duplicated or meaningless logs instead of annotating around them.
Accounts with free tools created on or after 4 February 2025 show only activities created in the last 30 days on timelines and activity cards. Most activities are covered, but not notes, tasks, a record's pinned activity or activities reached by direct link.
Activity index pages are the workaround for older entries. With a Starter, Professional or Enterprise subscription, activities created more than 30 days ago appear on both the timeline and activity cards.
Viewing communications such as LinkedIn, SMS and WhatsApp messages requires Super Admin permissions.
CRM activity visibility by subscription level (Australia)
- Free plans (created after 4 Feb 2025)
- Only show last 30 days of activities on timelines and cards
- Starter, Professional, Enterprise plans
- Show all activities, including those older than 30 days
- Viewing SMS, WhatsApp, LinkedIn messages
- Requires Super Admin permissions
How to clean up old or redundant CRM activity logs
- Go to Activity Index pageAccess bulk view of all activities across records
- Apply filtersFilter by type (calls, emails, notes), date range, or property values
- Select and actTick checkboxes to edit or delete duplicate or meaningless entries in bulk
Use consistent logging defaults and naming
Task defaults remove routine decisions. In Profile & Preferences, the Tasks tab sets a default due date as a number of days or weeks after creation, a default due time, and a default reminder lead time.
For example, every task could be due one week after creation at 11.00 am. Defaults populate new tasks created on the tasks index page or on a record, and can still be adjusted for individual tasks.
Apply the same consistency to titles and types: including call or email in a title sets the type automatically, and steady wording makes entries findable when you filter index views later.
Minimise and protect what you log
Under Australian Privacy Principle 3, an organisation may only collect personal information where it is reasonably necessary for its functions or activities. The OAIC's guidance treats this as a data minimisation approach: record what the customer relationship actually requires, not everything the system allows you to capture.
Personal information must be collected by lawful and fair means, and from the individual concerned unless that is unreasonable or impracticable. Sensitive information carries a higher bar — the individual's consent is required unless an exception applies.
Data minimisation under Australian Privacy Principle 3
- Permitted collectionPersonal information only where reasonably necessary for functions or activities
- Prohibited collectionRecording everything the system allows — even if irrelevant to the customer relationship
- Sensitive informationRequires individual consent unless an exception applies
Capture quality lead and customer information at the source
At trade shows and events, electronic capture often falls short: Wi-Fi in exhibit halls varies in quality, and equipment rental may be too costly or left out of the budget. A manual lead sheet remains a reasonable fallback.
Relying on a business card as the only source of follow-up is a common failure. The card carries a name and number, so the follow-up call becomes the discovery conversation all over again — and the prospect notices, asking whether you didn't cover this at the show.
Write down what you gleaned at that first meeting while it is fresh, and capture it against the customer record with the context attached.
Further reading: Filter activity index pages and record timelines (knowledge.hubspot.com).


