Enugula Estates · Ops Dashboard v2

Friday, August 28, 2026

9:00 AM ET · morning
Blue Slack ↗ · pruth@ email ↗ · stylish1@ email ↗ · 🆕 new · ⬆ escalated · ✓ done · Day chips age automatically. Every line linked.
SummaryJanine callDeadlinesDecisionsAttentionMoneyWatchlistOwnersBig issuesSmallerTeamIdeas

⏱ 60-second summary

  1. Stripe: $804.18 Stylish Sanctuary payout landed as expected; the $45 Citibank dispute (evidence due Oct 5) remains unread ~34.5h — still needs a reply. Source ↗
  2. The Airbnb Support message thread has ballooned to ~28-31 messages with no team reply — this is now the loudest unresolved case in the inbox. Source ↗
  3. New handling gap: Airbnb denied Eric Jackson reimbursement (CLSF-06050044) for missed 14-day notice — thread unread, no rebuttal filed. Source ↗
  4. Overnight ops ran clean: SOD/EOD checklist fully worked (check-ins, ECI/LCO, DOOR/Geokey, guest vetting), and the Kota 1143 wrong-unit guest was walked to the correct building successfully. Source ↗
  5. Automation and revenue are healthy: all pipelines ran green, August revenue $354,890 (80.2% occupancy), September pickup building (+$7,806 yesterday). Source ↗

🗒 Your notes for today 1 · from notes/<date>.md, matched against today’s traffic

Sam's review — check if it posted ↩️ Follow-up
Sam's review (the Airbnb I stayed at) — asked on Aug 21 to be reminded in about a week; check whether the review ever posted.
Owner — VishalStatus — no signal in this window — nothing in the digest references Sam's review or its posting status
August revenue
$354,890
▲ live · 24 bookings
August occupancy
80.2%
August · RevPAR $87
September revenue
$148,706
▲ live · 24 bookings
September occupancy
26.2%
September · RevPAR $38

💰 Money unread ≠ unhandled — team may be working cases in the extranet

—Stripe activity — steady, no change$804.18 payout
Stylish Sanctuary Stripe payout of $804.18 arrived as expected Aug 28. The $45 Citibank chargeback (Liz Franklin, reason: credit not processed) is still unread ~34.5h; evidence due Oct 5 so no immediate deadline pressure but needs a reply to avoid it going stale.
Link ↗
—Airbnb payouts flowing normally$360.88 / $2,196.83 / $51.18
Multiple routine Airbnb payouts landed this window (cancellation fee refund, standard payouts) — no discrepancies noted. Caveat: unread payout emails just mean the team works these in Guesty/the extranet, not that they're mishandled.
Link ↗
🆕CLSF-06050044 (Eric Jackson) reimbursement — deniedunspecified
Airbnb denied the Host damage protection claim for reservation HMJSXSZKAP citing missed 14-day guest-notice and 30-day form-submission windows. No dispute or rebuttal has been sent.
Link ↗

🎯 Handling gaps — coach the team 1 open · loss-exposure emails opened but not resolved in our favor

🆕CLSF-06050044 (Eric Jackson) — denied claim, no rebuttal sent

unquantified — original damage claim amount not stated in thread

What happened Airbnb's AirCover team denied the Host damage protection claim for missed 14-day guest-notice and 30-day submission requirements. The email remains unread with no reply from the team.

The gap Team never replied to challenge the denial or provide any additional context that might reverse it.

Coach the team Reply promptly noting any mitigating circumstances (e.g. guest contact attempts within window) and ask Airbnb to reconsider; if the 14-day notice truly was missed, at minimum acknowledge to close the loop.

Email ↗

🔁 Recurring watchlist

ItemStatusTrendSource
Airbnb Support message thread growing unansweredNow ~28-31 messages, still no team reply, last message ~1.1-1.2h ago▲Link ↗

👤 Open items by owner

WhoOpenOldestItems
Guest-comms10Airbnb Support thread, Generali claims, various reimbursement requests
Maintenance coordinators8Hideaway 1031 bedbugs, Monroe connectivity, Asteria 117 toilet, various unit tickets

The big issues, explained

⬆Airbnb Support thread unanswered and escalating

Serious

What’s going on A single Airbnb Support message thread has grown to roughly 28-31 messages back and forth with no team reply, most recently just over an hour ago.

Why it matters Unanswered support threads at this volume risk Airbnb closing the case against us, as already happened on a separate thread this window.

GGuest-comms
Email ↗

Smaller items

✓Kota North 1143 — guest at wrong building resolved resolved
Guest checked into a different unit in Building 19 by mistake; overnight agent worked the call and got them to the correct unit. Overnight team Link ↗
🆕Kota 2094 blinds broken (cleaner report) ticket filed
Cleaner flagged broken blinds; ticket filed and guest added to claims tracker. Maintenance coordinators Link ↗

⏱ Team performance

✓ Overnight agent (SOD/EOD shift)
Worked a live guest-at-wrong-building issue at Kota North 1143/Building 19 for ~1 hour via call and Slack, resolving it with the guest successfully checked in.
Link ↗

💡 Ideas & 🔁 patterns

Large volume of unread stylish1@ Airbnb/Guesty threadsThe loss-exposure audit shows dozens of stylish1@ threads (reimbursement requests, cancellations, review disputes) sitting unread for many hours, several of which have already closed against the company (e.g. Airbnb support thread closures).
Fix: Consider a daily stylish1@ inbox triage pass separate from Slack ops tasks, prioritizing anything with 'action required' or a stated deadline.
No notes yet