Activity Logging

What problem does it solve? Recording business development activity in a CRM is easy to forget and easy to get wrong — notes land on the wrong entity, calls lack outcome tracking, and IDs must be resolved from names. This Skill standardizes how calls, meetings, and notes are written into Buildr so every touchpoint is linked to the correct contact, deal, or company. ## Core Features & Use Cases - Typed activity helpers: Uses activities.log_call, activities.log_meeting, and activities.add_note with the correct field shapes instead of generic record creation. - Entity resolution and confirmation: Resolves people, companies, and deals by name before writing, disambiguates multiple matches, and confirms the target with the user. - Full-record path: Falls back to the generic dispatcher (calls.create, meetings.create) when outcome tracking, duration metadata, or complete meeting details are required. - Use Case: After a 30-minute call with a buyer, tell the assistant to log it — it resolves the contact, confirms the details, writes the call with duration in minutes, and returns the activity ID. ## Quick Start Ask the assistant to log the call you just had with a named contact in Buildr, including the notes and duration.