CallCatch — the spec

CallCatch is a SaaS platform that stops small home service businesses from losing revenue to missed and after-hours calls. When a call goes unanswered, the right team member gets an immediate SMS or push alert with the caller's details and a direct path to respond — turning a lost lead into a booked job. Built for owner-operated teams of 2–10 people who run lean and can't staff a phone line around the clock.

---

Decisions locked

---

The core loop

1. A customer calls the business outside hours or when the team is occupied — the call goes unanswered.
2. CallCatch detects the missed call in real time and pulls the caller's number, name (if available), and timestamp.
3. The assigned team member receives an SMS or push notification within seconds, containing the caller's details and a callback link.
4. The team member taps the link, calls or texts the customer back directly, and converts the lead.
5. The interaction is logged automatically against the caller's record for future reference.

---

v1 scope

Instant missed-call alerts
Detects a missed call and fires an SMS or push notification to the designated team member within seconds. Lives on the alert delivery layer — no app open required to receive it.

Caller info card
Each alert surfaces the caller's phone number, name (from carrier lookup or existing record), call time, and a one-tap callback button. Displayed in the notification body and mirrored on the Call Detail screen inside the app.

Team member routing
Configures which team member receives alerts by time of day or day of week. Lives on the Team Settings screen — prevents every alert from hitting everyone at once.

Missed-call log
A running list of every unanswered call with status (responded / unresponded), timestamp, and caller info. Lives on the Dashboard — gives owners a single view of outstanding opportunities.

Basic CRM record
Each caller gets a lightweight contact record that collects call history and any notes added post-callback. Lives on the Contact Detail screen — ensures no repeat caller is treated as a stranger.

---

Deliberately later

• One-tap job acceptance or decline — requires workflow state management better introduced once the core alert loop is proven with real users.
• AI-powered call transcription and detail extraction — adds meaningful cost and complexity; earns its place once teams are logging enough calls to make transcripts searchable.
• After-hours scheduling calendar with team availability — natural v2 add-on once routing rules are established and users are asking for availability-aware dispatching.
• Revenue loss analytics and opportunity tracking — needs a baseline of logged calls before the numbers are meaningful; a month of real data makes this far more valuable.
• Call recording archive — storage and compliance requirements (consent laws vary by state) make this a deliberate, scoped release, not a day-one toggle.
• On-call rotation and shift management — generalises the routing rules built in v1; extends naturally once teams hit the limits of simple time-based routing.
• Integration with booking/CRM systems — high ROI but high surface area; prioritised after the internal CRM record is stable and users name their specific tools.

---

Data model sketch

• businesses — id, name, phone_number, timezone, plan_tier
• team_members — id, business_id, name, phone_number, push_token, role
• routing_rules — id, business_id, team_member_id, days_of_week, start_time, end_time
• missed_calls — id, business_id, caller_number, caller_name, received_at, status (new/responded), assigned_to
• alerts — id, missed_call_id, team_member_id, channel (sms/push), sent_at, delivered_at
• contacts — id, business_id, phone_number, name, first_seen, last_seen
• call_notes — id, missed_call_id, team_member_id, body, created_at

---

Screens

• Dashboard — live feed of missed calls, outstanding vs. responded, at-a-glance status for the day.
• Call Detail — full caller info card, alert delivery status, callback button, and note entry.
• Contacts — searchable list of all callers with call history and saved notes.
• Team Settings — add/remove team members, assign phone numbers, configure notification preferences.
• Routing Rules — define who gets alerted by time of day and day of week.
• Account / Billing — plan management, connected phone number, and business profile.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are ready to act on.
• Keep it as the single source of truth while you build, so every feature decision and trade-off stays anchored to what CallCatch is actually for.