Support Case #7570 - Silverline Brands Comply v2 License Upgrade
Aegis will credit $255 for Comply v2 proration billing error
Silverline Brands reported a billing discrepancy after upgrading to Comply v2 on April 7th, as their April 14th invoice showed a full month charge instead of a prorated amount. Aegis support verified that the system calculated proration from April 1st rather than the activation date, resulting in an overcharge. The vendor agreed to issue a $255 credit on the May 1st invoice and send a calculation breakdown for the customer's finance team. The call also confirmed Comply v2 includes all four compliance frameworks and unlimited on-demand reporting.
How the call went
The customer opened neutrally with a billing problem and closed positively after receiving a clear resolution and confirmation of product capabilities.
Opening
0Close
+13 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
- 5
- Questions they asked
- 9
- Turns
- 40
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Dominic Flores?Matched on an initial rather than a full name, so attribution is weaker.
- Michelle Tan?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 raised2?A problem was brought up on the call.
Michelle reports that the Comply v2 upgrade was billed as a full month instead of a prorated amount.
David identifies that the system calculated the prorated charge from April 1st instead of the April 7th activation date.
Commitment1?Someone committed to doing something.
David commits to issuing a $255 credit, sending the calculation breakdown, and escalating the proration issue to the billing systems team.
Decision1?A decision was reached.
David confirms all four frameworks are included and reporting is unlimited under the Comply v2 license.
Recap1?A summary of what was agreed.
David summarizes the actions he will take; Michelle acknowledges and thanks him.
Expansion signal1?Interest in buying more, or in a broader rollout.
Michelle asks whether the v2 license covers SOC 2, PCI DSS, HIPAA, and ISO 27001 for upcoming audit reports.
Confusion1?Someone was unclear or misunderstood something.
Customer's $340 overbilling estimate conflicts with David's $255 calculation; Dominic realizes they used a 28-day month instead of 30.
What was promised3
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Attach proration calculation breakdown to case 7570 and send email summary via case portal. | David KimAegisCloud | 18 Apr 2026said “within the hour” | 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. | ||
| Issue a $255 credit to Silverline Brands account, applied to the May 1st invoice. | David KimAegisCloud | 1 May 2026said “May 1st” | 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. | ||
| Escalate the proration miscalculation to the billing systems team for broader review. | David KimAegisCloud | No date given | 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. |
Themes and issues3
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 | proration miscalculation | |
| Billing?Calls about invoices, licensing fees, overages, and payment issues. | licensing | compliance framework coverage | |
| Reporting?Calls about reporting, analytics, dashboards, and data visibility, excluding compliance-specific reporting. | reporting | unlimited on-demand reports |
Products mentioned
1 mentions
Issue reportedsaid “Comply v2”
Numbers stated on this call7
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Monthly price differential between Comply v2 and standard tier | “$1,275 per month” | money | David Kim | |
| Correct prorated charge for April (24 of 30 days) | “$1,020” | money | David Kim | |
| Proration percentage for 24 of 30 days | “80 percent” | percentage | David Kim | |
| Overbilled amount per customer estimate Differs from vendor's $255 calculation because customer used 28 days instead of 30 in proration. | “$340” | money | Michelle Tan | |
| Overbilled amount per vendor calculation Differs from customer's $340 estimate because Aegis uses a 30-day proration basis. | “$255” | money | David Kim | |
| Proration period after upgrade | “24 days out of 30” | duration | David Kim | |
| Days charged before v2 activation | “6 days” | duration | Dominic Flores |
Coaching4
How the AegisCloud side handled the call.
Strengths (3)
David confirmed the customer's issue by restating it and pulling up account records before diagnosing.
David explained the proration calculation clearly and offered to send the breakdown for the finance team.
David gave a clear recap of next steps and secured the customer's agreement.
Improvement notes (1)
David corrected the customer's day-count assumption without first explaining the 30-day standard month, which caused a brief back-and-forth. Proactively stating the proration basis would have avoided the confusion.
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.
8 min captured of 16 min stated. Anything said in the remaining 8 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
3 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 45.6% of a 16.3min meeting; 8.2min after the final turn is unaccounted for
The model's own note: Transcript is partial; only 8.1 minutes of the call are available, but the recorded portion contains a complete support interaction.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 23,947 tokens