IntelligenceQuickstart15 min

Operational Intelligence quickstart

Connect a source, watch events arrive, and set up your first AI Worker with a person approving what it does.

In about 15 minutes you’ll have events from one of your systems flowing into Operational Intelligence, the right people alerted, and an AI Worker proposing the next step for someone to approve.

You need: a Tyms account, and a system that can send events. A payment processor, CRM or your own app all work.

Sign in at ops.tyms.ai with Sign in with Tyms. Overview opens with a Get set up checklist. Each step builds on the one before:

  1. Connect a source. Choose Add a source and connect the system whose events you want to watch.
  2. Receive your first events. Choose Test a payload to send a sample, and check that it arrives.
  3. Choose where alerts go. Choose Add a channel, so the right team hears when something needs a person.
  4. Define who needs what. Choose Create a segment: a group of customers or records in a given stage, such as "invoices more than 7 days overdue".
  5. Act on it. Choose Set up a worker and pick a preset, such as dunning, a KYC document chaser or lead follow-up. It installs switched off, so you can review it before it runs.

Your first worker proposes, a person approves

New workers start in Proposes only. When a worker wants to act, your team channel gets a message like Approve: send a reminder to Acme Ltd. Anyone with the link can choose Approve, Send my edit or Reject. The link expires after a set number of hours.

ExampleOverdue invoice, proposed by the dunning worker

Approve: send a payment reminder to Acme Ltd

  • Invoice 1042 entered the "overdue 7 days" segment
  • Drafted a payment reminder
  • Posted it for approval in the finance channel

Approved by Peter, and the reminder was sent. The item’s run history shows every step.

Before you switch a worker on, choose Run dry-run to see what it would have done against past events, with nothing sent. When you trust it, change it to Acts on its own.

Keeping an eye on it

  • Items, Handoffs and Outcomes show what each worker has done. Every item has a Run history, with every step the worker took.
  • Each worker has a monthly budget, shown as "USD x of USD y". It stops when the budget is reached.
  • Handoff guardrails limit how many messages a person can receive, and how often.

What’s next