Map a controlled debtor-follow-up workflow
Design weekly statements with approval, delivery logs and exception handling.
What you will be able to do
- Place human approval before sending statements and route disputed balances for review.
Suggested preparation: Build a receivables ageing report ·
Try the task
- Fictional case: one company, 50 debtors, weekly Tally exports. Sequence: contact validation → reconciled PDF → approval → authorised email/WhatsApp channel → delivery log → exception queue. This exercise does not send messages.
- Use fictional or permitted inputs. Identify missing information before asking AI to help.
- Attempt the task yourself, then use the prompt to compare methods. Keep the source with your working.
- Check the result against the worked answer and complete the checkpoint. Correct an error before saving completion.
Fictional practice data
Party,Outstanding,ContactStatus,Disputed Sample A,6000,Verified,No Sample B,12000,Missing,No Sample C,4000,Verified,Yes
Try this prompt
Map the weekly statement process for 50 fictional debtors. Include contact verification, reconciliation, pre-send approval, consent, failed-delivery handling and duplicate-send prevention. Do not execute any send.
Your working notes
Check your result
Use only the supplied facts. This checkpoint validates these specific calculations or decisions; it does not certify professional competence.
Worked answer and review criteria
Only Sample A reaches the approval queue. Sample B needs a verified contact. Sample C needs dispute resolution. Nothing is sent automatically by this lesson.
- Every amount reconciles to the supplied data.
- Missing facts and unsupported conclusions are identified.
- The result can be independently reproduced.
Try the checkpoint yourself before relying on this answer.
What to do next
Read the full practical guide →
Understand what AI can and cannot do →
30-day daily practice plan → · Long-term AI mastery reference →