Capsule CRM - is it a CRM? | HowToUseACRM.com

Every verdict, with its evidence

Core objects

Not at all

Capsule holds Opportunity, Party and Task as separate objects, but the person and the organization are not separate objects: both are a Party, and a Party is typed either person or organization. One endpoint family serves both, a person carries an organization field linking it to another Party, and the reverse relationship is read through that Party's employees endpoint. Opportunity and Task associations are otherwise complete - an Opportunity carries a main contact plus additional parties, and a Task carries party, opportunity and project associations - and an opportunity can be linked to a person alone, so organization association is possible rather than compulsory. The dimension nevertheless fails on the data model: the interface behavior of separate views and separate add actions does not make two types of one object into two objects.

Source: https://developer.capsulecrm.com/v2/operations/Party, https://developer.capsulecrm.com/v2/operations/Opportunity, https://developer.capsulecrm.com/v2/operations/Task, https://capsulecrm.com/support/sales/adding-opportunities/

Verification: Verified

Pipeline stages

In full

Stages are called Milestones. Each opportunity sits on one milestone, milestones are configured by an administrator, and each carries a probability of winning. The pipeline is presented as a kanban board whose columns are the milestones ordered by that probability, and an opportunity is advanced by dragging it from one milestone column to the next.

Source: https://capsulecrm.com/support/sales/stages-of-an-opportunity/, https://capsulecrm.com/support/sales/an-overview-of-the-sales-pipeline/

Verification: Verified

Status

Not at all

The documented opportunity model has no open-or-settled attribute of its own: its fields are the milestone reference, value, expectedCloseOn, probability, closedOn, lostReason and similar. Whether the opportunity is settled is a property of the milestone it sits on, which carries a boolean named complete indicating that opportunities at that stage are closed. The list view offers an open-versus-closed filter, but the underlying fact is held on the milestone. Ruled 30 Aug 2026: status and stage must be completely separate values, so an outcome that is a property of the stage is not a status attribute at all.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone

Verification: Verified

Resolution

In part

Won and lost are milestones, selected from the same milestone menu used to advance the opportunity. The milestone model requires probability to be exactly 0 or 100 when complete is true, so the won-versus-lost distinction is read from the closed milestone's probability rather than from any attribute on the opportunity. The opportunity does carry an optional lostReason, but the vendor describes it as an optional reason applied to opportunities already lost, not as the record of the outcome.

Source: https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Value

In full

The opportunity model ships a value attribute holding an amount and currency.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Scope of work

In part

Only a generic description attribute; the vendor suggests tags or custom fields for what is sold.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Expected close date

In full

expectedCloseOn is a shipped date attribute, distinct from the actual closedOn date.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Actual close date

In full

The vendor ships a separate Actual Close Date, exposed in the API as closedOn and described as the date the opportunity was closed. The support documentation states that once the opportunity is won or lost, Capsule fills this field in to show when it closed, and contrasts it with the Expected Close Date a user enters, so the two can be compared. It does not appear in the documented create or update request bodies.

Source: https://capsulecrm.com/support/sales/adding-opportunities/, https://developer.capsulecrm.com/v2/models/opportunity

Verification: Verified

Opportunity owner

In full

Owner is a shipped user reference, alongside an optional team.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Linked buyer

In full

The required party attribute is the main contact, and additional parties can be linked.

Source: https://developer.capsulecrm.com/v2/models/opportunity, https://developer.capsulecrm.com/v2/models/milestone, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Record preservation

In full

Settled opportunities are kept rather than removed. The pipeline page filters between open and closed opportunities, a closed opportunity can be reopened, and the vendor advises closing as won or lost instead of deleting precisely so the history survives. Standard sales reports run on them, covering won and lost counts and values over time, by owner and by team, lost opportunities broken down by reason, and a conversion rate over rolling periods.

Source: https://capsulecrm.com/support/business-insights/reporting-on-your-sales/, https://capsulecrm.com/support/sales/an-overview-of-the-sales-pipeline/, https://capsulecrm.com/support/sales/managing-your-opportunities/

Verification: Verified

Structured lost reasons

In full

When an opportunity is marked lost the user can optionally select a Lost Reason from a list that an administrator configures in account settings, and the API carries a `lostReason` field on the opportunity. The list is account-wide and shared across all pipelines. Three native reports break lost opportunities down by reason, by owner and by team, so the field is structured and reportable rather than free text.

Source: https://capsulecrm.com/support/sales/stages-of-an-opportunity/, https://capsulecrm.com/support/sales/multiple-sales-pipelines/, https://capsulecrm.com/support/business-insights/reporting-on-your-sales/

Verification: Verified

Email sync

In part

A user connects a Google Workspace, Gmail, Microsoft 365 or Outlook mailbox and then composes and sends mail from a Send email button inside Capsule, on contact, opportunity and project records, with the sent copy landing in the provider's own sent folder. The return path is not a mailbox sync: inbound and externally sent mail reaches Capsule either by forwarding or BCC to the account's Mail Drop Box address, or through the Gmail add-on or Outlook add-in, which can be set to auto-store all mail to and from a chosen contact once switched on for that contact. Auto-store attaches only to contact records, not to opportunities or projects, and only catches mail where the contact is in the To or From field. There is no unified inbox inside Capsule and no documented account-wide automatic capture, so the two-way flow is present but constrained.

Source: https://capsulecrm.com/support/setup-and-configuration/sending-emails-and-email-templates/, https://capsulecrm.com/support/email-and-communication/storing-emails/, https://capsulecrm.com/support/email-and-communication/outlook-add-in/, https://capsulecrm.com/support/email-and-communication/gmail-add-on/

Verification: Verified

Calendar sync

In part

Two separate one-way mechanisms exist and neither is a two-way sync. Outbound, Capsule publishes an iCalendar feed of the user's tasks that Outlook, Google Calendar or Mac Calendar can subscribe to, and the vendor states this is a one-way feed from Capsule to the calendar app with changes made only in Capsule. Inbound, a connected Google or Outlook calendar surfaces its events inside the Capsule calendar and contact sidebars, but the vendor states those events can be viewed and not edited in Capsule and that Capsule tasks do not appear in the connected calendar. Only one of the two calendar providers can be connected at a time.

Source: https://capsulecrm.com/support/calendar-and-tasks/managing-your-tasks/, https://capsulecrm.com/support/integrations/google-calendar-integration/, https://capsulecrm.com/support/integrations/outlook-calendar-integration/

Verification: Verified

Schedulable activity types

In full

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.

Source: https://capsulecrm.com/support/calendar-and-tasks/getting-started-with-the-calendar-and-tasks/, https://capsulecrm.com/support/calendar-and-tasks/managing-your-tasks/, https://developer.capsulecrm.com/v2/operations/Task, https://developer.capsulecrm.com/v2/operations/Activity_Type

Verification: Verified

Opportunity reporting

In part

Two of the three are native dashboards. Conversion Rate gives the percentage of opportunities won out of all won and lost opportunities, over 30, 90 and 365 days. Pipeline Forecast projects value and count month by month from the opportunity's expected close date and value, weighted by the milestone probability, and expected close date is a first-class opportunity field the API exposes alongside probability and milestone. Stage conversion is the gap. Leaking Pipeline shows the percentage and number of opportunities lost at each milestone, but the vendor never states the denominator, so whether that percentage is a share of all losses or a loss rate against the opportunities that reached the milestone is unresolved, and a share of all losses is a distribution. No other report states the proportion advancing from one milestone to the next: the milestone reports are pipeline by milestone, by owner and by team, average time to won, won and lost over time, lost by reason, pipeline growth, average sales value and pipeline by tag, all counts, values or durations. The vendor does not state a refresh cadence.

Verification: Verified