Rylvo

Control Automation & Reports

Work that runs
while you don’t.

Give an agent a job and a schedule: a Monday brief, a daily check, a watch that only speaks up when something changes. It runs, saves the answer and sends it where you work.

Agent runs

Your agent, on a schedule.

Pick a bot or a whole agent team and write the job. It works just as it does in a conversation: same knowledge, memory, guardrails and tools. Start from a daily brief, a weekly report or a watch that sends only when something changed. Hand it its last answer, so each run picks up where the previous one stopped.

Built-in checks

10 checks that run themselves.

The jobs every team ends up doing by hand: reading conversations for problems, watching health and spend, running tests on a schedule.

  1. 01Edge-case scan

    Finds problems in the last day of conversations

    Problems
  2. 02Complaint watch

    Counts escalated, flagged and complaint-like conversations

    Problems
  3. 03Knowledge gaps

    Finds questions your bot couldn't answer well

    Problems
  4. 04Conversation quality

    AI reviews a sample of recent conversations

    Problems
  5. 05Connector & MCP health

    Flags failing, slow or signed-out integrations

    Health
  6. 06Cost & usage watch

    Adds up spend and warns before the budget

    Health
  7. 07Guardrail audit

    Lists guardrails and how often each fires

    Health
  8. 08Dev review

    Failed runs, open patterns and waiting insights

    Digest
  9. 09Red-team digest

    Summarises the last week of red-team tests

    Digest
  10. 10Scheduled test run

    Runs a bot's test suite

    Testing

Delivery

Sent where you already look.

Each destination gets a message shaped for it, not one blob pasted everywhere. Turn a channel off and the schedules that use it stay as they are.

  • Email
  • Slack
  • Microsoft Teams
  • Discord
  • Webhook
5
kinds of destination
3
retries for a run that fails
5
delivery attempts before a message is given up
12
parts of Rylvo a report can read

Reports

The numbers, in their inbox.

Choose what a report reads (edge cases, conversations, approvals, alerts, red-team tests, guardrails and more), which bots, and who gets it. Send it now, or every day, week or month. Pick a model to add a written summary with recommendations.

  • Weekly ops health

    Edge cases, complaints and escalations, failed agent runs and guardrails — the week at a glance.

  • Quality & safety digest

    Edge cases, guardrails and red-team results — how safe and correct the bots were.

  • Complaints & follow-ups

    Escalated conversations, approvals, alerts and reviewer insights waiting for someone.

Questions

Asked often.

What does an agent run actually do?
On each run Rylvo sends your instruction to the bot or agent team you chose, exactly as if a person had asked it, with its prompts, knowledge, memory, guardrails and tools. The answer is saved on the run and sent as a formatted report by email and to the channels you pick.
Do automations run in Test?
On a schedule, agent runs, reports and test-suite runs happen in Production only. The other checks also run in Test, but there they only save their results; nothing is sent. Press Run now on an agent run in Test to see its answer: it is saved, not sent.
How precise is the schedule?
Schedules use the time zone you choose. Due work is picked up about every 5 minutes, so a 9:00 run starts within a few minutes of 9:00: operational scheduling, not second-level cron.
What happens when a run fails?
It retries up to 3 times with a growing wait, and the run history shows the failure. An agent run can also tell its recipients that it failed. Deliveries to Slack, Teams, Discord and webhooks are retried several times before they are given up.
Can I schedule my own code?
No. You schedule an agent run, or one of the built-in checks. If the job needs logic, give it to an agent with the tools it needs and schedule that agent.
Which plans include Automation?
Automation starts on Lite, with 10 scheduled tasks; Pro has 25 and Enterprise is unlimited. Some checks also need the feature they read, such as Red Team.

Set it up once.
Hear about it every Monday.