Skip to content
← All resources
Published · Updated The Kirado Team

What to check when Kirado asks for review

Understand requests for missing details, action confirmation, and approval before sensitive business changes.

  • Review
  • Workspace

A Work task can read records, prepare a proposal, and carry out supported actions. It is more than a draft generator. Review checkpoints let you inspect the parts that need a decision while Kirado keeps track of the task.

A question is a request for context

Kirado may need a customer identifier, a date, or clarification of the outcome. Answer the question in the existing conversation. If a detail is unknown, say so instead of approving a guess. Providing information is different from approving a business change.

Confirmation is tied to an action

When Kirado shows a proposed change, inspect the action itself rather than only the assistant’s summary. For an invoice, check:

  • The selected company and customer.
  • Items, quantities, unit prices, currency, and tax.
  • Invoice and due dates, plus the intended document status.

For a customer update, check the customer code and the exact fields to change. If the proposal is wrong, request a correction or decline it using the available controls. Review the revised details before continuing.

Sensitive actions need approval

Posting or voiding a business document requires an authorised approval. A conversation does not grant extra permissions, and an action can still be unavailable because of your role, plan, or company configuration.

Approval applies to the proposed action; it is not blanket permission for every later step. Some configured workflows can carry out permitted steps between checkpoints, so do not assume the assistant can only draft or that every step needs a separate click.

Check what actually completed

Read the task result and open the affected record. A prepared invoice, a posted invoice, and a document delivered to a customer are different outcomes. Do not assume one means the others happened.

If work stops, inspect the completed steps before trying again. For the difference between conversation history and business records, see how changes remain traceable.