Returns, Disputes, and Quality Claims

Returns and disputes are limited to objective quality issues and account-specific policy terms.

Subjective sales outcomes are not valid return reasons.

Policy endpoint

GET /api/v1/buyer/return-policy
Authorization: Bearer YOUR_ACCESS_TOKEN

Allowed lead reason codes

Code	Meaning
invalid_phone	Disconnected or invalid phone.
bounced_email	Bounced or invalid email.
out_of_geo	Outside agreed geography.
out_of_filter	Outside agreed filter criteria.
duplicate	Duplicate within dedup window.
bot	Bot, non-human, or inflated submission.

Allowed booking reason codes

Code	Meaning
no_show	Verified no-show. Proof required.
filter_mismatch	Explicit filter mismatch. Proof required.

Submit a return

POST /api/v1/buyer/returns
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

{
"deliveryId": "recDelivery123",
"reason": "invalid_phone",
"proof": "Phone disconnected on first dial attempt"
}

File a dispute

POST /api/v1/buyer/disputes
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json

{
"deliveryId": "recDelivery123",
"reason": "filter_mismatch",
"detail": "Debt amount below agreed filter",
"evidenceUrl": "https://example.com/evidence.png"
}

Important rules

• Returns must be filed within the configured business-day window shown by the policy endpoint.

• Monthly return caps apply separately to lead and booking returns.

• No-response, not-interested, no-budget, gatekeeper, or late-follow-up outcomes are not objective return reasons.

• Evidence may be required for no-show and filter-mismatch claims.

• Approved returns, disputes, credits, and billing adjustments are reviewed through the approved workflow.