Thea - Checking Supervisor Availability

[krisnaBukitVista]

Description

This project enables Thea to check and communicate supervisor availability based on their Google Calendar events. Thea will use this information to provide owners with accurate updates on when a supervisor is available or when they can expect a response.

Problem

Currently, Thea lacks visibility into a supervisor’s schedule, leading to:

• Delays in informing owners about supervisor availability.
• Owners experiencing uncertainty about when they will receive assistance.
• Inefficiencies in communication, requiring manual follow-ups.

Solution

• Google Calendar Integration: Thea will read event blocks from a supervisor’s Google Calendar to determine availability.
• Automated Owner Updates: Thea will proactively inform owners about the supervisor’s availability and provide an estimated response time.
• Smart Response Handling: If a supervisor is unavailable, Thea will suggest alternative support options or escalate urgent cases appropriately.

Measurement Metrics

• Accuracy of Thea ability to set expectation on supervisor availability

SLA

• 85% accuracy of Thea’s ability to set expectation on supervisor’s availability during escalation

Evaluation

After evaluation :

• 2025-02-07
  • Escalate: 4/4 Message (100% Send message availability supervisor)
  • Partial: 6/6 Message (100% Send message availability supervisor)
• 2025-02-08
  • Escalate: 3/3 (100% Send Message availability supervisor)
  • Partial: 2/2 (100% Send Message availability supervisor)
• 2025-02-09
  • Escalate: 3/3 Message (100% Send message availability supervisor)
  • Partial: 2/2 Message (100% Send message availability supervisor)

Insights:

• OpenAI sometimes returns hallucinations for the date, even though the information provided is correct.
  • The date format needs to be fixed so that OpenAI returns the correct date.
• This implementation can be used by DavidAi to check availability as a supervisor.
  • The module implementation can also be used for DavidAi.
• If the available time range is less than 30 minutes, notify the user of the next available time.
  • Create a condition to assign the next available time.
• If there is a block marked as OFF, search for availability on the next days that are not OFF.
  • Create a condition so that if a day is marked as OFF, the module searches for days that are available.
• Automation works but wordings need to be refined
  • Use more human response, e.g.
    • Instead of Kayla is available from 14:00 - 16:00
      • We can say available in 2 hours
      • No need to tell why not available

[Vidiskiu]

@krisnaBukitVista @Ardy-BukitVista based on the agreement during our discussion, I will expect that the evaluation will be concluded by 2025-02-10 for this project in chapter scope. Please update accordingly

[Vidiskiu]

@krisnaBukitVista also, please help me update the SLA for this milestone, apparently there has been agreement with CTO Kak Bayu regarding the SLA for this project at 85% accuracy for detection/classification

[Ardy-BukitVista]

After evaluation :

• 2025-02-07
  • Escalate: 4/4 Message (100% Send message availability supervisor)
  • Partial: 6/6 Message (100% Send message availability supervisor)
• 2025-02-08
  • Escalate: 3/3 (100% Send Message availability supervisor)
  • Partial: 2/2 (100% Send Message availability supervisor)
• 2025-02-09
  • Escalate: 3/3 Message (100% Send message availability supervisor)
  • Partial: 2/2 Message (100% Send message availability supervisor)

Insights:

• OpenAI sometimes returns hallucinations for the date, even though the information provided is correct.
  • The date format needs to be fixed so that OpenAI returns the correct date.
• This implementation can be used by DavidAi to check availability as a supervisor.
  • The module implementation can also be used for DavidAi.
• If the available time range is less than 30 minutes, notify the user of the next available time.
  • Create a condition to assign the next available time.
• If there is a block marked as OFF, search for availability on the next days that are not OFF.
  • Create a condition so that if a day is marked as OFF, the module searches for days that are available.
• Automation works but wordings need to be refined
  • Use more human response, e.g.
    • Instead of Kayla is available from 14:00 - 16:00
      • We can say available in 2 hours
      • No need to tell why not available

[Vidiskiu]

Overall Point: 5.5

Functional Complexity: 1.5

The functionality requires interaction with Google Calendar and implementing logic to handle availability checks, alternative support suggestions, and escalation cases, which presents moderate complexity.

Technical Complexity: 2

Integration with Google Calendar API and the smart response handling indicates a higher technical effort, with API integration and the need to process and interpret calendar data.

UI/UX Complexity and Impact: 0.75

Improvements need to be made to the wording of automated responses to make them sound more human. UI/UX changes are not intricate but will have an impact on user interactions.

Testing and Quality Assurance: 0.75

Extensive testing is required to ensure Thea accurately gauges supervisor availability, but the concept is proven, hence a moderate score is given for testing and QA.

Risk and Dependencies: 0.5

There's moderate risk involved with dependencies on Google Calendar's API and potential for inaccuracies, but evaluation data shows high levels of accuracy, suggesting manageable risk.