القائمة
Surfaces overdue follow-ups, prioritizes the call list, and recommends specific outreach actions for each stuck deal or contact.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Mandatory compliance gate before any outbound (email, SMS, blast). Verifies consent, opt-out status, CASL footer, send window, and daily cap.
Queue a cold outreach campaign to a segmented lead list via the cold_outreach_campaigns endpoint, with CASL compliance enforced before any send.
Generates the structured daily call sheet for Ezra — 6 prioritized categories, specific opening lines for each call, and a clear action order.
Domain literacy for MCA and alternative business funding. Reference glossary and clarifying-question guide for when operators use ambiguous terms.
Uses historical lender feedback data to recommend the best lenders for a specific deal profile and surfaces typical terms and decline patterns.
Pause cleanly at a decision boundary, surface the decision to Ezra via Telegram or dashboard chat, and wait for explicit confirmation before proceeding.
| name | follow-up-discipline |
| description | Surfaces overdue follow-ups, prioritizes the call list, and recommends specific outreach actions for each stuck deal or contact. |
| triggers | ["what's stuck","who needs a follow-up","queue today's calls","follow-up list","what's overdue","who haven't we heard from","stuck deals"] |
| tier | stable |
| disable_model_invocation | false |
Where these endpoints live: All
/api/...URLs below are routes on the OASIS Command Center dashboard (repo:CC90210/oasis-command-center, deployed at https://agent-dashboard-sigma-eight.vercel.app). They are NOT served by this repo's localscripts/api_server.py(which only exposes/health,/status,/sms/send,/webhook/jotform). Solara's bridge makes authenticatedfetchcalls into the dashboard's API surface, and the dashboard then writes to Supabase / queues threads / dispatches the 8 daemons in this repo.
Enforce consistent follow-up cadence. Nothing kills a deal faster than silence. This skill surfaces what's overdue, prioritizes it, and recommends the right channel for each contact.
GET /api/follow-up-tasks?status=open&assigned_to=solara
Also pull daily plan items:
GET /api/daily-plan-items?date=today&status=pending
Sort into four buckets:
| Bucket | Criteria | Action |
|---|---|---|
| Hot | Task overdue > 48h OR lender response waiting > 24h | Call today — no delay |
| Warm | Task due today | Outreach today — email or call |
| Missing info | Application stalled waiting on docs from merchant | Personal email + text |
| Monitor | Task due in 1–3 days | Flag, don't act yet |
For each overdue item, recommend the right channel based on contact history:
| Situation | Recommended Channel |
|---|---|
| Merchant hasn't responded in > 72h | Personal email (not drip) + text |
| Lender hasn't responded to submission | Email nudge to lender contact |
| Merchant promised docs, hasn't sent | Text + email with specific doc list |
| Offer received, merchant not responding | Call — offers expire |
| Deal stalled at "thinking about it" > 7 days | Schedule a call, use urgency framing |
Format for Ezra:
Follow-Up Queue — [Date]
HOT (call today)
1. [Merchant Name] — submitted to 3 lenders 72h ago, no response. Nudge all 3 lenders.
2. [Merchant Name] — offer from Funder X expires today. Call merchant NOW.
WARM (outreach today)
3. [Merchant Name] — bank statements requested 3 days ago. Text + email.
4. [Merchant Name] — follow-up after initial outreach. Email + personal note.
MISSING INFO
5. [Merchant Name] — waiting on voided check + 4th month statement.
Draft: "Hi [Name], just following up on the checklist from [date]..."
MONITOR (due in 1-3 days)
6. [Merchant Name] — shop-out queued for Thursday. No action yet.
When Ezra confirms an action was taken (call made, email sent), update the task:
PATCH /api/follow-up-tasks/[id]
{ "status": "actioned", "actioned_at": "[timestamp]", "outcome": "[brief note]" }
Create the next follow-up task immediately if the situation is still open:
POST /api/follow-up-tasks
{ "application_id": "[id]", "due_at": "[+48h]", "type": "follow_up", "notes": "[context]" }
| Event | SLA |
|---|---|
| New inbound lead | First contact < 5 minutes |
| Application submitted to lender | Follow-up lender at 48h |
| Offer received | Merchant contact within 2h |
| Missing docs requested | Follow-up if not received in 48h |
| "Thinking about it" stage | Max 7 days before call |