Prioritize and record collections

Your next action

Open Collections for a paginated queue of overdue accounts and commitments due within seven days. The server applies your customer scope before counting and ranking. Review unallocated credit and disputes before requesting more money. Disputed balances stay in financial totals. My assigned customers narrows the queue further. Promise counters use the selected reporting period and reflect manually reported outcomes, not settlement confirmation.

Reviewed WhatsApp drafts

Prepare WhatsApp from an account or collection card when you have contact-creation, contact-detail and internal-history access. Review the recipient, local-number country and message, then affirm permission to contact them. Opening the draft shares that phone number and message with WhatsApp; you send it yourself. Opening alone creates no contact event. After sending, explicitly record your manually reported contact. DeniFlow has no WhatsApp Business API, automatic delivery receipts or inbound message sync.

Working on the web

Collection cards adapt to smaller screens and show when data was loaded. When your browser reports that it is offline, displayed data may be stale and collection writes are disabled. Reconnect and refresh before recording activity. No native mobile app or offline financial-write queue is included.

Import existing customers

Customers → Import CSV provides a blank template and row validation. Import up to 200 reviewed customer records at a time. Names, contact fields, terms and credit limits are supported; historical invoices or opening balances are not created. Identical rows within a batch are rejected. Review existing records before repeating an import: it is not an automatic merge tool.

Run a daily collection session

Start with a current view of your assigned portfolio.

1. Open Collections, refresh and apply My assigned customers if appropriate.
2. Review overdue invoices, upcoming commitments, unallocated credit and disputes.
3. Read the latest contact history before asking the customer to pay again.
4. Choose a respectful next action. For WhatsApp, check the recipient, message and contact permission before opening the draft.
5. After the real interaction, record the outcome and any promise date and amount.
6. Mark promise outcomes based on what actually happened. Record and allocate verified receipts through Payments.

Read promise metrics carefully

Kept and broken promise counts describe reported collection outcomes for the chosen period. They are not automated payment-provider checks and do not replace the ledger. Incomplete follow-up records can make these metrics misleading.