Solve CRM

View saved version →

---
name: solve-skill
description: >
  Using Solve CRM MCP/Connector searches for records (contacts, companies, project blogs, tickets) in Solve CRM based on complex user-defined criteria. Builds the following reports: activities, deals, follow-ups, next actions, time tracking. Loads, adds, updates and deletes records and activities. You **MUST** use this skill when asked to find records, build reports, change records or activities in Solve CRM or when user simply mentions Solve. Uses Solve CRM MCP tools to perform all these tasks.
---

# Solve CRM MCP Skill

This skill ensures you use the Solve CRM MCP tools correctly every time. Violations of the rules
below will cause API errors, data corruption, or wrong results for the user.

## Invoke This Skill When

- User mentions Solve, Solve360, or Solve CRM
- User asks to find records based on criteria possibly consisting of multiple conditions with "and" and "or" between them
- User asks to create, modify or delete contacts/companies/project blogs/tickets or activities. Activity types include task, tasklist, note, followup, call/interaction, photolist, google doc, website, opportunity/deal, time record, comment, linked emails, xerowidget and zendeskwidget
- User asks to find, create, modify or delete something other than contacts, companies or project blogs because user may rename "project blog" to something specific to their business
- User asks to show activities, deals, follow-ups, next actions or time tracking based on some filtering criteria
- User asks to show fields or category tags for a type of records or activities

## Critical Rules
- **NEVER** guess anything
- **NEVER** make assumptions
- **NEVER** say anything you are not sure about
- **ALWAYS** read the documentation if available for any tool you are going to use before using it
- **ALWAYS** follow all instructions in the documentation for any tool you use
- **ALWAYS** follow all instructions in this SKILL.md
Violating any of these rules will cause a bad user experience and is **STRICTLY PROHIBITED**.

---

## Step 1: Get User Timezone (Required for Most Tools)

Many tools require `user_timezone` as an IANA timezone string (e.g. `"America/Edmonton"`), eg when creating or updating records or activities with date/time fields, when searching for records with date/time criteria, or when building activities, deals, follow-ups or next actions reports. Always get the user's timezone before calling any of those tools.

- If you already know the timezone from earlier in the conversation, use it.
- If not, call `solve360_account` first. It returns `overridenzoneinfo` — use that value.
- If `solve360_account` doesn't return a timezone, ask the user directly before proceeding.

Never guess or assume a timezone. Passing the wrong timezone produces incorrect date formatting.

---

## Step 2: Check for Renamed Record Types

Solve CRM lets organizations rename "project blog" to something else (e.g. "Project", "Case", "Room").
If the user asks about something that's **not** a contact, company, or ticket, call
`solve360_account` first to check if blogs have been renamed (`bloglabel` field). Use that label
instead of "blog" or "project blog" when communicating with the user.

---

## Rule for getting information about the user currently logged in Solve CRM

When you need to get the ID of the user currently logged in Solve CRM, use `solve360_account` tool. It returns `userid` — use that value. ID lets you retrieve the information about the user's account using `solve360_ownership`.

---

## Rules for Searching (solve360_search)

Before constructing any search, you **MUST** read:
- `solve360_docs("search_args")` — full argument reference for solve360_search
- `solve360_docs("ucf")` — the only allowed formats for the `ucf` argument

**Never construct a `ucf` argument without reading `solve360_docs("ucf")` first.** The ucf format is strict and non-obvious — guessing will produce invalid queries.

**Never run multiple solve360_search calls*

Preview of the first 4,000 characters. Read full instructions →