Skip to Content
Using NairoProductActions

Actions

Actions are structured, repeatable tasks that teams can run to produce defined outputs, such as memos, reports, tables, draft emails and other deliverables.

Where the Assistant supports open exploration, Actions help teams run a more defined sequence of steps with clear inputs and expected results.

What Actions are for

Insurance teams repeat many review patterns, such as triaging a claims file, preparing a comparison memo, running a structured checklist or drafting a referral note.

Actions make these patterns easier to run without rewriting the same prompt each time.

They can be used on their own or made available to Experts where configured.

Typical uses include:

  • Preparing a summary or memo
  • Comparing documents
  • Running a checklist
  • Drafting a broker communication
  • Creating a structured review
  • Producing a table or report for review

How Actions work

Actions library

The Actions library lists Actions available in the workspace.

Users can browse, search, filter by category and type, sort by usage and mark favourites where supported.

Actions may include system-provided templates and custom Actions created for a specific team or process.

System Actions can be duplicated and adapted into custom Actions for the organisation’s workflow.

Running an Action

Opening an Action shows its definition and run interface.

A typical run may involve:

  • Inputs - provide required files, text or context
  • Step execution - run the configured steps in sequence
  • Deliverables - review outputs in the deliverables panel
  • Follow-up - continue working in the context of the run where supported
  • Timeline - review execution progress or run events where supported

Actions are designed to produce outputs for user review. They do not remove the need for human validation.

Custom Action editor

Teams can create or edit custom Actions.

The editor may define:

  • Steps and prompts
  • Input requirements
  • Expected deliverables
  • Deliverable type per step
  • Model selection where available

Custom Actions help teams turn repeated work patterns into more consistent processes.

What Actions are not

Actions are not unattended automation.

They do not make business decisions on their own.

They are not a replacement for core policy systems, claims platforms, underwriting engines or internal approval processes.

They do not guarantee audit-grade records on their own.

Each Action run should be reviewed by a qualified user before outputs are used in business decisions.

  • Experts - specialist assistants that can use selected Actions where configured
  • Projects - persistent document workspaces for case materials
  • Insight Table - structured review across many documents
  • Core Concepts - reviewing outputs before use

Getting started

  1. Browse the Actions library for tasks relevant to your team
  2. Run a test Action with sample inputs
  3. Review the deliverables before using them
  4. Duplicate a System Action and adapt it to your process
  5. Make useful Actions available to Experts if your team works through specialist assistants
ExpertsInsight Table