Why assignment rules skip imported trade show lists

After a trade show, your file reflects field conditions rather than a clean customer table. Phone formats vary, company names are shortened, one person may be scanned twice, and a badge may contain only a personal email address. Importing every row without preparation can create duplicate people, incorrect ownership, and tasks without context. The first follow-up therefore begins with decisions made before upload.

Sending a file to Zoho CRM does not start follow-up by itself. Automation options on the final screen run only when selected individually. An assignment rule is limited to choosing an owner, optionally creating a follow-up task, and sending unmatched records to the default user. No universal response interval applies. Your organization must use the commitment made in conversation and its approved working calendar.

Importing a file does not start follow-up

Treat the file as a controlled data-entry package first. When each row's source, distinguishing information, and expected owner remain unclear, generating tasks distributes uncertainty to the sales team. To use an assignment rule, relevant automation, or a follow-up task after import, select each option explicitly. Processing may continue for some time after the file finishes importing.

One person's name appears on two rows after the event. One row has a corporate email, while the other has only a phone number. Because email is the matching field, the phone-only row creates another record. The user later looks for approximate matching to combine them but finds none. Merge tools depend on exact values in selected fields.

Do not treat the assignment rule as a complete follow-up engine. It does not find duplicates, merge records, or determine an appropriate contact time. Its three actions remain limited. Without a commitment made during the conversation, your organization's accepted working pattern determines follow-up timing. Creating the task also does not mean an external message has been sent.

The import screen requires one of three behaviors

The Zoho import screen requires adding new records, updating existing records only, or performing both actions. Record ID, Email, or Record Name can identify duplicates or existing records, with case-insensitive matching. During updates, you may also keep blank file values from overwriting existing data. The selected behavior governs the entire import once processing begins.

Use the module identifier as a matching field only when re-importing records that were previously exported. Choosing it for another file can create duplicates. An import cannot be cancelled after it starts, but it can be undone within 30 days. File history remains available for 60 days, while record-level details for added, updated, and skipped rows remain for only 7 days.

Row ceilings are 10,000 for Standard, 20,000 for Professional, 30,000 for Enterprise, and 50,000 for Ultimate. CSV limits are 10 MB for Standard and Professional, 25 MB for Enterprise and Ultimate, and 5 MB for Free. VCF is limited to 5 MB in every edition. XLS, XLSX, and VCF accept no more than 5,000 records per batch.

Fix the field contract before touching the file

When establishing a lookup relationship, the file must contain the target record's name or a reliable identifier. Picklist values must already exist in the relevant CRM field. The first row must contain column headings. Checkbox values must use True or 1 and False or 0. Content following more than ten consecutive blank rows may be ignored during processing.

You cannot proceed without mapping the module's mandatory fields. These include Last Name for Leads and Contacts, and Deal Name plus Closing Date for Deals. The Zoho mapping screen can create fields, separate mapped and unmapped columns, reset mappings, or apply automatic mapping. A single source column may also be connected to multiple CRM fields.

You can fill blank mandatory fields and assign a default value to every record. Defaults are unavailable for Description, Call Duration, Auto number, unique fields, formula fields, and multi-select lookup fields. Assigning a default to an already mapped field replaces that mapping. If you combine event and row identifiers into a key, mark the resulting field as unique.

Assignment rules work through only three entry channels

An assignment rule operates only for records created through an import, web form, or API. It does not trigger for a manually created record. The rule can choose an owner, optionally create a follow-up task, and give an unassigned record to the default user. Recording an assignment reason or date requires a separate workflow field update using the same criteria.

After the upload, records open under their assigned owners. The next week, one of those contacts phones with a new request. A consultant creates the record manually, so the assignment rule does not run. The record stays with its creator and never enters the distribution list. This is the defined behavior of that entry channel, not an intermittent failure.

If no criterion matches, the record does not remain ownerless. For an import, the default user is the person who started it. The documented super administrator fallback applies to the web form channel only: when the user who created the web form rule is deactivated or deleted, ownership passes to the super administrator. No email notification to administrators is documented. In Zoho CRM, every record has one user as owner. A dedicated user account and sharing rule can model a queue.

Separate exception review from the sales queue

Owner assignment, automation, a follow-up task, and manual lead approval are separate choices on the final screen. An unselected action does not run. Date-based workflows trigger independently because they operate from dates. Notify Assignee does not work for a task selected here. With manual approval enabled, records pass through administrator review before they are assigned.

Do not organize exception review around ownerless records, because unmatched rows go to the default user or, when necessary, the super administrator. Keep multiple matches, unknown sources, undefined interest topics, and duplicate keys outside the regular sales sequence. Call the operational person responsible for correcting these records the data manager, avoiding confusion with a formal legal status.

This view defines the scope of review only. It does not create a task, correct a record, or begin external communication. The next action waits for the data manager to open the record and choose the appropriate correction. Uncertain rows therefore stay outside the normal sales order, while records accumulating under the default owner receive separate, user-led verification.

The first follow-up window is not permission

Set follow-up timing from the commitment made during the conversation or, when none exists, from your organization's working pattern. Consider an appropriate contact window separately for someone in another country. Do not treat your organization's system time as the recipient's local time. The first task makes the user responsible for validating the record and selecting a suitable communication channel.

Creating a task in Zoho does not mean a message was sent or communication permission exists. Scanning a badge is not, by itself, a legal basis or permission to communicate. Information stored in a permission field represents a record; it does not create the underlying basis. Keep the task, channel decision, and permission assessment as separate operational steps.

If automated external communication is contemplated, your organization must assess its authorized approval, transparency duties, and requirements under Law No. 6563 and the İYS framework for its own circumstances. CRM settings do not replace that legal assessment. Before sending, the initial task should require the user to check the person's record, the appropriate channel, and the basis determined by the organization.

Test every path with a small pilot file

The pilot should contain a single match, multiple matches, a blank email, a shared phone number, a picklist value absent from CRM, and missing lookup information. It should also test a duplicate key, an inactive user, and a promised date in another time zone. For every row, trace the import summary, ownership, task, review view, and reporting result.

Import requires the Import profile permission. Supported row ceilings remain 10,000 for Standard, 20,000 for Professional, 30,000 for Enterprise, and 50,000 for Ultimate. CSV size is 10 MB in the first two editions and 25 MB in the latter two; the documented Free limit is 5 MB. Assignment rules and Assignment Threshold require their corresponding profile permission.

When processing the same pilot again, confirm that new tasks do not multiply, exceptions remain visible, and manual correction reaches the intended owner. Review results in Import History before the detailed window closes, and use the available undo period when needed. Do not load the complete trade show file into Zoho in one operation until these checks have passed.

Zoho CRM