Coevera

Accounts, Contacts, Opportunities and Activities are separate entities in the vendor's own description of the data model, alongside Leads, Products and Product Line Items. The API describes accounts as holding company information, contacts as the people associated with them, and opportunities as tied to contacts or accounts and moving through a pipeline. An opportunity is created with `account_relations` and `contact_relations`, each requiring one entry flagged `is_primary`, and activities - tasks and appointments - are documented as linkable to opportunity, account and contact records. The account link can be relaxed: the import guidance describes Account Name as optional where an administrator has removed the requirement.

Source: https://developers.pipelinersales.com/api-docs/core-api-concepts/understanding-the-crm-concept, https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity, https://help.pipelinersales.com/en/articles/2724539-creating-activities-tasks-and-appointments, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner

Verification: Verified

An opportunity sits in a pipeline and moves across that pipeline's steps, which the vendor describes as columns representing the stages of the lifecycle. Administrators define the steps, rename them, and change their order by dragging and dropping, and each step carries a Probability of Closure percentage the vendor calls the Weighting. The step is held on the opportunity: the API creates an opportunity with a `step_id` naming the pipeline step it belongs in, and a pipeline requires at least three steps.

Source: https://help.pipelinersales.com/en/articles/2724115-managing-your-first-pipeline, https://help.pipelinersales.com/en/articles/3353269-the-pipeline-view-in-detail, https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity

Verification: Verified

The opportunity carries its own Opportunity Status field. The vendor's import documentation enumerates it among the opportunity's fields and states that the only allowed values are Open, Won or Lost, and the automation documentation describes the field changing without a user editing it: moving an opportunity to the final column of the pipeline updates Opportunity Status to Won from Open, and archiving an opportunity changes Opportunity Status to Lost. The field is separate from the pipeline step, which is imported as its own Pipeline Step column, and it is available as a report column and as an automation condition.

Source: https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner, https://help.pipelinersales.com/en/articles/3834789-automatizer-creating-and-running-processes, https://help.pipelinersales.com/en/articles/3967316-automatizer-use-case-archiving-opportunities-that-are-overdue-closing-date-in-the-past, https://help.pipelinersales.com/en/articles/2728834-reports-creating-a-standard-table-report-or-a-pivot-table-report

Verification: Verified

Won and Lost are two of the three values of the same Opportunity Status field that answers whether the opportunity is still open, so the outcome is derived from the open-or-closed field rather than held in an attribute of its own. No separate won flag or outcome field appears in the vendor's enumeration of opportunity fields. Won Date and Lost Date are documented as separate fields, but they record when the opportunity settled rather than how it ended.

Source: https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner, https://help.pipelinersales.com/en/articles/3834789-automatizer-creating-and-running-processes

Verification: Verified

Opportunity Value ships on the opportunity and is documented as a currency field. The API creates an opportunity with a required `value` object carrying `base_value`, `currency_id` and, in multi-currency accounts, `value_foreign`, so the platform treats the figure as money rather than as a plain number.

Source: https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner

Verification: Verified

Product Line Items attach to the opportunity, connecting it to records from the product catalog. The vendor documents setting up products, product line items and pricing for use in opportunities, with price lists and product categories behind them, and the import guidance maps Product Name, Quantity, Price, Price List, Product Currency and custom line item fields onto an opportunity. There is also an Opportunity Description field.

Source: https://help.pipelinersales.com/en/articles/2724329-setting-up-products-product-line-items-and-pricing-for-use-in-opportunities, https://developers.pipelinersales.com/api-docs/core-api-concepts/understanding-the-crm-concept, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner

Verification: Verified

Closing Date ships on the opportunity as a required date field. The API documents `closing_date` as the expected closing date, the date when the opportunity should be closed, and the vendor's guidance on qualifying a lead into an opportunity instructs the user to complete Value and Closing Date.

Source: https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner, https://help.pipelinersales.com/en/articles/2724543-creating-leads-opportunities-and-activities-and-managing-them-throughout-your-pipeline-sales-funnel-including-winning-and-losing-prospective-deals

Verification: Verified

Won Date and Lost Date are shipped fields on the opportunity, distinct from the expected Closing Date, and the vendor calls them important for the Insights analytics when historical won or lost opportunities are imported. The automation documentation also uses an Actual Closing Date on the opportunity to schedule an action a set number of days after the deal actually closed. Vendor documentation does not state whether the platform stamps these dates itself when the status changes.

Source: https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner, https://help.pipelinersales.com/en/articles/3834789-automatizer-creating-and-running-processes

Verification: Verified

The opportunity carries an owner. The API requires `owner_id`, the identifier of the user who owns the opportunity, when the record is created, and the import guidance requires an Owner column naming an active user by login email. Ownership is transferable: the vendor documents changing ownership when users leave the company, and roles can grant editor and manager rights over records a user does not own.

Source: https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner, https://help.pipelinersales.com/en/articles/2723710-changing-ownership-and-managing-users-who-leave-your-company

Verification: Verified

The opportunity links to contacts through `contact_relations`, and the API states that at least one contact must be marked primary. This is a separate association from `account_relations`, which links the opportunity to the organization, so the person being sold to is recorded in their own right.

Source: https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-opportunity, https://developers.pipelinersales.com/api-docs/core-api-concepts/understanding-the-crm-concept

Verification: Verified

Closed opportunities stay in the system. Won opportunities remain in the pipeline's final column. Lost opportunities are archived rather than removed: archiving sets Opportunity Status to Lost and moves the record to the Archive menu, where the vendor documents that they can still be displayed in the Pipeline view at the step they reached, can be reactivated in bulk, and where the Archive is one of the record types a report can be built on. Deletion is a separate and later action, and the vendor states that a record must be archived before it can be deleted. The Insights metrics count Lost Opportunities and Lost Amount and compute a win rate across won and lost opportunities, which requires the closed records to persist and stay queryable.

Source: https://help.pipelinersales.com/en/articles/3353269-the-pipeline-view-in-detail, https://help.pipelinersales.com/en/articles/3967316-automatizer-use-case-archiving-opportunities-that-are-overdue-closing-date-in-the-past, https://help.pipelinersales.com/en/articles/3023704-how-to-delete-data, https://help.pipelinersales.com/en/articles/2728834-reports-creating-a-standard-table-report-or-a-pivot-table-report, https://help.pipelinersales.com/en/articles/2790822-management-insights, https://help.pipelinersales.com/en/articles/3958187-bulk-operations-mass-actions-for-leads-and-opportunities

Verification: Verified

Lost Reason is a shipped field and the vendor states it is required in order to archive an opportunity, which is the action that sets the status to Lost. The list of values is administrator-controlled in the Admin Module under Fields & Forms, and the vendor's own guidance recommends creating a distinct reason for automated archiving so the two can be told apart in reporting. Bulk archiving also demands a reason for each record, and the import guidance treats Lost Reason as a required column for lost opportunities alongside a separate Lost Reason Description.

Source: https://help.pipelinersales.com/en/articles/3967316-automatizer-use-case-archiving-opportunities-that-are-overdue-closing-date-in-the-past, https://help.pipelinersales.com/en/articles/3958187-bulk-operations-mass-actions-for-leads-and-opportunities, https://help.pipelinersales.com/en/articles/2724316-importing-opportunities-and-products-into-pipeliner

Verification: Verified

Users connect their own Gmail or Microsoft 365 mailbox from inside the application, after which every email they send to or receive from a contact held in the CRM is copied to the Feeds tab of the matching records. Mail also goes the other way: the Create Email function composes and sends from inside the CRM through the connected Gmail or Microsoft 365 account, and the message is copied to the feeds of the recipients, optionally logged as an email task. One documented constraint: no historical mail is copied, only messages sent and received after the connection is activated. An Outlook add-in and a SendGrid route are documented separately and are not what this verdict rests on.

Source: https://help.pipelinersales.com/en/articles/2724420-integrating-your-gmail-with-coevera, https://help.pipelinersales.com/en/articles/3439521-gmail-integration-sending-emails-from-coevera, https://help.pipelinersales.com/en/articles/3367898-microsoft-365-office-365-outlook-email-integration, https://help.pipelinersales.com/en/articles/3339921-microsoft-365-office-365-sending-emails-from-coevera

Verification: Verified

The sync runs in both directions on the appointment, which is a real activity record rather than a date field. For Microsoft 365 the vendor states the sync is bi-directional, so appointments created in the selected Outlook calendar appear in the CRM's Activities menu and appointment activities created in the CRM sync to Outlook. Google Calendar behaves the same way through a dedicated calendar the integration creates, with the caveat that events added to any other Google calendar will not sync. Only a named set of fields crosses - subject, location, start, end, attendees and, on Microsoft, description - Google events can take up to fifteen minutes to appear, and recurring Outlook appointments arrive read-only.

Source: https://help.pipelinersales.com/en/articles/3322363-integrating-your-microsoft-365-office-365-appointments-with-coevera, https://help.pipelinersales.com/en/articles/2724425-integrating-your-google-calendar-with-coevera

Verification: Verified

Activities are scheduled inside the CRM as tasks or appointments, carrying a due date or start and end times, an owner, a status, a priority, a description and a type, and they can be linked to opportunity, account and contact records. A type field ships on both: tasks default to Call, Email and Task, appointments carry an appointment type. Customers can define their own types - the vendor documents custom appointment types for Business and Enterprise tiers and custom task activities for Enterprise, with the stated purpose of running a report on those activity types, and adds that custom task and appointment types can be created for Enterprise or Unlimited tier customers. Custom fields can be added to tasks and appointments on the Enterprise tier.

Source: https://help.pipelinersales.com/en/articles/2724572-understanding-activities-tasks-and-appointments, https://help.pipelinersales.com/en/articles/2724539-creating-activities-tasks-and-appointments, https://help.pipelinersales.com/en/articles/2714255-fields-forms

Verification: Verified

All three are native. Stage conversion is the Insights indicator Conversion Rate by Step, which the vendor defines as the proportion of opportunities converted from one step to the next - a rate, not a distribution, and the platform holds the underlying data because sales step changes are tracked in the change log and can be reported on historically. Win rate is the Insights indicator Win Rate, defined as the percentage of won and lost opportunities with closing dates in the selected period that were won, with a Pipeline Win Rate on the performance view. Forecast is the Forecasts module, which projects revenue for users, units, products and product categories against a date field that can be the opportunity's Closing Date, with quotas and drill-down. Both Insights and Forecasts carry a Business, Enterprise and Unlimited tier badge, so an entry-tier customer is left with the standard and pivot report builders, whose aggregations are count, average, sum, minimum and maximum.

Source: https://help.pipelinersales.com/en/articles/2790822-management-insights, https://help.pipelinersales.com/en/articles/2939236-forecasts-creating-quota-and-forecasts-for-opportunities-products-and-product-categories, https://help.pipelinersales.com/en/articles/2728834-reports-creating-a-standard-table-report-or-a-pivot-table-report, https://help.pipelinersales.com/en/articles/9065321-reports-creating-a-report-using-historical-data

Verification: Verified