2026-11-13

AI CRM lead intake: field maps, duplicates and manager tasks

Specify a bounded CRM intake pilot for a Kazakhstan sales team: source-backed fields, duplicate checks, replay recovery and one verified manager task.

AI CRM lead intake: field maps, duplicates and manager tasks cover illustration

A customer writes in Kazakh: “Сәлеметсіз бе! Алматыдағы кеңсеге 20 орындық керек. Баға ұсынысын қазақша жіберіңіз. Бюджет әлі бекітілмеген”. In English: “Hello! We need twenty chairs for the office in Almaty. Please send a quotation in Kazakh. The budget has not yet been approved.” The manager needs to register the enquiry, retain the quantity, note the reply language and clarify the specifications. If AI instead fills in an assumed deal value and creates three identical tasks when the email is delivered again, it will increase manual work.

Start with one workflow: incoming enquiry → verified set of fields → record or proposed update → one task for the manager. Giving the agent permission to “manage the CRM” is too broad a starting point. Sending quotations, setting prices and changing deal stages are outside this pilot. The sales head gets a map of fields and rules that can be checked against examples before CRM writes are enabled.

The scenario below is synthetic and concerns a company in Kazakhstan. The customer, message and identifiers are fictional; this is not a GolemWorkers implementation case study. The technical boundaries are drawn from current Bitrix24 documentation, but neither a live portal nor a ready-made connector has been tested here. For another CRM, the same business field map must be mapped afresh to its objects and permissions.

Start with one record, rather than the entire pipeline

Define the initial workflow: one approved incoming-message folder, one type of product enquiry and one sales queue. At the first stage, the agent prepares a review package, and the manager approves creation of a lead and its linked task. If a company does not use leads, another CRM object may be the target. Choose it before implementation; do not create both a lead and a deal “just in case”.

For this message, the package contains the original text, a link or internal identifier for the approved source, proposed fields and a separate list of unknowns. “20 орындық” means twenty chairs, not twenty employees. The enquiry is in Kazakh. The budget is unapproved: this means neither a zero budget nor permission to take an amount from a price list. The model must not guess the chair type, price, delivery date or buyer’s legal name.

If you have not chosen a process yet, first compare candidates for an initial pilot. Here, the task is more specific: getting a particular enquiry into the CRM without unreliable fields or unnecessary actions.

Source evidence, matching and approval gates before a request enters the CRM
Evidence and checks come before the write. Conceptual illustration, not a CRM interface.

The field map: value, evidence and what to do when data is missing

This is a business specification, not JSON to send to an API. System field names, required fields, lookup lists and custom fields come from the actual portal. Bitrix24 documents lead fields [1]; check that the fields you need are available in the chosen API version.

On a phone, scroll the table horizontally.

What to transfer Evidence Validation and action
Source and event ID Message envelope: channel mailbox-A, ID demo-0042 The pair must remain stable on redelivery. If missing, quarantine; do not write
Enquiry subject “20 орындық” and the city in the text “Enquiry: 20 chairs, Almaty”; no invented product model
Quantity The phrase “20 орындық” Integer 20; the unit is pieces, not KZT
Reply language The request “қазақша жіберіңіз” (“send in Kazakh”) kk; preserve the original text, which a translation must not replace
Contact Sender address buyer@example.invalid from the envelope A test address; in production, check that the source is permitted and do not treat the address as verified identity
Company Absent from the message Do not invent it; the manager asks
Budget and currency “Бюджет әлі бекітілмеген” (“the budget has not yet been approved”) Budget unknown. KZT is an example setting, not a currency extracted from the email
Assignee and deadline Approved queue and company rule Manager demo-user-17; set the deadline only under the rule, with a time zone

Keep the provenance as well as the result: “from text”, “from envelope”, “from rule” or “unknown”. A value supplied by a rule must not be presented as the customer’s words. A model confidence field cannot replace this check: a confidently invented amount is still invented.

The manager’s task should specify an action: “Clarify the chair type, company name, budget and delivery date; reply in Kazakh.” Links to the CRM record and original enquiry are mandatory. For tasks.task.add, the documentation requires a title and assignee ID, plus the portal’s required custom fields [2]. Check the deadline and CRM linkage separately. An agent saying “task created” does not confirm a write.

Two different kinds of repetition: the same customer and the same event

This is the central distinction in the design. Looking up a contact by phone or email answers “is there a similar record?”. An event key answers a different question: “have we processed this particular incoming message?”.

Bitrix24 documents crm.duplicate.findbycomm, which returns matching lead, contact and company IDs by phone or email [3]. This does not automatically verify identity. A shared purchasing mailbox may be used by several people; one person may send a new enquiry. In this pilot, a match provides candidates for a decision, not permission to merge records or overwrite a contact.

The method has limits: no more than 20 values per call; when no entity type is specified and 20 or more duplicates of one type are found, the search may omit other types [3]. Do not interpret that response as a complete list for the entire portal. Read permissions also constrain what is visible: “I cannot see it” does not mean “it does not exist”.

On a phone, scroll the table horizontally.

Situation Pilot decision What to avoid
Same channel and ID; result already confirmed Return the saved record and task IDs Creating the objects again
Same ID, changed content Stop processing and investigate the conflict Silently accepting the changed text
New event, one matching contact Show the candidate to the manager; link the new enquiry after approval Treating a new enquiry as an old delivery
Several candidates or conflicting contact details Manual review Picking the first candidate or merging automatically
No contact found; source and fields are acceptable Propose a new record; write after approval Promising no duplicates without checking permissions

For idempotency, store a key spanning the organisation, source and event, such as demo-org:mailbox-A:demo-0042, and a fingerprint of the normalised package. This is a design rule in our workflow, not a built-in Bitrix24 guarantee. An email address alone is not a suitable event key: it would cause the same customer’s second purchase to disappear.

Two repeated envelopes converge on one record while a separate request stays separate
A delivery replay is not a new request from the same customer. Conceptual illustration.

The record exists, but the task does not yet

Suppose the CRM accepted a lead, but the connection dropped before the response arrived. Immediately repeating creation risks a second lead. Even if the lead ID has been saved, the manager’s task may still fail to be created: it is a separate operation with a separate outcome.

Use a small state journal: received → reviewed → lead_confirmed → task_confirmed → completed. Each entry holds the event key, package fingerprint, reviewer’s decision, lead ID, task ID and time of the last check. Approval covers specific fields and actions. If the assignee or content changes after review, the earlier approval does not automatically carry over.

When the outcome is unknown, move to unknown, not “failed, safe to retry”. Reconcile the accessible records and technical log using an agreed operation marker. If the outcome cannot be determined, an operator investigates the event; blind repeat writes are prohibited. If the lead is confirmed and the task request has not yet been sent, continue with only the task step. If task creation itself has an unknown outcome, reconcile that task first.

A production implementation needs durable storage, a unique constraint on the key and protection against concurrent handlers. Reconciliation after a failure must account for how soon records become visible and for permissions. A promise of “exactly once” cannot replace these conditions: our local example checks the rules for choosing the next action. It does not prove a distributed guarantee or a working live integration.

What to check in Bitrix24 before estimating the work

As documented on 13 November 2026, the legacy crm.lead.add page is marked deprecated and points to REST 3.0 [4]. A familiar method name does not permit mixing field and response formats across versions. The developer must pin the version and verify object creation, reading and linkage in a test environment. This article contains no ready-to-run API request to copy into a production portal.

Check REST availability separately for the actual plan, trial period and transition terms. Having a cloud account does not establish access [5]. Confirm the CRM mode, required fields, technical user’s permissions, allowed queues, limits and access revocation procedure. Do not grant deletion, contact merging, bulk editing or customer messaging to support a single intake workflow.

For a company in Kazakhstan, add three checks. First, recognise the same product concepts in Russian, Kazakh and mixed-language messages without loosely translating names or formal business details. Second, verify units and currencies: an unlabelled “20” must not become a deal value. Third, give task deadlines an explicit Asia/Almaty time zone or agreed UTC offset; a vague “tomorrow” requires a reference date and a rule. An internal response deadline is neither a delivery date promised to the customer nor a GolemWorkers SLA.

Decide which data may be sent to the model, where the original is stored, who can see the journal and when it is deleted. This requires a separate review of your architecture and data requirements; the article is not a legal compliance assessment. Start with anonymised or synthetic examples. Do not attach passwords, webhook secrets or customer documents to a pilot application.

Pilot artifacts: a field map and eight checks

The article package contains localised blank and completed field maps, a pilot brief template and a small Python example with no network calls. It receives already extracted fields; it does not use a model to interpret emails. The eight synthetic checks cover a new enquiry, a completed replay, a content conflict, a missing contact, multiple candidates, an unknown lead outcome, continuation after a confirmed lead and an unknown task outcome. Running it shows the expected next action; it creates no objects and does not measure AI accuracy.

Use these situations in your portal’s acceptance checks. Verify more than the record’s existence: check the exact quantity, language, source, unknown fields and task linkage. After an interruption, ensure the operator can understand the state without rereading the whole conversation. Then add real, anonymised RU/KK examples authorised by the data owner, and separately measure incorrect fields, missed enquiries, duplicates, review time and unhandled exceptions.

Agree thresholds before enabling writes. Any write without the required approval, loss of the original or uncontrolled repeat creation is a reason to stop this workflow and investigate the defect. Success on a few demonstration examples does not establish quality across the entire mailbox. Assess useful impact through completed enquiries, including correction work; for the financial calculation, use the separate pilot budget template in tenge.

What to bring to a pilot discussion

You do not necessarily need a separate agent for every new field. A general-purpose agent platform, approved tools, extraction templates and validation checks can be reused where they fit the task. You still need to configure the source, portal objects, permissions, lookup lists, duplicate rules and recovery after failures. Staff need training to check evidence, correct fields and handle exceptions. Reuse reduces repeated work, but does not itself establish a ready-made connector or a free integration.

Describe one CRM scenario to discuss with GolemWorkers: which CRM and mode you use, where enquiries arrive, which fields you need, who approves writes and what is prohibited. You can start with a synthetic message and a completed field map. The application form is in Russian. The sensible next step is to check access and define the boundaries of a limited pilot, rather than promise autonomous management of the whole pipeline.

Sources and limits of the example

[1] Bitrix24 lead fields: descriptions, types and custom fields; verify the specific version before implementation.

[2] Create a task with tasks.task.add: required fields and CRM linkage.

[3] Find matches with crm.duplicate.findbycomm: entity types and response limits.

[4] Create a CRM object in REST 3.0 and the legacy lead creation page: do not mix their contracts.

[5] REST API access: check the current terms for the specific account. Product context: the GolemWorkers B2B offering.