Who can use this
- Everyone using Ergo, plus rollout owners and admins who need shared vocabulary.
Before you start
- Know which connected sources should be available for your workspace: CRM, email, calendar, Slack, meeting capture, or notetaker data.
- Confirm whether you are a user, admin, super admin, or spectator.
- Ask your rollout owner before changing access, recording, integration, or admin setup defaults.
Steps
- Identify whether the missing context should come from an ingest source, matching context, or destination.
- Use CRM, email, Slack, meeting capture, notetakers, and connected call sources as primary input sources. Use calendar mainly for meeting matching and attribution, not conversation content.
- Treat Pylon and reporting fields as destinations or outputs: Ergo can write call context or enriched fields there, but they are not standalone places Ergo reads conversation context from.
- Confirm the relevant object, channel, calendar event, queue, account, attendee email, or field is accessible and matched to the right Ergo user and organization.
- Treat meeting outputs as separate: capture, transcript, summary, insights, drafts, and reporting updates can become ready at different times.
What to expect
- Freshness depends on the source, sync path, matching, and processing state.
- Insights and drafts can depend on meeting classification, not only whether a recording or summary exists.
- Use product state and code-confirmed behavior over anecdotal expectations when sources disagree.
Common issues
- The wrong source, account, or organization context is selected.
- The needed source is disconnected, stale, or unmatched.
- A meeting attendee, account, or identity mismatch makes an attended meeting appear missing or inaccessible.
- A shared link, reporting grant, or spectator role is expected to provide broader access than it actually grants.