Configure Requirements
POST /accounts/:id/requirements
Define what documents or data points need to be collected.
string
required
Requirement name (e.g., “Government ID”)
string
required
document, text, email, phone, number, datestring
Instructions for the AI on how to collect this
boolean
default:"true"
Whether this is mandatory
201 Created
List Requirements
GET /accounts/:id/requirements
Returns all configured requirements for the account.
Update Requirement
PATCH /accounts/:id/requirements/:requirement_id
Delete Requirement
DELETE /accounts/:id/requirements/:requirement_id
Removes a requirement from the checklist. Existing collected data for this requirement on leads is preserved.
Get Lead Checklist
GET /accounts/:id/leads/:phone/checklist
Returns the checklist status for a specific lead — which items have been collected, which are still pending.
How Document Collection Works Over SMS
1
Lead receives a message
A follow-up sequence message triggers a conversation, or the lead texts in.
2
AI asks naturally
The AI weaves missing checklist items into the conversation naturally — it doesn’t dump a list of requirements all at once.
3
Lead sends documents
The lead can text back a photo or PDF. Recover automatically downloads the file and matches it to the correct requirement.
4
Data extracted automatically
Text-based requirements (email, phone, date) are extracted from the conversation automatically — no manual entry needed.
5
Real-time updates
The checklist updates in real-time. The embed and API reflect changes immediately.
6
Completion webhook
When all required items are collected, a
checklist.completed webhook fires so your system knows the lead is ready.