KeyCRM integration
A customer asks about a product at two in the morning. Your assistant answers from your KeyCRM catalogue and registers them as a buyer — without creating a second copy of someone you already have. In the morning you ask it what orders came in and put the promising buyers onto a pipeline, from the same chat.
Connecting KeyCRM
Copy the API key in KeyCRM
Settings → General, the API key field. If there is no key yet, generate one; if there is, copy it with the button next to the field.
Paste it into the assistant
Open the assistant, turn on Enable integration, choose KeyCRM and paste the key. It is checked against KeyCRM on the spot — a wrong key is flagged in the same window, before anything is saved.
Choose the tools for each level
Decide what the assistant may do in any conversation and what only you may ask of it. A tool that relies on a list switches that list on with it, so nothing ends up half-configured.
Try it as a customer, then as yourself
In the Playground, ask about a product the way a customer would; then ask for today's orders. Open KeyCRM and look at what appeared.
Where online sales lose customers
The customer is in the direct messages, not in the CRM
Instagram and Telegram are where people actually ask. The conversation happens there; the buyer card in KeyCRM gets created later, by hand, if somebody remembers.
The same person, three times
Once from Instagram, once from the website, once from a phone call — with a different spelling each time and a phone number with and without the country code. One customer's history ends up scattered across three records.
Product questions wait for a manager
What does it cost, what options are there, what exactly is in the set. The answer is sitting in your catalogue, but at night and at the weekend there is nobody to read it out.
Checking the day takes five screens
What came in today, which orders are still unpaid, what is waiting at which pipeline stage. The answers all exist in KeyCRM; they just take a lot of clicking to put together.
Two access levels, one assistant
KeyCRM in Mingleego is nineteen tools, and they are split by who is asking. The User tools are safe in any conversation, including with a stranger on your Instagram at midnight: create and update buyers and companies, link buyers to a company, browse your products and open a product card. What they cannot do is list anything — no buyer directory, no company directory, no orders. A visitor gets help with their own question and never a look at your client base. The Customer tools are for you, the owner of the account: the buyer and company directories, orders with their full details, sales pipelines with their stages and cards, and the custom fields your team has added. You ask for today's orders in the Playground the way you would ask a colleague. Three rules hold for every tool. The assistant asks before it creates or changes anything. It shows long lists one page at a time and asks before loading the next. And it keeps KeyCRM's internal ids to itself — you see names, statuses and amounts, never a UUID.
What it looks like in practice
A 2 a.m. question from Instagram
The assistant answers from your catalogue and records the person as a buyer, so the manager starts the morning with a contact, not a screenshot.
Every channel writes to one KeyCRM
Instagram, Telegram, WhatsApp, the website widget — one assistant, one account. No exports and no second inbox.
A returning customer stays one record
Checked by email, then by phone: the person who ordered in spring is recognised in autumn instead of being created again.
The morning review in one question
In the Playground: which orders came in yesterday, which are still unpaid, show me the largest one.
A warm conversation onto the pipeline
Ask the assistant to put the buyer onto a pipeline — it shows the stages, you confirm one, the card appears.
In the language they wrote in
Ukrainian, Polish, English — the language is detected from the message, and the buyer card is filled in correctly either way.
What the nineteen tools do
Buyers, without the duplicates
Before creating a buyer the assistant looks for one by email, then by phone, and reuses the match. Only when there is none does it create a new buyer — after confirming the full name, email and phone. A birthday or a second phone added later keeps the existing contacts and drops the repeats.
Companies and the people in them
Create a company from confirmed details, update only the fields that changed, and link buyers to it — when it is created or any time later. For B2B orders the organisation and its people end up connected.
Your catalogue, one page at a time
The assistant browses your products in small pages and asks before loading more, then opens the full card of the product that matters. Answers come from KeyCRM itself, not from a copy that went stale overnight.
Orders — the overview and the details
For you as the owner: a paginated list with buyer, status, total, payment state, date and source; then the whole order — products, quantities, prices, discounts, delivery, payment, comments and dates.
Pipelines, stages and cards
For you as the owner: your sales pipelines and their stages, the cards sitting in them, the full detail of any card — and a new card for an existing buyer, in the pipeline and stage you confirm.
Your custom fields, understood
For you as the owner: the assistant reads the custom field definitions your team added to KeyCRM, with option values when needed, so the fields specific to your business mean something to it too.
Before you connect KeyCRM
No. KeyCRM connects with the API key from Settings → General — there is no developer console and no OAuth application. Of the CRMs here it is the quickest to connect: copy the key, paste it, choose the tools.
Let every conversation leave a buyer card behind
One API key, pasted once, and conversations on every channel start landing in KeyCRM as buyers — with no duplicates to clean up afterwards.
Create an assistant