Agent Call Service is a customer service application that provides call center supervisors the ability to monitor their agents. This application helps the supervisor stay organized and manage their time efficiently by monitoring a web page for changes.
Report Bug
ยท
Request Feature
Table of Contents
This project is a web-based application for state visualization of massive amounts of entities in real time. The project handles requests/entities via a REST API & renders real time changes to a client. The updates and render page are tied to a SQL database that stores agents/entities information. The use case of this application is for a human supervisor who will use a web browser to observe the state of thousands of agents/entities, each entity being represented as a colored dot. This application allows a human observer to derive a sense of the overall state and dynamics of the entity/agent population ๐
To get a local copy up and running follow these simple example steps.
For building and running the application you need:
- Clone the repo
git clone https://github.com/jvniorrr/Team-Blue.git
- Change directory to where you have cloned the repository. Once you are in the directory of the cloned repository
cd "callservice/src/main/java/com/callservice/"
- There are several ways to run the Application on your local machine. One way is to execute the main method in the CallserviceApplication class from your IDE.
https://app.swaggerhub.com/apis/J_2/Call-Service-Team-Blue/1.0.0#/
- REST API implementation
- Server Side Event to emit calls.
- Create SQL Models
- Integrate SQL with our frontend, so if client refreshes HTML changes stay persistent
- Tweak SSE to not time out, and make asynchronous code.
- Bootstrap fundamentals (think frontend got already?)
- Mockups to base ideas off of.
- Create Supervisor render page (view agents in grid, needs some work.)
- Integrate Vanilla JS to handle events that are emitted.
- Add an agent
- Update an agent
- Remove Agent
- Retrieve all active agents
- Filters for agents to retrieve if active, busy etc.
- Database should store for now ID, status & a full name & an updatedTime/currentTime field as well.
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.