Close

All four objects exist. The Lead is the organization record - vendor documentation describes it as representing a company or organization and as covering what other systems split into lead and account - and Contacts are the people at that company. Opportunities and Contacts are dependent children of a Lead, so organization association is compulsory rather than optional, and an Opportunity carries a Contact field linking it to a named person. The constraint is on the activity side: vendor documentation states that activities belong to Leads and represent work done on a Lead or its Contacts, and there is no opportunity association on user-created activities. The only documented activity-to-opportunity link is the system-generated `opportunity_due` task, which the platform creates for an opportunity scheduled to close on a given date. Activity and opportunity are therefore related only through their shared Lead.

Source: https://developer.close.com/resources/leads/, https://help.close.com/feature-guide/leads, https://help.close.com/feature-guide/opportunities, https://developer.close.com/resources/activities/, https://developer.close.com/api/resources/tasks

Verification: Verified

A pipeline is a named and ordered group of Opportunity Statuses, and an opportunity moves through those statuses. Each status must have a name that is unique within its pipeline and a status type, and statuses can be dragged to reorder them, so the sequence is defined by the administrator rather than fixed.

Source: https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

The opportunity object itself carries a status_type attribute whose value is always one of active, won or lost, so whether the opportunity is still live is read straight off the record without looking up the pipeline status it sits on. The attribute appears in the documented create response alongside status_id and status_label.

Source: https://developer.close.com/api/resources/opportunities/create

Verification: Verified

The same status_type attribute on the opportunity distinguishes won from lost, since its three permitted values are active, won and lost. One combined attribute therefore carries both the live-or-settled fact and the won-or-lost fact.

Source: https://developer.close.com/resources/opportunities/

Verification: Verified

Value is a shipped monetary attribute, with one-off or recurring periods.

Source: https://developer.close.com/resources/opportunities/, https://help.close.com/feature-guide/opportunities, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

Only a generic note field; no scope or line-item facility on the opportunity.

Source: https://developer.close.com/resources/opportunities/, https://help.close.com/feature-guide/opportunities, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

Estimated Close is a shipped date field, separate from the recorded won date.

Source: https://developer.close.com/resources/opportunities/, https://help.close.com/feature-guide/opportunities, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

The opportunity ships date_won and date_lost attributes, separate from the Estimated Close date a user sets. The API reference states that date_won is filled in with the current date automatically when the status is changed to one typed won, unless a value was supplied, and that reverting the status later does not clear it. The equivalent automatic behavior for date_lost is not described.

Source: https://developer.close.com/api/resources/opportunities/update

Verification: Verified

The User field names the person responsible.

Source: https://developer.close.com/resources/opportunities/, https://help.close.com/feature-guide/opportunities, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

Contact ships on the opportunity, linking it to a contact on the parent lead.

Source: https://developer.close.com/resources/opportunities/, https://help.close.com/feature-guide/opportunities, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

Settled opportunities stay in the account and stay visible. The pipeline view can be set to display all statuses including won and lost, and its close date filter returns won opportunities settled on a chosen date. The Opportunity Funnels report counts won and lost opportunities, derives a win rate from them and reports an average number of days to close.

Source: https://help.close.com/feature-guide/opportunities/opportunity-pipeline-view, https://help.close.com/feature-guide/reports/opportunity-funnels-report

Verification: Verified

There is no dedicated lost reason field in Close. Custom fields can be attached to the Opportunity object and the available types include Dropdown (single) and Dropdown (multiple), so a structured picklist reason can be defined on the opportunity itself. Explorer accepts custom fields as a reporting dimension, with the documented exclusions being text fields and choice fields carrying more than ten options, so a reason list kept to ten or fewer choices is reportable. Additionally, statuses are user-created and each is assigned a type, so several separately named statuses of the Lost type can be defined.

Source: https://help.close.com/docs/custom-fields, https://help.close.com/docs/explorer, https://help.close.com/feature-guide/opportunities/opportunity-statuses

Verification: Verified

A Gmail or Google Workspace mailbox, a Microsoft Office 365 mailbox or a custom IMAP and SMTP mailbox can be connected, and the vendor describes it as two-way email integration. Mail is sent from inside Close and replies are logged automatically; mail sent from the external client or a phone is picked up from the Sent folder and logged to the lead's activity feed, and mail sent from Close appears in the connected mailbox's Sent folder. Vendor documentation states explicitly that there is no need to BCC Close when sending from an external client, so a dropbox address is not the mechanism.

Source: https://help.close.com/docs/email-configuration

Verification: Verified

The Meetings feature connects a Google Calendar or Office 365 Calendar and pulls scheduled meetings into Close, where they appear as meeting activities on the lead's feed and in the Inbox sidebar. Only events with an attendee matching a Contact on a Lead are pulled in, and internal or blocklisted domains are excluded. The documented flow is inbound only - vendor documentation describes meetings being pulled from the calendar into Close and does not describe creating a meeting in Close that is written out to the connected calendar - so the sync runs one way.

Source: https://help.close.com/docs/meetings, https://help.close.com/feature-guide/meetings

Verification: Verified

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 organization 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.

Source: https://help.close.com/docs/tasks, https://developer.close.com/api/resources/tasks, https://help.close.com/docs/custom-activities, https://help.close.com/docs/meetings

Verification: Verified

The Opportunity Funnels report shows the conversion rate between each pair of adjacent pipeline stages, and separately a Win Rate computed as won opportunities divided by won plus lost. It can be read by count, by annualised value or by weighted annualised value. For forecasting, the opportunity carries a first-class Estimated Close date, and Expected Value is defined by the vendor as value multiplied by confidence and described as a weighted pipeline value used for forecasting revenue. The Pipeline View can be set to show expected values, totals update per status column, and it can be filtered by the expected close date, which produces a projected revenue figure for a chosen period. There is no separately named forecast report; the projection is produced within the pipeline view.

Source: https://help.close.com/docs/opportunity-funnels-report, https://help.close.com/feature-guide/opportunities, https://help.close.com/docs/opportunity-pipeline-view, https://help.close.com/feature-guide/opportunities/opportunity-pipeline-view

Verification: Verified