Spotler CRM

All four record types exist and are distinct. Accounts, Contacts, Opportunities and Activities are separate objects with their own API v4 endpoints, and Tasks are a further separate record type in the interface. Two constraints hold the verdict below full. A contact cannot exist on its own: the vendor states that the product is designed for business to business markets "so Contacts always belong to Company Accounts", and that you cannot add a contact before you have created an account. And the working records hang off the account rather than off each other: activities are added on the account's Activities tab, and the vendor's own guidance says that "whilst an Opportunity or Task is held at the Account level you can add a Custom Field to the form to link it to a particular Contact within the Account". So an activity or task reaches a person or an opportunity only through the account, or through a field the buyer builds.

Source: https://support.reallysimplesystems.com/adding-contacts/, https://crm.spotler.help/hc/en-gb/articles/24564459873810-How-to-use-derived-tables, https://crm.spotler.help/hc/en-gb/articles/23503781646866-Accounts, https://crm.spotler.help/hc/en-gb/articles/23621049976722-Activities, https://crm.spotler.help/hc/en-gb/articles/24314867003922-Integration-API-V4

Verification: Verified

The opportunity carries a Status field holding the sales stage, and the stage list is the OpportunityStatus custom dropdown list. The vendor describes sales stages as "the sequence of steps you will go through in making a sale" and tells administrators to build them by adding values to OpportunityStatus in Custom Dropdown Lists. The sequence is held on the list itself, not on a view: dropdown values are reordered by dragging and dropping them into position and saving. Stage changes on an opportunity are written to Opportunity History, so movement along the sequence is recorded.

Source: https://support.reallysimplesystems.com/crm-sales-stages/, https://support.reallysimplesystems.com/dropdown-lists/, https://support.reallysimplesystems.com/opportunity-history/

Verification: Verified

The record side could not be settled. What the vendor does document is that open, won and lost are expressed through the Probability percentage on the opportunity: the support FAQ answers "What is a Won / Lost / Pipeline Opportunity?" with won at 100 percent, lost at 0 percent and pipeline at 1 to 99 percent, and the dashboard acts on that, moving an opportunity "from the Pipeline column to the Closed this Month column" when the probability is changed to 100 percent. The vendor's language around it is permissive rather than structural - "you could say the percentage sale probability is 100%" - and the Status field itself is a user-defined dropdown whose won and lost entries are stage names. Whether the opportunity object also carries a shipped open-or-closed attribute cannot be established, because the only enumeration of what the object holds is the API v4 datadictionary endpoint, which requires an authenticated call. No verdict is recorded rather than a failure. Ruled 30 Aug 2026: status and stage must be completely separate values, so an outcome read from which stage the record occupies is not a status attribute at all.

Source: https://support.reallysimplesystems.com/faq/, https://support.reallysimplesystems.com/won-lost-pipeline-opportunities/, https://support.reallysimplesystems.com/sales-weightings-probabilities/, https://crm.spotler.help/hc/en-gb/articles/24314867003922-Integration-API-V4

Verification: Pending vendor verification

Won and lost are readable, but only as a by-product of other fields. The vendor defines a won opportunity as one at 100 percent probability and a lost one at 0 percent, and two shipped fields exist for the aftermath - Loss Reason, described as the reason if the opportunity was lost, and Win/Loss Report, described as space to describe the outcome of the deal after it is won or lost. The sales stage dropdown also commonly carries Won as a value, and the vendor's automation example fires when "an Opportunity is updated and the status changed to 'Won'". Nothing documented is an outcome attribute in its own right. This is scored where the unreachable field list cannot change the answer: whether or not a dedicated won flag also exists, the outcome is recorded and readable, so the feature is met at least in part.

Source: https://support.reallysimplesystems.com/faq/, https://crm.spotler.help/hc/en-gb/articles/23789453795474-Opportunities, https://support.reallysimplesystems.com/crm-automations/, https://support.reallysimplesystems.com/won-lost-pipeline-opportunities/

Verification: Verified

The opportunity carries a monetary value shipped by the vendor. Opportunity Lines hold a product, a quantity and a unit price, and the vendor documents Opportunity.Value as "the total Value of the Opportunity, calculated as the sum of Quantity x Unit Value", with Opportunity.WeightedValue multiplying that by the probability. Both are available as report fields and drive the sales forecast. The account's currency is set once in Company Settings and applies throughout.

Source: https://crm.spotler.help/hc/en-gb/articles/23651969895314-What-is-the-Reports-terminology-of-Special-Fields, https://support.reallysimplesystems.com/crm-opportunity-management/, https://crm.spotler.help/hc/en-gb/articles/23654131522194-Forecast

Verification: Verified

Opportunity Lines are a shipped child record on the opportunity, each holding a product, a quantity and a unit price, with the product itself drawn from a dropdown list administrators maintain. The API exposes them as their own object, opportunity_lines, and returns id, opportunityid, product, quantity and unitprice. A free-text Description field and a Next Step field sit alongside them on the opportunity.

Source: https://crm.spotler.help/hc/en-gb/articles/24314867003922-Integration-API-V4, https://support.reallysimplesystems.com/crm-opportunity-management/, https://support.reallysimplesystems.com/dropdown-lists/

Verification: Verified

Close Date ships on the opportunity and the vendor documents it as the date the opportunity is expected to close. It is the default date the sales forecast phases by, so revenue is placed in a period from it.

Source: https://crm.spotler.help/hc/en-gb/articles/23789453795474-Opportunities, https://support.reallysimplesystems.com/crm-opportunity-management/, https://support.reallysimplesystems.com/sales-forecasting-reports/

Verification: Verified

One date field is documented on the opportunity and it is the expected one. Both vendor descriptions of the opportunity form name a single Close Date, described as the expected or projected completion date, and the forecast report phases by it. What the field holds once the opportunity settles is not stated anywhere: no vendor article says the platform stamps it at close, and none instructs the user to overwrite it with the date the sale actually ended. The date is recoverable in a roundabout way, because Opportunity History records every change to the Close Date, Status, Probability, Forecast Status and Value with the user and the time, and history is a reportable data source. That is a change log, not a close date on the record, and the spec requires establishing what the one field holds after close, which the documentation does not do.

Source: https://crm.spotler.help/hc/en-gb/articles/23789453795474-Opportunities, https://support.reallysimplesystems.com/crm-opportunity-management/, https://support.reallysimplesystems.com/opportunity-history/, https://support.reallysimplesystems.com/sales-forecasting-reports/

Searched: Searched both vendor sites for a closed date, date won, date settled or actual close date on the opportunity, and read the sales dashboard article describing the Closed this Month column without finding a statement of which date drives it. The opportunity field list at GET /datadictionary/opportunities is behind authentication.

Verification: Pending vendor verification

Ownership is carried by the account, not by the opportunity. Account Owner is a mandatory field on the company account, documented as "the person in your organisation responsible for managing that account", and it is the field user permission levels are built on. Neither vendor description of the opportunity form names an owner or assigned user, and the vendor's documented route to put a user reference on an opportunity form is a custom field pointed at the Users or LiveUsers derived table. Forecast reports can subtotal by User.Initials, which reaches the opportunity through the account.

Source: https://crm.spotler.help/hc/en-gb/articles/23503781646866-Accounts, https://crm.spotler.help/hc/en-gb/articles/25164397378962-Why-can-t-I-change-some-fields, https://crm.spotler.help/hc/en-gb/articles/24564459873810-How-to-use-derived-tables, https://support.reallysimplesystems.com/sales-forecasting-reports/

Verification: Verified

The opportunity is created from the company account and belongs to it. No contact link is documented on the opportunity form: the vendor's own instruction is that "whilst an Opportunity or Task is held at the Account level you can add a Custom Field to the form to link it to a particular Contact within the Account", built as a text custom field pointed at the ContactName derived table, which then makes the contact reportable. So a link to the person exists, but the buyer creates it.

Source: https://crm.spotler.help/hc/en-gb/articles/24564459873810-How-to-use-derived-tables, https://support.reallysimplesystems.com/adding-contacts/, https://crm.spotler.help/hc/en-gb/articles/23789453795474-Opportunities

Verification: Verified

Closing an opportunity changes its probability and status and nothing else. Records leave the system only when a user deletes them, and even then they go to a Recycle Bin an administrator can restore from. Closed opportunities stay reportable: opportunities are a listing report data source carrying Status, Loss Reason and the Win/Loss Report, the sales dashboard shows a Closed this Month column, and Opportunity History keeps the change record for every settled opportunity.

Source: https://support.reallysimplesystems.com/recycle-bin/, https://support.reallysimplesystems.com/listing-report-writer/, https://support.reallysimplesystems.com/won-lost-pipeline-opportunities/, https://support.reallysimplesystems.com/opportunity-history/

Verification: Verified

Loss Reason ships on the opportunity and is driven by the LossReason custom dropdown list, so the values are a defined set administrators control and reorder rather than free text. Opportunities are a listing report data source, so the field can be reported and filtered on, and on the Enterprise plan reports can summarize matching values into one line and custom charts can plot the field. A separate free-text Win/Loss Report field sits alongside it for narrative.

Source: https://crm.spotler.help/hc/en-gb/articles/23789453795474-Opportunities, https://support.reallysimplesystems.com/dropdown-lists/, https://support.reallysimplesystems.com/listing-report-writer/, https://support.reallysimplesystems.com/advanced-crm-reporting/

Verification: Verified

A real mailbox connection exists but it only fills the CRM. With Automatic MailSync the product "will look to find and connect automatically to your mailbox, then using the connection it will read from your inbox and sent box and process the emails into your CRM", covering Outlook, Google Mail and most other clients, though the vendor says it is unsuitable for free mailboxes. Manual MailSync is the alternative and is a hosted CRM mailbox fed by carbon copies, forwarding rules and blind carbon copies, which is a person doing the work by hand. Nothing runs the other way: there is no compose window in the CRM, and sending to a contact means clicking their email address to open the user's own mail client, with the CRM only adding a Bcc to itself.

Source: https://support.reallysimplesystems.com/email-synchronisation/, https://support.reallysimplesystems.com/sending-individual-email/, https://crm.spotler.help/hc/en-gb/articles/23605856619282-How-to-send-an-email-to-a-individual-contact

Verification: Verified

One direction only, and only to Google. The vendor documents pushing CRM Tasks to Google Calendar: the user picks Google as the Calendar Type in user settings, then a calendar icon beside a saved task opens a form that adds that task to Google Calendar as an event. Nothing is documented coming back the other way, and the CRM's own calendar article describes an internal view of tasks, opportunities and activities with no external calendar connection at all. No Outlook or Microsoft 365 calendar sync appears anywhere in vendor documentation. Google Contacts sync, by contrast, is documented as running through Zapier.

Source: https://crm.spotler.help/hc/en-gb/articles/23740629293586-How-to-sync-Google-Calendar-items-to-tasks, https://support.reallysimplesystems.com/google-contacts-crm-sync/, https://crm.spotler.help/hc/en-gb/articles/23627910309906-Calendar, https://crm.spotler.help/hc/en-gb/articles/24465740716050-Integrations

Verification: Verified

Tasks are the schedulable object and they carry a type the buyer defines. A task is created with a date picker and dropdown-driven fields, can be given a time by unchecking the all-day box, can be assigned to another user, and can repeat. Task Type and Task Status are both standard custom dropdown lists administrators add values to and reorder, and the vendor tells buyers to "change the dropdown options to suit your business needs". Tasks appear on the CRM calendar, and completing one writes it to the account's Activities.

Source: https://crm.spotler.help/hc/en-gb/articles/23607819310354-Tasks, https://support.reallysimplesystems.com/managing-tasks/, https://support.reallysimplesystems.com/dropdown-lists/, https://crm.spotler.help/hc/en-gb/articles/23627910309906-Calendar

Verification: Verified

Only one of the three is native. Forecasting is strong: a dedicated Sales Forecast report writer phases opportunities by close date across months, quarters, half-years or years and shows both unweighted values, quantity times unit price, and weighted values, quantity times unit price times probability. The other two are not expressible. The report builder produces listing reports with fields, criteria and sort levels, and its only arithmetic is subtotaling and a Summarise option that, in the vendor's words, "will add the values together into one line where values match" - sums and counts, with no percentage, ratio or rate anywhere in the documentation, so a win rate over closed opportunities cannot be built. Stage conversion is absent for the same reason plus a second one: the Sales Funnel widget shows "how many outstanding opportunities you have and their value in the different stages of your sales cycle", which is a distribution by stage, and although Opportunity History stores every status change with its date, nothing in the builder expresses the proportion moving from one stage to the next.

Source: https://support.reallysimplesystems.com/sales-forecasting-reports/, https://crm.spotler.help/hc/en-gb/articles/23654131522194-Forecast, https://support.reallysimplesystems.com/listing-report-writer/, https://support.reallysimplesystems.com/advanced-crm-reporting/, https://support.reallysimplesystems.com/won-lost-pipeline-opportunities/, https://support.reallysimplesystems.com/creating-report-widgets/

Verification: Verified