§ Triggers & IntakeDocument · REG-TRG-2026.06

A case can start from anything you already run.

An HRIS webhook, a ServiceNow ticket, an inbound SMS, a form submission. Once it’s running, Regisseur reaches out on the right channel — and chases the response so a person doesn’t have to.

Settings, Integrations, Incoming Webhooks — eleven real event sources with provider IDs, webhook URLs, routing rules, field mappings, and case-attribute seeds. — Event-driven intakeEleven event sources — provider IDs, routing rules, and case-attribute seeds

§ 01Intake

Event-driven intake.

Configure event sources and webhooks (HRIS, ServiceNow, messaging, and more) to start the right case automatically, with the trigger payload mapped onto case data from the first moment.

AI server connections — registered MCP servers and connected services, with a two-layer enforcement note. — Connected systemsAI server connections and services, two-layer enforced

§ 02Outreach

Multi-channel outreach.

Cases reach out over email and SMS — and message-correlated replies route back to the right case — through your own providers: SMTP / Microsoft Graph / SendGrid, Twilio / REST gateway.

The connected-tools registry — 33 tools with input and output contracts and agent assignments, including send_email and send_sms. — The tool registryPlatform tools including send_email and send_sms, with contracts

§ 03Follow-up

The follow-up agent.

When a case is waiting on an outside party, an autonomous follow-up agent chases the response on a schedule — under review where review is required — instead of leaving a person to remember to nudge.

§ Next step

Start a case from your trigger — and let it chase the response.

Bring the event that should start the work — a webhook, a ticket, an inbound message. We'll wire the intake, map the payload onto case data, and show the follow-up agent chasing the outside party on schedule.

Book a walkthrough →How it connects to your stack