Teach klax IQ from a ticket
The IQ opportunities control appears above the reply composer when klax IQ finds work that is best reviewed with the customer request in view. It can surface:
- Conflicting workspace guidance
- A missing policy or verified answer
- A correction recorded by a teammate
- The reusable resolution workflow for this request
- Approval and action rules
- A teammate's proposed update
- A document or contract workflow attached to the conversation
Open an opportunity to compare the available sources, edit the complete instruction, explain why the change is needed, and review any structured conditions or permitted actions.
What happens when you save
Workspace managers can save, activate, and re-check the current ticket. Other team members submit the update for manager review. A manager can edit the proposed instruction before approving or rejecting it.
Every saved version stays private to your workspace. klaxify records who created and reviewed the change, keeps the earlier versions, and provides a Restore action for managers. Activating or restoring a version causes klax IQ to re-evaluate the current customer request against that version.
Document and contract workflows
When a customer attaches a document or asks about a contract, agreement, renewal, SLA, or statement of work, the ticket can expose a document-review workflow. Keep the original document attached, confirm the terms and dates from the source, define the required approval, and communicate only the approved outcome.
Document-specific facts should not be turned into a universal workspace rule. The reusable instruction should describe how to review that kind of document. klax IQ is instructed not to invent missing terms and to require explicit approval before a document is changed, accepted, or sent for signature.
Good guidance
A complete instruction explains:
- When the rule applies
- Which source or evidence is required
- Eligibility and exceptions
- What klax IQ may recommend or prepare
- Which actions require approval
- What the customer should be told
- When the request must be escalated
Avoid literal customer names, agent names, order numbers, or one-time promises. klaxify resolves customer and sender names from the actual conversation at runtime.
