Required stack
필요 기술
JotformAirtableMake.comTwilioAPI IntegrationAutomation Workflow DesignData ModelingSoftware Testing
Project brief
프로젝트 내용
PROJECT UPDATE — FINAL SYSTEM BUILD
Total project: $250
Confirm acceptance before proceeding.
---
PROJECT
Build one working foreclosure prevention triage, navigation, and enforcement system using:
Jotform → Airtable → Make.com → Twilio
This is a strict execution project.
Do not redesign it.
Do not simplify it.
Do not remove components.
Do not add features.
Build exactly what is written.
---
SYSTEM REQUIREMENT
This is a full system. All components must exist and work together.
If any component is missing or not functioning, the system is incomplete.
---
COMPONENT 1 — ENTRY (INTAKE FILTER)
Purpose:
Allow only valid cases into the system.
Must capture:
- Ownership (Yes/No)
- Mortgage Status (Yes/No/Not sure)
- Property Address
- Property Type
- Entry Type (Taxes / Repairs / Both / Not sure)
Rules:
- If Ownership = No → STOP
- If Mortgage = Yes → STOP
---
COMPONENT 2 — TAX STAGE CLASSIFICATION
Purpose:
Determine exact position in foreclosure timeline.
Primary field:
- Current
- Delinquent
- Forfeited
- Foreclosure
- Not sure
If “Not sure”, ask:
- Received county letter?
- Mentions forfeiture?
- Received court notice?
- Behind on taxes?
System must assign:
- Current
- Delinquent
- Forfeited
- Foreclosure
“Not sure” is NOT allowed in Airtable.
---
COMPONENT 3 — REPAIR CLASSIFICATION
Purpose:
Detect repair-driven risk.
Must include:
Repair Issues:
- Yes / No
Repair Types (checkbox multi-select):
- Roof
- Furnace / Boiler (Heating)
- Plumbing
- Electrical
- Water Heater
- Sewer
- Structural
- Other
Repair Urgency:
- Yes / No
Repair Description:
- Required text
---
COMPONENT 4 — HOPE STATUS
Purpose:
Track program position.
Values:
- Not Started
- In Progress
- Submitted
- Approved
- Denied
---
COMPONENT 5 — DOCUMENT BLOCKER
Purpose:
Identify what prevents progress.
Fields:
- Documents Complete (Yes/No)
- Missing Documents (text)
---
COMPONENT 6 — CONTACT
Purpose:
Enable enforcement.
Fields:
- Name
- Phone (REQUIRED)
---
COMPONENT 7 — SOURCE OF TRUTH (AIRTABLE)
Table: Property Tax Cases
Fields:
- Name
- Phone
- Address
- Ownership
- Mortgage Status
- Property Type
- Entry Type
- Tax Stage
- Repair Issues Present
- Repair Types
- Repair Urgency
- Repair Description
- HOPE Status
- Documents Complete
- Missing Documents
- HOPE Deadline
- Next Action
- Date Submitted
- Follow-Up Date
- Last Weekly SMS Sent Date
- Missing Docs SMS Sent Date
- 14-Day Alert Sent
- 7-Day Alert Sent
- Risk Level
---
COMPONENT 8 — DATA MAPPING
All Jotform fields must map correctly into Airtable.
If mapping is incorrect, the system fails.
---
COMPONENT 9 — RULE ENGINE
System must enforce:
- Owner + no mortgage required
- Tax Stage must always be assigned
- If HOPE not started → push HOPE
- If documents missing → block progress
- If repairs present → increase risk
- Weekly follow-up only when Submitted
- Stop follow-up when Approved or Denied
- No duplicate alerts
---
COMPONENT 10 — NEXT ACTION
System must identify next step:
Examples:
- Apply for HOPE
- Complete documents
- Continue follow-up
- Repair assistance needed
- Case closed
---
COMPONENT 11 — ALERT SYSTEM
Must include:
Missing Documents Alert (send once)
SMS:
"You are missing required documents. Your application will be denied."
---
14-Day Alert (send once)
SMS:
"Reminder: Your property tax application must be submitted before the deadline."
---
7-Day Alert (send once)
SMS:
"URGENT: You must act now or risk denial."
---
Weekly Follow-Up
SMS:
"Checking status of your application. Please respond if needed."
---
COMPONENT 12 — DUPLICATE PREVENTION
Must use:
- Missing Docs SMS Sent Date
- 14-Day Alert Sent
- 7-Day Alert Sent
- Last Weekly SMS Sent Date
No repeated messages allowed.
---
COMPONENT 13 — STOP CONDITION
If HOPE Status = Approved or Denied:
STOP all follow-up immediately
---
COMPONENT 14 — TWILIO
Must be fully functional:
- Connected
- Approved
- Sending real SMS
System is not complete without successful message delivery.
---
COMPONENT 15 — TESTING
All must pass:
1. Intake creates record
2. Filters work
3. Tax stage assigned
4. Repair classification works
5. Missing-doc alert sends once
6. 14-day alert sends once
7. 7-day alert sends once
8. Weekly follow-up works
9. Weekly follow-up stops
10. No duplicate messages
11. Twilio sends real messages
---
COMPONENT 16 — PRIORITY LOGIC
System must identify high-risk cases based on:
- Tax Stage
- Repair urgency
- Missing documents
- HOPE status
- Deadline proximity
---
PASS / FAIL
System is complete only if ALL components above exist and function correctly.
If any component is missing or fails → project is incomplete.
---
REQUIRED PROOF
- Airtable screenshots
- Make.com run logs
- Twilio delivery logs
---
FINAL CONFIRMATION
Reply:
CONFIRMED
And confirm:
1. You will build exactly this system
2. You will not change logic
3. You understand pass/fail
4. Payment only after full completion
Total project: $250
Confirm acceptance before proceeding.
---
PROJECT
Build one working foreclosure prevention triage, navigation, and enforcement system using:
Jotform → Airtable → Make.com → Twilio
This is a strict execution project.
Do not redesign it.
Do not simplify it.
Do not remove components.
Do not add features.
Build exactly what is written.
---
SYSTEM REQUIREMENT
This is a full system. All components must exist and work together.
If any component is missing or not functioning, the system is incomplete.
---
COMPONENT 1 — ENTRY (INTAKE FILTER)
Purpose:
Allow only valid cases into the system.
Must capture:
- Ownership (Yes/No)
- Mortgage Status (Yes/No/Not sure)
- Property Address
- Property Type
- Entry Type (Taxes / Repairs / Both / Not sure)
Rules:
- If Ownership = No → STOP
- If Mortgage = Yes → STOP
---
COMPONENT 2 — TAX STAGE CLASSIFICATION
Purpose:
Determine exact position in foreclosure timeline.
Primary field:
- Current
- Delinquent
- Forfeited
- Foreclosure
- Not sure
If “Not sure”, ask:
- Received county letter?
- Mentions forfeiture?
- Received court notice?
- Behind on taxes?
System must assign:
- Current
- Delinquent
- Forfeited
- Foreclosure
“Not sure” is NOT allowed in Airtable.
---
COMPONENT 3 — REPAIR CLASSIFICATION
Purpose:
Detect repair-driven risk.
Must include:
Repair Issues:
- Yes / No
Repair Types (checkbox multi-select):
- Roof
- Furnace / Boiler (Heating)
- Plumbing
- Electrical
- Water Heater
- Sewer
- Structural
- Other
Repair Urgency:
- Yes / No
Repair Description:
- Required text
---
COMPONENT 4 — HOPE STATUS
Purpose:
Track program position.
Values:
- Not Started
- In Progress
- Submitted
- Approved
- Denied
---
COMPONENT 5 — DOCUMENT BLOCKER
Purpose:
Identify what prevents progress.
Fields:
- Documents Complete (Yes/No)
- Missing Documents (text)
---
COMPONENT 6 — CONTACT
Purpose:
Enable enforcement.
Fields:
- Name
- Phone (REQUIRED)
---
COMPONENT 7 — SOURCE OF TRUTH (AIRTABLE)
Table: Property Tax Cases
Fields:
- Name
- Phone
- Address
- Ownership
- Mortgage Status
- Property Type
- Entry Type
- Tax Stage
- Repair Issues Present
- Repair Types
- Repair Urgency
- Repair Description
- HOPE Status
- Documents Complete
- Missing Documents
- HOPE Deadline
- Next Action
- Date Submitted
- Follow-Up Date
- Last Weekly SMS Sent Date
- Missing Docs SMS Sent Date
- 14-Day Alert Sent
- 7-Day Alert Sent
- Risk Level
---
COMPONENT 8 — DATA MAPPING
All Jotform fields must map correctly into Airtable.
If mapping is incorrect, the system fails.
---
COMPONENT 9 — RULE ENGINE
System must enforce:
- Owner + no mortgage required
- Tax Stage must always be assigned
- If HOPE not started → push HOPE
- If documents missing → block progress
- If repairs present → increase risk
- Weekly follow-up only when Submitted
- Stop follow-up when Approved or Denied
- No duplicate alerts
---
COMPONENT 10 — NEXT ACTION
System must identify next step:
Examples:
- Apply for HOPE
- Complete documents
- Continue follow-up
- Repair assistance needed
- Case closed
---
COMPONENT 11 — ALERT SYSTEM
Must include:
Missing Documents Alert (send once)
SMS:
"You are missing required documents. Your application will be denied."
---
14-Day Alert (send once)
SMS:
"Reminder: Your property tax application must be submitted before the deadline."
---
7-Day Alert (send once)
SMS:
"URGENT: You must act now or risk denial."
---
Weekly Follow-Up
SMS:
"Checking status of your application. Please respond if needed."
---
COMPONENT 12 — DUPLICATE PREVENTION
Must use:
- Missing Docs SMS Sent Date
- 14-Day Alert Sent
- 7-Day Alert Sent
- Last Weekly SMS Sent Date
No repeated messages allowed.
---
COMPONENT 13 — STOP CONDITION
If HOPE Status = Approved or Denied:
STOP all follow-up immediately
---
COMPONENT 14 — TWILIO
Must be fully functional:
- Connected
- Approved
- Sending real SMS
System is not complete without successful message delivery.
---
COMPONENT 15 — TESTING
All must pass:
1. Intake creates record
2. Filters work
3. Tax stage assigned
4. Repair classification works
5. Missing-doc alert sends once
6. 14-day alert sends once
7. 7-day alert sends once
8. Weekly follow-up works
9. Weekly follow-up stops
10. No duplicate messages
11. Twilio sends real messages
---
COMPONENT 16 — PRIORITY LOGIC
System must identify high-risk cases based on:
- Tax Stage
- Repair urgency
- Missing documents
- HOPE status
- Deadline proximity
---
PASS / FAIL
System is complete only if ALL components above exist and function correctly.
If any component is missing or fails → project is incomplete.
---
REQUIRED PROOF
- Airtable screenshots
- Make.com run logs
- Twilio delivery logs
---
FINAL CONFIRMATION
Reply:
CONFIRMED
And confirm:
1. You will build exactly this system
2. You will not change logic
3. You understand pass/fail
4. Payment only after full completion