David Kim
On 1 call in this window, owning 6 open commitments.
What they owe6
Measured against 28 Apr 2026, the most recent call in the corpus.
| Commitment | Due | Action type | Account | |
|---|---|---|---|---|
| Escalate case to Protect infrastructure team as P1 and confirm whether backend routing changes caused throughput drop Support Case #9856 - Silverline Brands Backup Window Exceeded | 12 Apr 2026Pastsaid “today” | escalate case | Silverline Brands | |
| Deploy backup agent 4.2.0 as a manual deployment via console Support Case #9856 - Silverline Brands Backup Window Exceeded | 12 Apr 2026Pastsaid “within the hour” | engineering or configuration change | Silverline Brands | |
| Adjust backup job priorities and throttle lower-priority file-server jobs to prioritize SQL workloads Support Case #9856 - Silverline Brands Backup Window Exceeded | 12 Apr 2026Pastsaid “now” | engineering or configuration change | Silverline Brands | |
| Send calendar invite for follow-up call tomorrow at 10 AM Central with a Protect platform engineer Support Case #9856 - Silverline Brands Backup Window Exceeded | 12 Apr 2026Pastsaid “within the next 30 minutes” | schedule session | Silverline Brands | |
| Check in on tonight's backup run tomorrow morning before the follow-up call Support Case #9856 - Silverline Brands Backup Window Exceeded | 13 Apr 2026Pastsaid “tomorrow morning before our call” | follow up | Silverline Brands | |
| Set an alert so David is paged if SQL job duration exceeds six hours Support Case #9856 - Silverline Brands Backup Window Exceeded | No date | engineering or configuration change | Silverline Brands |
Coaching4
Recorded against the calls this person was on. Where several AegisCloud people attended, the same notes appear for each of them.
Strengths (4)
Acknowledged the slow initial response and apologised directly instead of deflecting.
Asked targeted diagnostic questions to isolate affected workloads and backup type.
Moved to concrete action: P1 escalation, agent update, priority adjustments, alert, and scheduled engineering follow-up.
Shared suspected internal cause transparently before confirming it.
Improvement notes (0)
Nothing recorded.
Their calls1
| Call | Account | Date | Outcome | Sentiment | Talk share |
|---|---|---|---|---|---|
Support will escalate Silverline backup issue and push agent update before follow-up call | Silverline Brands | 12 Apr 2026 | Escalated | -1 | 60% |