When OpenTag gets it wrong

Stop or redirect the work

Tell OpenTag to stop in the thread, or use the available stop control in the web conversation. A stop request does not undo an action that has already reached another app.

Check the conversation and source app for what completed. If something was sent or changed incorrectly, identify that result before asking for a repair.

Correct the result

Be specific:

• “That is last quarter; use this quarter.”
• “Exclude trial accounts from the customer count.”
• “The source names Sam as the new owner; you used the earlier handover.”

A correction can change the current work without becoming a standing company fact. Say which you intend.

Make a lasting correction

For a personal preference, ask OpenTag to remember it for you and check Memory. For a company claim, name the wrong statement, replacement and supporting source. Shared company corrections require the appropriate authority and may take time to appear in generated articles.

If the problem is a procedure, edit the skill or routine instructions. For “never post here”, an admin can change the channel's reply permission in Slack settings.

Report the reply

Use the feedback controls on a Slack reply. Thumbs-down can include an explanation. Include what you expected and the source that supports it.

Feedback does not replace a follow-up if you still need the job completed. Reply in the thread with the correction too.

Check common causes

A wrong account, wrong date range, unavailable source, stale wiki article or incomplete import can all change an answer. Ask what was checked and inspect the citations.

If the problem persists, contact support with the conversation link, approximate time and expected result. If an unintended change reached a customer or another tool, say exactly what happened.