# Sequences (https://riska.io/platform/sequences)

_Sequences_

## Follow-ups that keep quotes and renewals moving.

Multi-step email that goes out from your own mailbox, and everything that comes back matched to the record it belongs to. Quiet submissions get chased, expiring accounts hear from you early, and every reply is on the file before anyone opens it.

## Out on a schedule. Back on the record.

The campaign sends from a real mailbox, and every message that returns is matched to the policy, the claim or the invoice it concerns before anyone opens it.

- **Steps and waits.**: Order the emails and set the days between them. Write each one inline, or pull a saved template into the step.
- **Replies find their record.**: An answer on the thread ends the campaign for that person and files itself against the account it concerns. Nobody forwards anything.
- **Nothing lands in one inbox.**: A message the system cannot place goes to triage rather than to a person, so it is visible work instead of somebody’s unread mail.
- **Nothing sends off a draft.**: The working copy is yours to edit all week. A sequence only enrols and sends once the release holding it is live.

> "“We used to keep a spreadsheet of who had been chased and when. Now the sequence keeps it, it stops the moment someone writes back, and the reply is already sitting on the account.”" — Head of distribution, Regional wholesaler · 12 states

## One engine, every conversation a policy generates.

A sequence is a step a workflow can take, so what starts it is whatever just happened elsewhere in the system: a submission clearing triage, a risk falling to referral, a term approaching, an invoice going past due, a claim opening. The same engine keeps brokers, insureds and the capital partners carrying the book with you current.

### New business.

A submission clears triage, the underwriter has questions, and the producer goes quiet. Three emails across a week from the underwriter’s own address, ending the moment a reply comes back. A risk that falls to referral starts its own conversation instead of waiting in a queue.

### Renewals.

Work the expiring book on a cadence instead of a reminder. Every account inside the window gets the same considered approach, the accounts you want to keep hear from you early, and a meeting on your calendar takes it out of the campaign.

### Collections.

Billing knows what is owed and when it went past due. The chase around it is a sequence: one thread, from the address the account already replies to, ending when somebody writes back.

### Claims.

Keep the claimant, the adjuster and the broker on one thread as the claim moves. Every message lands on the claim rather than in four separate inboxes.

### Capital partners.

The people carrying the book with you need the same picture on the same day each month. Send it on a schedule, from a real address, and keep what comes back on the file it concerns.

## Sent the way a person would send it.

From your own mailbox, inside the hours you set, and filed the way a system would file it the moment anything comes back.

- **Your own mailbox**: Connect Gmail or Microsoft once. The message comes from a real address, and the reply lands in your inbox and in Riska.
- **Sending windows**: Set the hours and the timezone. With weekdays only, a delay landing on a Saturday waits for Monday.
- **Mailbox rate limits**: Daily and per-minute caps on every connected mailbox, so a thousand enrolments never overrun your provider.
- **Variables that resolve**: Insert a field from the recipient’s record with a fallback, or generate the line from a prompt at send time.
- **Inbound routing**: An arriving message is matched by reference number, then by the thread it is already on, then by who sent it.
- **Attachments keep going**: Whatever arrives on the thread is registered against the record and enters the same extraction pipeline as anything else.

## One recipient, start to finish.

Follow a single person through the campaign and you can see every send before it happens, every reason it might end, and where the answer goes when it comes.

### Enrolled.

The moment a record joins, every step is scheduled with its own send time. Nothing waits on someone remembering to hit send.

### In flight.

Each email is queued, sent, and written to the recipient’s timeline. Pause a person and they hold their place; resume and they pick up on the same step.

### Something comes back.

A reply arrives on the sending mailbox and is matched to the thread it belongs to. The message is filed against the record, and the campaign stops for that person.

### Exited.

A reply, a meeting booked on your calendar, an unsubscribe or a bounce ends it. The reason is recorded against the enrolment and anything still queued is cancelled.

## It works because the rest of it is here.

The record a sequence writes to is the record extraction, rating, billing and claims already work from. A workflow in any of them can start a campaign, and what comes back returns to the same place.

## See the loop close on your own book.

Bring the follow-up list you keep in your inbox. We will build it as a sequence and show you exactly where the replies land.