Drop the renewal in a channel. Get the analysis back.
Most Slack integrations just send you notifications. This one does the work. Drag a carrier renewal into a Slack channel and it is treated exactly as if you had uploaded it — same reading, same actuarial engine, same record — and the result comes back in the conversation a few minutes later.
Four steps, none of which are yours.
Step 1
Someone shares a PDF
An advisor forwards the carrier’s renewal into the channel your team already uses for renewals. No upload screen, no tab switch.
Step 2
blankit picks it up
It marks the file so you know it landed, then reads the renewal letter, the claims pages and the rate tables.
Step 3
The engine runs
Pooling stripped out, incurred-but-unreported claims added, experience trended and credibility-blended, and the carrier held to their own target loss ratio — line by line.
Step 4
The answer comes back in the thread
A draft analysis waiting in blankit, linked from the reply. Everyone in the channel sees it at the same time.
The channel says what the document is.
You tell blankit once what usually turns up in each channel. After that it knows what to do with anything you drop there, without asking. Channels you have not listed are left alone.
| #renewals | Renewal proposals | A draft fair-renewal analysis lands in your pipeline, matched to the client. |
| #claims | Claims experience reports | Parsed into your claims library; the branded report comes back in the thread. |
| #quoting | Carrier quotes | Attached to the client’s open quote case, and the case moves to received. |
| #commissions | Commission statements | Reconciled paid-against-owed per group, with shortfalls flagged. |
| #revisions | Coverage revisions | Mid-year plan changes priced and returned as a branded summary. Reads the message text too — no PDF needed. |
Your book, answerable in a message.
Mention it in a channel, send it a direct message, or use a slash command. It reads your own records — clients, renewal history, claims experience, quotes, coverage, assumptions, pipeline and tasks — and answers from the actual figures. When the data doesn’t hold the answer, it says so instead of estimating.
Nothing changes in your account because a message said so.
Ask
Open a follow-up task, generate the carrier one-pager, record a figure the carrier just disclosed, move a renewal along the pipeline.
Review
You get a card showing the exact change, with Approve and Dismiss. Only the person who asked can approve it, and it expires after an hour.
Recorded
What was applied, by whom, and when — in the same audit log as every other change your firm makes.
Where the team already looks.
Renewals coming due, cycles that have gone quiet, quotes still outstanding, loss ratios worth a conversation. Point them at a channel and they arrive alongside the in-app and email versions — using the notification settings you already chose, so nothing you muted comes back.
A workspace has guests in it.
Slack is a shared room — clients, carriers and contractors turn up in channels. The integration is built on that assumption rather than around it.
Only the channels you choose
blankit sees channels it has been invited to, and processes files only in the ones you have explicitly mapped.
Only your people
Access is matched by email to a blankit user in your firm. Guests, clients and carriers in shared channels get nothing.
Nothing sent on your behalf
No carrier email, no client document, no change to your account happens without someone approving it first.
Canadian hosting, unchanged
Documents shared through Slack are processed and stored in Canada, exactly as an upload or a forwarded email would be.
More on how your data is handled on the Trust & security page.
Set it up in about five minutes.
Connect the workspace, pair a channel with a document type, invite the bot. There is a guide inside blankit that walks you through it.