CRM MVP
Any kind of activity can be scheduled from inside the CRM, and the types are defined by the buyer rather than fixed by the vendor.
Selling is not only meetings and calls. Preparing a quote, chasing a reference, and sending a contract are all work that has to be scheduled and owned, and none of them fits a vendor's default list.
When the type set is fixed, that work either goes untracked or gets mislabelled, and the activity report stops describing what the team actually does.
Activities of any kind must be schedulable without leaving the CRM, and the platform must record what kind of work each one is. Scored on four rungs, top first.
Yes where the platform ships a type field on the schedulable activity and the buyer can define their own types.
Partial where the type set is fixed and cannot be extended, but still covers meeting, call and task.
Partial where there is no type field, but the buyer can impose a naming convention in the activity title and report on it.
Fails if activities cannot be scheduled at all, or a naming convention could not be reported on.
That last condition is what keeps the third rung honest. A prefix in a title is only a taxonomy if the platform lets you filter, group or count activities by that text. Where the activity cannot be filtered by its title, and where the activity does not appear in the platform's reporting at all, the convention is decoration and the capability fails. This is checked directly rather than assumed.
This is not the same test as Core objects. That one asks whether an activity record exists and can be linked to the others. This one asks whether it can be scheduled forward and whether the system knows what kind of work it is. Three platforms pass the first and fail this one, and two do the reverse. Call logging is covered there and is not assessed again here.
Activities are created and scheduled inside Act!, including recurring activities, and are scheduled against known contacts with multiple attendees invited. The supplied types are Call, Meeting and To-Do, and Act! documents creating custom activity types so that activities can be added to types other than those three, which makes the type set user-definable and covers internal operational work.
https://www.act.com/training-videos/act-premium-cloud/creating-custom-activity-types/
https://www.act.com/training-videos/act-premium-cloud/creating-a-new-activity/
https://www.act.com/training-videos/act-premium-cloud/scheduling-recurring-activities/
https://www.act.com/products/connections/outlook-integration/
Tasks are created from a deal or a contact record with a due date and due time, and assigned to any user with permission to view the pipeline. Task types are user-definable: the API documents that task types are configurable and vary by account, with endpoints to create, update, delete and list them, and the help centre states that administrators add task types and task outcomes in task settings. Documented examples of task types include a call, an email, a meeting and lunch, so operational internal work can be modelled as its own type.
Activities are created from inside any record and from the home page. Events take a title, location, start and end date and time, all day and billable flags, attendees drawn from employees and contacts, notes and an association to a customer, contact, lead or other object, and appear in the calendar and in My Agenda. Tasks take start, end and due dates, an estimated duration, a priority, a category, a status and an assignee, and link to any object, which covers internal work such as preparing a quote. Follow ups take a date, a reminder time and a description against a chosen record, and call logs are recorded against records. The constraint is that these are a fixed set of activity kinds - event, task, follow up, call log, note - and no vendor document describes defining a new activity type, though the type set does cover meeting, call and task.
https://answers.apptivo.com/questions/10313/how-do-i-create-new-event
https://answers.apptivo.com/questions/10854/how-do-i-create-and-associate-tasks-from-home-page
https://answers.apptivo.com/questions/12234/how-do-i-create-a-follow-up-in-my-agenda
https://www.apptivo.com/user-manual/user-interface-navigation-global-features/
Activities can be scheduled without leaving Attio. Tasks are created from a record page, the Tasks page or the Home page, take a due date set in natural language, take assignees, and link to records by an at mention. Meetings are logged as activities from a record's Activity tab. The dimension fails on type. The task model exposes only content, format, deadline, completion, assignees and linked records, with no type or category field, and no vendor page describes defining activity types. Nor can a buyer substitute a naming convention in the task title and report on it. Task content is not a filterable field: the documented task filters are assignee, linked record, due date, completion, creator and created date, the automation block that finds tasks offers the same set, and the REST list-tasks endpoint accepts no text or search parameter. Attio's contains text operator exists only in object and list views, which tasks do not appear in. Tasks are also not a reporting source - a report's data source is an object or a list, and tasks are neither. A prefix convention in Attio is therefore decoration that the product cannot count, chart or segment by.
https://attio.com/help/reference/productivity-collaborating/tasks
https://docs.attio.com/rest-api/endpoint-reference/tasks/list-tasks
https://attio.com/help/reference/automations/workflows/workflows-block-library
https://attio.com/help/reference/managing-your-data/dashboard-and-reports/reports
https://attio.com/help/reference/managing-your-data/views/filter-and-sort-views
Activities are scheduled inside Bigin and the set covers the three required shapes: tasks carry a name, owner, due date, priority, status, repeat and reminder; events carry a title, location, from and to times, participants and reminder; calls carry a start time, call type, purpose, duration and outcome. All three can be related to contacts, companies and pipeline records, and the Activities module offers a calendar view. The constraint is that the type set itself is fixed at task, event and call, presented as three sub-tabs, and no vendor article describes creating a new activity type. A task's name is free text so internal work such as preparing a quote can be scheduled, and custom fields including picklists can be added to the Tasks, Events and Calls modules, but a user-defined type is a field the buyer adds rather than a native construct.
Tasks can be created from anywhere in the CRM and from the browser extension, set against a lead, given a due date, made recurring and assigned to one or more team members, with email and in-app reminders, and they are viewed in a Tasks section grouped into late, dated and undated. The dimension fails on type. The vendor's own API schema for the scheduled-activity object carries no field recording what kind of work a task is: the create request body is the lead identifier, a resource link, a name, a date, a recurrence and users, with no type, category or kind field and no fixed list of values on any field. So a call, a meeting and an hour spent preparing a quote are the same record with different words in the title, and nothing in the product reads those words. The separate activity concept does not fill the gap - it is a passive log of things that have already happened, such as emails sent, replies received, interactions and completed tasks, rather than something that can be put in the diary - and the webhook event catalogue exposes only lead, list, status and tag events, with no call or meeting event.
https://developer.breakcold.com/v3/api-reference/reminders/create-a-reminder
https://developer.breakcold.com/help/tasks-activities/how-to-create-tasks-reminders
https://developer.breakcold.com/help/tasks-activities/how-is-activity-tracked-in-breakcold
https://developer.breakcold.com/help/tasks-activities/what-counts-as-an-activity
Tasks are created inside Capsule with a due date and an optional due time, an owner, and links to a contact, an opportunity or a project, and are viewed in a task list or a calendar view. Tasks are classified by category: Call, Email and Follow up are supplied by default and users can create their own categories to fit their processes, so internal operational work such as preparing a quote can be modelled. A separate Activity Type list classifies logged history entries and can also be extended with custom types.
Tasks are scheduled from inside the CRM on any lead, with a free-text description, a date and time, an optional contact and an assignee, which covers internal operational work such as preparing a quote. Call Tasks schedule a call to a named contact at a date and time and require a completed call activity to be marked done. Beyond those, the schedulable task types are system-defined - the API enumerates a fixed list including email follow-up, missed call, voicemail and opportunity due - and no user-defined task type is documented. Custom Activities do let an organisation define its own activity types with their own fields, but they are recorded against a date the activity occurred rather than scheduled forward, and meetings arrive by calendar sync rather than being created in Close. So activities can be scheduled and the type set covers task, call and meeting, but the schedulable type set itself is not user-definable.
Tasks are created inside Copper with a due date, reminder, assignee, priority, status, a related record and an Activity Type, and can be single or recurring with subtasks. Activity types ship with Phone Call, Meeting and To-do, and administrators can create custom types, up to thirty enabled at a time, optionally counting as interactions for reporting. Calendar events for meetings can also be created directly from a record.
Activities can be scheduled without leaving folk in two ways. A task is created against a person, a company or a deal with a title, rich-text description, due date with optional time, one or more assignees and a public or private visibility setting, which covers internal operational work such as preparing a quote. An interaction can be logged against a person or a company with any date including a future one, which is how a meeting or call is put in the diary. Types are not user-definable. Tasks have no type field at all, and the interaction activity type is a fixed vendor-defined list covering call, meeting, message, coffee, lunch, event and drink plus a set of messaging-app values; the only user-supplied option is an arbitrary emoji rather than a named, reportable type of the buyer's own making. The fixed set does cover meeting and call, and tasks cover the task case, so the dimension is met but constrained.
Tasks and Appointments (Meetings) ship as default activity types, and an admin can add further activity types of their own under Admin Settings, up to a documented ceiling of 50 custom activities per account, each with its own icon and its own set of outcome choices. Activities carry a start and end date, a related contact, a sales owner and collaborators, so operational work such as preparing a quote can be modelled and scheduled without leaving the CRM.
Calls, meetings, tasks, notes and emails can all be created or scheduled from inside a record, with due dates, reminders and assignment. Call and meeting types are user-definable by a super admin, up to 100 per account, and are reportable. Task types, however, are a fixed set of Call, Email and To-do; a long standing HubSpot Ideas request to make task types customisable remains undelivered. Internal operational work therefore has to be modelled as a To-do task with a descriptive title rather than as its own activity type.
Tasks are created inside the CRM from the quick-add menu or from a record, with due date, start date, assignee, reminder, recurrence and links to opportunities, contacts, organisations and pipeline stages. Task type is expressed through Categories, whose values and colours administrators create and edit under System Settings, so the type set is not fixed. Meetings are handled by the Event object. Activity Sets can generate tasks and events automatically at a pipeline stage.
Appointments are booked directly inside Keap by selecting a contact, an appointment type and a time, without using a booking link. Appointment types are buyer-defined: two types are supplied by default and can be edited or deleted, and further types are added by the user, so a meeting type and a call type can both be created. Tasks are a separate documented record with a name, a due date and a reminder, which covers internal operational work.
Activities are created from inside a record - Related, then Activities, then New Activity - and shipped types cover appointment, recurring appointment, phone call, task, email, letter and fax, each with subject, start and stop times, due date and duration. Types are user-definable: a maker can create a new table with the Activity type and tick Display in Activity menus, which puts the custom type in the activity menus alongside the shipped ones, so internal operational work such as preparing a quote can be modelled as its own type.
Emails & Activities creates activities from inside the CRM with an adjustable date and time and free notes, and the first activity created spawns an Activities board carrying columns for description, owner, start and end date, an Open or Done status and activity type. Beyond the supplied meeting, call summary and note types, users create custom activities by naming them and choosing an icon and colour, and those types are saved for reuse - so the type set is user-definable rather than fixed.
Scheduled and completed activities are created inside Nimble and cover tasks with due dates, calendar events and calls. The type set is not fixed: an administrator creates custom activity types under Settings, choosing the form and whether completing that type updates the contact's last-contacted date, with webinars, appointments and campaigns given as examples. New activities of a custom type are raised from a contact, a company, a deal or the Activities tab, and the activity list filters and edits inline on Related Contact and Related Deal.
Activities are scheduled from the add-new menu or from a lead, person or company page, with an activity type chosen from a drop-down, participants, related leads, location and agenda notes. Activity types are user-definable: administrators add their own types under organisation settings, alongside the supplied defaults, to cover things such as product demos or cold calls. Internal work that is not a customer interaction is handled by Tasks, which can be recurring.
A Schedule an activity window inside the CRM sets the activity, its owner and its link to a deal, organisation or person. Default types cover call, meeting, task, deadline, email and lunch, and a global administrator can add custom activity types with their own name and icon, so internal operational work such as preparing a quote can be modelled.
Tasks are created inside the CRM from the global create menu, a record's activity feed or the task list, carrying a name, assignee, date, type, description and parent record, and multiple tasks can be set against one record with email notification to the assignee. Both Activity Types and Task Types are administrator-defined lists that can be added to and edited, with the vendor's own examples covering calls, customer meetings and general contact, so internal operational work can be modelled as its own type.
Tasks and events are created and scheduled from the activity composer on the record itself, covering to-do work, logged calls and meetings, and events appear on the Salesforce calendar. The Type picklists on both Task and Event are standard editable picklists: Salesforce documents administrators adding their own values via Object Manager, and the predefined Subject picklist for tasks and events is likewise defined by the admin. So internal operational work such as preparing a quote can be given its own activity type.
Tasks are created from inside a box, from the Gmail sidebar or from the global upcoming list, and carry a free-text title, a due date set by picker or natural language, and an assignee, so future work of any description can be scheduled without leaving the CRM. The dimension fails on type. A task has no type attribute, and the only other activity records are call logs and meeting notes, two fixed record types that document a conversation after the fact and cannot be scheduled forward. A naming convention in the task title cannot substitute, because nothing in the product reads that text: the only documented narrowing control on the task list is a pipeline picker, the command palette searches boxes, pipelines, saved views, contacts and organisations rather than tasks, and the API's read-tasks endpoint takes no text parameter. Task data does reach reporting, but only in aggregate and never as text - the task magic columns are counts, percentages, dates and assignee sets, with no column carrying the task title, and the pipeline reports run on boxes and their columns.
Events are scheduled from the calendar, from the create menu or from inside a record such as a deal, with invitees, reminders and recurrence, and the calendar covers both Events and Tasks so internal work that is not a customer meeting has a home. Activity types are user-definable: six ship by default, being Call, Meeting, Mobile Call, Onsite Meeting, Onsite Service and Group Event, and administrators add their own values to the Events Activity Type picklist under configuration settings, giving each a colour and controlling who may assign it, so a team can track something like a demo separately.
Tasks, Meetings and Calls are scheduled from inside the CRM, each with an owner, timing, reminders by email or popup, recurrence, and links to the contact, lead or account they belong to, and they surface as related lists on the parent record. The set of activity types is the three built-in modules; vendor documentation describes no way to define an additional activity type, so internal operational work has to be modelled as a task rather than as its own type.