Connect what you already run.
Your mailbox, your calendar, your identity provider and your system of record, wired into one graph. Nothing to rip out, nothing to re-key.
Four connections, wired all the way through. A short list rather than a wall of logos, and each one carried to the record instead of to an inbox folder.
Your mailbox.
Google or Microsoft, connected once. Riska backfills your recent history and keeps up as new mail arrives.
Your calendar.
The same consent covers calendar, so meetings sync on the connection you already made.
Your identity provider.
SAML or OIDC for sign-in and directory sync for provisioning, so access follows the directory you already keep.
Your system of record.
Send records in on the ids your policy system already uses. A matching id updates the record instead of duplicating it.
“We connected one mailbox and stopped forwarding submissions to ourselves the same week.”
From the inbox to the record. Mail that lands in a connected mailbox becomes a submission, and the submission becomes a change you approve.
It arrives.
Mail syncs from the connected inbox as it lands. Senders and domains on the blocklist are dropped at sync time and never stored.
It routes.
A reference number in the mail matches an existing record first, then a linked thread, then the sender. When nothing matches cleanly it goes to triage rather than to a guess.
It lands.
Attachments are classified and read, and the result is written as a pending changeset. You see every proposed value before the graph moves.
Connections you can govern. Who sees a connection, what it is allowed to touch, and which environment it feeds.
Connect once, enable per environment
A mailbox is ingested once for the workspace. Turn it on in a test environment and in production without a second consent screen.
Scoped to your products
Point an inbox at named products so it never triages business it was not meant to see.
Every file logged on arrival
Uploaded by a person or pushed by a connection, each file is recorded with its source and every job that ran on it.
Bring the sources you already have. Each one lands in the same graph, so a value read off a form and a value pushed from your policy system sit on the same record.
Documents
ACORD forms, loss runs, schedules, invoices and claim files are classified on arrival and read into the fields you defined.
System of record
Send a nested record keyed on your own ids. It is validated against that product's object graph, and anything rejected comes back with the exact path that failed.
People and companies
Every sender becomes a contact. A company is created behind them unless the address is a personal one, so a shared mail domain never collapses into one bogus account.
Connected, then useful.
Everything a connection feeds: the graph underneath, the pipeline that reads it, and the workflows that act on it.
Bring the systems you run.
Send us one real submission email, attachments and all. We will connect a test mailbox on the call and run it through to a record.
Usually 30 minutes. Bring your IT lead if you want the sign-on detail.