Support Case #1993 - Forge Industries Comply v2 Early Access Question
Forge learns Comply v2 GA is April 7; custom labeling question to be followed up
Forge's security manager Dana Moretti asked whether they could get early access to AegisCloud Comply v2, wanting on-demand multi-framework reporting ahead of a SOC 2 audit. Elena Vasquez told them v2 is in final QA and will hit general availability on April 7, available to all existing Comply customers, with reporting for SOC 2, PCI DSS, HIPAA, and ISO 27001. The update will roll out automatically, though customers will need to map controls to new framework templates. Forge said this removes their need to look at a separate HIPAA point solution. The vendor agreed to send the webinar invite and follow up in writing on custom control labeling.
How the call went
Customer sentiment moved from neutral to clearly positive as v2's timing and fit were confirmed, with Dana enthusiastic about avoiding a separate HIPAA tool and both customers thanking the vendor.
Opening
0Close
+17 scored turns of 43. 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
- 3
- Questions they asked
- 9
- Turns
- 43
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Dana Moretti?Matched on an initial rather than a full name, so attribution is weaker.
- Gerald Hutchins?Matched on an initial rather than a full name, so attribution is weaker.
What happened6
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised3?A problem was brought up on the call.
Dana explains that Forge manages SOC 2, HIPAA, and PCI reporting manually in Comply and that pulling reports for each framework is a lot of work.
Dana asks whether Forge can get early access to Comply v2 because its SOC 2 audit window is approaching and on-demand multi-framework reporting would help.
Dana asks whether v2 supports tagging controls with internal policy numbers; Elena says v2 has a custom metadata option but she will verify and follow up in writing.
Commitment1?Someone committed to doing something.
David commits to sending the April 10 webinar invite and to follow up on the custom control labeling question by end of week.
Decision1?A decision was reached.
Elena reveals Comply v2 is in final QA and will be generally available on April 7 for all existing Comply customers, with SOC 2, PCI DSS, HIPAA, and ISO 27001 reporting.
Expansion signal1?Interest in buying more, or in a broader rollout.
Dana reacts positively, saying this means Forge likely does not need a separate HIPAA point solution and can keep compliance in one platform.
What was promised4
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Send the April 10 Comply v2 customer webinar calendar invite to Dana and her two compliance analysts. | David KimAegisCloud | No date given | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. | ||
| Email David the addresses of the two compliance analysts to add to the webinar invitation. ComplyImplied only | Dana MorettiCustomer | No date given | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Map existing controls to the new framework templates in Comply settings when v2 rolls out. ComplyImplied only | No owner | No date given | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Follow up in writing on whether Comply v2 supports custom control labeling with internal policy numbers. | David KimAegisCloud | 3 Apr 2026said “by end of week” | follow up?Check on the status of a prior action, open question, or pending deliverable, or chase and reconnect with someone to keep an item moving. |
Left unanswered1
Does Comply v2 support custom metadata fields or tags for controls with internal policy numbers?
AegisCloudProduct Roadmap
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 | |
|---|---|---|---|
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance reporting | multi-framework report generation | |
| Product Roadmap?Calls about the product roadmap, planning, launch, release, and delivery of new capabilities. | product release | general availability timing | |
| Infrastructure?Calls about infrastructure, architecture, deployment, upgrades, and system configuration. | upgrade preparation | control mapping configuration | |
| Product Feedback?Calls about feedback on product features, including feature requests and suggestions. | feature request | custom control labeling |
Products mentioned
1 mentions
In usesaid “Aegis Comply”
Numbers stated on this call4
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Comply v2 general availability date | “April 7th” | date | Elena Vasquez | |
| Comply v2 customer webinar date | “April 10th” | date | David Kim | |
| Length of time Forge has used Comply | “about eight months” | duration | Dana Moretti | |
| Expected report rendering time in Comply v2 | “a minute or two” | response time | Elena Vasquez |
Coaching4
How the AegisCloud side handled the call.
Strengths (3)
Elena tied the v2 release details directly back to Forge's specific frameworks and audit pain points, confirming fit rather than just reading release notes.
Elena answered Gerald's question about report lag plainly and without dismissing it, clarifying that the data is continuously synced.
David secured concrete next steps with an owner and a deadline.
Improvement notes (1)
The migration guide will be published on the same day as the GA release, which leaves no lead time for customers to prepare their control mappings ahead of the rollout.
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 26 min stated. Anything said in the remaining 17 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 30.5% of a 25.6min meeting; 17.1min after the final turn is unaccounted for
The model's own note: Transcript is partial (8.4 minutes); analysis covers only the available portion.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 21,749 tokens