Skills crm
Contact memory and interaction log — remembers callers across calls, logs every conversation with outcome and personal context
install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/batthis/amber-voice-assistant/amber-skills/crm" ~/.claude/skills/openclaw-skills-crm && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/batthis/amber-voice-assistant/amber-skills/crm" ~/.openclaw/skills/openclaw-skills-crm && rm -rf "$T"
manifest:
skills/batthis/amber-voice-assistant/amber-skills/crm/SKILL.mdsource content
CRM Skill — Contact Memory for Voice Calls
Remembers callers across calls and logs every conversation.
How It Works
On Every Inbound Call
- Lookup — Call
withcrm
using the caller's phone number (from Twilio caller ID).lookup_contact - If known — Greet by name and use
to personalize (ask about their dog, remember their preference, etc.)context_notes - If unknown — Proceed normally, listen for their name.
During the Call
When someone shares their name, email, company, or any personal detail, silently upsert it via
crm.upsert_contact. Don't announce this.
At End of Call
- Log the interaction:
with summary + outcomelog_interaction - Update context_notes with any new personal details learned, synthesizing with what was known before
On Outbound Calls
Same exact flow: lookup at start, upsert + log_interaction at end.
API Reference
| Action | Purpose |
|---|---|
| Fetch contact + last 5 interactions + context_notes. Returns null if not found. |
| Create or update a contact by phone. Only provided fields are updated. |
| Log a call: summary, outcome, details. Auto-creates contact if needed. |
| Get past interactions for a contact (sorted newest-first). |
| Search by name, email, company, notes. |
| Add/remove tags (e.g. "vip", "callback_later"). |
Privacy
- Event details stay private. Like the calendar skill, never disclose event details to callers.
- CRM context is personal. The
field is for Amber's internal memory, not for sharing call transcripts. Use it to inform conversation, not to recite it.context_notes - PII storage. Phone, name, email, company, context_notes are stored locally in SQLite. No network transmission, no external CRM by default.
Security
- Synchronous SQLite (better-sqlite3) with parameterized queries — no SQL injection surface
- Private number detection — calls from anonymous/blocked numbers are skipped entirely
- Input validation at three levels: schema patterns, handler validation, database constraints
- Database file created with mode 0600 (owner read/write only)
Examples
Greeting a known caller:
Amber: "Hi Sarah, good to hear from you again. How's Max doing?" [context_notes remembered: "Has a Golden Retriever named Max. Prefers afternoon calls."]
Capturing new info silently:
Caller: "By the way, I got married last month!" Amber: [silently calls upsert_contact + updates context_notes with "Recently married"] Amber (aloud): "That's wonderful! Congrats!"
End-of-call log:
Amber: [calls log_interaction: summary="Called to reschedule Friday appointment", outcome="appointment_booked"] Amber: [calls upsert_contact with context_notes: "Prefers afternoon calls. Recently married. Reschedules frequently but always shows up."]