We strongly believe that an integrated communication approach should be the starting point of large Direct Benefit Transfer (DBT) programmes. It certainly helps to be as clear and succinct as possible to manage expectations. In the previous blog we highlighted how poor and often contradictory communication is leading to mass confusion and apprehension amongst beneficiaries. In this blog, we present a case for beneficiary centric communication.

Is communication really a challenge?

The first step is to assess why communication is confusing to beneficiaries?

There are multiple entities and interlinked processes in the DBT delivery channel. This is, understandably, a real challenge for beneficiaries to understand.

For example Sita Devi, a 45 year old in Ramgarh district in Jharkhand, was supposed to receive MNREGS payments directly in her account from January 2013 onwards. Previously she used to receive her payments from the Sarpanch (village head) every fortnight.

However, it did not turn out to be that simple. She was asked to open a new bank account for which she was asked to visit the bank that was 12 km. from her village. She could not do this for long because she could not go by herself. When she finally reached the bank branch, she discovered that she was also required to bring along her job card to open the bank account. She had to wait for another three weeks before she could go back to bank, but again her account could not be opened as she did not have proper KYC documents in place. Finally, after two months of running from pillar to post, she managed to open her account.
All this while, she was not aware that there was one BC agent of bank working in her Panchayat. This agent was just 2 km. from her village but having opened account at the bank branch, she could not transact at agent location. Though now she had bank account, she was using it only for withdrawals as she was not clear she could use it for other banking services such as savings or fund transfer. She assumed that it was government’s account thus she should not leave any money in account.

Many others in the area were aware of agent location and services offered, but were unsure whether they could open accounts to receive MNREGS or government benefits there.

Thus Sita’s is not an isolated case. Most of the DBT beneficiaries have faced/are facing similar challenges, for want of a proper communication strategy.

Successful examples from past

MicroSave worked on an assignment to improve communication to beneficiaries of Dilli Annshree Yojana (DAY) in Delhi. Under this scheme, beneficiaries receive the cash food subsidy directly in beneficiaries’ accounts based on Aadhaar authentication. The communication campaign prepared and delivered under the assignment had a far reaching impact on the knowledge and awareness of beneficiaries of the scheme. Before the campaign, DAY beneficiaries had very little knowledge about the very basic issues such as:

  • The need to open an account
  • How linking such accounts to Aadhaar can help the payment of future benefits etc.
  • Whether they are required to withdraw all money, or can leave balances in the account
  • Whether they needed separate accounts for the different DBT schemes

They were under an impression that DAY accounts cannot be used for personal savings; that one should not leave any money in the DAY accounts; and that different accounts were required for each benefit they received. These myths and apprehensions were removed after a comprehensive Financial Education (FE) module was developed and delivered to a representative sample of beneficiaries.

Particularly in case of Delhi, the impact was evident when we compared the awareness of beneficiaries after the campaign. For example, 69 per cent of sample beneficiaries believed that Government can access individual account and therefore if they save money in this account, government might remove them from the beneficiary list. But after the campaign, this figure came down to only 26 per cent of beneficiaries. Similarly, there was a substantial positive impact on their understanding about the utility of their account, the need for Aadhaar linking and so on.
The fundamental reason for success of this campaign was its bottom-up approach. Rather than carpet bombing information, MicroSave conducted a need assessment survey to understand the communication gap. Based on this assessment, communication content, media, and manner were decided. For example, MicroSave found that for this population segment, communication material should not be written, but pictorial, because the latter enhances understanding and retention of the message. Examples of the few pictorial posters embedded here depict user centric approach of campaign.
The results of the campaign prove that with beneficiary centric communication, a lot of pain can be prevented. This is a win-win proposition for all the stakeholders. The scale and scope of DAY communication campaign can be considered small, given the huge volumes in all G2P benefit schemes, but it can be customised and scaled up for a larger impact. The only thing we need to keep in mind throughout the exercise is that beneficiary must be at the centre of all activities and decisions.

  1. Dear colleagues … thank you very much for highlighting on this very important issue of agaents (or other front line staff) COMMUNICATIONS skills with benefitiaires/clients. This is really an important issue, but largely ignored by microfinance practitioners, especiaslly those who need to attract potential clients for 'voluntary' savings. We assessed the challenges of voluntary saviing mobilization challenges of 12 MFIs (who can only mobilize less than 10% of their outstanding loans from 'voluntary' savings, in spite of having the lisence to do so some two decades ago!!) and found that this issue of (last mile) communication is the key challenge. We have posted at microfinancegateway

    Regards, Getaneh (getanehg2002@yahoo.com)


Leave Comments

*   can't be blank


can't be blank

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>