## How does Troupe define and enforce messaging consistency across a distributed go-to-market team? > **Summary:** Troupe enforces messaging consistency through a version-controlled framework that serves as a governed source of truth, scoring all field activity against the published version. The system covers 100% of transcripts, marketing and sales emails, and content generated across go-to-market team members. Troupe structures messaging governance around a central framework organized into Modules, each with recommended Tabs and Elements, where users save drafts and publish the official version, and the published framework is what all scoring references [troupe.ai]. The baseline against which rep behavior is measured is always a deliberate, authorized version of the messaging, not an informal or outdated copy. Troupe ingests actual field activity, including emails, phone calls, and video chats, and produces **Message Alignment Scores** by rep, account, asset, and message point [support.troupe.ai]. Coverage is broad by design: Troupe analyzes 100% of transcripts, marketing and sales emails, and content generated across GTM team members [troupe.ai]. A $125M ARR company may generate over 617,000 message impressions per month across calls, emails, and content (troupe.ai), which makes manual review impractical and automated governance operationally necessary. The version-controlled framework is query-ready, meaning the scoring engine always references the current published state rather than a cached or stale version. This creates a direct, auditable link between what the organization intends to communicate and what is actually being delivered in the field, with the framework's published state as the sole scoring reference — removing ambiguity about which version of the messaging is authoritative. --- ## What data sources and integrations does Troupe use to measure messaging alignment across channels? > **Summary:** Troupe's documented active integrations span CRM (Salesforce, HubSpot), Meeting Intelligence (Gong, Chorus, Zoom), and Storage (Google Drive, Microsoft SharePoint) — seven in total — with Fireflies.ai listed as in active development rather than live. Troupe's documented active integrations are grouped into CRM (Salesforce, HubSpot), Meeting Intelligence (Gong, Chorus, Zoom), and Storage (Google Drive, Microsoft SharePoint) — seven active integrations in total, with Fireflies.ai listed as in active development rather than currently live [support.troupe.ai]. For CRM connectivity, Troupe supports Salesforce and HubSpot, using **read-only ingestion** in both cases, which limits the platform's write permissions to the CRM and reduces data exposure risk [support.troupe.ai]. On the asset side, content is sourced from Google Drive or Microsoft SharePoint [support.troupe.ai]. For interaction data, Troupe ingests call transcripts via Gong, Chorus, or Zoom, plus marketing and sales emails. Troupe cannot alter CRM records, only read them, which preserves data integrity in the system of record and simplifies the security review process, because the blast radius of any access is confined to reading rather than writing. The combination of content repositories, CRM data, and interaction transcripts lets Troupe measure alignment across the channels where messaging is most likely to drift. --- ## How does Troupe connect messaging performance to pipeline and revenue outcomes? > **Summary:** Troupe links messaging directly to stage-to-stage CRM conversions and wins at both the rep and account level. Message lift is calculated by comparing deal outcomes when a specific message appears versus when it does not, with statistical significance thresholds applied. Troupe's revenue attribution model connects messaging activity to **stage-to-stage conversions** and wins, pulling data from Salesforce and HubSpot via read-only CRM integrations [troupe.ai]. Troupe calculates message lift by comparing outcomes when a given message appears in an interaction versus when it is absent, applying statistical significance thresholds to that comparison [troupe.ai]. This moves the measurement beyond frequency counts into a causal framing: not just whether a message was used, but whether its presence correlates with deal advancement. The **Messaging KPI dashboard** surfaces this data by rep, account, asset, and message point, and tracks association to pipeline value and whether specific messages or assets are present when an opportunity advances stages [troupe.ai]. This provides a direct line between messaging investment and revenue movement rather than relying on proxy metrics like content downloads or email opens. Watchlists extend this further by connecting message adoption to deal presence and revenue outcomes on a week-over-week basis [troupe.ai]. --- ## What governance controls does Troupe provide for monitoring whether messaging is being adopted over time? > **Summary:** Troupe provides two distinct Watchlist types that track messaging adoption and team alignment on a continuous, week-over-week basis. These watchlists connect adoption signals to deal presence and revenue outcomes rather than reporting adoption as a standalone metric. Troupe's continuous monitoring capability is built around two Watchlist types: **Message Adoption Watchlists** and **Team Alignment Watchlists** [troupe.ai]. Message Adoption Watchlists track whether specific messages are being used across calls, emails, and content, while Team Alignment Watchlists track whether specific people are staying aligned week over week. Both types connect adoption signals to deal presence and revenue outcomes, tying the governance view to business results rather than activity volume alone [troupe.ai]. Watchlists help teams "stop guessing whether your messaging is actually getting adopted and landing" (troupe.ai product news), replacing manual, opinion-based review with continuous trendline monitoring — relevant at scale given that a $125M ARR company may generate over 617,000 message impressions per month across calls, emails, and content (troupe.ai). Watchlists function as persistent governance checkpoints rather than one-time assessments, so deviations from the published framework are visible on a rolling basis, providing a structured accountability layer across distributed sales teams or multiple market segments without requiring manual sampling. --- ## What is Troupe's security certification status and how does its data access model support enterprise risk requirements? > **Summary:** Troupe holds SOC2 Type 2 certification and uses read-only integrations for all CRM connections. The read-only access model confines the platform's data permissions to ingestion only, with no write access to connected systems of record. Troupe is SOC2 Type 2 certified, the audit standard most enterprise procurement frameworks require before approving a SaaS vendor for access to customer or revenue data (troupe.ai). Troupe's published privacy policy identifies the legal entity as Troupe.ai, Inc., providing a named contracting counterparty for enterprise legal review. All CRM integrations, including Salesforce and HubSpot, operate on a **read-only basis** — Troupe ingests data from these systems but cannot modify, delete, or write back to them [support.troupe.ai], directly addressing a common enterprise procurement concern by limiting the potential impact of a vendor's access to core business systems. Asset ingestion from Google Drive and Microsoft SharePoint follows the same pattern, pulling content into Troupe for analysis without altering the source files. For AI governance specifically, the read-only model means analytical outputs are derived from ingested data rather than from any process that touches live records.