Solve CRM

Contacts, Companies, Project Blogs and Tickets are the record types, and the API states that its methods and parameters are the same for all four. The opportunity is not one of them. It is an activity, segment name `opportunity` and type id 32, and the vendor's own walkthrough describes the step as placing the activity "Add a revenue opportunity" on a contact, project blog or company page. Every activity is created against a parent and the API states that the parent element "is required", so an opportunity cannot exist on its own. The documented activity hierarchies allow only a comment beneath a deal, so a task or a follow-up cannot be attached to an opportunity, and the work and the sale meet only through the record they share.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

The deal activity carries `stage` as an integer from 0 to 100, alongside a separate `probability` integer from 0 to 100, and the vendor's MCP documentation gives "Update deal stage to 60%" as an example instruction. Position is therefore ordered and held on the record rather than on a view, but no vendor documentation describes a defined set of named stages, and no stage list or pipeline reference appears among the enumerated deal fields.

Source: https://solve360.com/api/records/, https://solve360.com/api/mcp-server-for-ai-agents/

Verification: Verified

The API's activity definition table enumerates what a deal carries, and `status` is one of those attributes, with the documented values Discussion, Pending, Won, Lost and On-hold. Whether an opportunity is still running is therefore readable from the opportunity itself, and the reporting endpoint /report/opportunities/ filters on those same five values.

Source: https://solve360.com/api/records/, https://solve360.com/api/activity-reports/

Verification: Verified

Won and Lost are two of the five values of the same `status` attribute that says whether the opportunity is still running, so the outcome is answered as a by-product of the open-or-closed question rather than by a field whose job it is. No separate outcome attribute appears among the enumerated deal fields.

Source: https://solve360.com/api/records/

Verification: Verified

The deal ships `valueunit` as a decimal together with `valuecurrency` chosen from twenty-three currency codes, plus `valueinterval` for fixed price or a rate per hour, day, week, month, quarter or year and `valueduration` for how many of those units, so the vendor treats the figure as money rather than as a plain number.

Source: https://solve360.com/api/records/

Verification: Verified

The deal ships `description` as free text and nothing else for what is being sold; no product or line-item facility appears among the enumerated fields or anywhere in vendor documentation. An administrator can add custom fields to the opportunity activity, and the vendor's customization walkthrough uses a Product custom field as its worked example, which it says appears in the opportunities report in editable form.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/feature-walkthroughs/customizing-forms-and-fields/

Verification: Verified

The deal ships `closingdate` as a date field. The opportunities reporting endpoint filters on it with forward-looking options of now, the next seven days, the next thirty days or no date, and the vendor's walkthrough says the interface report can be filtered by closing date, so the shipped date is the one the deal is expected to settle on.

Source: https://solve360.com/api/records/, https://solve360.com/api/activity-reports/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

`closingdate` is the only date among the enumerated deal fields, and no vendor documentation states what that field holds once a deal is marked Won or Lost, or that Solve stamps a settled date at that point. The vendor's walkthrough says opportunity details are edited by double-clicking them in the opportunities report, so a person could put the date a sale ended into the same field, but the vendor does not document that as its purpose.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/get-started/activity-reporting/

Searched: Read the API activity definition table for the deal, the activity reports reference, the vendor's activity reporting walkthrough and the dashboard feature page; no vendor text describes a second date field or a date recorded when a deal closes.

Verification: Pending vendor verification

The deal ships `responsible`, a group or user id, and it is not a creation stamp: the vendor's opportunities report groups opportunities by who is managing them, the reporting endpoint filters by that user or group id, and the report can be filtered by person responsible.

Source: https://solve360.com/api/records/, https://solve360.com/api/activity-reports/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

An opportunity is created against a parent record, the parent element is required, and the vendor describes the step as placing the revenue opportunity activity on a contact, project blog or company page, with the documented activity hierarchy running Contact then Deal. Where the parent is a contact, the link to the person is the opportunity's own anchor and is shipped rather than built.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

Closing a deal sets its status rather than removing it, and closed deals stay reportable. The opportunities reporting endpoint takes won and lost as status filters, and the vendor's walkthrough says the opportunities report is filtered by person responsible, closing date or status of the opportunity, naming won, lost or in progress.

Source: https://solve360.com/api/activity-reports/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

No lost-reason field appears among the enumerated deal fields, and the vendor's guidance is free text: it says the Note field is a good place to document why the opportunity was won or lost. An administrator can add custom fields to the opportunity activity, and the vendor states that such fields show up in the opportunities report in editable form, but no vendor documentation says the opportunities report or search can group, filter or count opportunities by a custom field or by note text. The report's documented filters are person responsible, closing date and status.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/get-started/activity-reporting/, https://crm.solve360.com/help/feature-walkthroughs/customizing-forms-and-fields/

Searched: Read the API activity definition table, the activity reports reference, the activity reporting walkthrough, the customizing forms and fields walkthrough and the search feature page; none states whether a custom field on an opportunity can be counted or grouped in a report.

Verification: Pending vendor verification

Solve links to the team's individual Google Workspace mailboxes, and the vendor's options are to link all emails automatically or to fine-tune which ones with Gmail labels, then choose who to share them with, so mail sent and received in Gmail reaches the matching records without anyone forwarding it. The API carries a `linkedemails` activity holding the fields, keywords and exceptions that govern what links. Outbound, the vendor lists email sending from Solve through scheduled activities, webmail and marketing services, names the Webmail feature as one of the things the Google connection is needed for, and offers rich-format templates that merge record data and go out through the user's Google account. The connection is Google only: no vendor documentation describes a Microsoft mailbox connection, although Microsoft sign-in is supported.

Source: https://solve360.com/features/google/google-email-gmail-integration/, https://solve360.com/google-oauth/, https://crm.solve360.com/help/, https://solve360.com/api/records/

Verification: Verified

The vendor describes the Google connection as intelligently syncing event data between Solve and Google Calendar. Outbound it is explicit: events created or modified directly in Solve automatically sync into a Google calendar named Solve360 in near real time. Inbound, each user selects which of the Google calendars they can see are linked into Solve, and the vendor states that Solve automatically organizes Google events from across the domain into a single view for each contact, job, property or case. Solve holds events as objects of its own - its calendar report covers events and tasks with a due date, and events are linked to contacts, projects or companies. The connection is Google only.

Source: https://crm.solve360.com/help/integration-walkthroughs/google-synchronization/, https://solve360.com/features/google/google-calendar-scheduling-integration/, https://solve360.com/features/google/google-calendar-scheduling-setup/, https://crm.solve360.com/help/get-started/activity-reporting/

Verification: Verified

The activity types are a fixed vendor-defined set, enumerated in the API with their own type ids: attached file, comment, deal, file, follow-up, Google doc, interaction, linked emails, note, photo, photo list, task, task list, time record and website. No vendor documentation describes an account defining a new activity type. The shipped set covers the three that matter: a task carries a title, details, an assignee, a due date and a priority, a follow-up carries details, an assignee and a due date, an interaction records a call with the date it occurred and its duration, and calendar events are scheduled and linked to a contact, project or company. Administrators can add custom fields to activities, but the type itself is not one of them.

Source: https://solve360.com/api/records/, https://crm.solve360.com/help/get-started/activity-reporting/, https://crm.solve360.com/help/feature-walkthroughs/customizing-forms-and-fields/

Verification: Verified

The vendor enumerates its reports as next actions assigned to, calendar events with, follow-ups assigned to, opportunities managed by, activity changes for, time tracking for, and actions logged for. The opportunities report groups deals by who is managing them and by current status and filters by person responsible, closing date and status, which the vendor says tallies them into a pipeline that helps forecast future revenue. That is at most the forecast. There is no win and loss rate, because grouping by status yields counts rather than a stated proportion. There is no stage-to-stage conversion rate, because the deal holds a stage percentage rather than a defined stage sequence and no stage-transition history is documented. For anything beyond this the vendor points the buyer at its Google Sheets add-on, saying Solve reports live inside Google Sheets and naming pipeline and funnel sales reports as what is built there, which is reporting outside the product.

Source: https://crm.solve360.com/help/get-started/activity-reporting/, https://solve360.com/features/dashboard/, https://solve360.com/api/activity-reports/, https://solve360.com/features/google/google-sheets-integration/

Verification: Verified