Meeting and Conversation Intelligence
Meeting and Conversation Intelligence
On this page
Internal and external meeting intake, ASR, diarization, topics, summaries, preparation, live assistance, and history. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.
Overview
Package: BND-MEETING · Type: Business capability · Documentation: 1.0
Marketplace listing · Technical reference
Only Overview and Audio & Transcript are owned here. Findings, Decisions & Actions, Context, Files & Versions and Activity are contributed by other packages.
User guide
- Open Meeting Overview to see the purpose, participants, topics and evidence-linked outcomes.
- Use Audio & Transcript to inspect the exact passage, timestamps, speaker attribution and transcript confidence.
- Correct an uncertain span or speaker, then follow affected analysis through the finding and source-history contributions.
Screens owned by this package
- Meeting — Overview —
SCR-MTG-01. - Meeting — Audio & Transcript —
SCR-MTG-02.
Contributions to other screens
- My Development — Recommendations — owned by
BND-DEVELOPMENT; this package contributes analysis or interface content. - My Development — Today — owned by
BND-DEVELOPMENT; this package contributes analysis or interface content. - My Development — Progress — owned by
BND-DEVELOPMENT; this package contributes analysis or interface content. - Overview — owned by
BND-OVERVIEW; this package contributes analysis or interface content. - Meeting — Files & Versions — owned by
BND-EVIDENCE; this package contributes analysis or interface content. - Meeting — Activity — owned by
BND-EVIDENCE; this package contributes analysis or interface content. - Commercial Intelligence — Buying Signals — owned by
BND-COMMERCIAL; this package contributes analysis or interface content. - Relationship & Trust — Observed Signals — owned by
BND-RELATIONSHIP; this package contributes analysis or interface content. - Relationship & Trust — Trends — owned by
BND-RELATIONSHIP; this package contributes analysis or interface content.
Configuration
| Setting | Purpose and behavior |
|---|---|
| Media processing | Select local ASR, language profiles, diarization and alignment capabilities. |
| Speaker resolution | Define matching rules and review thresholds; unresolved speakers remain provisional. |
| Analysis timing | Choose post-meeting processing and separately authorize real-time assistance. |
Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.
Technical reference
The implementation reference identifies DM-MEETING, WFP-MEETING-LIFECYCLE, 5 owned agents, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.
Compatibility and dependencies
- Sources, Integrations, and Evidence Foundation —
BND-EVIDENCE. - Organization, Identity, Access, and Governance —
BND-ORG.
Direct consumers: Decisions, Commitments, Actions, and Follow-Up, Internal Team Intelligence and Personal Development.
Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.
Extensions and enrichment
Add meeting taxonomies, language/model profiles or topic classifiers through declared analysis slots. New detectors produce findings through the shared review contract.
Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.
Versions and upgrades
The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.
- Compare release manifests, permission changes and migrations against the current lock.
- Test package behavior and affected dependent workflows with representative, authorized evidence.
- Promote the signed release after approval and record the resulting lock.
- Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.
Used in solutions
Technology Consulting & Delivery includes this package as mandatory. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.