crmy

CRMy — Operational Customer Context For Agents

You have access to CRMy through the crmy tool. CRMy is not just a CRM table surface; it is the operational state layer that lets agents remember customer context, work with typed revenue objects, and leave audit-safe state behind.

Every call uses:

crmy({ action: "<action>", params: { ... } })

Use CRMy to:

• Get a one-call briefing before acting on a customer record.
• Search and update contacts, accounts, opportunities, use cases, activities, context entries, assignments, and HITL requests.
• Ingest messy customer context as Sources, then review Signals before they become Memory.
• Route work to humans or agents through assignments and approval requests.
• Check audit events and operations health when trust matters.

---

Default Agent Workflow

1. Identify yourself

Start substantive work with:

crmy({ action: "actor.whoami" })

This tells you which actor will be attributed on writes.

2. Resolve the customer record

Search before creating. Prefer exact records over guessed names.

crmy({ action: "search", params: { q: "Acme", limit: 10 } })
crmy({ action: "contact.search", params: { q: "Sarah Chen", limit: 10 } })
crmy({ action: "account.search", params: { q: "Acme", limit: 10 } })

3. Brief and check Action Context before acting

Before outreach, deal changes, handoffs, or context writes, call briefing.get for customer context and action_context.get when the work may affect a customer, record, system, or commitment.

crmy({
  action: "briefing.get",
  params: {
    subject_type: "contact",
    subject_id: "<uuid>",
    context_radius: "adjacent",
    token_budget: 4000,
    format: "json"
  }
})

crmy({
  action: "action_context.get",
  params: {
    subject_type: "contact",
    subject_id: "<uuid>",
    context_radius: "adjacent",
    proposed_action: { action_type: "customer_outreach" }
  }
})

Use context_radius: "account_wide" for deal reviews, renewal risk, and handoffs where related account/contact context matters. After sends, approvals, writebacks, assignments, workflows, or sequences, call context.lineage and inspect lineage.outcomes before dependent follow-up. If Action Context returns human_unblock.required, call action_context.unblock so the approval or assignment preserves the packet, proof, and handoff snapshot.