Drop the renewal in a channel. Get the analysis back.
Drag a carrier renewal into a Slack or Microsoft Teams channel and it is handled exactly like an upload: same reading, same engine, same record. The analysis comes back in the thread minutes later. Not in a chat tool? Send it from Outlook, forward it, or drop it in a Drive folder.
Four steps, none of which are yours.
Step 1
Someone shares a PDF
Drop the carrier’s renewal into the channel your team already uses.
Step 2
blankit picks it up
It confirms the file landed, then reads the letter, claims pages and rate tables.
Step 3
The engine runs
The full fair-premium sequence, line by line — no lighter chat version.
Step 4
The answer comes back in the thread
A draft analysis in blankit, linked from the reply for the whole channel.
The channel says what the document is.
Tell blankit once what turns up in each channel, or use auto-detect. Unlisted channels are left alone. The types are the same in Slack and Teams.
| #renewals | Renewal proposals | A draft fair-renewal analysis in your pipeline, matched to the client. |
| #claims | Claims experience reports | Into your claims library; the branded report comes back in the thread. |
| #quoting | Carrier quotes | Attached to the client’s open quote case. |
| #commissions | Commission statements | Paid reconciled against owed, shortfalls flagged. |
| #revisions | Coverage revisions | Mid-year changes priced and returned as a branded summary — even from message text. |
| #booklets | Coverage booklets | Into the booklet library, ready to benchmark, compare or build an employee site. |
| #carrier-bills | Carrier bills | A new carrier’s first bill after a move, checked against the rates you sold. |
| #funding | ASO quotes and statements | A self-funding quote set against the insured renewal, or an administrator’s statement filed on the client. |
| any channel | Detect automatically | Skip the mapping: blankit works out what each file is. |
Slack connects in two clicks. Teams takes a code.
Only the connection differs. Everything after a file lands is the same. Paige, the chatbot for your clients’ employees, is a separate app.
Slack
Click “Add to Slack” in firm settings, pair a channel with a document type, then type /invite @blankit in that channel.
Two clicks to connect. Disconnect any time.
Microsoft Teams
Coming soonYour Teams admin adds blankit from the app package we send. Send it the connection code from firm settings, then type @blankit set up this channel in each channel.
No Azure, no tenant ID. The code works once, for thirty minutes.
Your book, answerable in a message.
Mention it or message it directly, in Slack or Teams. It answers from your own records — clients, renewals, claims, quotes, pipeline, tasks — and says so when the data doesn’t hold the answer.
Nothing changes in your account because a message said so.
Ask
Open a task, generate the carrier’s Fair Renewal Summary, record a figure, move a renewal along.
Review
A card shows the exact change. Only the person who asked can approve it, and it expires after an hour.
Recorded
What, by whom and when — in your firm’s audit log.
Email and Drive do the same job.
The route in changes; nothing after it does. Same reader, same engine, same audit trail.
The Outlook add-in
A “Send to blankit” button in Outlook. Open the insurer’s email, say what the attachment is, send.
Installed once per firm; each person connects in seconds.
Forward it by email
Your firm gets one address that takes any carrier document, from any mail client. blankit reads each attachment, files what it is sure of, and asks you about the rest. Type-specific addresses are there too if you want them.
Nothing it is unsure of is filed until you confirm it.
A watched Google Drive folder
Connect a Drive folder and claims experience reports saved there are picked up every hour.
Optionally tidies processed files after a set number of days.
Where the team already looks.
Renewals coming due, quiet cycles, outstanding quotes, loss ratios worth a conversation — in a Slack channel, following the notification settings you already chose.
A workspace has guests in it.
Clients, carriers and contractors turn up in channels. The integration assumes they will.
Only the channels you choose
blankit sees only where it was invited, and processes files only in channels you mapped.
Only your people
Access is matched by email to a user in your firm. Anyone else gets nothing unless an admin allows read-only answers, and only your people can approve a change.
Nothing sent on your behalf
No carrier email, client document or account change without someone approving it.
Handled like an upload
Documents arriving by chat, Outlook, email or Drive are stored and read exactly as an upload is, with the same checks.
More on how your data is handled on the Trust & security page.
Set it up in about five minutes.
Connect, pick a channel, invite the bot. There is a guide inside blankit for Slack, Teams and the Outlook add-in.