yuri-val / call-center-software

Dev Challenge 11 | FINAL

Home Page:http://devchallenge.it/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Task

Call center software: There is a call center with employees that have certain expertise areas; customers are calling and indicate their desired area.

You have to write the server that directs the calls (binds customers to employees) maximizing the number of customer contacts that are fulfilled.

The server should handle 3 types of requests:

  1. http://server.name/register?name=EmployeeName1&area=bills&area=contracts&area=special-offers This request defines EmployeeName1 as an employee with three areas of expertise: bills,contracts and special-offers. Only one employee can be defined in a request. The same name can be redefined multiple times, because employees are becoming available after handling a customer. The response must be code 200, with content: WELCOME

  2. http://server.name/call?area=bills&area=leases&area=bills This indicates that a new batch of 3 customers are on the line. Two of them are interested in "bills" and one in "leases". Based on the list of registered employees, you have to assign (or decline) each call, in the order they appear in request. You have to respond with HTTP code 200 OK, and content is a JSON indicating the assigned employees. For example:

    {
      "totalAssignments" : "1",
      "assignments" : [
          {
            "area" : "bills",
            "employee" : "EmployeeName1"
          },
          {
            "area" : "leases",
            "employee" : ""
          },
          {
            "employee" : "",
            "area" : "bills"
          }
      ]
    }

    The reply above indicates that only one assignment was possible: EmployeeName1 takes the first call about "bills". The other calls should be postponed because no employee is available. This is indicated by empty "employee" value. Once an assignment is set, the employees listed are busy taking the call, so they are no longer available. They may return later (via a register request).

  3. http://server.name/reset This is done usually at the end of a work day. It means that all registered employees leave home: the system can restart tomorrow.

README

Algorithms

The easiest method of application operation was chosen. Only one model (database table) was added to store data on employee areas. The model contains only 2 fields: name (employee name) and area.

When the query /register is executed, records are created in the table with the employee and his areas.

When the /call request is executed, the most previously registered user is selected based on the specified area.

When the query /reset is performed, all records in the table are cleared.

How to run

Run with docker:

Just one command:

docker-compose up

Work with app

Application will be available at 'http://localhost:8080'.

About

Dev Challenge 11 | FINAL

http://devchallenge.it/


Languages

Language:Ruby 97.2%Language:Shell 2.2%Language:HTML 0.6%