Bitrix24

The crm.deal.fields enumeration lists COMPANY_ID and CONTACT_ID as links to separate Company and Contact entities, and activities (crm.activity) attach to any CRM entity via OWNER_TYPE_ID/OWNER_ID. Deal, contact, company and activity are four distinct, mutually linkable record types.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html, https://apidocs.bitrix24.com/api-reference/crm/timeline/activities/activity-base/crm-activity-list.html

Verification: Verified

A deal's STAGE_ID references a crm.status directory entry, and crm.status.add documents a SORT field ('Sorting. Default is 10') that fixes stage order, with a stated rule that in-progress stages sort before the success stage before failure stages.

Source: https://apidocs.bitrix24.com/api-reference/crm/status/crm-status-add.html, https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html

Verification: Verified

crm.deal.get documents CLOSED as its own char field ('Indicates whether the deal is closed. Possible values: Y - yes, N - no'), returned separately from STAGE_ID in the same record.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-get.html

Verification: Verified

Deals have no separate won/lost field. STAGE_SEMANTIC_ID is documented as generalizing STAGE_ID into P (in process), S (success/won) and F (failure/lost) groups - won-vs-lost is read from which stage group the current stage belongs to.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html, https://apidocs.bitrix24.com/tutorials/crm/how-to-get-lists/how-to-get-stages-with-semantics.html

Verification: Verified

OPPORTUNITY is a native double field on the deal, documented as 'Amount. By default 0.00'.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-add.html

Verification: Verified

crm.deal.productrows.get and crm.deal.productrows.set let a deal carry structured product line items, not just a free-text description.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-productrows-get.html, https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-productrows-set.html

Verification: Verified

CLOSEDATE is a native date field, documented as 'Close date. By default - the date the deal is created plus 7 days', editable by the user as a target.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-add.html

Verification: Verified

The full crm.deal.fields enumeration (44 fields) has no distinct actual-close-date field; CLOSEDATE is documented only as an editable target defaulting to creation+7 days, and MOVED_TIME records only the last stage change, not a close event.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html, https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-get.html

Verification: Verified

ASSIGNED_BY_ID ('Responsible person. By default - the user calling this method') is documented separately from CREATED_BY_ID ('Read-only field identifying who created the record').

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-add.html, https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html

Verification: Verified

CONTACT_ID/CONTACT_IDS link a deal to a Contact record, documented separately from the COMPANY_ID company link.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html

Verification: Verified

CRM analytics documentation describes Employee Performance and Sales Trends reports drawing on won-deal totals and historical deal amounts over selected periods, showing closed deals persist and feed reporting.

Source: https://helpdesk.bitrix24.com/open/17988776/

Verification: Verified

No lost-reason field appears in the crm.deal.fields enumeration. A buyer-built custom field (e.g. a list-type field via crm.deal.userfield.add) can be added, and Bitrix24 documents custom fields as usable dataset columns in BI Builder reports; note the separate classic 'CRM analytical reports' restrict custom fields to Number/Integer type only.

Source: https://apidocs.bitrix24.com/api-reference/crm/deals/crm-deal-fields.html, https://helpdesk.bitrix24.com/open/16457718/, https://helpdesk.bitrix24.com/open/24292640/

Verification: Verified

Connecting a mailbox with CRM integration enabled brings incoming replies into the CRM item ('incoming emails will appear in the corresponding CRM item form'), and the same connected mailbox is used to compose and send email from within the CRM.

Source: https://helpdesk.bitrix24.com/open/17229402/

Verification: Verified

Google Calendar sync is documented as real-time and bidirectional: 'Sync works in real time and in both directions: from Google Calendar to Bitrix24 and from Bitrix24 to Google Calendar.' (Separately, generic CalDAV sync to other calendars is documented as one-way only, into Bitrix24.)

Source: https://helpdesk.bitrix24.com/open/25047258/, https://helpdesk.bitrix24.com/open/25163280/

Verification: Verified

crm.activity.type.add lets an administrator register a custom activity type beyond the standard call/meeting/email/task set, for use when scheduling activities.

Source: https://apidocs.bitrix24.com/api-reference/crm/timeline/activities/types/crm-activity-type-add.html

Verification: Verified

The Sales Funnel report natively shows stage-to-stage conversion rate, and the vendor's sales-reporting page documents 'weighted revenue by stage: probability-adjusted totals' as a native forecast. No native report is documented expressing deal win rate as a rate rather than a count or trend.

Source: https://helpdesk.bitrix24.com/open/24279544/, https://www.bitrix24.com/tools/crm/features/sales-reporting.php

Verification: Verified