Manual users

Manual users

UA

image-20240611-123449.png

US

image-20240611-123805.png

RU

image-20240611-131051.png

UA

image-20240611-123449.png

US

image-20240611-123805.png

RU

image-20240611-131051.png

1. Introduction

Definition

Manual users are special system technical users in Leeloo.AI that are created automatically to record actions not tied to an identified subscriber: payments made via a direct link and webinar attendance without prior identification. A manual user is a marker of an incorrectly identified client: you cannot contact them, and their card remains inactive.

From a lifecycle perspective, a manual user belongs to the Manage stage — it is a data anomaly that the operator must recognise and resolve. Manual users optionally touch the Convert stage: if a payment goes through but the client is not identified, the conversion is recorded "into the void", and the manual user becomes part of the Convert pipeline with no further communication possible.

The B2B operator (marketer, manager, analyst) sees manual users in subscriber lists and in payment and webinar reports. Their job is to distinguish a manual user from a real client, understand why they appeared, and redesign the offer or webinar launch flow so that clients are identified by leeloo id before the target action takes place.

1-20250131-190817.png

The B2C client interacts with the manual user indirectly: they do not know a manual user has been created in the system. From the client's perspective it looks like a normal payment by link or webinar entry, but the platform cannot connect their action to their card — the link breaks, and downstream funnel triggers do not fire.

The Client's Card for a manual user is a null-record: the record exists, but no real subscriber can be mapped to it. Identification fields (telegram_id, email, phone) are empty or contain raw data from the payment form, communication history is absent, and the status is "inactive". This is a signal to the operator that the identification chain broke at some step of the scenario.

After reading you will understand:

  • what a manual user is and why one appears in the system;

  • the two scenarios that create a manual user — payments and webinars;

  • how the platform searches for a client by leeloo id → email → phone;

  • how to prevent manual users from appearing by using the "Buy" button inside an offer message;

  • how to set up the transition to a webinar platform through a "Link" button so the client keeps their leeloo id;

  • how to read a manual user's card and why it stays inactive.

Purpose

A manual user is a service marker for data quality in Leeloo.AI. Its USP is to let the platform preserve the fact of a payment or webinar attendance even when the client was not correctly identified: the data is saved, but in a separate "quarantine" record so the operator can see the problem and fix it at the scenario level.

On the Manage stage a manual user is the main indicator. The appearance of a manual user means the operator lost contact with the subscriber at a critical point (payment or webinar). The job is to find the cause (link-based offer instead of a button, direct entry to the webinar platform without identification), redesign the scenario, and prevent manual users from accumulating in the database.

On the Convert stage the role is optional: if payment via a direct link cannot be avoided (for example, the offer is hosted on an external resource), the manual user becomes part of the Convert pipeline — the money is received, but the client is lost for further communication. The job is to minimise the share of such payments by routing clients through the "Buy" button inside platform messages.

2. Manual users from payments

A manual user from a payment (Manual user from payment) is a record created at the moment the payment is completed when the platform cannot link the payment to a specific subscriber. This situation arises in the two cases described below.

2.1. How they appear

A Manual user from payment appears when:

  • the offer is paid via a direct link (not through the "Buy" button inside a platform message) — the platform has no binding to the payer's leeloo id;

  • during payment the client selects the "This is not me" option — the system explicitly records that the payer does not match the subscriber for whom the offer was opened.

1-20250131-190817.png

2.2. How to prevent it

To avoid creating a Manual user from payment, let the subscriber reach the offer not via a link but via a "Buy" button inside a platform message. In this case the payment goes through with a binding to the subscriber's leeloo id: the information is correctly reflected in the Client's Card, the configured funnel conditions fire, and no manual user is created.

3. Manual users from webinars

A manual user from a webinar (Manual user from webinar) is created at the moment a webinar attendee is recorded, when the platform cannot find a matching client card by any of the identification keys.

3.1. How they appear

The platform searches for the client sequentially: first by leeloo id, then by email, and only then by phone number. If the client is not found by these parameters, a manual user is created, and the entire webinar information (attendance, entry/exit time) is assigned to them.

3.2. How to prevent it

To prevent a Manual user from webinar from being created, design the scenario so that the client reaches the webinar platform from http://Leeloo.Ai while already carrying their personal leeloo id. To do that, the transition to the webinar must happen through a "Link" button — it passes the subscriber's identifier to the webinar platform and preserves the identification chain.

To display complete, ordered information and to ensure funnel conditions fire correctly, we recommend avoiding manual users on the platform.

Related instructions

Instruction

Why read it

Instruction

Why read it

Client's Card

Understand which Client's Card fields stay empty for a manual user and how to read its null-record.

Offers

Learn how offers are configured and where to place the "Buy" button so that you do not generate a Manual user from payment.

Purchase

Understand the payment mechanics and the payer identification logic.

Webinars

Understand how the transition to a webinar platform is configured and how the "Link" button preserves the participant's leeloo id.

Orders and Sales

Find payments attached to manual users and assess the share of "lost" conversions.

Communication Channels

Understand why a manual user is not linked to any communication channel and why contact with them is impossible.

Key terms

Term

Explanation

Term

Explanation

Manual user

A system technical user in Leeloo.AI, created automatically on a link-based payment or webinar attendance when the platform could not identify the client. The card stays inactive — the subscriber cannot be contacted.

Manual user from payment

A subtype of manual user, created when an offer is paid through a direct link or when the payer selects the "This is not me" option.

Manual user from webinar

A subtype of manual user, created when a webinar attendee is recorded and the search by leeloo id, email and phone does not match an existing card.

leeloo id

The internal identifier of a subscriber in Leeloo.AI — the main key used to link the client's actions (payments, webinars) to their card.

Client's Card

The central data entity of the platform: a single record about a subscriber that all modules write to. For a manual user it is a null-record with no identifiers and no communication history.

"Buy" button

A platform message element through which a subscriber goes to payment with a preserved binding to their leeloo id — the main way to avoid creating a Manual user from payment.

"Link" button

A platform message element for navigation to an external resource (for example, a webinar platform) that passes the subscriber's leeloo id and prevents the creation of a Manual user from webinar.

"This is not me"

The payment option chosen by a payer when they pay for someone else's offer. It explicitly signals to the platform that the payer does not match the subscriber — the payment is recorded against a manual user.

Manage

The stage of the customer lifecycle in Leeloo.AI on which the operator manages subscriber data and database quality. The appearance of a manual user is the main signal of a data quality problem at this stage.

Convert

The stage of the customer lifecycle on which the subscriber becomes a buyer. A Manual user from payment is an artefact of a broken conversion: the money is received, but the client is lost for further communication.