What Qyra can change on its own

Nothing, until you say so. Qyra can look things up and draft work whenever you ask, but every change to your workspace is shown to you as a plan first and waits for you to approve it.

How it works

Ask Qyra for something that would change your workspace and it first shows what it will do and what will change.

The plan sits there doing nothing until you choose one of three things.

• Approve and apply — Qyra calls the workspace area that owns the change.
• Revise — tell it what to change and it rewrites the plan.
• Cancel — it's dropped.

Contact imports have two separate choices: Save review saves the configuration without importing, and Import Contacts runs that reviewed import. Changing the configuration requires another review.

What happens after approval

Qyra stays in the conversation, makes the approved change in the right part of your workspace, checks the result and tells you what happened. The created or updated item then appears where you normally manage it. You do not need to leave Qyra to finish the action.

Higher-risk changes require clearer confirmation. Risk alone does not create a separate reviewer task. A different reviewer is involved only when the workspace capability explicitly requires independent review.

What Qyra never does itself

Qyra does not perform critical actions that must remain under direct operator or provider control. For those actions, it explains what remains and gives you the information needed to complete it safely.

Qyra reports success only after the part of your workspace making the change confirms it.

What doesn't need a plan at all

Reading does not need an approval plan. Qyra can look up the conversations, contacts, leads, orders, Catalog and reports your current access allows. A previous answer or an open page does not grant access to information you can no longer read.

Simple suggestions do not need a plan. Generated artifacts are different: Qyra keeps a reviewable draft so you can refine it before applying it through the destination owner.

When a plan doesn't finish

• It needs more information. Answer the question in the conversation so Qyra can finish preparing the action.
• The name didn't match. Choose the intended item from the question, or correct its name. Qyra should not replace a name it couldn't find with a different item just because only one is available.
• The customer has no matching booking. Qyra won't repeat another customer's booking instead. Check the customer and booking, or choose to set up a new repeat.
• It needs independent review. The owning capability explicitly requires another qualified person to decide it.
• It needs you to finish a critical step. Qyra provides the details but does not perform the action.
• A step failed on permissions. Qyra checks your permissions again before each step rather than trusting the plan. If your access changed in the meantime, the step stops instead of running.
• The plan needs another review. Requirements may have changed since the plan was prepared. Review the refreshed plan and answer any new questions before approving it. If a stopped step asks you to prepare it again, ask Qyra to revise the plan; retrying that step will not approve the changed requirements.
• The item changed after review. Open a fresh review of the exact item. Approving the older request does not approve changes made since you reviewed it.
• A preparation question changed. The item, available choices or terms may have changed while you were answering. Refresh the plan and answer the current question. Qyra does not apply your old answer to the changed question. Changing an earlier choice may also reopen questions that depend on it; unrelated answers stay in the plan.
• You approved and nothing happened. Check the plan card in the conversation — it shows which step is running and where it stopped.

Related

• What Qyra can do
• Where Qyra gets its knowledge
• Troubleshoot Qyra and Help
• Manage your team and roles