> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Turn a verified meeting into a CRM update

> Extract reviewed contact, deal, decision, objection, and next-step fields from a meeting without automatically writing uncertain data.

The safest meeting-to-CRM workflow creates a proposed record beside the transcript. A person reviews it, resolves duplicates, and decides which fields belong in the CRM.

```mermaid theme={"system"}
flowchart TD
    A["verified transcript"] --> B["proposed CRM fields"]
    B --> C["duplicate and policy check"]
    C --> D["human approval"]
    D --> E["CRM update"]
```

## Define the schema first

| Field | Extraction rule |
| - | - |
| Contact and company | Use stated identity or existing CRM record; do not infer from appearance or voice |
| Stage | Update only when the meeting contains an accepted stage-changing event |
| Problem and use case | Summarize the participant's stated need |
| Objections and risks | Preserve material nuance; avoid sentiment scoring |
| Next step | Require an explicit action; retain unknown owner or date |
| Commercial terms | Copy exact approved terms only; mark proposals as proposals |

## Step by step

**1. Verify the meeting**

Confirm the correct meeting, participants, time range, and transcript coverage. Fix important names and speaker labels before extracting fields.

**2. Load the target schema**

List the CRM fields that are allowed to change and who may approve them. Exclude internal-only notes and fields the meeting cannot support.

**3. Extract a proposed record**

Create a table with current value if known, proposed value, source moment, and confidence. Leave unsupported fields blank.

**4. Distinguish proposal from acceptance**

A quoted price, suggested timeline, or possible next step is not an agreement. Preserve the exact evidence state.

**5. Check duplicates and later context**

Search the CRM for the contact, company, and open deal. Check for a later email or meeting that changed the outcome.

**6. Review the delta**

Approve each changed field, especially stage, owner, amount, close date, and next action. Remove private transcript detail.

**7. Write after approval**

Apply the approved changes through the CRM UI or connection, then read back the saved record. Keep the extraction artifact for traceability if policy allows.

## Extraction prompt

```markdown theme={"system"}
Create a proposed CRM update from this verified meeting transcript.

For each allowed field provide:
- current value, if supplied
- proposed value
- source transcript time
- evidence state: stated, accepted, proposed, inferred, or unknown
- whether human confirmation is required

Never infer identity, deal stage, amount, owner, close date, or sentiment.
Keep proposals separate from accepted decisions.
Return a draft only; do not update the CRM.
```

> [!NOTE]
>
> Use [meeting follow-up](https://docs.screenpipe.com/meeting-follow-up.md) first when transcript quality or action items still need review.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.