Import

Import

UA

US

UA

US

RU

1. Introduction

Definition

Import is a bulk action in the Leeloo.AI platform that lets you upload a client database from an external Excel file (.xlsx extension) into the Audience section. Import belongs to the Manage stage of the customer lifecycle: the operator bulk-loads subscribers into the platform for further communication, segmentation, and movement through sales tunnels.

Import works in tandem with other platform modules: it writes data into the Client's Card, subscribes clients to the chosen tunnel and LGT, and assigns them tags for later filtering in the Filter Panel. The data source is an external file (CSV/Excel) exported from a third-party CRM (AmoCRM, Zoho, Salesforce, etc.) or from Leeloo.AI itself.

The B2B operator (account owner, marketer, audience manager) launches Import via Mass Actions in the Audience section. They select the file, specify the sender bot (communication channel), target tunnel, LGT for subscription, and optional tags — after clicking Import clients, the platform creates or updates client cards and attaches them to the chosen route.

The B2C client does not interact with Import directly — they don't see the upload interface. Indirectly, Import affects the client this way: after a successful import, their card appears in the platform with the specified communication channel (Telegram, WhatsApp, Email, etc.), and they begin receiving tunnel messages or broadcasts from the operator as if they had subscribed via an LGT.

During Import, the following are written to the Client's Card: social_id (messenger identifier or email), name, the binding to the selected bot/communication channel, the current tunnel, the LGT subscription, and tags. On a repeat import of an existing client (match by social_id + channel type), the card data is updated — this is a key invariant: one client = one card per channel.

After reading you will understand:

  • What import means in Leeloo.AI and the scenarios where it is used (migrating from a third-party CRM, reverse-loading a previously exported base, bulk-connecting clients to a tunnel).

  • How to perform Import step by step through AudienceMass ActionsImport.

  • Which file fields are required (social_id), which are recommended (name), and which are optional.

  • How the update logic works for existing client cards during a repeat import.

  • How to avoid typical errors: bot-channel mismatch, missing social_id, duplicates, invalid email/phone format.

  • How to re-subscribe an imported base without real social_id via email/SMS campaigns and LGT.

Purpose

The key role of Import is the fast, controlled entry of an external client base into the Leeloo.AI platform with automatic binding to a communication channel, tunnel, and LGT. Without Import, the operator would have to enter each client manually — for a base of 1,000+ subscribers, that's hours of work. Import compresses this task into a single operation: upload a file + select a route = hundreds/thousands of ready client cards in the Client's Card spine, subscribed to the right tunnel.

At the Engage stage of the lifecycle, Import is a tool for rapidly filling the subscriber base for later warm-up through tunnels and broadcasts. Imported clients become immediately available for communication through the chosen channel, enter the tunnel, and receive their first messages as full-fledged subscribers.

At the Manage stage, Import is a tool for bulk insertion of subscribers into the platform's managed field. After import, clients become available for segmentation in Audience, filtering through the Filter Panel, broadcasts via Smart Sender, task creation in CRM, and movement through sales tunnels. The goal is to transfer a base from a third-party system (AmoCRM, Zoho, Salesforce) in a single operation, or to return previously exported clients to Leeloo while preserving the communication channel structure and tag segmentation.

2. How to perform Import

Import is launched from the Audience section through the Mass Actions menu. Before launching, prepare an Excel file (.xlsx) with the social_id and name fields filled — a sample is available at exported 03.12 13.28.27.xlsx.

2.1. Open the Audience section and click Mass Actions

Go to the Audience section. In the top-right corner of the screen, click Mass Actions — a panel of available operations on the client base opens on the right.

2.2. Select the Import option

In the menu that opens on the right, select Import — the file upload form opens with routing fields (bot, tunnel, LGT, tags).

2.3. Fill in the import form

The Import form contains several required and optional fields:

  1. Select the file in Excel format with .xlsx extension and required social_id and name fields filled. Other parameters are optional.

  2. Select the bot from which the campaign will be sent to imported clients. The bot type (communication channel) must match the social_id type in the file: Telegram bot for Telegram IDs, WhatsApp bot for WhatsApp numbers, Email provider for email addresses, etc.

  3. Select the tunnel — the Sales Tunnel where imported clients will land. If unspecified, Default tunnel is assigned.

  4. Subscribe to LGT — specify the landing page / lead-gen-tool to which clients will be counted as subscribed.

  5. Select tags (optional) — tags for later segmentation in the Filter Panel.

  6. Click Import clients — the button activates after the file and bot are selected. The platform performs the import.

We recommend preparing several .xlsx files split by messenger types before importing. If the identifier in the social_id field does not match the bot channel type, messages will not be delivered to that client.

On a repeat import of previously exported clients, the card data will be updated with values from the file. The match condition: social_id + bot channel type must match an existing record. On a mismatch, a new card is created.

3. Import file structure

The import file is a table in Excel .xlsx format. A detailed description of fields and formatting per communication channel (Telegram, WhatsApp, Email, Facebook, Instagram, Viber) is in the How to prepare an Excel file for import guide.

Required and recommended fields:

  • social_id — the client's identifier in the messenger (Telegram ID, FB ID), phone number for WhatsApp/SMS, or email address for email channels. Required.

  • name — the client's name. Recommended.

  • Other fields (phone, custom fields) are optional and depend on the channel.

For email channels (SendGrid, Mandrill), duplicate the subscriber's email in the social_id field as well.

If the social_id field is empty, the import will fail with an error.

4. Importing a base without real social_id

If you have a client base from a third-party service but no real social_id (Telegram ID, FB ID, etc.), Import is still possible — but it will require re-subscribing clients to a real communication channel via email/SMS campaigns and an LGT.

  1. Prepare a .xlsx file with the required social_id field — fill it with temporary numeric values (e.g., 111, 222, 333) or email addresses / phone numbers depending on the re-subscription channel.

  2. Import the file by following the steps in the "How to perform Import" section.

  3. Run a message campaign with a link to your LGT (the landing page with a messenger button for entry) through the email/SMS channel.

  4. Clients who follow the LGT will subscribe to a real communication channel — their cards will be updated with valid social_id.

  5. Further communication continues within the platform through the chosen channel and tunnel.

Sample file for import: exported 03.12 13.28.27.xlsx. Open the link and click the Download icon — open the file and edit it according to the rules above.

5. Common errors

Problem

Cause

Solution

Problem

Cause

Solution

Error: missing social_id

The field is missing from the file or the column name is incorrect.

Add the social_id column, save the file in .xlsx format, and repeat the import.

Messages are not delivered

The bot type does not match the social_id type in the file.

Split the file by messenger types and import each one with the corresponding bot.

Duplicate cards

social_id in the file differs from an existing one, or the selected bot does not match the card's channel.

Verify keys before import; filter duplicates in Excel.

Emails not delivered

SendGrid/Mandrill integration is not connected, or social_id does not contain the email address.

Check the email provider settings and duplicate the email in social_id.

Invalid file format

The file is saved as .csv or is corrupted.

Re-save the file in Excel .xlsx format and repeat the import.

Related instructions

Instruction

Purpose

Instruction

Purpose

Export

Inverse operation: unloading the client base from Leeloo.AI into an Excel file.

Mass Actions with clients

Overview of all mass actions over the client base in the Audience section.

How to prepare an Excel file for import

How to prepare an Excel file for import/export: field structure per communication channel.

Base migration

Full cycle of migrating a client base between platforms/accounts.

Client's Card

The platform's central entity — where Import writes client data.

Audience

The platform section where Import is launched and the base is filtered.

Filter Panel

Cross-platform component for filtering the client base by tags and attributes.

Key terms

Term

Explanation

Term

Explanation

Import

A bulk action in the Audience section that loads a client base from an external Excel file (.xlsx) into the Leeloo.AI platform with binding to a bot, tunnel, LGT, and tags. Engage/Manage stage of the lifecycle.

social_id

The unique identifier of a client in a communication channel: Telegram ID, FB ID, phone number (WhatsApp/SMS), or email address. Required field of the import file.

Client's Card

The platform's central data spine — a single client's card where Import writes social_id, name, communication channel, tunnel, LGT, and tags.

Mass Actions

The menu in the Audience section with operations over the entire base: import, export, broadcast, tagging, etc.

LGT

Lead-Generation Tool — landing page / form / QR code for subscribing a client to a communication channel. During Import, the LGT specifies which entry point clients are credited to.

Default tunnel

The default tunnel assigned to a client during Import if the operator did not choose a specific Sales Tunnel.

Communication Channel

The delivery method for messages to a client: Telegram, WhatsApp, Facebook Messenger, Instagram, Viber, Email (SendGrid/Mandrill), SMS. Determined by the selected bot during Import.

Engage

Engagement stage of the customer lifecycle — filling the subscriber base for warm-up through tunnels and broadcasts.

Manage

Management stage of the customer lifecycle — bulk management of the subscriber base (import, export, segmentation, broadcasts, tags).