Support and change management
When something goes wrong, record the organization, project, affected record and approximate time. Include useful status or error details in your support request. Do not send passwords, API keys, applicant documents or unnecessary personal data.
An answer is missing or unexpected
Check that the question is being asked in the intended project, that its sources have finished indexing and that the source contains the relevant information. Review project sharing and document access using an account that represents the affected user. If restricted content appears in an answer, pause the affected use and contact your administrator.
A conversation or application changed after an update
Check which published settings and source content were in effect when the work started. Existing conversations or applications can retain the settings they started with, while new work uses the current published settings. Current access permissions still apply. Do not change an existing record to match today’s settings without reviewing its history.
A review or handoff seems stuck
Check the current status, assigned reviewer, expected information and any deadline. Some work may be waiting for an applicant or a staff member. If an external handoff was attempted, check its delivery status and destination receipt before retrying; a repeated attempt can create duplicate work.
Before changing or rolling back a live workflow
Pause affected new work when needed, identify applications or conversations that are already in progress, and confirm that their owners and review history will be preserved. Test the proposed change with sample data. If delivery status is uncertain, reconcile it with the destination before sending again.
What to include in a support request
- Organization and project names or IDs
- The affected conversation, application or delivery ID
- Approximate time and the action that led to the issue
- Relevant status, error message and configuration version, if available
- What you already checked and whether the issue affects one user or several
Your administrator owns organization access, source permissions and institutional policy. The deployment operator owns infrastructure and backup procedures. Use the support channel provided for your deployment for help with product behavior.