Inspiration
My family owns four locations of a multi-unit franchise, PJs Coffee of New Orleans. We are planning our expansion and shift management is a primary concern. We currently must text and email back and forth multiple times between managers and employees to handle shift changes (sickness, conflicts, etc). This is currently painful beyond words, and adding new franchises will only make this exponentially worse.
When evaluating 'why' managers need to approve shift changes, usually it boils down to org rules around employee compliance (part time vs full time, over time, back to back shifts, employee matching, and employee preferences). If we could build Shift Mela in Vertex AI, this would remove 9/10ths of the reasons (save for visibility into the process) for managerial review. Turning it into a high level function, rather than a laborious process.
What it does
Shift Mela handles the intercommunication and coordination for shift changes. This handles almost all of the shift change process, removing the 'necessity' of managerial approval.
How we built it
Combining Google's Cloud SQL, Homebase's API and Twilio's API in VertexAI. We built an agent that handles the workflow of managing a shift change. The agent gate-keeps every step in the process, managing the communication between potential employees that are viable for a shift change while keeping organizational rules in mind (over time, part vs full time workers, schedule preferences) .
Challenges we ran into
- Determining if VertexAI can be a webhook consumer for Twilio's API. I
- Determining if VertexAI has a job scheduler to manage the 'queue time' for requests to potential shift change filler employees
Log in or sign up for Devpost to join the conversation.