Thanks for the response Isaac, The current SMS implementation is a one-way communication from the MFI to the customer/Staff only.
Eg: A new customer account has been created. And so the customer is notified of this event or a loan gets approved hence, the customer is informed. However, the customer cannot initiate communication with the MFI's system. So the USSD service I'm referring to is more customer self-service oriented. This will establish two-way communication giving the customer a real-time interactive session with the MFI's system. Hence, allowing the customer to get self-service via a USSD code. In this case, a customer can make a request through the MFI's USSD code and get a list of options: Eg: Account Balance, Common information, Loan Products available, Branch Locations, Transaction statements, Loan status etc. We can then improve it over time to include more advanced processes. The ultimate benefit here is the fact that everybody can access the MFI's financial services without a smartphone. *At your service,* *Ebenezer Graham* *BSc (Hons) Computing* [image: EmailSignature.png] African Leadership University, Power Mill Road, Pamplemousses, Mauritius. GitHub <https://github.com/ebenezergraham> | LinkedIn <https://www.linkedin.com/in/ebenezer-graham/> | ebenezergraham.me *Skype*: ebenezer.graham <http://ebenezergraham.me/> *This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and then delete this email. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.* On Tue, 26 Mar 2019 at 04:49, Isaac Kamga <isaac.ka...@mifos.org> wrote: > Thanks for your responses Grace, Pembe, Graham > > @Grace, do you still experience error https://pastebin.com/9ftKYDg8 from > the teller service ? Have you been able to find some time to look at issues > FINCN-100 to FINCN-102 ? +Mark van Veen <mark.vanv...@kuelap.io> Can you > kindly lend a hand here ? > > @Miriam, can you develop a road map for micro-finances with center-based > operations ? > > @Graham, Thanks for sharing the roadmap around the notifications service.I > thought item 5 : USSD services for notifcations service was already done. > Kindly expand more on that ? > > Cheers, > Isaac Kamga. > > On Sun, Mar 24, 2019 at 10:17 PM Ebenezer Graham <egraha...@alustudent.com> > wrote: > >> Hello Isaac, >> >> I hope this email finds you well. >> >> *Work done* >> I produced the initial code for the notification service. I implemented >> the email and SMS services for the service. I implemented the event >> listeners for customer service. I have written rest-docs for the service's >> APIs. I am currently developing the front-end in the fims-web-app >> >> *Challenges/Errors faced* >> The service is unable to authenticate using the permitted feign client. >> It returns a 404 error when I use the permitted feign client. However, >> changing the authentication to use the permitted feign client for >> authentication is the recommended approach. >> >> *Improvements* >> 1. Containerize the notification service in fineract-cn-containers >> <https://github.com/openMF/fineract-cn-containers>. >> 2. Implement email and sms listeners for the portfolio and group services. >> 3. Complete the implementation of the front-end in the fims-web-app and >> the new Web app implemented by Pembe to allow re-configuration of the email >> and SMS services. >> 4. Change the authentication to use permitted feign client for >> authentication. >> 5. Add USSD services to the notification service >> You can find more improvement considerations here: >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75975771 >> >> *At your service,* >> >> *Ebenezer Graham* >> >> On Sat, 9 Mar 2019 at 02:02, Isaac Kamga <isaac.ka...@mifos.org> wrote: >> >>> Hello GSoC 2018 students, >>> >>> Please could you provide a succinct summary of your project's status. >>> >>> Any form of information containing >>> 1. Work done >>> 2. Challenges/Errors faced, and >>> 3. Possible Further work/Improvements, will be helpful for the community >>> to know how to help make progress. >>> >>> At Your Service, >>> Isaac Kamga. >>> >>>
