Article 4: Sales Activity FAQ — Calls, Emails, Notes, Tasks, and Follow-Up Expectations Category
Purpose: This article explains how ChainIT Pay Account Executives should document sales activity in HubSpot. The goal is to create a consistent activity standard across the sales team so that Contacts, Companies, Leads, and Deals show the real history of what happened, what was discussed, and what needs to happen next.
This article covers:
- Calls
- Emails
- Meetings
- Notes
- Tasks
- Follow-up expectations
- Activity logging standards
- What should be documented on each record
Sales activity must be logged because HubSpot is ChainIT Pay’s system of record.
Logged activity helps the team understand:
- Who was contacted
- When they were contacted
- What was discussed
- Whether the prospect engaged
- What objections came up
- What the next step is
- Whether a Lead should become a Deal
- Whether a Deal is moving forward
- Whether a customer or prospect issue needs support
If activity is not logged, leadership and the rest of the team may not know it happened.
2. What counts as sales activity?
Sales activity includes any meaningful action related to prospecting, qualification, follow-up, pipeline movement, customer support, or account management.
Examples include:
- Calls
- Emails
- Meetings
- Notes
- Tasks
- LinkedIn messages
- SMS messages, if used
- Customer issue updates
- Internal handoff notes
- Demo follow-ups
- Pricing conversations
- Referral partner updates
- Objection handling
- Onboarding conversations
3. What activities should be logged in HubSpot?
AEs should log:
- Outbound calls
- Inbound calls
- Voicemails
- One-to-one sales emails
- Email replies
- Meetings
- Demo notes
- Pricing discussions
- Objections
- Follow-up commitments
- Customer or prospect issues
- Internal updates that affect the record
- Next-step tasks
Do not rely on memory, inbox history, or spreadsheets.
4. Where should activity be logged?
Activity should be logged on the record where it belongs.
Contact recordLog person-specific communication.
Examples:
- Email reply from a decision maker
- Call with an office manager
- Meeting with a referral partner
- Notes about that person’s role or preferences
Log account-level information.
Examples:
- Company payment setup
- Current provider
- Business model
- Multi-location details
- Account-level pain points
- Support issues affecting the business
Log active prospecting and qualification activity.
Examples:
- Outreach attempts
- Lead status updates
- Qualification notes
- Disqualification notes
- Follow-up tasks
Log opportunity-specific activity.
Examples:
- Pricing
- Demo
- Proposal
- Contracting
- Onboarding
- Decision timeline
- Close plan
- Competitive information
5. What is the difference between a note and an activity?
An activity is a logged action, such as a call, email, meeting, task, or message.
A note is a written summary that explains context.
A good activity log shows that something happened.
A good note explains why it matters.
Example activity:
“Call logged with Jane Smith.”
Better note:
“Spoke with Jane Smith, office manager. Current provider is Stripe. Main issue is reporting and reconciliation. She asked for pricing and said the owner must review. Follow-up task created for Monday.”
6. What should a good sales note include?
A good sales note should include:
- Who you spoke with
- Date of interaction
- What was discussed
- Current provider, if mentioned
- Pain points
- Objections
- Decision makers
- Timing
- Next step
- Any internal follow-up needed
Good notes should be clear enough that another team member could understand the account without asking you to explain everything again.
7. What is a poor sales note?
Poor notes are vague and not useful.
Examples:
- “Called.”
- “Sent email.”
- “Talked to prospect.”
- “Follow up.”
- “Interested.”
- “Not ready.”
- “Good call.”
These notes do not explain what happened or what should happen next.
8. What is a good sales note example?
Example:
“Spoke with Dr. Smith on June 5. He currently uses Square for in-person payments and invoices patients manually for some services. Main concern is reducing manual follow-up and improving reporting. He asked for more information on online payments and recurring billing. He is open to a follow-up call next week. Task created for Monday.”
This note is useful because it includes:
- Contact
- Current provider
- Pain point
- Product interest
- Timing
- Next step
9. When should I log a call?
Log a call when:
- You speak with a prospect
- You leave a voicemail
- You attempt a call
- You receive an inbound call
- You discuss pricing, product, timing, or objections
- You speak with a referral partner
- You discuss an active Lead or Deal
Call activity helps show outreach volume and engagement.
10. What should I include in a call log?
Include:
- Whether the call connected
- Who you spoke with
- Summary of the conversation
- Objections or questions
- Pain points
- Next step
- Follow-up task
- Whether a Deal should be created or updated
Example:
“Connected with office manager. She confirmed they use Stripe and Chase terminal. Owner handles payment decisions. She asked me to send an overview and follow up next Tuesday.”
11. When should I log an email?
Log sales-related emails when they involve:
- Outreach
- Follow-up
- Pricing
- Demo scheduling
- Product questions
- Objections
- Referral introductions
- Decision-maker conversations
- Onboarding
- Customer or prospect support issues
If the email matters to the sales process, it should be visible in HubSpot.
12. Should every email be logged?
No.
Do not log unrelated emails, personal emails, or internal conversations that do not belong on a CRM record.
Log emails that help tell the sales, support, onboarding, or account history.
13. How should AEs use the HubSpot email plugin?
AEs should use the HubSpot email plugin for Outlook or Gmail to help log and track sales communication.
Before sending important sales emails, confirm:
- You are logged into the HubSpot plugin.
- The email is associated with the correct Contact.
- The email should be logged.
- Tracking is enabled or disabled according to company practice.
- The email content is appropriate for CRM history.
14. When should I create a task?
Create a task whenever there is a future action.
Examples:
- Call tomorrow
- Follow up next week
- Send pricing
- Confirm demo
- Check on proposal
- Follow up after meeting
- Ask Sales Ops for review
- Send onboarding information
- Confirm decision maker
- Follow up after support issue
A task should prevent important follow-up from being missed.
15. What should every task include?
A good task should include:
- Clear action
- Due date
- Associated Contact, Company, Lead, or Deal
- Priority, if applicable
- Short context
Poor task:
“Follow up.”
Better task:
“Follow up with Jane Smith on pricing questions and confirm whether owner can join next call.”
16. When should I create a meeting record?
Create or log a meeting when:
- A demo is scheduled
- A discovery call is scheduled
- A pricing review is scheduled
- A partner conversation is scheduled
- A follow-up meeting is confirmed
- An internal handoff meeting affects the prospect or customer
Meetings should be associated with the relevant Contact, Company, Lead, or Deal.
17. What should I document after a meeting?
After a meeting, document:
- Who attended
- What was discussed
- Pain points
- Objections
- Product interest
- Current provider
- Decision process
- Timeline
- Next step
- Deal status
- Follow-up task
A meeting without notes creates lost context.
18. What should be documented after a prospect asks for pricing?
Document:
- What they asked for
- Current provider
- Monthly volume, if known
- Average ticket, if known
- Payment methods used
- Pain points
- Decision maker
- Timing
- Whether leadership review is needed
- Next step
Pricing requests are strong sales signals and should not be left undocumented.
19. What should be documented after an objection?
Document:
- The objection
- Who raised it
- Why it matters
- How the AE responded
- Whether follow-up is needed
- Whether leadership or Sales Ops should assist
Common objections:
- “We already use Stripe.”
- “We are happy with our processor.”
- “Your rates are too high.”
- “We are not ready.”
- “Send me information.”
- “We do not want to switch right now.”
Objections are valuable sales intelligence.
20. What should be documented after a referral introduction?
Document:
- Who made the referral
- Who was introduced
- Relationship context
- Prospect need
- Any promised next step
- Whether the referral partner expects updates
- Associated Contact and Company
Referral opportunities should be handled carefully because they affect partner trust.
21. What should be documented when a customer or prospect has an issue?
Document:
- What issue was reported
- Who reported it
- When it happened
- What system or process is affected
- Business impact
- Whether support was contacted
- Ticket reference, if available
- Next step
Sales should also submit support issues through the approved support process when appropriate.
22. What should I do after every meaningful sales interaction?
After every meaningful interaction:
- Log the activity.
- Add a clear note.
- Update Lead status or Deal stage if needed.
- Create the next task.
- Associate the activity with the correct record.
- Escalate internally if needed.
This should happen the same day whenever possible.
23. What is the minimum activity standard for active Leads?
Every active Lead should have:
- Recent activity
- Updated Lead status
- Clear qualification note
- Next-step task
- Correct owner
- Correct Contact or Company association
An active Lead with no recent activity is not being actively worked.
24. What is the minimum activity standard for active Deals?
Every active Deal should have:
- Deal owner
- Deal stage
- Close date
- Associated Contact
- Associated Company
- Recent activity
- Next step
- Clear notes
- Realistic forecast status
A Deal with no next step is not being managed properly.
25. How often should AEs update HubSpot?
HubSpot should be updated as work happens.
Do not wait until the end of the week.
Recommended rhythm:
- Log calls immediately after the call.
- Log notes immediately after the meeting.
- Create follow-up tasks before moving to the next record.
- Update Lead status the same day.
- Update Deal stage as soon as the opportunity changes.
26. What are common activity logging mistakes?
Common mistakes include:
- Not logging calls
- Not logging replies
- Writing vague notes
- Forgetting next-step tasks
- Logging activity on the wrong record
- Creating tasks without due dates
- Leaving Deals without next steps
- Forgetting to update Lead status
- Working outside HubSpot
- Keeping important context only in email inboxes
27. What should AEs review every morning?
Every morning, review:
- Tasks due today
- Overdue tasks
- New Leads
- Recently engaged Contacts
- Open Deals
- Follow-Up Needed view
- Meetings scheduled today
This helps the AE prioritize work before starting outreach.
28. What should AEs review at the end of the day?
At the end of the day, review:
- Did I log all calls?
- Did I log all important emails?
- Did I update Lead statuses?
- Did I update Deal stages?
- Did I create follow-up tasks?
- Did I document objections?
- Did I escalate support issues?
- Did I leave any active record without a next step?
29. What should I do if I forgot to log activity?
Log it as soon as possible.
In the note, be clear about when the activity actually happened.
Example:
“Follow-up note entered on June 6 for call that occurred on June 5. Prospect asked for pricing and requested a follow-up next week.”
Do not leave important activity undocumented because it was not entered immediately.
30. Final Standard
HubSpot should tell the story of the sales relationship.
For every active Contact, Company, Lead, and Deal, another team member should be able to understand:
- Who we are working
- What happened
- What the prospect needs
- What objections exist
- What the next step is
- Whether the opportunity is real
The ChainIT Pay activity standard is simple:
If it happened, log it.
If it matters, note it.
If there is a next step, task it.
If it is an opportunity, manage it in the Deal.
Clean activity creates clean pipeline.