# Turn a client chat into CRM updates

> Reads a WhatsApp, iMessage, Slack or email thread and proposes stage, next step, notes, tasks and contacts as a before and after table.

Canonical: https://www.altaratech.com/store/skills/chat-to-crm-update
Shelf: Skill · Job: Keep the CRM current
SKILL.md: https://www.altaratech.com/store/skills/chat-to-crm-update/SKILL.md
Zip for Claude: https://www.altaratech.com/store/skills/chat-to-crm-update.zip
Install: npx skills add https://www.altaratech.com --skill chat-to-crm-update -g -a claude-code (or -a codex, -a cursor)

---

---
name: chat-to-crm-update
description: >-
  Use this skill when a client conversation on WhatsApp Business, iMessage, Slack or email holds
  news the CRM does not have. Paste or export the chat; it proposes the stage, the next step with
  a date, notes, tasks and new contacts, shows them as a before and after table with the line
  that supports each change, and applies only what you approve.
license: CC-BY-4.0
metadata:
  author: ALTARA
  version: "1.0"
  homepage: https://www.altaratech.com/store/skills/chat-to-crm-update
---

# Turn a client chat into CRM updates

Deals move in chats long before anyone updates the CRM. This skill reads one client conversation, finds what changed (a decision, a date, a new person, a promise) and proposes the CRM updates, each with the message that supports it. You see a before and after table and approve line by line. It works the same with any CRM, and with no CRM at all: the table is then a checklist you apply by hand.

## Inputs

- **The conversation,** with dates and who said what. Any of: pasted text, a WhatsApp export (see "How to export your chat history" in WhatsApp Help), screenshots, an email thread, or a Slack thread the agent can read. For iMessage, paste the messages or share screenshots.
- **Which side is the seller:** the seller's name as it appears in the chat.
- **The CRM record:** with CRM access, find the deal by the contact's phone, email or company. Without it, ask the user to paste the current values: stage, amount, close date, next step, contacts.
- **The stages and what each one means,** so a move is justified by the chat and not by tone.
- **Today's date and time zone.**

## Steps

1. **Read only what is new.** Find the date of the last CRM note or activity on the record and work from the messages after it, so nothing is logged twice.
2. **Extract facts, with evidence.** For each, keep the timestamp, who said it and a short quote: decisions; dates and deadlines; quantities and amounts; commitments by the seller; commitments by the client; new people (name, role, contact details they shared themselves); objections and risks; documents asked for or sent. Resolve "next Thursday" against the date of the message, not today.
3. **Map facts to changes.**

   **Stage:** move it only when the chat meets the stage's rule. "Looks good" is not a signed order. If the rule is not met, keep the stage and say what is missing.

   **Next step:** one action, one owner, one date, ideally the date someone wrote in the chat.

   **Note:** three to six dated lines of facts. Leave out personal remarks that do not matter to the deal.

   **Tasks:** one per commitment the seller made, due when the seller said it would happen.

   **Contacts:** only people who appear in the chat, with only the details shared there. Never guess an email.

   **Amount and close date:** only when stated in the chat.

4. **Check against the record.** Flag conflicts (the chat says 40 units, the CRM says 25) and possible duplicates (a "new" contact who already exists under another spelling).
5. **Show the table.** Before, after, the evidence and a confidence for each line. Keep quotes in the language of the chat.
6. **Apply only approved lines.** Then read the record back and confirm what changed. Lines the user skips are dropped, not kept for later.

## Output

```
Deal: Vale Alto Construction · Fleet telematics pilot · owner: you
Chat: WhatsApp, 2026-11-12 to 2026-11-19 · 23 messages · you and Marco Lima (Procurement)
Last CRM update: 2026-11-11 · reading from 2026-11-12

| # | Field        | Before                 | After                                               | Evidence                                                       | Conf.  |
| 1 | Stage        | Proposal sent          | Negotiation                                         | 11-18 14:02 Marco: "scope is fine, we need 5% off to sign"     | high   |
| 2 | Next step    | "Follow up"            | Send revised proposal · you · Fri 2026-11-20        | 11-18 14:05 you: "I'll send the new version by Friday"         | high   |
| 3 | Task         | none                   | Confirm delivery schedule for 40 units · you · 11-23 | 11-19 09:12 Marco: "need delivery dates before the board"     | high   |
| 4 | New contact  | none                   | Paula Reis, Finance Director (no email shared)      | 11-19 09:15 Marco: "Paula from finance signs off"              | medium |
| 5 | Note         | none                   | 2026-11-18: scope accepted, 5% discount requested.  | 11-18 messages                                                 | high   |
|   |              |                        | Board meets 2026-11-26. Finance signs.              |                                                                |        |

Not changed: Amount stays $42,000 (discount not agreed). Close date stays 2026-11-30
(board date 11-26 supports it).
Conflict: CRM says 25 units, chat says 40 (11-17 16:40). Update the amount line?

Approve with the line numbers ("1, 2, 3, 5") or "all". Nothing has been written.
```

## Guardrails

- **Reads:** the conversation the user provides or points to, and the matching CRM record.
- **Writes:** only the approved lines, to the CRM record. Never to the chat.
- **Asks before:** every field change, new contact, task and note, and before reading any chat the user did not point to.
- MUST show the message behind every proposed change, with its timestamp.
- MUST resolve relative dates from the message's date, and show the resolved date.
- MUST keep the stage when the chat does not meet the stage's rule, and say why.
- NEVER send, reply or react in the client's chat.
- NEVER invent an email, a phone number, an amount or a date the chat does not contain.
- NEVER store the conversation beyond the task or copy it whole into the CRM; the note holds facts, not the transcript.

## Sources

- [How to export your chat history](https://faq.whatsapp.com/1180414079177245/?locale=en_US), WhatsApp Help Center.
- [WhatsApp Business Messaging Policy](https://whatsappbusiness.com/policy/), WhatsApp: the rules for any reply you send afterwards (read 2026-11-20).

Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store
