Policy & controls
Deterministic rules the merchant owns. The AI only proposes an understanding of the case — it cannot bypass any of these.
How a decision is made
AI
Understands the case
Reads Hinglish / English replies, screenshots, voice-note text. Extracts amounts, dates and the likely blocker. Outputs HIGH or NEEDS REVIEW.
Policy engine
Decides what is allowed
Payment recheck, state gates, never-contact list, review-first, amount and date limits, contact caps. Returns ALLOW / REVIEW REQUIRED / BLOCK.
Workflow engine
Executes / routes
Explicit state transitions, timers, routing to Accounts or Sales, approvals, part-payment links.
Outcomes
Update buyer + invoice
Audit trail with evidence for every transition; plain-count promise history; labelled review set.
Merchant policy
merchant-policy@v1Review-first
Every buyer-facing plan needs merchant approval before it is sent.
Part payments allowed
Minimum part payment
Currently ₹50,000
₹
Maximum extension
Latest date in a plan or wait, counted from today
days
Corrected invoice
Resolve drafts; it never issues tax documents
Approval required
Credit note / invoice split
Always requires approval
Approval required
Promise grace period
After the promised day ends, before follow-up resumes
Reminder frequency cap
Max standard reminders per 7 days
/ week
Pause Resolve
Blocks all buyer-facing actions; everything else needs manual action
Never contact these buyers
No buyers excluded.
Hard rules (not configurable)
- Paid-but-unmatched → no buyer communication
- Paperwork blocked → no reminders
- Needs review → no buyer message
- Resolved → no collection action
- Payment detected right before send → block and re-evaluate
- AI cannot mark invoices paid or resolved
- No pressure or false-urgency language
Labelled review set
Merchant classifications are collected here for future evaluation. Nothing is retrained automatically; any prompt or model change must be evaluated first.
No merchant labels yet.