Initial skills documentation — 25 categories, all SKILL.md + references + scripts
This commit is contained in:
@@ -0,0 +1,69 @@
|
||||
# Session Highlights — 2026-07-07b (afternoon)
|
||||
|
||||
## Debt Recovery Workflow — Key Additions
|
||||
|
||||
### Payment & Billing
|
||||
- Every debtor touchpoint includes a **Stripe ACH payment link** — email, certified letter, text-to-pay, and phone-in payment portal
|
||||
- Xero can be added later for accounting (Stripe integration is seamless)
|
||||
- Debtors can pay in installments via Stripe
|
||||
|
||||
### Fee Calculator
|
||||
- New mockup: `dre-fee-calculator.html` — live 4-tier side-by-side comparison
|
||||
- Input any amount, see what client receives and DRE fee at each tier immediately
|
||||
- Cards color-coded: green (Tier 1) → blue → amber → red (Tier 4)
|
||||
- One-time build for the site, no ongoing API costs
|
||||
|
||||
### Case Aging Dashboard
|
||||
- New mockup: `dre-case-aging.html` — monitors stalled cases
|
||||
- Color-coded: green (on track), amber (approaching limit), red (past target)
|
||||
- Targets: Tier 1 = 5 days, Tier 2 = 7 days, Tier 3 = 10 days
|
||||
- Stalled cases show alert banner with escalation action link
|
||||
|
||||
### Agent D.R.E Chatbot — Authentication & Messaging
|
||||
|
||||
**Three states:**
|
||||
1. **Lead capture** (non-logged-in): Name, Company, Email*, Phone. Required before Q&A.
|
||||
2. **Logged-in greeting**: "Welcome back, {Company}! Your claim against {Debtor} is in {Tier}."
|
||||
3. **Conversation**: FAQ + message-to-team form.
|
||||
4. **PII verification trigger**: If asked for case-specific details (claim number, case details), require claim number from welcome email to verify before sharing.
|
||||
|
||||
**Message team form:** Subject dropdown (Question about claim, New debtor info, Payment received, Update contact, Complaint, Other) + free text + Send/Cancel. Logs to case file.
|
||||
|
||||
**Knowledge isolation rules enforced:** Public vs private (scoring methodology, skip tracing, weakness criteria, approval workflow, partner names, strategy docs all PRIVATE).
|
||||
|
||||
### AI Re-Analysis on Document Upload
|
||||
- When client uploads new document, AI re-scores the claim automatically
|
||||
- Score delta tracked in timeline: "Score: 78 → 82 ⬆"
|
||||
- Logged in change history as System event with reason "New docs uploaded"
|
||||
- Re-analysis is per-claim, not per-client
|
||||
|
||||
### Two-Binder System Finalized
|
||||
- DRE Internal: Full record with AI analysis, internal notes, all docs
|
||||
- Client Package: Claim summary, LPOA, settlement, fee statement — NO AI analysis or research
|
||||
- Archive: `DRE-YYYY-NNNN_evidence.zip` with original uploads
|
||||
- Client can download from portal after case close
|
||||
|
||||
### Professional Touches Added
|
||||
- Post-closure survey (auto-sent)
|
||||
- Referral tracking (5% off next claim)
|
||||
- Settlement agreement templates in DocuSeal
|
||||
- Automated compliance checkers before each communication
|
||||
- One-click case notes (every action auto-logs to timeline)
|
||||
- Batch small claims under $2K
|
||||
- SMS notifications to clients (Twilio slot)
|
||||
- Text-to-pay for debtors
|
||||
|
||||
### CRM & Infrastructure
|
||||
- Anita's Gmail app password flow: instructions sent, waiting for her to email her Gmail app password
|
||||
- Tony reminder sent for Telegram bot setup
|
||||
- Bounce fix: re-sent Cartagena itinerary to correct address (anitabrownwrites@gmail.com)
|
||||
|
||||
### Notary Research (ongoing)
|
||||
- Proof.com Premium plan needed for API — estimate ~$90-150/mo
|
||||
- OneNotary alternative has REST API, likely lower per-doc pricing
|
||||
- Subagent dispatched to research OneNotary API docs and Proof Premium pricing
|
||||
|
||||
### API Keys Dashboard
|
||||
- New table in capabilities page: vendor, masked key, usage, status
|
||||
- 7 keys tracked: Firecrawl, ScrapingAnt, Cloudflare, admin-ai, SMTP, DocuSeal, Turnstile
|
||||
- Hover tooltips with credit limits and service descriptions
|
||||
Reference in New Issue
Block a user