Sales engagement or prospecting tool
Not a CRM - fails on core objects, status, expected close date, schedulable activity types, opportunity reporting; actual close date, structured lost reasons unresolved
Core objects
In part
Breakcold carries a People section, a Companies section, a Deal object and a Task object. A person is linked to an organization through a Company field on the lead profile, which searches existing company records or creates one, and each company record exposes a People section listing the individuals attached to it. A deal is a tracked opportunity to which multiple people and companies can be added from the deal information page, and each deal is tracked independently with its own stage, value and notes. Companies are held as lead records flagged as companies rather than as a wholly separate entity, and vendor documentation describes tasks being linked to leads and to inbox conversations but does not describe attaching a task to a deal.
Source: https://developer.breakcold.com/help/contacts-lists/what-is-a-company-in-breakcold, https://developer.breakcold.com/help/contacts-lists/how-to-add-a-lead-to-a-company, https://developer.breakcold.com/help/contacts-lists/can-i-attach-multiple-leads-or-companies-to-a-deal, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/tasks-activities/are-tasks-linked-to-a-message
Verification: Pending vendor verification
Pipeline stages
In full
A pipeline is a set of ordered statuses that records move through. Stages are added from the pipeline view, renamed, given a color and reordered by dragging the columns. The public API models a stage as a Status object carrying a name, an explicit numeric order, a color, a stage type and the identifier of the list the stage belongs to, and a deal's stage can also be changed in bulk from the deal list.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-customize-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/how-do-i-change-the-status-of-multiple-deals-in-one-go, https://developer.breakcold.com/v3/api-reference/openapi.json
Verification: Verified
Status
Not at all
Whether an opportunity is live or settled is a property of the pipeline stage it sits in. The vendor documents a status type selector on each stage when the pipeline is edited, with Deal Won, Deal Lost and Default as the choices, Default covering every stage still in progress. The public API schema matches this: the Status object, which is the stage, carries a type enum of DEAL_WON, DEAL_LOST or null, alongside name, order, color, success_rate and the identifier of the list it belongs to. The stage must be looked up to learn the answer. 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.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/v3/api-reference/openapi.json
Verification: Verified
Resolution
In part
The same stage-level status type separates the two outcomes, since Deal Won and Deal Lost are its two settled values and the API enum spells them as DEAL_WON and DEAL_LOST on the Status object. The vendor states plainly that the type is chosen while editing a stage, not on the individual opportunity.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/v3/api-reference/openapi.json
Verification: Verified
Value
In full
Each deal is tracked with its own value, and pipeline currency is configurable.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline
Verification: Verified
Scope of work
In part
The only shipped descriptive facility is per-deal notes; no scope or line-item field.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline
Verification: Verified
Expected close date
Not at all
No expected close date field exists on the deal, confirmed by the reporting research; only a manual chance-of-closing percentage.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline
Verification: Verified
Actual close date
No verdict
No vendor documentation was found that either names a field holding the date an opportunity was settled or states that none exists. The pipeline analytics page reports revenue over time and counts of created, won and lost opportunities, but does not say which date those measures are keyed to.
Searched: Read the Breakcold help center index for pipeline and deals and worked through the articles on what a deal is, adding a deal, using the sales pipeline, creating and customizing deal attributes, exporting and importing deals, checking when a lead entered the pipeline, and pipeline analytics: none lists the fields an opportunity carries. Also read the published OpenAPI schema, which documents user, status, workspace, member and lead objects but no opportunity object, so no field list could be confirmed there either.
Verification: Pending vendor verification
Opportunity owner
In full
Deals carry an owner, assignable individually or in bulk.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline
Verification: Verified
Linked buyer
In full
A deal can be linked to a contact or to a company, so a person link ships.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/pipeline-deals/can-each-deal-have-its-own-stage-and-value, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline
Verification: Verified
Record preservation
In full
Settled opportunities stay in the workspace in their won or lost stage, and previously created opportunities remain listed under Recent Deals for reference or reuse. Pipeline analytics reports on them directly: the documented blocks include counts of opportunities created, won and lost, an average value of those won, a lost or closed value, and a comparison of open pipeline against closed business.
Source: https://developer.breakcold.com/help/pipeline-deals/what-is-pipeline-analytics, https://developer.breakcold.com/help/pipeline-deals/can-i-see-past-deals-ive-added
Verification: Verified
Structured lost reasons
No verdict
A lost outcome is recorded by moving the record into a stage whose status type is Deal Lost, and each deal carries its own notes, which can be created, edited and replied to, so the reason can be written against the lost record as free text. No dedicated lost reason field, structured or otherwise, appears anywhere in vendor documentation, and no lost reason breakdown exists among the seven pipeline analytics blocks. Deal attributes can be created and customized from settings, so a structured reason could be built, but the vendor does not document which field types are available on the deal object.
Source: https://developer.breakcold.com/help/pipeline-deals/how-to-identify-or-set-the-status-type-in-your-pipeline, https://developer.breakcold.com/help/contacts-lists/how-do-i-create-edit-and-reply-to-notes, https://developer.breakcold.com/help/pipeline-deals/where-can-i-create-and-customize-my-deal-attributes-or-properties, https://developer.breakcold.com/help/pipeline-deals/what-is-pipeline-analytics
Searched: Searched the vendor documentation index for lost reason, loss reason and why a deal was lost; no article returned.
Verification: Pending vendor verification
Email sync
In full
A mailbox is connected through Google Workspace authorisation, a Gmail application password, a Microsoft 365 or Outlook account, or IMAP and SMTP. Once connected, mail sent and received in the external mailbox syncs automatically onto the matching contact, and the vendor states that activity from integrations such as Gmail is synced and includes emails, messages and interactions related to leads. Mail is composed and sent from inside the CRM, both from the unified inbox and from the lead view alongside LinkedIn, WhatsApp and Telegram. Ingestion is broad enough that the vendor supplies an email filtering rule set to exclude unwanted mail by subject, sender name, sender address or body content.
Source: https://developer.breakcold.com/help/contacts-lists/will-emails-from-office-365-sync-with-contacts-in-breakcold, https://developer.breakcold.com/help/integrations-api/is-activity-synced-across-integrations-like-gmail-or-linkedin, https://developer.breakcold.com/help/inbox-messaging/how-can-i-send-my-email-whatsapp-linkedin-and-telegram-messages-from-the-lead-view, https://developer.breakcold.com/help/inbox-messaging/how-to-connect-a-gsuite-account, https://developer.breakcold.com/help/workspace-permissions/how-can-i-filter-emails-from-being-ingested-into-my-workspace
Verification: Verified
Calendar sync
In part
Connecting a Google or Outlook calendar syncs the user's upcoming meetings into the CRM, where the built-in recorder can join them automatically, and the help center instructs users to ensure the email on the meeting invite matches the one held on the lead so that the meeting is filed against the right record, which is invite-level matching rather than transcript matching. The vendor states plainly that creating and updating invites from Breakcold does not exist, so nothing travels from the CRM outwards, and the sync is inbound only. The calendar connection is documented in vendor articles rather than appearing in the integration directory, which lists around thirty integrations and includes no calendar product.
Source: https://developer.breakcold.com/help/contacts-lists/how-can-i-make-sure-the-meeting-is-synced-in-breakcold-for-the-contact-i-invited, https://www.breakcold.com/blog/crm-with-google-meet-calendar-integration, https://www.breakcold.com/blog/crm-with-meeting-recorder, https://www.breakcold.com/integrations
Verification: Pending vendor verification
Schedulable activity types
Not at all
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 catalog exposes only lead, list, status and tag events, with no call or meeting event.
Source: 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, https://developer.breakcold.com/events
Verification: Verified
Opportunity reporting
Not at all
One of the three exists, and the rule requires two. Each pipeline stage carries a manually set percentage representing the chance of closing, and the vendor states that these feed a forecasted revenue figure, so a weighted-pipeline forecast is computed by the product rather than assembled outside it - although it runs on manual stage probabilities rather than on an expected close date, and no expected close date field exists on the deal. The other two are absent. The seven documented pipeline analytics blocks - Pipeline Activity, Pipeline vs Closed, Created Leads, Average Deal Value Won, Deal Lost or Closed Value, Pipeline Generated, and Deals Created, Won and Lost - are overviews, volumes and values, none expressed as a rate, so there is no overall win or loss rate and no stage-to-stage conversion measure. A vendor product page markets win rate reporting, which no help article supports. Activity logs cannot be exported and the analytics module is described by the vendor as still in beta.
Source: https://developer.breakcold.com/help/contacts-lists/what-do-the-percentages-mean, https://developer.breakcold.com/help/pipeline-deals/what-is-lead-chance-of-closing-in-the-pipeline, https://developer.breakcold.com/help/pipeline-deals/what-is-pipeline-analytics, https://developer.breakcold.com/help/analytics/whats-coming-next-in-crm-analytics-beta-roadmap, https://developer.breakcold.com/help/imports-files/can-i-export-activity-logs
Verification: Verified