Salesflare

Accounts, contacts and opportunities are separate records with their own API resources and schemas: a contact carries an `account` reference, and an opportunity carries both `account` and `main_contact`. Activities are records too - tasks, calendar meetings, logged calls and internal notes. The constraint sits on the activity side, because vendor documentation attaches activities to the account. A task related to an account is found on the Tasks tab of the account timeline, synced calendar meetings get logged automatically in the right account timeline, calls are logged to the contact and the account timeline, and the fields offered when editing tasks in bulk are the account and the description. The opportunity's own documented attributes carry no activity association, and a custom field on an opportunity can reference an account, a contact or a user but not an activity. `account` is also the only required property when creating an opportunity through the API, so organization association is compulsory rather than optional. An activity therefore reaches an opportunity only through the account the two share.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/2352878-how-do-tasks-work, https://howto.salesflare.com/en/articles/624705-where-do-the-meetings-from-the-calendar-appear, https://howto.salesflare.com/en/articles/625058-how-are-calls-automatically-logged-to-salesflare, https://howto.salesflare.com/en/articles/4100649-what-are-bulk-actions, https://howto.salesflare.com/en/articles/2321233-can-i-make-different-types-of-custom-fields

Verification: Verified

An opportunity carries a stage, and the stage object exposes an `order` property giving its position within the pipeline alongside a win probability. Stages are created with a plus button, edited with a pencil icon and reordered by dragging them in Settings, and each pipeline's stage set is defined by the account rather than fixed by the vendor.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/624720-how-do-i-best-set-up-my-sales-pipeline, https://howto.salesflare.com/en/articles/1013258-can-i-configure-multiple-pipelines

Verification: Verified

The opportunity object ships a boolean `closed`, documented as whether the opportunity is closed, held on the record alongside `stage`. Whether an opportunity is still running is therefore readable from the opportunity itself with no stage lookup. A separate `status` string exists on the same object and the vendor marks it deprecated.

Source: https://api.salesflare.com/openapi.json

Verification: Verified

The opportunity's documented attributes are `closed`, `close_date`, `stage`, `lost_reason`, `probability`, `value`, `currency`, `owner`, `assignee`, `creator`, `main_contact`, `account`, `lead_source`, `name`, `start_date`, contract and recurring revenue fields, `tags`, `files` and `custom`. None of them records won or lost. Vendor material identifies a won opportunity by the name of the stage it sits in: the Salesforce migration guide tells the user to rename Closed Won and Closed Lost to Won and Lost before importing, the funnel report counts the opportunities that also make it to "Won", and the vendor's own Slack and Trello automation guides filter on the Stage field being Won. What could not be established is whether a stage carries metadata marking it as a won or a lost stage. The stage object embedded in the opportunity exposes `id`, `order`, `probability` and `fixed_stage`, and `fixed_stage` is documented only as the Salesflare ID of the fixed or default stage. That gap is exactly the difference between an outcome readable from stage metadata and won and lost being stage names with nothing behind them, so there is no verdict.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/8955290-how-to-migrate-your-data-from-salesforce-to-salesflare, https://howto.salesflare.com/en/articles/5782648-how-does-the-sales-funnel-analysis-work, https://howto.salesflare.com/en/articles/1237389-can-slack-notify-me-when-i-win-a-deal

Searched: Read the opportunity schema in the vendor's OpenAPI document in full and searched it for won, lost and resolution attributes; there are none. The `/pipelines` response schema, which would say what `fixed_stage` identifies and whether a stage is flagged as won or lost, lies beyond the truncation point of the fetched document. Searched the help center for marking an opportunity won or lost, for won and lost stages and for pipeline configuration; no article describes an outcome field.

Verification: Pending vendor verification

`value` ships on the opportunity as its monetary value, with a companion `currency` reference, and the vendor's regional settings article states that the account's currency is used for opportunity values, targets and the insights dashboard. Value is a recommended column on an opportunity import and is entered as a plain number without a currency symbol. Recurring revenue can additionally be expressed as a price per unit, a number of units and a frequency.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/2429528-what-are-the-regional-settings-used-for, https://howto.salesflare.com/en/articles/7002951-do-you-have-a-template-for-import-available

Verification: Verified

There is no products or line items facility on the opportunity, and the documented attributes include no description or notes field, so what is being sold goes into the opportunity name or into a custom field the buyer adds. Custom fields can be created on opportunities in sixteen types including long text, which runs to 21,844 characters, so a description can be arranged, but the buyer builds it. The recurring revenue fields record a price per unit, a number of units and a frequency rather than what the units are.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/2321233-can-i-make-different-types-of-custom-fields, https://howto.salesflare.com/en/articles/2346157-what-are-predefined-custom-fields

Verification: Verified

`close_date` ships on the opportunity, and the vendor states that the close date a user is asked to fill out is an expected close date, meaning when you would expect to win the opportunity. It is a required column on an opportunity import, and the vendor notes that moving an opportunity into a stage with a probability above zero requires a close date.

Source: https://howto.salesflare.com/en/articles/952868-why-am-i-asked-to-fill-out-a-close-date-what-does-it-mean, https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/7002951-do-you-have-a-template-for-import-available, https://howto.salesflare.com/en/articles/3185217-how-do-i-update-opportunity-stages-automatically

Verification: Verified

Salesflare ships one close date field and it carries both facts in turn. The vendor states that the close date is an expected date unless you close an opportunity as won or lost, and then it is the effective close date. The date a sale ended is therefore kept on the record. Vendor documentation does not state whether Salesflare stamps that date itself at close or whether the user sets it, and close date can be edited in bulk.

Source: https://howto.salesflare.com/en/articles/952868-why-am-i-asked-to-fill-out-a-close-date-what-does-it-mean, https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/4100649-what-are-bulk-actions

Verification: Verified

`owner` ships on the opportunity as the user who owns it, with `assignee` and `creator` held separately, so ownership is not the creation stamp. Owner and assignee can both be changed in bulk, and the vendor's migration guide treats the owner as a user reference matched by name or email.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/4100649-what-are-bulk-actions, https://howto.salesflare.com/en/articles/8955290-how-to-migrate-your-data-from-salesforce-to-salesflare

Verification: Verified

`main_contact` ships on the opportunity as its primary contact, a reference to a contact record and held separately from `account`. The vendor lists Main contact among its predefined fields on opportunities and describes it as a contact-type field.

Source: https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/2346157-what-are-predefined-custom-fields

Verification: Verified

Closed opportunities stay in the account and stay measurable. Marking an opportunity Done archives it out of the pipeline view, and the vendor states that although done opportunities are removed from view they are still used to calculate the insights dashboard, with the records found again by filtering on Done. The insights themselves rest on settled records - revenue from won opportunities, average sales cycle, top lost reasons, and a funnel calculated across all opportunities closed in the selected period.

Source: https://howto.salesflare.com/en/articles/2353405-how-do-i-hide-old-opportunities, https://howto.salesflare.com/en/articles/2446281-what-do-the-insights-mean, https://howto.salesflare.com/en/articles/5782648-how-does-the-sales-funnel-analysis-work

Verification: Verified

Lost reason is one of Salesflare's predefined fields on the opportunity, held on the record as `lost_reason`. The vendor ships default reasons and an administrator adds, edits and deletes the options under Settings > Customize fields, so the values are a controlled list rather than free text. They are counted natively: the insights dashboard carries Top Lost Reasons, the most common reasons an opportunity was lost. Lost reason can also be set across many opportunities at once with a bulk action.

Source: https://howto.salesflare.com/en/articles/1431794-how-do-i-add-a-custom-lost-reason-on-opportunities, https://howto.salesflare.com/en/articles/2446281-what-do-the-insights-mean, https://api.salesflare.com/openapi.json, https://howto.salesflare.com/en/articles/4100649-what-are-bulk-actions

Verification: Verified

A mailbox is connected under Settings > Email settings and as many addresses as needed can be connected. The sync runs both ways. Mail sent from a connected address is always picked up and synced into Salesflare irrespective of the mail program used, and clicking the email or reply icon anywhere in Salesflare opens a compose window that sends through the connected address. Synced mail populates the account timeline with the history between the contacts on an account and the team members on it. Provider coverage is broad: Microsoft 365 mailboxes, Google Workspace and Gmail, Apple mail using an app-specific password, and other mailboxes over IMAP through the vendor's email infrastructure partner.

Source: https://howto.salesflare.com/en/articles/1007208-can-i-send-emails-from-salesflare, https://howto.salesflare.com/en/articles/1007170-can-i-connect-multiple-email-addresses, https://howto.salesflare.com/en/articles/4818228-how-does-salesflare-s-email-sync-work, https://howto.salesflare.com/en/articles/1020082-my-emails-are-not-syncing-anymore-how-can-i-fix-this, https://howto.salesflare.com/en/articles/8926469-how-do-i-install-and-set-up-the-outlook-add-in, https://howto.salesflare.com/en/articles/6992325-can-i-connect-salesflare-to-my-apple-emails-calendar

Verification: Verified

Calendars are connected in the same settings, more than one can be added, and the sub-calendars that hold customer meetings are selected, after which past meetings appear on the account timelines and future ones in the Today and Upcoming task lists. The sync runs one way only. The vendor states that the sync is currently one-way, meaning Salesflare can pull meetings in but will not push tasks or meetings created in Salesflare to the calendar, and the route it offers for the return leg is a Zapier automation, which is not a shipped connection and does not count.

Source: https://howto.salesflare.com/en/articles/952673-how-can-i-connect-a-calendar, https://howto.salesflare.com/en/articles/624705-where-do-the-meetings-from-the-calendar-appear, https://howto.salesflare.com/en/articles/4406041-can-i-push-my-salesflare-tasks-to-my-google-calendar

Verification: Verified

Tasks are created inside Salesflare from the tasks page, the blue plus button or an account's Tasks tab, and carry a due or reminder date, an assignee, a description and a related account. They can be snoozed, reassigned, edited and deleted in bulk. A task carries a type: the vendor's own automation guide filters a trigger down to the Manual type of tasks in order to exclude the automatically created ones. The type values are Salesflare's own, covering manual tasks and the reminders the platform generates for meeting notes, email replies, meeting preparation and account inactivity, and no vendor documentation describes a buyer adding a type. Meetings and calls are separate records rather than task types, and custom fields in the interface can be added to accounts, contacts and opportunities but not to tasks.

Source: https://howto.salesflare.com/en/articles/2352878-how-do-tasks-work, https://howto.salesflare.com/en/articles/4406041-can-i-push-my-salesflare-tasks-to-my-google-calendar, https://howto.salesflare.com/en/articles/2436745-will-salesflare-remind-me-when-to-follow-up, https://howto.salesflare.com/en/articles/4100649-what-are-bulk-actions, https://howto.salesflare.com/en/articles/2321233-can-i-make-different-types-of-custom-fields

Verification: Verified

All three reports are native. The sales funnel analysis shows the stage names and, next to the downward arrows, the percentage of opportunities that moves to the next stage, calculated across all opportunities closed in the selected period, and it also shows how many of the opportunities reaching a given stage go on to Won. Win rate is stated as a proportion in the insights dashboard as Closing % per rep, out of the opportunities a rep makes how many they close, with a team distribution beside it. The forecast is Expected revenue, the sum of the value in each stage multiplied by that stage's probability, shown against a revenue target. Alongside the fixed insights, a report builder covers accounts, contacts, opportunities and tasks with view by, measure by and segment by axes, its own filters, and column, bar, line, scorecard, pie and pivot outputs.

Source: https://howto.salesflare.com/en/articles/5782648-how-does-the-sales-funnel-analysis-work, https://howto.salesflare.com/en/articles/2446281-what-do-the-insights-mean, https://howto.salesflare.com/en/articles/2317345-how-is-expected-revenue-calculated, https://howto.salesflare.com/en/articles/5511505-how-can-i-make-custom-dashboards-reports

Verification: Verified