Support Case #8179 - Clearwater Medical Overage Charges Dispute
Clearwater Medical disputes $4,000 April overage charges tied to Comply and Detect
Clearwater Medical reported unexpected overage charges on their April invoice, primarily from Comply on-demand report generation after the v2 launch and an $840 Detect event ingestion overage. Aegis support identified that the account generated 47 reports against a 20-report limit, but no threshold alert was sent; a configuration flag suggests alerts were not enabled by default on migrated accounts. The Detect overage appears linked to event replay from the March outage, which the customer questions. Sarah Chen committed to escalating both disputes internally, asking Clearwater to hold off on disputed payments, and promised a written Comply response within 48 hours and Detect analysis by end of day.
How the call went
Customer expressed consistent frustration over unexpected overage charges and potential billing of outage replay traffic, with only a terse acknowledgment of the vendor's transparency at the end.
Opening
-1Close
-112 scored turns of 40. Hover a point for the model's reason, or read the transcript.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 13
- Questions they asked
- 9
- Turns
- 40
- Longest silence
- 1s
Who was on the call
AegisCloud
Customer
- Ajay Mehta?Matched on an initial rather than a full name, so attribution is weaker.
- Natalie Simmons?Matched on an initial rather than a full name, so attribution is weaker.
What happened7
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised4?A problem was brought up on the call.
Natalie and Ajay report unexpected overage charges just over $4,000 on the April invoice, primarily tied to the Comply module and a Detect event ingestion overage.
Ajay explains the Comply overage stems from reports run after the v2 launch; he had no warning that exploring new features would incur extra billing.
Marcus identifies that Clearwater generated 47 on-demand compliance reports against a 20-report plan limit between April 7-9, causing the Comply overage.
Marcus finds the $840 Detect overage correlates with an event ingestion spike during the March outage window.
Commitment1?Someone committed to doing something.
Sarah commits to escalating both disputes internally, asks Clearwater to hold off on the disputed payment, and promises a written Comply response in 48 hours and Detect analysis by end of day.
Risk1?A risk to the account, project, or system was surfaced.
Marcus finds the overage alert configuration for Comply on-demand reports was likely not enabled by default on accounts migrated to v2, so no threshold alert was sent.
Escalation1?The matter was raised to a higher tier during the call.
Natalie challenges the fairness of being charged for outage-related event traffic; Sarah acknowledges the replay/backfill theory and says such a charge should not stand if verified.
What was promised5
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Escalate both overage disputes (Comply and Detect) internally to billing and product teams as high priority today. | Sarah ChenAegisCloud | 10 Apr 2026said “today” | escalate case?Raise the priority or visibility of a ticket, case, incident, or request to a higher-tier team, manager, or leadership, including P1/P2 designation and formal escalation paths. | ||
| Verify event ingestion logs to identify queued replay events from the outage period and document a volume breakdown. | Marcus WilliamsAegisCloud | 10 Apr 2026said “end of day” | internal review or investigation?Conduct QA, audit, verification, investigation, post-mortem, root-cause analysis, or assessment, including testing and analyzing to understand or validate something. | ||
| Provide a full written response on the Comply overage dispute. | Sarah ChenAegisCloud | 12 Apr 2026said “within forty-eight hours” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Send a written summary of the call and next steps. | Sarah ChenAegisCloud | 10 Apr 2026said “before end of business today” | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Hold off on payment of the disputed portions of the April invoice pending investigation. Implied only | No owner | No date given | billing and commercial?Manage financial or commercial account work, including invoices, credits, prorations, overages, contracts, renewals, and service credits, and prepare or send commercial proposals or agreements. |
Left unanswered1
Will the Detect overage be reversed if verification shows it came from queued replay events during the March outage?
AegisCloudBilling
Themes and issues4
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Billing?Calls about invoices, licensing fees, overages, and payment issues. | billing | unexpected overage charges | |
| Billing?Calls about invoices, licensing fees, overages, and payment issues. | overage | comply report limit exceeded | |
| Monitoring?Calls about system monitoring, alerting, and visibility tools and practices. | alerting | missing threshold notifications | |
| Outage?Calls about active service outages or downtime events. | outage | event replay charge dispute |
Numbers stated on this call7
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Total overage charges on April invoice | “just over four thousand dollars” | money | Natalie Simmons | |
| Comply overage amount | “three thousand two hundred and change” | money | Marcus Williams | |
| Detect overage amount | “eight hundred and forty dollars” | money | Ajay Mehta | |
| Included on-demand compliance reports per billing cycle | “up to twenty” | count | Marcus Williams | |
| On-demand compliance reports generated between April 7 and April 9 | “forty-seven” | count | Marcus Williams | |
| Outage visibility gap duration | “six hours” | outage duration | Natalie Simmons | |
| Customer tenure with Aegis | “three years” | duration | Natalie Simmons |
Coaching5
How the AegisCloud side handled the call.
Strengths (3)
Validated customer frustration over the March outage and kept focus on specifics before investigating.
Avoided speculation on the Detect cause, requiring verification of timestamps before making commitments.
Provided clear next steps and timelines for both disputes.
Improvement notes (2)
The request to hold payment on disputed portions was not explicitly confirmed by the customer; follow-up may be needed.
Next step secured?Whether the rep locked in a concrete next step.FYIThe term 'disputed portions' of the invoice was left vague; customer may not know exactly what to withhold.
Clarity?How clearly the rep explained things.FYI
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
9 min captured of 22 min stated. Anything said in the remaining 13 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
2 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 39.2% of a 21.5min meeting; 12.4min after the final turn is unaccounted for
The model's own note: Transcript covers only 8.9 minutes of the call; the meeting may have continued after the recording.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 21,277 tokens