Who can use this
- Everyone using Ergo, plus admins responsible for setup, source configuration, or output review standards.
Before you start
- Know which connected sources and CRM or reporting setup should support the output you are reviewing.
- Confirm whether you are a user, admin, super admin, or spectator.
- Ask the admin responsible for setup before changing access, recording, integration, template, or field-mapping defaults.
Steps
- Check the source objects attached to an answer, draft, report, summary, insight, deal overview, or CRM update.
- Verify names, dates, commitments, owners, links, prices, and next steps before external use.
- Compare the output against the source transcript, meeting summary, deal or company record, email thread, document, Slack channel, or report field when available.
- Edit the output when only wording needs cleanup.
- Correct the source configuration when the output used the wrong meeting, deal, company, document, channel, field, or meeting classification.
- For CRM or reporting updates, verify field mapping and field permissions before writing changes back.
What to expect
- AI output quality improves when CRM fields, company details, templates, meeting-title phrases, and connected sources are configured.
- Drafts, summaries, insights, answers, and reporting updates can use different source objects and processing states.
- If the output is wrong because source data is missing or mismatched, fix the source or setup path instead of only editing the generated text.
Common issues
- The wrong source, account, or organization context is selected.
- The needed source is disconnected, stale, or unmatched.
- The output used the wrong meeting, deal, company, document, channel, field, or classification.
- A user expects a role, shared meeting view, or reporting grant to include more output visibility than it actually grants.