Stuck on something? A person answers.

In blankit: Settings → Connections → HubSpot, Zoho & Dynamics 365. Salesforce has its own panel just above. Zoho is the quickest — about thirty seconds, with no key to create: you press Connect, sign in to Zoho, and approve blankit. HubSpot takes a couple of minutes and needs a Super Admin. Dynamics 365 is a job for whoever manages your Microsoft account. There’s a step-by-step guide inside blankit — press Start and search for “Connect your CRM”. More on what each one does on the CRM integrations page.

Zoho keeps each account in one region, and blankit is registered separately in each. Canada and the United States both work — plenty of Canadian firms are on the US one, since that was the only choice before Zoho opened a Canadian data centre. Any other region is listed but not yet switched on; email us and we’ll enable yours. Not sure which you’re in? Check the address bar in Zoho: zohocloud.ca is Canada, zoho.com is the United States.

That’s usually a book where several clients share a first or last word — a corporate family, or a group of numbered companies. blankit will never guess between two similar names, so it shows them to you instead of picking one. Work down the list and choose the right record; each choice is remembered, and anything you dismiss stays dismissed. If a client is spelled very differently in your CRM, add that spelling as an alias on the client record and run the match again.

Matching your clients and reading renewal dates are two separate steps. After the match, pick which field on your company records holds the date — it’s a dropdown, so you choose by name rather than typing anything — then press Fill in renewal dates. It only fills gaps: a renewal you’ve already scheduled keeps the date you gave it. If you don’t track renewal dates in your CRM, leave the field unset — matching still works without it.

Not unless you ask it to. Out of the box blankit only reads. If you want figures written back, you turn that on yourself and then choose exactly which ones go where. Disconnecting changes nothing in your CRM either — it just stops blankit reading from it.

Then you don’t need one — a CRM is entirely optional. If you keep your clients in a spreadsheet, go to Clients → Import client list and upload it. blankit shows you exactly what it will do before saving anything, and you can upload the same file again later to refresh it.

Yes, any time. Clients → Export client book downloads an Excel file with one row per client — carrier, lives, primary contact, policy numbers, the renewal in progress, what the group pays today and how the last renewal ended, with expected and paid commission — plus every renewal on file and each client’s premiums by benefit. Need it for a CRM import? Export as CSV gives you the same client list as one plain table, and Renewal history (CSV) one row per renewal. Filter the client list first and Export these clients downloads just the ones on screen.

Yes. On the client’s Documents tab, Download all documents gives you one zip of their booklets, contracts, renewal documents and reports, negotiation rounds, client packages and carrier quotes. For the whole book, use Clients → Download all documents: blankit prepares it in the background, with a folder per client, emails you when it is ready, and deletes it after seven days. For a few clients, filter the client list and choose Their documents (.zip).

Use the Forgot password link on the sign-in page to reset by email. If your firm requires two-step verification and you’ve lost access to your authenticator or passkey, your firm’s admin can reset it — or email us and we’ll help.

Every figure blankit extracts can be reviewed and corrected before anything is sent anywhere — nothing goes to a carrier or a client without you approving it. If a renewal reads with the same benefit twice, blankit shows you both rows and asks whether they are one benefit printed twice or two different benefits — it never guesses which. And a renewal whose premiums don’t add up to the carrier’s own printed total, or whose claims are wildly out of scale with them, is not priced at all: blankit shows you both figures and asks which one is wrong, rather than producing a report on a premium it cannot stand behind. Where a carrier splits extended health across several experience pages, blankit also checks that the health line’s claims cover all of them — a line built from one page reads calmer than the group actually ran, and that costs you the argument for challenging it. And if you spot a wrong figure after an analysis is saved, you don’t need to upload the document again — “Correct the carrier’s figures” on the renewal re-prices it in place. If a carrier’s format is consistently read wrong, email us the document type and carrier name (not the document itself) and we’ll tune the reader for it.

Upload their next document as usual. When a booklet arrives under the new name and clearly belongs to an existing client — same policy number, or you attach it yourself — blankit renames the client and keeps the old name as an alias, so everything filed under the old name (claims, commissions, past renewals) stays with the same client. The upload tells you what it recorded, with an undo, and a match made on policy number alone is flagged for you to confirm. An older document being backfilled records its name as a former name instead of renaming anyone. A group that also adds a second class of coverage lands as one client with two coverage classes, not a duplicate.

Carriers often issue one booklet with a separate schedule for each class — Management and All Other Employees, Salaried and Hourly. blankit spots this when it reads the booklet. Until each class is set up, the employee chatbot reads the whole booklet and asks the employee which class they are in before quoting anything that differs by class. To give every class its own entry, open the booklet in your library and choose Set up each class: tick the classes, name them the way employees know them, and blankit reads each one from the same PDF. Employees then pick their class when they look their plan up, and each class can have its own chatbot link.

In Canada. blankit runs in AWS’s Montreal region (ca-central-1), and client documents, the database and backups are stored there. Reading a document is a separate step. Documents are read by Anthropic’s Claude through Amazon Bedrock. Requests enter AWS in Montreal, and AWS may process them outside Canada, including in the United States, under the AWS Data Processing Addendum. blankit runs Amazon Bedrock with data retention set to “none” (zero data retention). AWS states that in this mode no request or response data is written to durable storage or shared with the model provider. The full picture — sub-processors, encryption, access controls — is on the Trust & security page.

Once you’re signed in, every page has a “Found an issue?” button in the bottom-right corner. Say what looks wrong and press Send — the page you were on, and the client or renewal it belongs to, are attached for you, so there’s no need to describe where you were. A person on the blankit team reads every report.

Email hello@blankit.ca with “Security” in the subject line and we’ll prioritize it. Please don’t include client data in the report itself.