Activities, notes and calls
What this page is — the four engagement tabs on a lead record: Activity Log, Comments, Emails and Calls.
What it is for — recording and reading what has actually happened with a lead — the calls made, the meetings held, the notes colleagues left.
The problem it solves — the history is what makes a lead workable by somebody other than whoever created it. It also explains why the timeline fills up with entries nobody wrote: editing a lead logs its own activity, so the feed mixes human work with an audit trail.
On: the lead record · Permission to read: View Marketing Suites lead management Permission to add: Edit Existing Leads
1. What each tab is
| Tab | Holds | Table |
|---|---|---|
| Activity Log | Logged calls, emails, meetings, notes — and system-recorded edits | lead_activities |
| Comments | Free-text notes, pinnable and markable private | lead_notes |
| Emails | Email correspondence recorded against the lead | lead_activities, filtered |
| Calls | Voice-agent call logs from Orbit Vox | lead_voice_logs |
2. Activities
An activity carries a type, a subject, a description, a direction (inbound / outbound), an outcome
and a duration in seconds.
Editing a lead writes its own Lead Updated activity describing the change — "Grade changed from D to
A", "Budget Range updated to $50K - $100K". So a record that has been edited several times has a
timeline mixing what a person did with what the application recorded.
This is useful and occasionally confusing: a busy timeline is not necessarily a busy relationship.
3. Comments and notes
| Control | Effect |
|---|---|
| Rich-text editor | Bold, italic, lists, links, images |
| Internal Note | Marks the note private (is_private) |
| Pin | Sorts the note above the rest (is_pinned) |
@someone | Mentions a user in the note text |
4. Calls — the Orbit Vox boundary
The Calls tab reads lead_voice_logs, written by Orbit Vox when a voice agent calls the lead.
| Owned by Pulse | Owned by Vox |
|---|---|
| Showing the call log on the lead | Placing the call |
| Add to VOX Backlog as a conversion target | The dialler, the agent script, the recording |
Configuring the handoff is convert to VOX backlog.
5. The admin contract
| Needs | Or |
|---|---|
| Edit Existing Leads | Activities and notes are read-only |
| Orbit Vox configured | The Calls tab stays empty |
| Users to mention | @ finds nobody |
6. Don't confuse this with…
| This | Not this |
|---|---|
| Comments | Activity Log — comments are notes, activities are events |
An activity_type of note | A row in lead_notes — different tables, both called notes |
| The Calls tab | Webhook logs, which record inbound submissions |
7. Troubleshooting
| Symptom | Cause |
|---|---|
Timeline full of Lead Updated | Field edits write activity rows. Section 2 |
| Calls tab empty | No Vox voice logs for this lead |
| A note will not save | Missing Edit Existing Leads |
| A pinned note is not at the top | Pinning affects sort within the list, not across tabs |