Suite 16 Oyes Plaza,

Kubwa Extension
Abuja
Nigeria.
TO:
__________________________________
__________________________________
__________________________________

PROPOSAL FOR THE DEVELOPMENT OF WHATSAPP CHATBOT

The project describes a chatbot that operates within the WhatsApp messaging platform. It is
designed to simulate conversation with human users, just like any other chatbot, but it is
specifically designed to be used on WhatsApp.

To use this WhatsApp chatbot, a user will send a message to the dedicated WhatsApp phone
number or interact with it through a link provided by the chatbot developer.

The chatbot will then respond to the user's message, either with pre-written responses or by
generating a response using natural language processing algorithms, depending on the
conversation flow.

A fully described conversation flow will be provided by the client which is required to be used in
building the language models.

These conversation flows would be categorized into intents that describe the end goal of a chat.

The solution would work on two fronts:

1. The admin front
2. The user front.

The admin views and edits conversation flows from the interface and also gets access to
previous conversations.

The admin would also be able to add agents whose primary duty would be to respond to
customer service queries.

The solution would be implementing Language Models from Google Cloud or IBM Watson
depending on the complexity of the chat models.
OBJECTIVES AND REQUIREMENTS

Functional Requirements
● Whatsapp should implement conversation chat flows as submitted by the client
● Response latency should be less than 2 seconds
● Whatsapp UI elements (buttons, options, selects) should be available during the
conversation
● All Conversations should be logged by the system and seen by the administrator
● The administrator should be able to edit chat flows comfortably

Non-Functional Requirements
● 24/7 Uptime
● an unlimited number of synchronous users

IMPLEMENTATION PLAN

1. Obtain the conversation flows from the client

2. Build chat models from conversations
3. Build a management dashboard to enable the modification of Bot responses

MAINTENANCE

Item Cost (NGN)

Addition of New Chat Flows after deployment 50,000

Annual Server Maintenance with DNS 70,000

PROJECT TIMELINE

S/N Activity Number of weeks

1 Information Gathering: Obtaining chat flows from 1-week

client

2 ChatBot Development 3 weeks

3 Management Dashboard Development 2 weeks

4 Testing 1-week

5 Deployment and Release 1 week

TOTAL 8 weeks
IMPLEMENTATION BUDGET

S/N ITEM COST

1 Building Chat Models and Access Points 450,000

2 Building Management Dashboard 200,000

3 Server and DNS Set up 130,000

TOTAL 780,000

PAYMENT SYSTEM
60% upfront payment is required to commence the job, the remaining 40% should be paid after
the final deployment.

PROJECT TERMS

1. The project would be delivered in line with the client’s requirement and would be deemed
completed by the client in line with outlined specifications and agreed design.

2. We shall ensure that the Development Services are provided in accordance with the
timetables agreed in writing (Software Development Particulars) and that the Software
and Documentation are delivered to the Client by means of a secure online file-sharing
system, in accordance with that timetable.

3. The Customer acknowledges that a delay in the Customer performing its obligations
under this Agreement may result in a delay in the performance of the Development
Services; and subject to this, we will not be liable to the Customer in respect of any
failure to meet the Development Services timetable to the extent that that failure arises
out of a delay in the Customer performing its obligations under this Agreement.

4. We shall ensure that the Source Code, and any interpreted code, comprised in the
Software created by or on behalf of the Developer during the provision of the
Development Services is written to a professional standard, conforms with any coding
standards document agreed between the parties, and incorporates sufficient
commentary to enable a competent third party developer to understand, adapt, maintain
and update the code.

5. We shall keep the Customer reasonably informed of the progress of the Development
Services and, in particular, shall inform the Customer of any substantial obstacles or
likely delays in the performance of the Development Services.

6. We shall during the course of the Development Services at the request of the Customer
supply the Customer a current development version of the Software for the purposes of
enabling the Customer to assess the progress of the Development Services and provide
feedback to the Developer regarding the Software.
 7. After the final release, the client is not supposed to come up with further changes or
improvements, thus it is required that a full test of the platform be made before the
project is released. In situations where there are changes to be made, an appropriate
fee would be charged based on the extent of work required to be done.

Sunday Mba,
OCity Cybernetics Limited.