You keep track of follow-up calls with customers who owe you money by logging each one against that party: the channel, the outcome, a next-action date, and an optional promised amount and date. Entries are append-only, so Monday's "kal bhej dunga" stays on the record when Wednesday's visit produces a different sentence. A payment follow up log lives on the party inside the Recovery view in Collect, available on request. At 7 PM a Guwahati owner calls Barpeta Chemist, hears ₹45,000 tomorrow, and writes channel call, outcome promised, promised date Tuesday. Outcomes stay in four labels: paid, promised, no answer, disputed. A newer promise supersedes the older one. Tally still holds the bills. The log holds the chase the ageing report cannot show, including the Saturday WhatsApp that got no answer from the Dibrugarh kirana.
Key Highlights
- A payment follow up log records channel (call, WhatsApp, in person, or other), outcome, next-action date, and an optional promised amount and promised date against the party
- Entries are append-only; a newer promise supersedes the older one, and nobody rewrites Friday's sentence on Tuesday
- Outcomes stay in four labels: paid, promised, no answer, disputed
In This Article
- How do I keep track of follow-up calls with customers who owe me money?
- What belongs on a payment follow up log
- Channels, outcomes, and the next-action date
- Append-only, and why a newer promise supersedes
- The Monday chemist: one log entry that runs the week
- Where the log sits inside Collect
- Frequently Asked Questions
How do I keep track of follow-up calls with customers who owe me money?
The ageing list tells you Barpeta Chemist is at ₹1,20,000 and 62 days. It does not tell you that you called at 7 PM on Monday, that he named ₹45,000 for Tuesday, or that Saturday's WhatsApp got no answer. That is the gap a payment follow up log fills. Each chase becomes a dated line on the party, next to the bills Tally already holds.
Without the log, the chase lives in three places that never agree. The owner's head. A WhatsApp thread titled "vasuli". A notebook the accountant keeps for two weeks after someone complains, then drops. By Thursday nobody can say whether the chemist was called, messaged, or visited, and the next person on the route repeats Monday's conversation as if it were new. That is still how a lot of Indian distributors manage collections: the book is clean, the chase is oral.
The working unit is one party, one entry, one next-action date. You do not log "chased the 90-day bucket." You log that this chemist, on this evening, on this channel, produced this outcome. The payment recovery dashboard then reads those dates in the morning brief: follow-ups due today, promises due today. The log is the input. The brief is the morning.
What belongs on a payment follow up log
Four fields earn their place. Everything else is noise the owner will stop filling in by week two.
Channel. Call, WhatsApp, in person, or other. Four doors. A "called twice, also WhatsApp" afternoon is two entries, not one mash. The chemist who never picks up the phone and always replies on WhatsApp should show that pattern after a fortnight, and the channel field is how it shows.
Outcome. Paid, promised, no answer, disputed. That is the whole set. "Spoke, seemed positive" is not an outcome. "Will try" is not an outcome. If money moved, the outcome is paid. If a date and an amount were named, the outcome is promised. If the phone rang out, no answer. If the party is arguing a rate, a shortage, or a return, disputed. Four labels are enough to run a Tuesday.
Next-action date. The day this party comes back onto the morning list. After a no-answer on Saturday, the next-action date might be Monday. After a promise for Tuesday, the next-action date is Tuesday. After a dispute, it is the day you said you would check the invoice. A log without a next-action date is a diary. A log with one is a queue.
Promised amount and promised date, optional. Only when the outcome is promised. The chemist said ₹45,000 tomorrow. Both numbers go on the entry. A vague "this week" is not a promise you can mark missed. If the party will not name a day, log the call as no answer or as disputed, and set a next-action date you chose, not one they hinted at.
The log does not store a new phone number, a credit-limit change, or an edited bill. Those jobs live elsewhere. The log is the chase against outstanding that already sits in Tally.
Channels, outcomes, and the next-action date
A week on one Dibrugarh kirana shows why the four fields have to travel together.
Saturday 11 AM, salesman Ramesh WhatsApps the overdue statement. No reply by evening. Channel WhatsApp, outcome no answer, next-action date Monday. Monday 6:40 PM the owner calls, the kirana says the bill is wrong on a scheme rate. Channel call, outcome disputed, next-action date Wednesday, after the accountant has pulled the invoice. Wednesday 9:15 the owner visits, they agree the rate, and the kirana names ₹28,000 on Friday. Channel in person, outcome promised, promised amount ₹28,000, promised date Friday, next-action date Friday.
Each line is still on the party on Friday morning. Nobody has to remember the scheme argument. Nobody has to guess whether Saturday's WhatsApp counted as a chase. The promise to pay that Friday depends on is the Wednesday entry, not a feeling that "we spoke."
"Other" is the fourth channel for the odd door: a relative who runs the counter, a visit to the accountant's office, a note sent with the delivery boy. Use it when the three named channels are wrong. Do not use it as a dump for every lazy entry.
The next-action date is what the daily collection brief reads. Promises due today and follow-ups due today are dates you put on the log, not dates the software invented. If you skip the date, that party will not appear on Tuesday's card, and you will be back to scrolling 180 ledgers.
Append-only, and why a newer promise supersedes
Entries are append-only. Monday's call is still Monday's call on Thursday. If the chemist changes his story, you add Thursday's entry. You do not open Monday and type a different sentence over it. The history is the point. A log you can rewrite is a log you will rewrite when the Monday meeting gets uncomfortable, and then you cannot see the pattern.
A newer promise supersedes the older one. Wednesday's ₹28,000 on Friday replaces Monday's "full bill by month end" as the promise that counts. The Monday line stays visible. It is no longer the live promise. That rule stops a party from carrying three overlapping dates, each of which some salesman treats as current.
The same rule applies when the outcome changes from promised to paid. The receipt in Tally is the money. The log gets a new line with outcome paid, so the next person on the route does not call a party whose money already landed. The ageing will catch up once the receipt is allocated. The log is how the chase stops on the same morning, including in the hours when Tally has not yet seen the UPI.
Append-only also protects the owner from his own optimism. A salesman who likes a retailer will soften Friday's "no answer" into "busy, will pay" if the field is editable. If the field cannot be edited, the next-action date still fires, and the brief still names the party. That is the whole discipline.
The Monday chemist: one log entry that runs the week
Barpeta Chemist at ₹1,20,000 is three invoices, visible on Bills, and 62 days on Parties. Habits will show whether 62 is normal for him. None of that tells you what to do at 7 PM.
Monday 7 PM, owner calls. Chemist says ₹45,000 tomorrow against the oldest bill. The payment follow up log records channel call, outcome promised, promised amount ₹45,000, promised date Tuesday, next-action date Tuesday. That is the whole entry. It takes less time than typing the same thing into the vasuli WhatsApp group, and it sits on the party instead of in a thread 40 people can mute.
Tuesday 8:40 the owner opens Collect, opens Recovery, and the brief shows that promise as due today. If a receipt for that party has landed in Tally, the chase for ₹45,000 is over and the remaining ₹75,000 is a different job. If it has not, the owner still treats Tuesday as due, not as broken, until the date has passed and the receipt is still missing, with allowance for sync lag. The mechanic for that missed mark belongs with promise to pay tracking. The log's job on Tuesday morning is to make sure the chemist is the first call, not the fortieth ledger.
If Tuesday produces no answer, that is a new entry: channel call, outcome no answer, next-action date Wednesday. Monday's promise is still there. Wednesday's next action is now the live one. The chemist does not fall off the list because somebody "already spoke."
By Friday the party has a week of lines. The owner can see whether this is a payer who slipped or a party that has stopped picking up. That reading is what a receivables ageing view on mobile cannot do alone. Ageing is the stock. The log is the work.
Where the log sits inside Collect
Open Collect, open Recovery, open the party. The follow-up log is on that party, not in a separate app section. Parties still shows ageing as of today. Bills still shows the vouchers. The log is the third thing you look at once you know which party you are chasing.
Tally remains the book of record. A log entry does not raise a receipt, does not allocate a bill, and does not change the outstanding. When the chemist pays ₹45,000 on UPI, that money still has to land in Tally against the bill. The log only records that you asked, what he said, and when you will ask again.
Reminders are a different machine. The company-wide cadence can still send WhatsApp on the due-date schedule, and those reminders can carry a UPI payment link once payment collection is active, after KYC. The log is the human half: the call you made at 7 PM, the visit on Wednesday, the "no answer" on Saturday. Automation does not replace those. It also does not record them. That is why the log exists.
On a book of 180 parties, you will not log every courtesy hello. You log the chase against outstanding: the call that produced a date, the WhatsApp that produced silence, the visit that produced a dispute. Those are the lines the Tuesday brief can use. Everything else can stay in the chat.
Frequently Asked Questions
Q: How do I keep track of follow-up calls with customers who owe me money?
A: Log each follow-up against that party: channel as call, WhatsApp, in person, or other; outcome as paid, promised, no answer, or disputed; a next-action date; and an optional promised amount and promised date. Entries are append-only. A newer promise supersedes the older one. The morning brief then names follow-ups and promises due today from those dates.
Q: What is a payment follow up log?
A: A payment follow up log is the dated chase history on an outstanding customer: who was contacted, on which channel, what the outcome was, and when the next action is. It sits on the party in the Recovery view inside Collect. It does not replace Tally bills. It records the work the ageing report cannot show.
Q: Can I edit Monday's call after the chemist changes his story?
A: No. Entries are append-only. Add Thursday's entry with the new outcome or the new promise. Monday's line stays. The newer promise is the one that counts, and the history is how you see a party that keeps moving the date.
Q: Which outcomes can I record?
A: Four: paid, promised, no answer, disputed. If money moved, use paid. If a date and amount were named, use promised and fill the optional promise fields. If the phone rang out or the message sat unread, use no answer. If the party is arguing a bill, use disputed and set a next-action date for the check.
Q: Does the follow-up log send a WhatsApp reminder on its own?
A: No. The log records a chase you already made. Reminders run on the company-wide cadence, separate from the log. You can share the daily brief as text through the phone's share sheet when you want someone else to see today's list. That share is manual.
Takkada is a Tally-integrated receivables and auto-reconciliation app for Indian distributors, with 0% MDR UPI collection and WhatsApp dispatch. Book a free demo.