---
title: Rapport — AI operating guide
version: 1.6.0
updated: 2026-11-15
canonical_url: https://rapport.instructedintelligence.com/mcp/prompt.md
version_url: https://rapport.instructedintelligence.com/mcp/prompt/version
---

# Rapport — AI operating guide

This is how Rapport works for any workspace. Your workspace's own stages, signals, channels and tool list are in `get_guide`, generated from its definition: read that too.

Rapport's version is also this guide's version. It appears in the connect-time instructions, on every tool result (`_meta.rapport.version`) and at `GET /mcp/prompt/version`; when it rises, read this again. What changed is in the changelog.

Rapport: a CRM whose shape this organisation's own AI defines. Not outreach (that is Reticle).

## The shape

everything is a Record of an OBJECT TYPE the tenant declared — organisation, person, deal, interaction, task by default, but the tenant may have renamed, extended or replaced them. Each type has tenant-defined FIELDS; a pipeline type has a FUNNEL of stages; RELATIONSHIP TYPES link records (a person works_at an organisation); VIEWS are the tenant's dashboards.

START with describe_process. It returns THIS tenant's types, fields, funnels, relationship types and views. Do not assume Salesforce's shape — read the definition, then work in it. The tool list itself changes with the definition: there is an add_<type> tool per object type with that type's fields.

## Shaping the process

define_process replaces the whole definition; update_process evolves it (upsert types, fields, funnels, stages, relationship types, views; remove by key). Keys are lower snake_case. A funnel needs at least one terminal stage; mark the winning one won. This is how the organisation's AI makes the CRM fit how they actually work — use it when the shape is wrong, not as a workaround for a record that does not fit.

## Records

create_record / add_<type> / add_contact, get_record, list_records (filter by type, stage, owner, name search, field equality, rel_to, open/closed), update_record (fields merge; null clears), link / unlink for relationships, advance to move a pipeline record. A TERMINAL stage REQUIRES a reason, and a closed record does not move again — the reason is what the pipeline exists to collect.

## People

every record of a person type needs lawful_basis (legitimate_interest, consent or contract). That is a data-protection requirement, not a formality: do not invent one — ask, or use legitimate_interest only where a business relationship genuinely exists.

## Tenants

a caller may belong to several. list_tenants shows them; every tool accepts an optional tenant argument to act in one other than the default.

## Flows

follow-ups the organisation designs in words. define_flow (a trigger, steps with waits, exits), then rehearse_flow and SHOW the person what it would send and to whom; only they turn it on (enable_flow, when they say so). A live flow cannot be changed: pause_flow first. list_enrolments answers "why did they get that email?".

## From reticle

graduate_prospect turns a won Reticle prospect into an organisation + person + open deal here, with source reticle:<prospect_id>. Rapport never calls back into Reticle.

