Skip to content

Automations

Work that starts on its own.

Set a trigger and Poh does the work without being asked: when new mail arrives or on a schedule. Every run is recorded for its owner, and a run Poh works through is a conversation they can open and continue.

The automation editor with a new email trigger and a plain-English check

Visible

Nothing happens in the dark.

Every run shows what triggered it and what it changed. When Poh works a run, open it and continue the conversation from where it stopped.

An example run
  1. TriggerNew email in submissions@
  2. Check“Is this a new submission?” Yes
  3. ReadThe email and its four attachments
  4. FileDocuments saved to the submission on IMS
  5. DraftReply to the broker, waiting in Outlook
  6. RecordThe run, kept for its owner and audited
  • Each message handled once
  • Runs with its owner’s access
  • Every run audited
  • Pick up Poh’s runs in chat
An automation run shown as a conversation

How it works

  1. Pick a trigger

    New mail in a personal or shared inbox, or a schedule.

  2. Describe the work

    In plain English, or with a saved skill your team already uses.

  3. Review the runs

    Each run shows what started it and what it did. Open a run Poh worked through and continue from there.

What automations do

  • Email triggers

    Filter by sender and subject, or add one plain-English check.

  • Schedules

    Daily sweeps, such as policies coming up for renewal.

  • Real outputs

    Update a page, file documents on IMS, and draft replies in Outlook.

  • Team inboxes

    Managers attach automations to a shared inbox for the whole desk.

  • Approved up front

    Setting up the automation is the approval, and every run is audited.

  • Built from skills

    Reuse the workflows your team has already saved.

Hand Poh the work that repeats.

We'll connect Poh to your systems and work real examples with your team.

See it on your data