Universal Data Sync (UDS) now supports TCP (Transmission Control Protocol) as both a Trigger and an Action. This allows LeadSquared to integrate with healthcare and legacy systems that rely on socket-based communication instead of REST/HTTPS APIs.

With TCP support, UDS workflows can:

• Receive inbound HL7 messages over TCP and trigger workflows in real time
• Send outbound HL7 messages to external systems using TCP or MLLP

This capability is primarily intended for healthcare integrations and legacy platforms where message accuracy, ordering, and reliability are mandatory.

2. Use Cases

Receive Healthcare Data

• Accept inbound HL7 messages from EHR/EMR systems
• Trigger workflows for patient registration, updates, and appointment events

Send Data to Healthcare Systems

• Push ADT and appointment-related HL7 messages to partner systems
• Support outbound integrations with hospitals and healthcare platforms

Integrate with Legacy Systems

• Connect to systems that do not expose REST APIs
• Enable socket-based communication using TCP or MLLP

3. Key Technical Concepts

Supported HL7 Message Types

ADT Events

• ADT-A04 – Patient creation / registration
• ADT-A08 – Patient information update

SIU Events

• SIU-S12 – New appointment booking
• SIU-S14 – Appointment modification
• SIU-S15 – Appointment cancellation

4. Configure TCP Trigger

A TCP Trigger starts a workflow when HL7 data is received over a TCP connection.

Step 1: Trigger Selection

• Request Data Format: HL7 (pre-selected)
• Connection Type:
  • TCP
  • MLLP (recommended for HL7)
• Message Type: Select the relevant ADT or SIU event

Sample HL7 Payload

Provide a sample HL7 message from the source system or send a test message. This sample is used to identify segments and enable variable mapping.

MSH|^~\\&|HIS|Hospital|LSQ|LeadSquared|202401011230||ADT^A04|MSG00001|P|2.3
EVN|A04|202401011230
PID|1||12345^^^Hospital||Doe^John||19800101|M|||123 Main St^^City^State^12345||9876543210
NK1|1|Doe^Jane|SPOUSE|9876543211

Step 2: Configuration

After saving the trigger, UDS generates:

• Host (IP Address)
• Port Number
• App ID
• Flow ID

Configure the external system to send HL7 messages to the provided host and port.

Note: All TCP triggers within a tenant share the same host and IP. App ID and Flow ID help identify the target workflow.

5. Configure TCP Action

Variable Mapping

• Variables extracted from the TCP trigger or previous actions can be inserted into the HL7 request body
• Users should map values based on HL7 segment definitions (PID, EVN, MSH, etc.)

Configuration Details

Provide the following information:

• Destination Host / IP Address
• Port Number
• Protocol Type: TCP or MLLP
• Data Transmission Type: HL7
• Message Type: ADT or SIU event
• Request Body: HL7 message (supports variables)

6. Logs

Execution logs are available for monitoring and troubleshooting.

FAQs

Is TCP supported for non-healthcare use cases?

TCP support is designed primarily for healthcare and legacy systems. Non-healthcare use cases are supported only if the external system uses HL7 over TCP.

Can I send or receive JSON data over TCP?

No. Currently, only HL7 data format is supported for TCP triggers and actions.

What is the difference between TCP Trigger and Webhooks?

Webhooks use HTTPS endpoints, while TCP Triggers rely on socket-based communication using IP and port. TCP is commonly required by legacy and healthcare systems.

Should I use TCP or MLLP?

MLLP is recommended for HL7 communication as it safely wraps messages over TCP.

Are UI changes expected for TCP workflows?

Yes. UI improvements for TCP configuration are ongoing and may change in future releases.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post TCP Trigger and TCP Action in UDS appeared first on LeadSquared Help and Support.

The Union and Union All options in the Analytics Report Builder allow you to combine the results of two or more queries into a single dataset by stacking rows vertically.

Unlike Joins, which merge related tables side-by-side (column-wise), Union combines datasets that share the same structure and appends them together (row-wise).

Union is useful when you want to consolidate similar data from multiple sources into one unified report.

2. Prerequisites

• SIERA is a paid feature. To enable it for your account, contact your account manager or [email protected].
• For details on Report Builder Data Sources, refer to this article.

3. When to Use Union

Use Union when you want to:

• Merge similar datasets into one report
• Combine data from parallel entities (e.g., Leads and Activities)
• Create unified workload or engagement reports
• Append filtered query results together
• Avoid relational joins where no direct relationship is required

3.1 Union vs Union All

3.2 Important Rules for Using Union

Union can only be applied between queries, not base tables.

Before applying Union, ensure:

• Both queries return the same number of columns
• Columns appear in the same order
• Corresponding columns use compatible data types
• Business meaning of each column matches across queries

If these conditions are not met, Analytics will show a validation error when saving the report.

4. Union Configuration

4.1 Use Case

For example, let’s say you want to combine Lead Source information from:

• Leads table
• Activities table

The goal is to create a single dataset that shows all sources (from both Leads and Activities) in one report. This combines Lead Source at the lead level with Traffic Source from activities (for example, form submissions or other interactions), so both the lead’s origin and activity-driven sources are included in one dataset—allowing you to see where the lead originally came from and how the lead interacted later.

Step 1: Create Query 1 (Leads)

1. Click + New Query
2. Select Leads as the data source
3. Add the following rows:
   • Lead Source
   • Prospect ID
4. Apply required filters, such as Created On (date range)
5. Save the query

Step 2: Create Query 2 (Activities)

1. Click + New Query
2. Select All Activities as the data source
3. Add the following rows in the same order as Query 1:
   • Traffic Source
   • Related Prospect ID
4. Apply filters such as:
   • Activity Event
   • Created On (date range)
5. Save the query

Step 3: Apply Union

1. In the Data Source section, Under Combine Tables, select Union or Union All
2. Choose:
   • Query 1 (Leads)
   • Query 2 (Activities)

If both queries follow the validation rules, the union will execute successfully and combine the datasets into a single result.

4.2 Showing Query Filters in the Main Report

You can control query-level filters from the main report page:

1. Edit the query
2. Go to Filters
3. Click the three-dot menu on a filter
4. Enable Show this filter in the main report page

This allows centralised filtering after union is applied. You

FAQs

1. Can I use Union directly on tables?

No. Union works only between queries.

2. What happens if column data types do not match?

The report will fail validation and show an error.

3. Which column names appear in the final report?

Column display names are inherited from the left-hand (primary) query.

Any Questions?

We’d love to hear your feedback to help improve this article. Feel free to enter your questions or in the comments section below.

The post Combining Query Results Using Union in Analytics Report Builder appeared first on LeadSquared Help and Support.

Users can customise the Tasks page to reflect their priorities. There are two views available on the Tasks page –

• List View – All tasks appear in a list, with columns that show details such as Status, Due Date, and Task Owner. This helps you view key task information at a glance.
• Calendar View – All tasks are displayed as part of a calendar. This helps plan your work for the day, week or month.

2. Prerequisite

Any LeadSquared user can customise their Tasks page.

3. List View

The List view shows a grid with details of all tasks. By default, it displays the tasks created by you. To access it, navigate to Lead Management>Tasks, and click the List View icon.

3.1 Customise the Columns

You can add or remove task and lead fields as required. To do this –

1. On the top-right corner, click the Manage Columns icon.
2. On the Manage Columns pop-up, use the checkboxes to select the fields you want to display on the page.
   • To remove a field, uncheck the field or use the ‘x’ icon.
3. Toggle between the Leads and Tasks tabs to choose the fields you want to display.
4. Drag and drop the Scrollable Columns in your preferred order.
   • You cannot edit the order of the Pinned Columns.
5. Once you’re done, click Update.

3.2 Other Actions

On the List View page, you can also perform the following actions.

• Sort – You can sort all the columns (except Status) in ascending or descending order.
• Edit – To update a task (such as the Schedule, Owner, etc.) use the Edit icon.
• Complete – To complete a task, use the Mark Complete icon.
• Delete – To delete a task, use the Delete icon.
• More Actions – Hover on the three-dots menu to perform the following actions –
  • Mark Open – Let’s you reopen a completed task.
  • Delete Recurrence – Lets you delete future occurrences of a recurring task.
  • Cancel – Let’s you cancel a task.
• Add Task – Let’s you add a new task directly from the Tasks page. To know more, refer to Manage Tasks for Users.
• Export – Let’s you export tasks. To know more, refer to Export Tasks out of LeadSquared.

4. Calendar View

The Calendar view displays your tasks on a calendar, for the day, week or month you’re currently viewing. To access it, navigate to Lead Management>Tasks, and click the Calendar View icon.

4.1 Day View

• This view shows the tasks set up for a specific day. By default, it shows the current day.
• Click a date in the monthly calendar on the left pane to change the day.
• The calendar supports multiple time zones. To change the time zone, click the time zone dropdown.
  • Each user sees tasks in their own time zone, which you configure while creating or editing a user in Manage Users.
• Working Hours also appear on the calendar, with white slabs for working hours and grey slabs for non-working hours.
  • If a workday template with a break time applies to a user, the calendar marks it in grey.
• You can use the day view to view tasks for multiple users at the same time by using the name dropdown and selecting the users whose tasks you want to see.

4.2 Week and Month View

• Use the calendar on the left pane to change the week and month.
• Only one user’s tasks appear at a time in the week and month views. Use the owner dropdown to switch between users.

4.4 Other Actions

You can also perform the following actions from the Calendar View. To do this, click an existing task.

• Edit – To update a task (such as the Schedule, Owner, etc.) use the Edit icon.
• Complete – To complete a task, use the Mark Complete icon.
• Delete – To delete a task, use the Delete icon.
• More Actions – Hover on the three-dots menu to perform the following actions –
  • Mark Open – Let’s you reopen a completed task.
  • Delete Recurrence – Lets you delete future occurrences of a recurring task.
  • Cancel – Let’s you cancel a task.
• Add Task – Let’s you add a new task directly from the Tasks page. To know more, refer to Manage Tasks for Users.

5. Filters and Advanced Filters

Filters help narrow down specific tasks, such as tasks with an Overdue status or a Due Date of today. The Advanced Search feature lets you search for tasks that meet one or more task and/or lead filters.

5.1 Filters

1. Click the Filter button, and then click Configure Filter Fields.
2. On the pop-up, select the task and lead fields to display as filter options, and click Update.
3. Then click the Filter button again, and select the fields you want to use to filter tasks from the available list.
   • If the selected field has sub-fields, you can also filter tasks by those sub-fields. For example, if you select Task Status, you can filter by Open, Completed, Pending, or Overdue.

5.2 Advanced Filters

Advanced Filters let you set up If/Else conditions to identify and narrow down specific tasks in your account, such as tasks where the Status Is Pending + Overdue AND Lead City Is Bangalore.

1. Click the Filter button, and then click Advanced Filters.
2. On the Advance Search pop-up, click Add Condition.
3. On the first dropdown, Task is selected by default. You can keep it as is or change it to a lead field if required.
   • The second and third dropdowns are non-clickable and preset with default values.
4. On the fourth dropdown, select the task field to filter by, such as Status, Due Date, Owner, etc.
   • Based on the selected field, choose the operator to filter tasks (such as Is, Is Not, Contains, Ends With, etc.).
5. Then, from the final dropdown, add the field values to filter the results. You can select multiple values.
6. Once you’re done, click Add.
   • To add additional conditions, use the AND or OR operators.
7. Once you’re done, click Show Results.

Any Questions?

We’d love to hear your thoughts on this article and the tasks feature in general. Feel free to start a conversation in the comments section below.

The post Customise the Tasks Page appeared first on LeadSquared Help and Support.

Export tasks from LeadSquared directly from the Tasks page in an Excel file. This makes it easy to analyse data, share updates, and track your users’ performance offline.

2. Prerequisite

Any LeadSquared user can export tasks.

3. Export Tasks

1. Navigate to Lead Management>Tasks, and select the List View.
2. Select the tasks you want to export. You can choose specific tasks or export all tasks on the page.
   • To export all the tasks visible on the page, click the checkbox on the top-left corner, under the searchbox.
3. Hover on the three-dots menu, and click Export Task.
4. On the Export Task pop-up, choose to export –
   • All Fields – This includes all configured task fields for the selected tasks, along with key lead identifier fields.
   • Selected Fields – You can select the task and lead fields you want to export.
5. Once you’re done, click Export. The CSV file is saved directly to your desktop.

Any Questions?

We’d love to hear your thoughts on this article and the tasks feature in general. Feel free to start a conversation in the comments section below.

The post Export Tasks out of LeadSquared appeared first on LeadSquared Help and Support.

Offline Task Completion allows field users to complete tasks on the LeadSquared Mobile App even when they are not connected to the internet. Users can mark tasks as Completed in offline mode, fill out associated completion forms, and continue working without interruption.

When connectivity is restored, all offline task data, including form submissions, is automatically synced to the server. Until the sync is successful, tasks appear as Completed (Offline) on the mobile app, ensuring visibility while preventing data loss. This feature is especially useful for field teams working in low-connectivity or no-network environments, where task completion would otherwise be delayed.

2. Prerequisites

You must be an Admin to set up Offline Task Completion on the LeadSquared Web App.

3. How It Works

1. Enable the relevant settings for Offline Task Completion on the LeadSquared Web App.
2. On the LeadSquared Mobile App, users can mark tasks as Completed when they are offline.
3. If a completion form is associated, it can be filled and saved. It will sync once the connection is restored.

4. Enable Offline Task Completion Settings

To complete tasks offline on the LeadSquared Mobile App, the admin must enable the following settings on the web app.

1. Navigate to Settings>Mobile App>Permissions.
2. Enable the Offline Leads and Offline Tasks permissions for the relevant type of users
3. Additionally, if a completion form is associated, enable Offline Dynamic Forms in Mobile App>Additional Settings.

Additionally, configure the relevant task types for offline completion in the below JSON using the new Task Completion Offline Additional Setting on the web app.

Sample JSON

{
 "taskTypesName": [
   "<Tasktype name>"
 ]
}

5. Use Offline Task Completion on Mobile

Once enabled,

1. Open the Task List on the LeadSquared Mobile app while offline and mark the relevant task as Completed.
2. If a completion form is associated, the form is filled and saved locally on the device.
3. The task is marked as Completed (Offline).
4. Once the device reconnects to the internet, the task and form data sync automatically and the task status updates to Completed.

6. Access Offline Synced Forms

Irrespective of your connectivity, you can access the forms that were saved while offline and make relevant changes if required.

1. Navigate to the side menu on the Mobile App.
2. Select Offline: Pending Sync and tap Forms.
3. You will see the offline-saved forms here. You can modify the form as required and save it.
4. Once you’re online, on the Offline: Pending Sync screen, tap Sync Offline Data to sync the form online.

7. Please Note

Offline Task Completion is currently not supported for:

• Tasks associated with Opportunities
• Geofenced tasks
• Tasks with multi-level forms
• Tasks with pre-submission LAPP configured
• Task types not enabled in the offline configuration

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Complete Tasks Offline on the LeadSquared Mobile App appeared first on LeadSquared Help and Support.

Distribution Engine is a simple, rules-based way to automatically assign Leads and Opportunities to the right users. It replaces complex automation-based assignment with an easy-to-manage setup that helps you distribute records fairly, reduce manual effort, and meet response SLAs.

You can use Distribute Engine to:

• Automatically assign new records as soon as they are created or updated.
• Distribute work evenly across users using predefined methods.
• Reassign records if a user does not act on them within a defined time (SLA).
• Track assignments and SLA breaches from a single dashboard.

When should you use Distribute Engine?

Use this feature if you want to:

• Assign incoming leads from forms, imports, APIs, or integrations automatically.
• Balance workload across sales or support teams.
• Ensure faster follow-ups by reassigning records when SLAs are missed.
• Avoid maintaining multiple automation rules for assignment logic.

How Distribute Engine works (at a glance)

1. A record (Lead or Opportunity) enters the Distribute Engine.
2. The engine checks which assignment rules apply.
3. An eligible user is selected based on your configuration.
4. The record is assigned and tracked for SLA compliance.

2. Prerequisites

• To enable Distribution Engine, contact [email protected]
• This feature is only available on NextGen.

3. Trigger Modes in Distribution Engine

Distribution Engine supports two trigger modes that control how records enter the engine for assignment.

3.1 Entity Trigger Mode (Default Behaviour)

In Entity Trigger Mode, records automatically enter the Distribute Engine based on the trigger conditions defined inside each assignment rule.

For example:

• When a Lead is created
• When a Lead is updated
• When Stage/Status changes

When the selected event occurs, the engine:

1. Evaluates the rule criteria
2. Checks for a match
3. Assigns the record if matched

3.2 Automation Trigger Mode

In Automation Trigger Mode, records enter the Distribution Engine only when explicitly sent from an Automation workflow. An automation card called Send to Distribution Engine is available in the automation.

3.2.1 How it Works

1. A record enters an automation flow.
2. The flow reaches the Send to Distribution Engine card.
3. The record is sent to the Distribute Engine for assignment.
4. The engine assigns the record.
5. The engine sends a callback to automation.
6. The automation flow continues.

3.2.2 Timeout & Default User

If the Distribution Engine does not respond within 10 minutes, the automation card assigns the record to a default user defined inside the “send to distribution engine” card configuration.

3.2.3 Supported Automation Triggers

The Send to Distribution Engine card is available only for specific automation triggers:

For Leads:

• Lead Created
• Lead Updated
• Activity Posted on Lead
• Opportunity Created
• Task Created

For Opportunities:

• Opportunity Created
• Opportunity Updated
• Activity Posted
• Task Created

3. Create a Distribution Rule

This section explains how to create and manage assignment rules.

3.1 Creating a new assignment rule

Navigate to Distribution Engine>Distribution Rules. Click + Create Distribution Rule.

Enter basic information about the rule:

• Rule Name (required, must be unique)
• Description (optional)

You can edit these details later using the pencil icon

Rule creation is a 4-step guided process. You can save progress at any step:

Step 1: Rule Criteria

This step decides when the rule runs and which records qualify.

Select entity and event

1. Choose the entity: Lead or Opportunity
2. Select the entity type (if applicable)
3. Choose when the rule should run, such as:
   • Lead Entity – Lead Created, Lead Updated, Activity Created On Lead, Opportunity Created On Lead, and Task Created On Lead.
   • Opportunity Entity – Opportunity Created, Opportunity Updated, Activity Created On Opportunity, and Task Created On Opportunity.

Only records that match this entry event and conditions will enter the rule.

Define rule conditions (AND / OR logic)

Rule conditions help you narrow down exactly which records should be assigned.

Step 2: Select Users

Choose who can receive leads when this rule runs.

You can only select one of the following and cannot combine them in a single rule:

• Individual users (Manual selection)
• Teams
• Sales groups

At least one user or one group is required. Also, you can choose to Assign only if the User is available.

Step 3: Distribution Method

Select one assignment method:

Step 3.1 Round Robin Distribution Method

Round Robin assigns records one by one in sequence.

Example with 3 users:

User A → User B → User C → User A → User B → User C → …

Step 3.2 Weighted Distribution Method

Weighted distribution lets you control how many records each user, team, or sales group should receive compared to others.

Instead of assigning records equally, you define a weight. A higher weight means that entity receives more records in each distribution cycle. Records are always assigned one at a time, and distribution follows a Round Robin pattern.

How It Works

1. You select either:
   • Manual Users
   • Teams
   • Sales Groups
2. You assign a weight to each selected entity.
3. The system distributes records in rotation, ensuring the total assignments in each cycle match the defined weights.

Example 1: Manual Users

You configure:

• User A = 3
• User B = 2
• User C = 1

Total weight = 6

This means in every 6 assignments:

• A receives 3
• B receives 2
• C receives 1

Distribution still follows Round Robin, not bulk allocation.

Example sequence:

A → B → C → A → B → A → (cycle complete)

Then the cycle repeats.

Example 2: Teams or Sales Groups

When you select Teams or Sales Groups, Round Robin is followed at two levels:

Level 1: Between Groups (Based on Weight)

Example:

• Sales Group East = 2
• Sales Group West = 1

Total weight = 3

In every 3 assignments:

• 2 records go to East
• 1 record goes to West

The engine distributes between East and West using Round Robin while respecting the weight.

Example sequence:

East → West → East → (cycle complete)

Then the cycle repeats.

Level 2: Inside the Group (Round Robin)

Once a record is assigned to a group:

• The system assigns it to users inside that group using Round Robin.
• Only eligible users are considered.

So the full flow looks like:

Record → Group (Round Robin with weight) → User (Round Robin inside group)

Step 4: Fallback

If no eligible user is available, assign the lead to a default user.

Next, you can:

• Save as Draft – Keeps the rule inactive
• Publish – Makes the rule live and adds it to the priority order

3.2 Managing Distribution Rules

Rule list includes:

• Order (priority)
• Rule name
• Action (entity)
• Status (Draft, Active, Inactive, Error)
• Created on
• Created by

You can:

• Click any rule to open its details
• Search rules by name or creator
• Filter rules by status, creator, or distribution method

Reordering rules

Rule order decides which rule gets applied first when a record enters the Distribute Engine.

When a Lead or Opportunity evaluated:

1. The engine checks the first active rule in the list.
2. If the record matches the rule’s entry criteria, the assignment is made.
3. Once a record is assigned, no further rules are evaluated.
4. If the record does not match, the engine moves to the next rule in the order.

Why rule order matters

If multiple rules can apply to the same record, only the highest‑priority rule will run.

Example:

• Rule 1: Assign All Website Leads to Team A
• Rule 2: Assign High‑Score Website Leads to Team B

If Rule 1 is above Rule 2, all website leads (including high‑score ones) will be assigned to Team A.

To ensure high‑score leads go to Team B, place Rule 2 above Rule 1.

4. Viewing assignments and performance

Navigate to Distribution Engine>Home. The Home page gives you a quick distribution overview. Click the filter icon to filter the data by a date-range.

• Records Created: Total number of records that entered the Distribute Engine during the selected time period.
• Records Assigned: Number of records successfully assigned to users by the Distribute Engine.
• Assignment Success Rate: Percentage of created records that were successfully assigned to a user.
• Records Unassigned: Number of records that could not be assigned due to no matching rule or no eligible user.
• Rule Match Overview: Shows how many records matched each assignment rule.
• Assignment Method Split: Displays how records were distributed across different assignment methods.

5. Logs and reports

The Reports & Logs section helps you understand how records are being assigned and identify issues such as missed assignments.

You can use these reports to:

• View assignment history for each record
• See when and why fallback assignment was used
• Troubleshoot rule execution issues

All reports can be filtered by date range, sales group, assigned user, and entity type to quickly narrow down the data you need.

6. Assignment Settings

The Assignment Settings section defines the global controls used by the Distribute Engine, including who can receive assignments and how many records they can be assigned.

User Assignment Limits

Admins can map user fields to control how many records a user can receive on an hourly, daily, weekly, or monthly basis. If no limit is configured, the user is treated as having unlimited capacity.

User Eligibility for Assignment

Admins can control which users are eligible to receive assignments based on their Check-in / Check-out status. Only users who meet the configured eligibility conditions are considered during assignment.

FAQs

What happens if no user is available?
The record is assigned to the fallback user configured in the rule or settings.

Can I temporarily stop assignments to a user?
Yes. Mark the user unavailable, apply leave, or remove them from the rule.

Can I edit an active rule?
Yes. Changes take effect once you save and activate the rule again.

The post Distribution Engine appeared first on LeadSquared Help and Support.

The FloStack–UDS integration lets you automatically sync key lead interactions—such as appointments, reschedules, cancellations, callback requests, and microsite information—from FloStack into LeadSquared.

All FloStack actions are pre-configured in UDS, so you only need to authenticate and complete field mappings. Once configured, new appointment bookings, updates, and microsite events flow directly into LeadSquared without any manual intervention.

The integration ensures that:

• Leads created or updated in FloStack are reflected accurately in LeadSquared
• Appointment lifecycle events stay in sync (create, update, cancel)
• Callback requests raised on FloStack become actionable tasks
• Personalized FloStack microsites can be stored on the lead record
• Lead assignment configured inside FloStack is automatically pushed to LeadSquared

This helps admissions, counseling, or sales teams engage leads quickly and consistently, using the same data generated from FloStack’s routing and booking journeys.

How the Integration Works

FloStack sends data to UDS each time a relevant event occurs.

UDS then:

1. Identifies the lead using the configured unique field
2. Selects the appropriate action
3. Creates/updates the Lead, Activity, or Task based on mapping
4. Processes the sync in real time.

2. Available Pre-Configured UDS Actions

Once you search for “FloStack” in the UDS App, you will see the following actions already configured:

• Create Appointments 
• Update Appointments 
• Cancel Appointments 
• Call Back Request
• Microsite Creation & Lead Owner Assignment

Each action serves a specific use case in the FloStack workflow.

3. Create Appointments

3.1 What this action does

Captures appointment bookings from FloStack microsites and creates corresponding LeadSquared records.

Triggered When

A user books a new appointment on a FloStack microsite.

3.2 Basic Settings & Authentication

Enter the following details –

Field	Description
Lead Source	Enter the lead source through which the leads were captured (e.g., Flostack). This detail will appear on the Lead Details page under Lead Source.
Default Country Code	Select a default country code. If the lead’s mobile number is captured without a country code, the default country code is added to the lead’s mobile number.
Select Time Zone	The time zone of your Flostack account.
Lead Capture Primary Search By Criteria	To avoid duplicate lead creation, select one unique lead field (e.g., mobile number/email) as the search key. Leads will be searched by the value mapped to this field. If a matching lead is found, it will be updated. Otherwise, a new lead will be created. To know how to mark a LeadSquared lead field as unique, please refer to How to Make a Custom Field Unique.
Lead Capture Secondary Search By Criteria	If lead identification and capture through the primary Search By criteria fails, the system will reattempt using the secondary Search By criteria.
Select User to Notify on Failure	If there’s an error in fetching leads, the selected user will receive a failure message via email. Choose a user from the list of available users in your LeadSquared account.To know more about the type of errors, please refer to Error Notifications.
Enable Notification	Enable the  checkbox to ensure notification emails are sent to the selected user when there’s a failed query.

Supports custom unique fields and composite keys (email + phone) as search keys. Once you’re done entering all the details, click Save.

3.2 Configuration Breakdown

• Lead/Contact Entity
  • Sync Behavior: The Capture (Create and Update existing record) behavior is recommended. LeadSquared will search for an existing lead (by email/phone). If not found, it creates one.
  • Edit Mapping: Use this to map FloStack appointment fields (name, phone, email, UTM parameters, custom attributes, etc.) to LeadSquared Lead fields.
• Task Operations
  • Create Task: Enabled. Creates an appointment task for the lead owner based on FloStack details (date, time, meeting type).
  • Edit Mapping: Task mappings for standard appointment tasks are preloaded. Use the Edit Mapping to view mappings, but note these mappings are locked in the default packaged action.
  • Note:
    • To change task schema or add fields, clone the app and edit the clone.
    • FloStack sends a Meeting ID, UDS uses this to relate tasks to activities for updates/cancels.
• Activity Entity
  • Activity Type(s) Definitions: Alongside FloStack Appointment, click Create Activity.
  • Sync Behaviour Options: The Create + Update (recommended) – UDS creates an “Appointment” activity and updates it on subsequent events.
  • Edit Mapping: Map incoming appointment attributes to the Activity fields. You can add custom activity mappings.

4. Update Appointments

4.1 What this action does

Updates existing appointment records in LeadSquared when the appointment is modified (rescheduled, advisor changed, etc.) from FloStack.

Triggered When
A user reschedules or edits an existing appointment on a FloStack microsite.

4.2 Basic Settings & Authentication

Enter the following details –

Field	Description
Lead Source	This detail will appear as Update Appointments from Flostack on the Lead Details page under Lead Source.
Default Country Code	Select a default country code. If the lead’s mobile number is captured without a country code, the default country code is added to the lead’s mobile number.
Select Time Zone	The time zone of your Flostack account.
Lead Capture Primary Search By Criteria	To avoid duplicate lead creation, select one unique lead field (e.g., mobile number/email) as the search key. Leads will be searched by the value mapped to this field. If a matching lead is found, it will be updated. Otherwise, a new lead will be created. To know how to mark a LeadSquared lead field as unique, please refer to How to Make a Custom Field Unique.
Lead Capture Secondary Search By Criteria	If lead identification and capture through the primary Search By criteria fails, the system will reattempt using the secondary Search By criteria.
Select User to Notify on Failure	If there’s an error in fetching leads, the selected user will receive a failure message via email. Choose a user from the list of available users in your LeadSquared account.To know more about the type of errors, please refer to Error Notifications.
Enable Notification	Enable the  checkbox to ensure notification emails are sent to the selected user when there’s a failed query.

Supports custom unique fields and composite keys (email + phone) as search keys. Once you’re done entering all the details, click Save.

4.3 Configuration Breakdown

• Lead/Contact Entity
  • Sync Behavior: Do Nothing is recommended. Lead creation/update is not required since the lead already exists.
• Task Operations
  • Get Task ID: Enabled. Performs an advanced search to locate the appointment task using the Meeting ID.
  • Update Task: Enabled. Applies updated appointment details (new time, rescheduled date, status changes).
  • Note:
    • To change task schema or add fields, clone the app and edit the clone.
• Activity Entity
  • Activity Type(s) Definitions: Alongside FloStack Appointment, click Create Activity.
  • Sync Behavior Options:Update only existing record is recommended. Updates the same activity created during appointment creation.
  • Edit Mapping: Map incoming appointment attributes to the Activity fields. You can add custom activity mappings.

5. Cancel Appointments

5.1 What this action does

Marks appointments as cancelled in LeadSquared when a prospect cancels via the FloStack microsite.

Triggered When
A user cancels a previously booked appointment.

5.2 Basic Settings & Authentication

Enter the following details –

Field	Description
Lead Source	This detail will appear as Update Appointments from Flostack on the Lead Details page under Lead Source.
Default Country Code	Select a default country code. If the lead’s mobile number is captured without a country code, the default country code is added to the lead’s mobile number.
Select Time Zone	The time zone of your Flostack account.
Lead Capture Primary Search By Criteria	To avoid duplicate lead creation, select one unique lead field (e.g., mobile number/email) as the search key. Leads will be searched by the value mapped to this field. If a matching lead is found, it will be updated. Otherwise, a new lead will be created. To know how to mark a LeadSquared lead field as unique, please refer to How to Make a Custom Field Unique.
Lead Capture Secondary Search By Criteria	If lead identification and capture through the primary Search By criteria fails, the system will reattempt using the secondary Search By criteria.
Select User to Notify on Failure	If there’s an error in fetching leads, the selected user will receive a failure message via email. Choose a user from the list of available users in your LeadSquared account.To know more about the type of errors, please refer to Error Notifications.
Enable Notification	Enable the  checkbox to ensure notification emails are sent to the selected user when there’s a failed query.

Supports custom unique fields and composite keys (email + phone) as search keys. Once you’re done entering all the details, click Save.

5.3 Configuration Breakdown

• Lead/Contact Entity
  • Sync Behavior: Do Nothing is recommended. No lead updates are required for cancellations.
• Task Operations
  • Get Task ID: Enabled. Retrieves the appointment task mapped to the Meeting ID.
  • Cancel Task: Enabled. Cancels the appointment task for the lead owner.
  • Edit Mapping: Task mappings for cancellation are preloaded/locked. Clone the app to edit mappings.
• Activity Entity
  • Activity Type(s) Definitions: Alongside FloStack Appointment, click Create Activity.
  • Sync Behavior: Create and Update record is recommended. Update the original appointment activity status to “Cancelled” and also capture any cancellation event as an activity if you want a separate audit trail.
  • Edit Mapping: Map cancellation reason, cancelled timestamp, and any notes to activity fields.

6. Call Back Request

6.1 What this action does

Creates a callback task and logs an activity whenever a prospect requests a callback from the FloStack microsite.

Triggered When
A user clicks “Request Callback” or submits a callback form on a FloStack microsite.

6.2 Basic Settings & Authentication

Enter the following details –

Field	Description
Lead Source	This detail will appear as Flostack Call Back Request on the Lead Details page under Lead Source.
Default Country Code	Select a default country code. If the lead’s mobile number is captured without a country code, the default country code is added to the lead’s mobile number.
Select Time Zone	The time zone of your Flostack account.
Lead Capture Primary Search By Criteria	To avoid duplicate lead creation, select one unique lead field (e.g., mobile number/email) as the search key. Leads will be searched by the value mapped to this field. If a matching lead is found, it will be updated. Otherwise, a new lead will be created. To know how to mark a LeadSquared lead field as unique, please refer to How to Make a Custom Field Unique.
Lead Capture Secondary Search By Criteria	If lead identification and capture through the primary Search By criteria fails, the system will reattempt using the secondary Search By criteria.
Select User to Notify on Failure	If there’s an error in fetching leads, the selected user will receive a failure message via email. Choose a user from the list of available users in your LeadSquared account.To know more about the type of errors, please refer to Error Notifications.
Enable Notification	Enable the  checkbox to ensure notification emails are sent to the selected user when there’s a failed query.

Supports custom unique fields and composite keys (email + phone) as search keys. Once you’re done entering all the details, click Save.

6.3 Configuration Breakdown

• Lead/Contact Entity
  • Sync Behaviour: Create + Update is recommended. Callback requests often originate from prospects who may not yet exist in CRM; create if new, update if existing so the task is associated with correct lead.
  • Edit Mapping: Map contact info, preferred callback time window, page source, and any form fields to Lead fields.
• Task Operations
  • Create Task: Enabled. Creates a Callback task for the owner.
  • Edit Mapping: Default callback task mappings are preloaded and locked. To add/modify task fields, clone the app and edit the clone.
• Activity Entity
  • Activity Type(s) Definitions: Alongside FloStack Call Back Request, click Create Activity.
  • Sync Behaviour: Create only is recommended. Every callback event triggers a new activity.
  • Edit Mapping: Map callback metadata: timestamp, preferred time, reason, page URL, UTMs, etc.

7. Microsite Creation & Lead Owner Assignment

7.1 What this action does

Updates lead records with:

• A personalized FloStack microsite URL
• The assigned lead owner (as routed by FloStack)

Typical use cases

• Website form leads entering FloStack journeys
• Walk-in or call leads where you later want to send a personalized microsite
• Automations that require the Microsite URL field (e.g., email/SMS triggers)

You can configure automations in LeadSquared to instantly send the personalized microsite link to the lead.

7.2 Basic Settings & Authentication

Enter the following details –

Field	Description
Lead Source	This detail will appear as Flostack: Microsite Link Generated on the Lead Details page under Lead Source.
Default Country Code	Select a default country code. If the lead’s mobile number is captured without a country code, the default country code is added to the lead’s mobile number.
Select Time Zone	The time zone of your Flostack account.
Lead Capture Primary Search By Criteria	To avoid duplicate lead creation, select one unique lead field (e.g., mobile number/email) as the search key. Leads will be searched by the value mapped to this field. If a matching lead is found, it will be updated. Otherwise, a new lead will be created. To know how to mark a LeadSquared lead field as unique, please refer to How to Make a Custom Field Unique.
Lead Capture Secondary Search By Criteria	If lead identification and capture through the primary Search By criteria fails, the system will reattempt using the secondary Search By criteria.
Select User to Notify on Failure	If there’s an error in fetching leads, the selected user will receive a failure message via email. Choose a user from the list of available users in your LeadSquared account.To know more about the type of errors, please refer to Error Notifications.
Enable Notification	Enable the  checkbox to ensure notification emails are sent to the selected user when there’s a failed query.

Supports custom unique fields and composite keys (email + phone) as search keys. Once you’re done entering all the details, click Save.

7.3 Configuration Breakdown

• Lead/Contact Entity
  • Sync Behaviour: Capture (Create and Update existing record) is recommended. Ensures leads entering through FloStack microsites are added/updated.
  • Edit Mapping: Map microsite URL, owner email, and other custom metadata to Lead fields.
• Activity Entity
  • Activity Type(s) Definitions: Alongside Flostack Microsite URL Generated, click Create Activity.
  • Sync Behaviour: Create + Update is recommended. Create activity on microsite generation and update if the microsite is re-generated or modified.
  • Edit Mapping: Map microsite metadata to activity fields.

8. Configuration in FloStack

Navigate to Settings>Workspace Settings>Integrations in FloStack, select LeadSquared and enter:

• Your LeadSquared Host URL, Access Key, and Secret Key
• UDS Webhook URLs
  • Create Lead (Microsite Creation & Lead Owner Assignment Webhook URL)
  • Create Meeting (Create Appointments Webhook URL)
  • Update Meeting (Update Appointments Webhook URL)
  • Cancel Meeting (Cancel Appointments Webhook URL)
  • Request Callback (Call Back Request Webhook URL)

This configuration will allow FloStack to trigger the corresponding UDS actions.

Any Questions?

Did you find the content in this article helpful? Feel free to leave doubts/questions in the comment section below. We’ll get back to you as soon as possible.

The post Integrate Flostack with UDS appeared first on LeadSquared Help and Support.

The Bookings & Events module is the central hub for publishing, managing, and sharing all scheduling experiences created in Flostack. Whether you’re hosting personal consultations, running large-scale webinars, or offering multiple types of sessions to leads and customers, this module brings everything together in one place.

It consists of three core components:

• Booking Links – Personalized one-on-one scheduling pages that let individuals book time directly with an advisor, counselor, or team member.
• Events – group sessions such as webinars, orientations, demos, or training programs with configurable capacity, presenters, and landing pages.
• Listing Pages – A single, public-facing catalog displaying all your booking links and events, making it easy for users to browse and register.

All these components are powered by Meeting Types, which define the underlying rules—availability, duration, buffers, capacity, form fields, and more. Meeting Types ensure consistent scheduling behavior across every booking experience, while Bookings & Events determine how these experiences are shared with your audience.

2. Prerequisites

To learn more about FloStack (www.flostack.io), and enable it on your account, contact [email protected].

3. Booking Links

Booking Links allow you to create personal or team scheduling pages for one-to-one meetings. Each link is powered by either your default availability or Meeting Type and automatically respects your availability, duration, buffers, and calendar sync settings.

Create a Booking Link

1. Navigate to Booking & Events>Booking Links.
2. Click Create Booking Link.
3. Configure:
   • Booking Link URL – The public link attendees will use to book time with you
   • Name – Internal name for identifying the booking link
   • Use Default Availability –When enabled, the link will use the default availability configured on your Settings page.
     • Duration – Pulled from the default calendar, this can be overridden.
   • Meeting Type – Instead of the Default Availability option, you can select a meeting type that defines the availability, buffers, increments.
   • Welcome Message – Shown on the public scheduler
4. Save to generate your booking link.

Note: Click the icon to copy the booking link.

4. Events

Events let you create group sessions such as webinars, workshops, or open houses. An event uses a meeting type as its base configuration and allows you to add presenters, capacity limits, and a fully customizable landing page.

The Events section in Flostack provides a centralized view of all scheduled and created events. It includes two primary tabs—Agenda and All Events—along with options to create new events and manage attendees.

4.1 Agenda Tab

The Agenda tab displays the full calendar of upcoming and past event occurrences, helping organizers quickly track what’s scheduled.

Key Features

• Upcoming / Past View: A side toggle lets you switch between upcoming and past event occurrences.
• Event Overview: Each event entry shows details about the events.
• Manage Attendees: Click the Manage Attendees button on an event to – 
  • View the list of all registered attendees
  • Check in attendees who have arrived, and specify if they’ve brought guests.
  • Export the attendee list
  • Add attendees manually

This tab is ideal for tracking real-time event activity and managing participant lists.

4.2 All Events Tab

The All Events tab shows every event that has been created in your workspace—regardless of event status or number of attendees. This tab acts as your complete repository of events.

Creating an Event

Click Create Event to start building a new event. You will first choose between two creation modes:

4.2.1 Event Scheduler

Choose this when you want a standard scheduler-based booking experience. This option is ideal for straightforward scheduling without a custom landing page.

You can configure:

• Event Details –
  • Name
  • Description
  • Meeting type
  • Organizers & Presenters
  • Capacity management
• Schedule –
  • Date & event duration
  • Availability/working hours
  • Meeting limits.
• Booking Form –
  • Create Event Link
  • Invitee Form Questions
    • Enable or disable the option to allow the registrants to bring guests.
  • Confirmation Page

Most of the configuration for the Schedule and Booking Form section will be autopopulated with the Meeting Type configuration you’ve selected. It’s possible to further modify some of the configuration once it’s autopopulated.

4.2.2 Event Landing Page

Choose this when you want a fully branded event page with images, highlights, multimedia, and custom sections. This option provides a richer, marketing-friendly page to promote the event.

You can configure:

• Type of Event Landing Page – Select either one-off or recurring. Select one-off if you want to create a fresh events landing page without a pre-configured meeting types template. 
• Event Details –
  • Name
  • Description
  • Meeting type (only available in the recurring type, in the one-off event you can select the Mode of meeting).
  • Organizers & Presenters
  • Capacity management
• Schedule –
  • Date & event duration
  • Availability/working hours
  • Meeting limits.
• Booking Form –
  • Create Event Link
  • Invitee Form Questions
  • Confirmation Page
• Landing Page Design –
  • Upload Images: Add Banner and Main Image to the page.
  • Register Button: Configure the button label and color for the Register/CTA button.
  • Landing Page Widgets: The following widgets are available –
    • Highlights: Add highlights to showcase important numbers or information.
    • Embed URL: Enter URL to embed resources from web in your landing page.
    • Image Gallery: Add images alone or with text content as cards.
    • Text Block: Add heading and body text.

Note: Click the  icon to copy the Event link.

5. Listing Page

A Listing Page serves as a unified public catalog for all your Events and Booking Links, making it easy for visitors to discover and register for any session you offer.

Use Case

• A university publishes a Listing Page to showcase all available sessions—counseling appointments, campus tours, orientation events, and workshops—allowing prospective students to browse and register from one central page.
• A multi-specialty clinic uses a Listing Page to display all consultation types and group health sessions in one place, enabling patients to quickly find and book the right appointment without contacting the clinic.

How It Works

On the Listing Page screen, you can create dedicated listings for Events or Booking Links.

• In the Events tab, click Create to build a listing page that showcases selected events.
• In the Booking Links tab, click Create to publish a listing page containing selected one-on-one scheduling links.

For either type, you can configure:

• Name – Internal and public-facing title of the page
• Link – The URL for sharing the listing page
• Description – A short summary shown at the top of the page
• Items to Display – Add the specific events or booking links you want to include

Once saved, the listing page becomes a single, shareable destination for visitors to browse and register for your events or book one-on-one sessions.

Note: Click the icon to copy the listing link.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Flostack – Booking and Events appeared first on LeadSquared Help and Support.

The Meetings Type feature in Flostack enables users to define and manage different categories of meetings with tailored scheduling rules. It supports instant scheduling, allowing users to specify availability for specific purposes, while controlling duration, time slots, visibility, and participant capacity.

Meeting types can be one-on-one or group meetings, and can be virtual (with calendar integration) or in-person. This ensures smooth scheduling, prevents conflicts, and improves the overall attendee experience.

Benefits

• Targeted Scheduling: Allocate time for specific purposes, such as KYC verification, interviews, training sessions, or client meetings.
• Efficient Time Management: Control availability by day, time, and meeting type to reduce conflicts and no-shows.
• Automation-Friendly: Preconfigured meeting types integrate with booking links, events, and UDS (e.g., LeadSquared) to automate lead capture.
• Enhanced Attendee Experience: Participants see only relevant time slots and available capacity, simplifying the booking process.

2. One-on-One Vs Group Meetings

The following are the differences between One-on-One and Group Meetings –

2.1 One-on-One Meetings

These are private sessions with a single attendee. They are ideal for interviews, consultations, or client calls where focused, individual attention is required. Each slot is booked by one participant, and availability is blocked automatically via calendar integration.

Use Case

• A prospective student wants a personal consultation with an admissions advisor about program eligibility.
• A potential customer needs a detailed walkthrough of a product or service.

2.2 Group Meetings

These sessions accommodate multiple participants at the same time. They are suitable for workshops, webinars, or training sessions. Users can define the maximum capacity for each slot, while availability is managed for the organizer, allowing multiple attendees to book until the capacity is reached.

Use Case

• A university wants to run a campus tour or program orientation for multiple students simultaneously.
• A company runs a product demo webinar where multiple leads join at the same time.

3. Creating Meeting Types

From the FloStack dashboard, navigate to Meeting Types in the left-hand menu. You’ll see all created types with details like name, duration, and type. Click + Create Meeting Type and choose the type, One-on-One or Group.

3.1 Add Meeting Details

• Name: e.g., “Campus Orientation Session”
• Mode: In-Person or Virtual
  • Location: Required if In-Person
• Private Option: Select if the meeting should not appear publicly. Only you can view and use this meeting type.
• Meeting Capacity (Group Only): For Group Meetings, you have the option to limit the number of spots and display remaining spots on the booking page.

3.2 Set Schedule & Availability

• Date Range: Defines when the meeting type is available for booking.
  • You can choose between fixed range or indefinite.
• Duration: Length of each meeting in minutes.
  • For example, 15, 30, or 60 minutes.
• Weekly Hours: Days of the week and time ranges when the advisor is available for booking.
  • For example, Monday and Wednesday, 9:00 AM–5:00 PM.
• Calendar Sync: Connects the advisor’s external calendar (Google, Outlook, etc.) to FloStack and automatically blocks times that are already booked, preventing conflicts.
  • You can sync your calendar on the My Integrations page.
• Timezone: Select your preferred timezone.
• Meeting Buffers: Buffer time added before and after each meeting.
  • For example, add a 10-minute buffer before a 30-minute call so that an advisor has time to prepare.
• Minimum Schedule Notice: Minimum lead time required before a lead can book a meeting. It prevents last-minute bookings that the advisor cannot accommodate.
  • For example, if you add a 2-hour notice and the current time is 2 PM, the earliest bookable slot is 4 PM.
• Start Time Increments: Defines the frequency at which time slots appear for booking.
  • For example –
    • 15-minute increments → slots at 9:00, 9:15, 9:30, 9:45, etc.
    • 30-minute increments → slots at 9:00, 9:30, 10:00, etc.

3.3 Customize Booking Form

• By default, the form collects Name and Email of the attendees, these are mandatory fields. 
• Additionally, configure up to 10 custom questions to ask the attendees, and even mark them as mandatory.
  • The following Answer Types can be configured: Dropdown, Checkbox, Radio Buttons, Multiple Lines Text, Single Line Text, Count, Phone Number, and Email Input Box.
• Post-booking re-direction can show a FloStack confirmation page or redirect to a custom URL. Configuration for auto-redirect after a certain duration is also available.
  • Note: This selection will not be applied if the meeting is booked through the microsite.

4. Generate the Booking Link and Routing Rule

Once you’ve set up a meeting type, you can use it in Bookings & Events and configure Meeting Type Rules to automatically route leads based on form submissions.

• Booking and Event links can be shared on microsites, emails, or other channels.
• Leads can view available time slots and book meetings directly.

Any Questions?

Did you find this article helpful? If you have any questions or comments, please let us know in the comments section below. We’d love to hear from you and help you out!

The post Create Meeting Types on Flostack appeared first on LeadSquared Help and Support.

Iframes let you embed custom designs or external tools inside Portals or Landing Pages Pro without affecting the main layout. To ensure your embedded content works smoothly, follow the guidelines listed on this page.

2. Guidelines For Iframe or Custom Code

1. When using AI tools to generate custom designs or widgets

If you’re using AI to generate HTML, CSS, or JavaScript:

• Clearly specify that the code will run inside an iframe.
• Prompt the AI not to use external JavaScript libraries—stick to basic HTML, CSS, and JS to avoid slow load times and reduced conversions.
• Request the design in small sections, and embed each section in its own iframe instead of placing everything inside one large block.
• Ensure all buttons, scrolling, and interactions work even within the confines of the iframe.

2. Do not use AI-generated code for forms

If you need a form next to your custom design, use the built-in drag-and-drop form builder. Place your LSQ form beside a custom code block to create a hybrid layout—this ensures proper tracking, reliable submissions, and consistent behavior across portals and landing pages.

3. Adjust spacing, width, and styling for a seamless embed

To make the iframe full width, remove padding, and align it neatly with your layout, refer to the platform’s instructional video (shown below) for spacing and container setup.

If the embedded content looks cut off or doesn’t extend fully at the bottom, add this CSS:

body, iframe {
    height: 1000px;
}

This helps the iframe appear smooth and continuous, without borders or unwanted scrolling.

The post How to Use Iframes or Custom Code on Portals and Landing Pages Pro appeared first on LeadSquared Help and Support.

1. Overview

The post Portal Redirection & Error Handling appeared first on LeadSquared Help and Support.

LeadSquared Portals now support UDS-based validation for signup (registration/login) forms. This ensures that only verified and approved users can sign up on your portal

When a user submits a registration form, the portal sends the form data to a UDS flow for real-time validation before the user account is created. UDS can run any custom logic—such as checking duplicates, verifying phone or email, blocking blacklisted users, or validating against external systems.

The validation runs on the Register Save Request at each step of the signup process — applicable to both single-step and multi-step forms.

2. Core Rules

3. Response Handling and Error Logic

The Portal’s behavior depends strictly on the HTTP status code returned by the UDS endpoint.

3.1 Successful Submissions

The signup submission proceeds only if the UDS returns a 200 status code.

Example – Success Response (200)

{
  "statusCode": 200,
  "responseHeaders": {},
  "body": {
    "status": "SUCCESS",
    "success": true,
    "errors": {},
    "data": "{{Write your message here}}",
    "requestId": "c1d2e3f4-5678-9012-3456-abcdefabcdef"
  }
}

3.2 Error Handling

If the UDS returns any other status code (e.g., 400, 500), the save request will be restricted. The error message displayed to the user depends on the response body received from the UDS.

Here are two possible error scenarios:

3.2.1 Scenario 1 – Custom Error Message (From UDS)

If the UDS response includes a correctly formatted body with an errors message array, the portal displays the custom message returned by UDS.

Example:

As seen in the screenshot, the user enters a blacklisted number.

The UDS returns a 500 status code, the UDS response body includes a requestId and an errors.message array containing, “This is a blacklisted number. Please try with another number.“.

The portal UI correctly displays this custom message to the user.

3.2.2 Scenario 2 – Default Error Message (Fallback)

If the UDS response is not formatted correctly or lacks required fields, the portal shows a default error message.

Default Message: “Portal-Form Validation Failed. Please check the Portal-Form Validation service.“

Triggers for Default Message:

• UDS returns an error status, but the response body does not include errors.message field.
• The UDS response is missing either the status code or the request ID.

Example:

The screenshot shows a 500 status in the network request, but the UI displays the default “Portal-Form Validation Failed...” error. This indicates the UDS response for that specific error did not provide the required message or Request ID in the expected format.

4. UDS Configuration

To ensure successful validation, the flow should be a custom configuration type with real time response. Configure the UDS flow with the following settings:

The flow must be initiated by a Custom Trigger and must use the Return Response action to send data back to the portal.

Next, copy the custom webhook URL.

On the Portal Designer, select your Registration Form. Under States, paste the webhook URL in the UDS URL field. You should see a succesful validation.

5. Trigger Details – Sample Payload data

Below is a sample payload sent from the Portal during registration save. You can copy this payload directly into UDS to create a sample flow.

{ 

    "TaskId": "", 

    "ActivityId": "", 

    "FormId": "bf34eb59-4520-11ef-8227-064299b60867", 

    "PageId": "dllkufl5y", 

    "IsFormPreValidationEnabled": true, 

    "OpportunityId": "", 

    "FormEntity": [ 

        { 

            "FormId": "bf34eb59-4520-11ef-8227-064299b60867", 

            "TabId": "tab1", 

            "SectionId": "bf34eb59-4520-11ef-8227-064299b60867_tab1_section1", 

            "LeadFields": [ 

                { 

                    "SchemaName": "EmailAddress", 

                    "Value": "[email protected]", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Email", 

                    "RenderType": "Email" 

                }, 

                { 

                    "SchemaName": "Phone", 

                    "Value": "+91-9123411101", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Phone", 

                    "RenderType": "Phone" 

                }, 

                { 

                    "SchemaName": "FirstName", 

                    "Value": "firstname", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Text", 

                    "RenderType": "Textbox" 

                }, 

                { 

                    "SchemaName": "mx_Street1", 

                    "Value": "address", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Text", 

                    "RenderType": "Textbox" 

                } 

            ], 

            "ActivityFields": [], 

            "TaskFields": [], 

            "OpportunityFields": [] 

        } 

    ], 

    "ProcessFormEntity": [ 

        { 

            "FormId": "bf34eb59-4520-11ef-8227-064299b60867", 

            "TabId": "tab1", 

            "SectionId": "bf34eb59-4520-11ef-8227-064299b60867_tab1_section1", 

            "LeadFields": [ 

                { 

                    "SchemaName": "EmailAddress", 

                    "Value": "[email protected]", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Email", 

                    "RenderType": "Email" 

                }, 

                { 

                    "SchemaName": "Phone", 

                    "Value": "+91-9123411101", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Phone", 

                    "RenderType": "Phone" 

                }, 

                { 

                    "SchemaName": "FirstName", 

                    "Value": "firstname", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Text", 

                    "RenderType": "Textbox" 

                }, 

                { 

                    "SchemaName": "mx_Street1", 

                    "Value": "address", 

                    "RuleAppliedInfo": { 

                        "Hidden": 1, 

                        "Mandatory": 0 

                    }, 

                    "DataType": "Text", 

                    "RenderType": "Textbox" 

                } 

            ], 

            "ActivityFields": [], 

            "TaskFields": [], 

            "OpportunityFields": [] 

        } 

    ], 

    "ExecutionId": "", 

    "ActionId": "", 

    "ProcessDesignerId": "", 

    "ActivityCodeToUpdate": "", 

    "FormOpportunityCode": "0", 

    "ActivityCodesToUpdate": [], 

    "FormOperation": 1, 

    "DraftId": "", 

    "ActivityIdsToBeRemoved": [], 

    "RemovedOriginalSubformIds": [], 

    "PaymentVerificationKey": "", 

    "CurrentTabId": "", 

    "IsPortalRegistrationForm": true, 

    "UseRegisterV2": true, 

    "RegisterLeadEntity": { 

        "Email": "[email protected]", 

        "Password": "e5/ttqpaoGaZ8YOwJi1oMhD5G84sNxxxxxxxxxxxxxxxxxxxnQsxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd88fnYUpUG8s4NJYLYSRPuJJiimQCZLnomE5+4E5WTCpP3ok4EAXJt9LEfZxxxxxxxxxxxxxx=", 

        "ConfirmPassword": "iJtO8GCA0LWnogZ0BrjXXZ8lXQKTKxxxxxxxxxxxxxxxxxxxqErxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxDKbOvM0d19OeYujwgDx52sbZlyhry0ZilMBfQs6TqCMZttI/nOECUjaubcxPJ1CUtdKna9AZyYXLQTxxxxxxxxxxxxx=" 

    }, 

    "PortalSpecificDetails": { 

        "TimeZoneInfo": "US/Central" 

    }, 

    "URLSearchParams": {}, 

    "LockKey": "", 

    "PortalDetails": { 

        "URL": "https://landingpagecreate4-dobwavuz.marketxpander.net/", 

        "IPAddress": "10.230.13.6", 

        "ConnectionSpeed": "4g", 

        "Platform": "Windows", 

        "BrowserName": "Chrome", 

        "BrowserVersion": "141.0.0.0", 

        "DeviceType": "Desktop", 

        "PageUrl": "https://landingpagecreate4-dobwavuz.marketxpander.net/", 

        "ReferrerUrl": "" 

    }, 

    "RenderSettings": { 

        "ProcessDesignerId": "", 

        "ActionId": "" 

    }, 

    "SavedTabIds": [], 

    "ConnectionSpeed": "4g", 

    "Platform": "Windows", 

    "BrowserName": "Chrome", 

    "BrowserVersion": "141.0.0.0", 

    "DeviceType": "Desktop", 

    "PageUrl": "https://landingpagecreate4-dobwavuz.marketxpander.net/", 

    "ReferrerUrl": "" 

}

6. Sample Return Response Logic

Here’s an example of how the Return Response action can handle phone number validation within a UDS Custom Flow.

const main = (input) => { 

    const phoneField = input?.data?.FormEntity?.[0]?.LeadFields?.find( 

        field => field?.SchemaName === "Phone" 

    ); 

 

    const phone = phoneField?.Value; 

 

    function findLead(phone) { 

        if (!phone) { 

            return { 

                statusCode: 200, 

                responseHeaders: {}, 

                body: { 

                    status: "SUCCESS", 

                    success: true, 

                    errors: {}, 

                    data: "Number is not provided", 

                    requestId: "c1d2e3f4-5678-9012-3456-abcdefabcdef" 

                } 

            }; 

        } else if (String(phone) === "+91-9876543210") { 

            return { 

                statusCode: 500, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "This is a blacklisted number. Please try with another number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "3bfcfe46-39dd-7c86-6a87-5196d2c65971" 

                } 

            }; 

        } else if (String(phone) === "+1-9876543210") { // +1 -> 400 

            return { 

                statusCode: 400, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Bad request for this US number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "a1111111-2222-3333-4444-555555555001" 

                } 

            }; 

        } else if (String(phone) === "+93-9876543210") { // +202 -> 202 

            return { 

                statusCode: 202, 

                responseHeaders: {}, 

                body: { 

                    status: "SUCCESS", 

                    success: true, 

                    errors: {}, 

                    data: "Accepted for asynchronous processing", 

                    requestId: "a1111111-2222-3333-4444-555555555002" 

                } 

            }; 

        } else if (String(phone) === "+98-9876543210") { // +98 -> 400 

            return { 

                statusCode: 400, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Invalid or malformed number for +98 sample." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "b2222222-3333-4444-5555-666666666098" 

                } 

            }; 

        } else if (String(phone) === "+95-9876543210") { // -> 401 

            return { 

                statusCode: 401, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Unauthorized - sample number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "c3333333-4444-5555-6666-777777777401" 

                } 

            }; 

        } else if (String(phone) === "+355-9876543210") { // -> 405 

            return { 

                statusCode: 405, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Method Not Allowed - sample number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "d4444444-5555-6666-7777-888888888405" 

                } 

            }; 

        } else if (String(phone) === "+213-9876543210") { // -> 415 

            return { 

                statusCode: 415, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Unsupported Media Type - sample number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "e5555555-6666-7777-8888-999999999415" 

                } 

            }; 

        } else if (String(phone) === "+376-9876543210") { // -> 429 

            return { 

                statusCode: 429, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Too Many Requests - sample number." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "f6666666-7777-8888-9999-aaaaaaaa429" 

                } 

            }; 

        } else if (String(phone).toUpperCase() === "NA" || String(phone).toUpperCase() === "N/A") { 

            return { 

                statusCode: 422, 

                responseHeaders: {}, 

                body: { 

                    status: "ERROR", 

                    success: false, 

                    errors: { 

                        message: [ 

                            "Phone value marked as NA (not applicable)." 

                        ] 

                    }, 

                    data: null, 

                    requestId: "09876543-21ab-cdef-0000-00000000NA01" 

                } 

            }; 

        } else { 

            return { 

                statusCode: 200, 

                responseHeaders: {}, 

                body: { 

                    status: "SUCCESS", 

                    success: true, 

                    errors: {}, 

                    data: "Valid number for registration", 

                    requestId: "96d8df97-0c27-821f-5cc8-ee04ac8c91b7" 

                } 

            }; 

        } 

    }

7. Debugging Errors

Refer to the UDS logs for any failures in execution. The Logs feature in UDS allows you to monitor and troubleshoot the execution of your data sync flows: Universal Data Sync (UDS) – Logs.

Any Questions?

If you have any questions related to forms that weren’t answered here, please leave comments below. We’ll be happy to help!

The post How UDS Helps You Sign-up Only Verified Users in Portals appeared first on LeadSquared Help and Support.

In LeadSquared, lead conversion potential was traditionally measured using Lead Scores, Engagement Scores, and Lead Quality Scores. While these metrics offer valuable insights, they are static, require manual setup, and assess each parameter independently without understanding their interrelation.

To overcome these limitations, LeadSquared introduces the AI-powered Lead Propensity Score – a dynamic and automated way to predict how likely a lead is to convert.
This score is generated using a proprietary AI/ML model that analyzes behavioral and historical data across your account to identify the attributes most associated with conversions. It eliminates manual scoring setup and provides a unified, data-driven prediction to help you prioritize high-potential leads efficiently.

Key Benefits

• Objective, data-driven lead prioritization
  Engage with the right leads first based on AI-based predictions rather than subjective judgment.
• Reduced manual effort
  No manual configuration or scoring logic is required – the system automatically learns and adapts.
• Improved sales efficiency
  Helps sales teams focus their time on high-propensity leads to improve conversion rates and optimize sales performance.
• Actionable insights
  Correlate lead attributes, activities, and behaviors with conversion outcomes to improve sales strategy and customer engagement.

2. Prerequisite

This is a paid feature. To get it enabled on your account, contact your account manager, or write to [email protected].

3. How it Works

• Identifies Conversion Attributes
  The AI model automatically analyzes historical lead data to identify the attributes and behaviors that have influenced conversions in the past.
• Builds a Predictive Model
  The system continuously learns from your lead and activity data, building a model that determines which characteristics best predict successful outcomes.
• Predicts Conversion Likelihood
  Every new or updated lead is evaluated by the model and assigned a conversion likelihood (e.g., High, Medium, or Low), helping users focus on the most promising leads.
• Continuously Refines Predictions
  As lead data evolves, the model retrains itself to refresh propensity scores, ensuring predictions remain accurate and relevant over time.

4. Manage Leads Page

On this page, Propensity Scores are visible by default for all leads. You can use the score in Advanced Search to filter leads based on their propensity.

5. Lead Details Page

The Propensity Score is visible on the vCard.

6. Smart Views Page

The Propensity Score can be used to create a Smart Views page.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post AI Propensity Score – Automatically Predict Conversion Chances appeared first on LeadSquared Help and Support.

LeadSquared’s Field-Level and File-Level Encryption (FLE) enhances data security by encrypting sensitive information at the individual field level. This ensures that critical data, such as identification numbers, attached documents or financial details, remain protected from everyone outside your organization.

This feature enables secure storage and access to sensitive data across Leads, Opportunities, and Activities. Encryption can be applied to both system and custom fields, as well as Lead CFS. Additionally, LeadSquared supports Bring Your Own Key (BYOK) through AWS Key Management Service (KMS), allowing organizations to manage and control their own encryption keys for advanced security and compliance.

Example

Suppose your sales team collects customers’ PAN Numbers and Bank Account Details in LeadSquared. With Field-Level Encryption enabled, when a PAN Number like ABCPD1234F is entered, it’s stored encrypted (e.g., M7p9aZ1Qw==).

2. Prerequisites

• Field-Level Encryption is not available by default. Reach out to [email protected] to get it enabled.
• You must be an Admin to configure Field-Level Encryption.
• If you’d like to control your own Encryption Key instead of generating from LeadSquared directly, you can get it through AWS Key Management Service (KMS).

3. How It Works

1. The admin configures the Encryption Key in the Key Management page and selects the fields to be encrypted in the Web App Settings.
2. When a user enters data into an encrypted field (including fields in Leads, Opportunities, or Activities), the CRM automatically encrypts the data before saving it.
3. The encrypted value is securely stored in the database or storage system.
4. When user accesses the record, LeadSquared decrypts the data using the configured encryption key (including BYOK if enabled via AWS KMS).

4. What Can Be Encrypted

Field-Level Encryption can protect the following types of sensitive data (non-exhaustive list):

Full Name, Phone/Mobile, Email, Address, PAN, Aadhar, ABHA, DL, Voter ID, SSN, Passport, Bank & Credit Card Info, Vehicle Plate Number, etc.

5. Field-Level Encryption Settings

To access Field-Level Encryption Settings, navigate to Settings>Data Management & Privacy>Field Level Encryption.

5.1 Key Management

Once Field-Level Encryption is enabled, the admin can configure the encryption by entering an Encryption Key which can either be directly generated from here or be imported from any Key Management System. This key is used to convert data (like a customer’s phone number or ID) into unreadable encrypted text when stored in the database, and to decrypt it back into readable form for authorized users.

5.1.1 Key Generation

If you select the Generate Key option, then the Encryption Key will be automatically generated. If required, you can change the key periodically by clicking the Rotate Key option. Once you update the new key, the ability to make changes to the key will be restricted for 90 days.

5.1.2 Key Import

if you select the Import Key option, you can Bring Your Own Key (BYOK) through AWS Key Management Service (KMS) copied from AWS Key Management Service (KMS) and click Import Key. If required, you can import a new key periodically by clicking the Import Key option. Once you update the new key, the ability to import a new key will be restricted for 90 days.

5.2 Encryption Key History

View a log of all the updates that were made to the encryption key. Here you can see –

• Key Version – The version of the key based on the number of times it was updated
• Created Via – The method through which the encryption key was entered
  • Key Generation – Either Key Generation or Manual Key Rotation
  • Key Import – Import
• Created On – The date and time when the encryption key was created
• Created By – The admin user who created the encryption key

5.3 Encrypted Fields

View the Lead, Opportunity and Activity fields marked for encryption in dedicated tabs. The tabs contain grids with the following details –

• Field Name – Name of the field
• Schema Name – Unique identifier assigned to a field
• Field Type – Either Custom or System (specific to Lead Fields)
• Data Type – Text, Number, Email, Phone or Date
• Encryption Status – Either Encrypted or Queued for Encryption (Encrypting)

6. Select Fields to be Encrypted

After configuring the Encryption Key, the admin must select the relevant Lead / Object, Lead CFS, Opportunity and Activity Fields to be encrypted from the Web App Settings.

6.1 Encrypt a Lead / Object Field and Custom Field Set (CFS) Field

To secure a lead field –

1. Navigate to Settings>Leads>Lead Fields.
2. Click the Actions icon alongside the relevant system or custom lead field and select Edit.
3. On the Edit Lead Field page, under Lead Field Properties, check the box alongside Encrypt Field.

Similarly, to secure a Lead CFS field –

1. Click the Actions icon alongside the relevant custom field set and select Edit.
2. On the Edit Lead Field page, under Lead Field Properties, check the box alongside Encrypt Field.

6.2 Encrypt an Opportunity Field

To secure an opportunity field within an opportunity type –

1. Navigate to Settings>Opportunities>Opportunity Types.
2. Click the Actions icon alongside the relevant opportunity type and select Edit.
3. On the Field Configuration Tab in the Update Opportunity Type popup, click the Actions icon alongside the relevant field.
4. Check the box alongside Encrypt Field.

6.3 Encrypt an Activity Field

To secure an activity field –

1. Navigate to Settings>Leads>Custom Activities & Scores.
2. Click the Edit icon alongside the relevant activity type.
3. On the second page of the Update Custom Activity Type popup, click the Actions icon alongside the relevant field.
4. Check the box alongside Encrypt Field.

7. View Request History

To see the details about your existing field encryption request, navigate to Settings>Profile>Request History.

8. Limitations

• Global & Quick Search: The Quick Search, Global Search, and Advanced Search features may not function correctly while encryption is in progress.
• Advanced Search: Only the operators Equals, Not Equal, Contains Data, and Does Not Contain Data are supported. All other operators are not available for encrypted fields.
• Search Limitations During Encryption: The Quick Search, Global Search, and Advanced Search features may not function correctly while encryption is in progress.
• Sort/Filter: Sorting and filtering are disabled for encrypted fields.
• Reporting: In some cases, encrypted fields may display ciphertext if the report or integration does not handle decryption.
• Uniqueness: Only the system fields Email, Phone, and Mobile can be marked as unique if encrypted. Any other field marked as unique cannot be encrypted.
• Uniqueness Criteria Impact: If unique fields (such as Phone, Mobile, or Email) are marked for encryption, the uniqueness validation will not work until the encryption process is complete. This can lead to duplicate records being created. It is strongly recommended to pause record creation and updates while encryption is in progress on unique fields to avoid data inconsistencies.
• Audit: Historical audit records created before encryption was enabled will remain unencrypted. Encryption applies only to new audit entries generated after the field has been encrypted.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post How to Secure Sensitive Data with Field-Level Encryption appeared first on LeadSquared Help and Support.

By default, users can only search UDS logs using a Request ID, making it difficult to trace business-critical records such as Loan ID, Customer ID, or Phone Number when issues arise. This slows down investigations, increases developer dependency, and delays resolution.

Logger Parameter solves this by allowing users to define up to three custom key-value pairs (like Loan ID, Applicant ID, or Phone Number) along with the Request ID.

This empowers admins to instantly locate relevant records, reduce error resolution time, and minimize reliance on developers. As a result, it helps maintain data integrity, prevent workflow disruptions, and ensure a smoother experience.

2. Configure Logger Parameter

2.1 Access Advanced Options

Logger Parameters are available under Flow Advanced Options. Navigate to UDS App>Flow card(⋮ menu)>Advanced Options>Logger Parameter.

2.2 Add Logger Parameters

Up to three keys can be configured. Parameters can be mapped using dropdowns or custom mappings.

Keys may be selected from:

• Request data fields
• Headers
• Query parameters
• Action response fields.

2.3 Save Configuration

Once parameters are added and saved, they are automatically logged with every request.

2.4 Custom Mapping

You can define custom keys in Logger Parameters to capture specific values from the incoming request.

For example, you can capture values from the request URL’s query string in Logger Parameters. If the incoming request is:

https://webhook.leadsquared.com/api/v2/uds?entityType=Loan&partnerId=ACME001

You can configure the Logger Parameters as follows:

3. Using Logger Parameters in Logs

On the Logs screen, search is available for Request ID by default, and Logger Parameters will appear as additional searchable fields.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Logger Parameters in UDS appeared first on LeadSquared Help and Support.

Field Intelligence provides tools for real-time reporting and visual analytics to help admins and managers monitor their field users’ productivity and movement throughout the day from the LeadSquared web app or mobile app. It includes the following key tools:

• Distance Travelled Report – Track how far users travel each day using GPS-based calculations.
• Field Force Insights – Get a breakdown of your users’ check-in/out status, working hours, routes, and device details directly from your LeadSquared Web and Mobile App.
• My Teams – Monitor your team’s individual activity directly from your LeadSquared Mobile App and connect with them instantly via call, SMS, or WhatsApp.
• Device Binding – Secure app access by binding each user to a single approved device.

With Field Intelligence, you can:

• Visualize users’ daily routes, distance travelled, check-ins, tasks, activities and customer visits.
• Understand how users’ work hours are spent: on travel, customer interaction, or idle time.
• Contact the user directly from the LeadSquared Mobile App.
• View user activity on an interactive map for better field oversight.
• Ensure data security by binding a user to one device.

2. Prerequisites

• Users must have the LeadSquared Mobile App installed on their device, and location permission access must be enabled. To know more, please refer to Location Tracking on LeadSquared Mobile.
• Admins must enable location tracking permissions for their users:
  • Navigate to Settings>Mobile App>Permissions.
  • Under Location Tracking, enable all the permissions.
• To get data with highest location accuracy, refer to Measures to Ensure Higher Distance Computation Accuracy in Mobile App.
• Ensure that Track Location is enabled for relevant Custom Activities.
  • Navigate to Settings>Leads>Custom Activities & Scores.
  • Click the edit icon alongside the relevant activity and ensure that the Track Location box is checked.
• On the mobile devices, users must have Notifications turned on for the LeadSquared Mobile App.
• Enable user check-in in your account for location tracking and distance calculation:
  • Navigate to Settings>Users and Permissions>User Check-in.
  • Enable the Show check-in widget to web users setting.
• All mobile users must Check-In/Check-Out daily for the system to effectively track their location and calculate the distance travelled during the day. Distance calculation will not be initiated for the day if the mobile user has not checked in.
• Admins must set up an automation that automatically checks out users at the end of the day if they haven’t done it manually. Refer Auto Check-In/Check-Out for Mobile.
• To post an activity on completing a task, associate an activity to a task type. To learn more, refer Task and Activity Completion.

3. Distance Travelled Report

The Distance Travelled Report helps you monitor the daily travel of your field users through GPS data captured by the LeadSquared Mobile App. Displayed in a tabular format, it consolidates travel information across users, enabling better estimation of travel expenses and reimbursements.

4. Field Force Insights

When Field Intelligence is not enabled, the Location History Tracker Report lets you monitor your field sales users’ daily activities. With Field Intelligence, Field Force Insights provides admins and managers a detailed, real-time view of each user’s day on the LeadSquared Web and Mobile App.

It enables tracking of check-ins and check-outs, viewing live route maps and total distance travelled, monitoring time spent working, traveling, or on breaks, exporting user data, and accessing device details.

5. My Teams

The My Teams feature on the LeadSquared Mobile App empowers sales group managers or reporting managers to monitor team performance in real time, right from their mobile device. With My Teams enabled, you can —

• View check-in/check-out status and travel summaries of the users directly reporting to you.
• Track KPIs of users such as leads added, tasks completed, and opportunities created.
• Instantly contact the users via call, SMS, or WhatsApp.

This mobile-only feature is especially useful for managers on the move, offering a quick snapshot of team activity and availability throughout the day.

6. Device Binding

Device Binding is a mobile security feature that locks each LeadSquared Mobile App login to a single, registered device. It safeguards sensitive business data, ensures accurate location tracking, and blocks unauthorized access. When a user logs in, their first device is automatically bound; any attempt to log in from another device is blocked until an admin approves or resets the binding.

Any Questions?

We’d love to answer your questions or hear your own unique use cases. Feel free to share your experiences in the comments section below.

The post Field Intelligence – Feature Guide appeared first on LeadSquared Help and Support.

ACE Notifications help keep users and managers engaged by sending timely nudges about their progress. Notifications can be configured as time-based (pre-defined time intervals or cycle completion based) or progress-based (triggered when a percentage of the goal is achieved).

2. Prerequisites

• Only Admins and Super Admins can manage notifications and create custom notifications.
• At present, custom notifications are only available for Goals.

3. Types of Custom Notifications

1. Time-Based Notifications

Triggered on specific intervals during the goal cycle.

Example:

• Send a reminder every week-day (Monday–Friday) in the morning.
• Send nudges at 10%, 30%, or 75% of the goal cycle duration.

2. Progress-Based Notifications

Triggered when a user’s achievement crosses a percentage of their target.

Example: Send a nudge when a user reaches 25%, 50%, or 100% of their target.

4. Notification Settings

Notification settings provide centralized control over how goal-related updates are sent. They include General Settings, which act as the high-level switch to enable or disable notifications across the account, and the Notifications Library, which stores all saved custom notification templates (both automatic and manual).

4.1 General Settings

Navigate to Settings>Notifications>General Settings.

This is the high-level control for notifications. From here, you can enable or disable notifications for the entire account. If notifications are disabled at this level, no automatic or manual notifications will be sent, even if they are configured in individual goals. To start using goal-based notifications, ensure that general notifications are enabled first.

4.2 Notification Library

Navigate to Settings>Notifications>Notification Library. The library lists all custom notification templates.

5. Creating a Notification

Navigate to Settings>Notifications>Notification Library and click Create Custom Notification.

Enter a name and description for the custom notification.

6. Configuring Time Based Notifications

Follow these steps to configure time-based notifications –

6.1 Set Attributes

1. Choose the notification category (refer to section 3): Time-based.
2. Communication Preferences: Select the relevant module to define the focus of the notification, then choose your preferred delivery channels to ensure updates reach users in the most effective way.
   1. Module: Goals, Incentives, and Leaderboard (At present, only Goals as a module is available).
   2. Select Channel(s): Email, App, or both.
3. Choose Trigger:
   1. Automatic – Sent based on configured frequency.
   2. Manual – Template saved for on-demand use.
4. Configure Notification Details: Select the frequency and delivery time for the notification.
   1. Notification Frequency:
      • Daily.
      • Weekdays (Mon–Fri).
      • Cycle-based intervals (e.g., 10%, 30%, 75% of the cycle).
   2. Notification Time:
      • Morning (time close to 10:00 A.M).
      • Evening (time close to 9:00 PM).
5. Optionally, you can assign this notification to specific goals (by frequency type: monthly, weekly, etc.).

6.2 Compose Notification

1. Create Separate Content for Managers and Users – By default, the messages will be auto-generated. But you can edit these messages and draft tailored messages for each audience on Email and Push-App. For example, managers may need consolidated team performance updates, while users should receive individual progress updates.
2. Insert Dynamic Values – Personalize notifications by adding placeholders such as:
   • Achievement Percentage – Show how much of the goal has been achieved.
   • Reporting Manager – Reference the user’s reporting manager.
   • On-Track/Off-Track Status – Provide a quick performance indicator to keep recipients aware of their standing.
3. Supporting Details – Add key information to make the notification more useful. This includes audience-specific content for managers and users, dynamic values like required vs. actual run rate, and actionable links that redirect recipients to goal details for quick follow-up.
4. Preview Before Finalizing – Verify that dynamic fields and links render correctly for both users and managers before saving the notification.

7. Configuring Progress Based Notifications

Follow these steps to configure progress-based notifications –

7.1 Set Attributes

1. Choose the notification category (refer to section 3): Progress-Based.
2. Communication Preferences: Select the relevant module to define the focus of the notification, then choose your preferred delivery channels to ensure updates reach users in the most effective way.
   1. Module: Goals, Incentives, and Leaderboard (At present, only Goals as a module is available).
   2. Select Channel(s): Email, App, or both.
3. Choose Trigger:
   1. Automatic – Sent based on configured frequency. In progress-based notification, you can only select an automatic trigger.
4. Configure Notification Details: Select the frequency and delivery time for the notification.
   1. Notification Frequency:
      • Select a predefined or custom percentage of achievement.
   2. Notification Time:
      • Morning (time close to 10:00 A.M).
      • Evening (time close to 9:00 PM).
5. Optionally, you can assign this notification to specific goals (by frequency type: monthly, weekly, etc.).

7.2 Compose Notification

1. On-Track/Off-Track Messages For Managers and Users – For each achievement percentage configured in the notification frequency, the system sends an on-track or off-track message. Default messages are provided, but you can edit the content for both Email and App notifications.
2. Insert Dynamic Values – Personalize notifications by adding placeholders such as:
   • Achievement Percentage – Show how much of the goal has been achieved.
   • Reporting Manager – Reference the user’s reporting manager.
   • On-Track/Off-Track Status – Provide a quick performance indicator to keep recipients aware of their standing.
3. Supporting Details – Add key information to make the notification more useful. This includes audience-specific content for managers and users, dynamic values like required vs. actual run rate, and actionable links that redirect recipients to goal details for quick follow-up.
4. Preview Before Finalizing – Verify that dynamic fields and links render correctly for both users and managers before saving the notification.

8. Sending Manual Notifications

If you selected a manual trigger while creating a notification, you’ll need to send it manually from the Manage Goals page. You can also choose to send automated notifications manually, provided they are already assigned to that goal.

1. Go to Manage Goals – Navigate to the Manage Goals page and locate a goal that is currently in progress.
2. Open Goal View – Click on the goal to open its detailed view.
3. Select Users – Choose one, multiple, or all users assigned to the goal.
4. Click Send Notification – Once users are selected, a Send Notification button will appear at the top.
5. Compose Notification – In the Compose Notification window:
   1. Pick a manual notification or an automation-based notification already linked to the goal.
   2. Select delivery channels (Email, Push-App, or both).
   3. Edit manager content, user content, and add supporting details like required vs. actual run rate.
6. Preview & Send – Review the notification and click Send Notification to deliver it immediately.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Create Custom Notifications on ACE appeared first on LeadSquared Help and Support.

Device Binding is a mobile security feature that ensures users access the LeadSquared mobile app only from a single, registered device. This protects sensitive business data, maintains accurate location tracking of the user, and prevents unauthorized access. Device Binding ties a user’s mobile app login to one specific mobile device. Once a device is bound:

• Any login attempt from a different device is automatically blocked.
• Only an admin can approve or reset the device binding to allow access from a new device.

2. Prerequisites

• Device Binding is a feature only for LeadSquared Mobile App users.
• This feature is available only if you have enabled Location Insights in your account. To enable Location Insights and Device Binding, reach out to [email protected].

3. How It Works

• Once enabled, Device Binding automatically links a user’s account to the first mobile device they log in with.
• If a user upgrades or changes their device, they must send a device binding request to their admin to register the new device.
• From the LeadSquared Web App, admins can manage device registrations by:
  • Approving or rejecting new device requests
  • Unmapping existing devices when required

4. Device Binding on LeadSquared Mobile App

Once Device Binding is enabled, the mobile user will be logged in seamlessly. This device will become their bound device for all future logins. If a user needs to switch to a different device, there are methods to do so. These options are described in the sections below.

4.1 Login using Unregistered Device

If a user logs in on a new, unregistered device, a non-dismissible pop-up appears saying “This device is not registered with us. Please contact your admin to register this device.”

From here, the user can make one of these choices:

• Contact Admin – Sends device binding request to admin, displays “Request Sent”, and logs the user out.
• Cancel – Logs the user out without sending a request.

4.2 Login using Unmapped Device

In certain cases, the admin can unmap a user’s device (for example, if the device is lost or stolen). If a user tries to log in from a previously registered device that has been unmapped, they will see a pop-up message: “This device is no longer linked to your account. Please contact your admin to regain access.” They will be logged out immediately. The user can then attempt logging in again, which will trigger the Login Using Unregistered Device flow.

5. Device Binding Management on LeadSquared Web App

Admins get full access to all details about the users’ registered devices from the Device Binding page on the LeadSquared Web App.

5.1 View Bound Devices

To view the bound devices of all users –

1. Navigate to Apps>Field Sales Territories>Device Binding.
2. All the registered devices and their details are displayed under the All User Devices tab.

Alternatively,

1. Navigate to Apps>Location Insights>Device Binding.

5.2 View Device History

To view a user’s device history, click the icon next to their name. This will display a list of all devices the user has previously registered with LeadSquared along with its platform, model, OS version, app version and other device-related details.

5.3 Approve / Reject Devices

Admins can approve or delete device binding requests sent by mobile users from Location Insights>Device Binding>Approval Requests tab in web app. The admins can:

• Approve – Marks new device as approved, unmaps old device, sends notification that says, “New device registration request approved”.
• Delete – Discards the request, shows toast “Request Deleted”.

Once the new device is approved, the user can log in and continue with their daily workflows.

5.4 Unmap User Devices

If a user loses their device or no longer has access to it, they can request the admin to unmap it. Once unmapped, the lost or stolen device will no longer provide access to any data. Admins can complete this action directly from the web app by unmapping the user’s active device.

Any Questions?

We’d love to answer your questions or hear your own unique use cases. Feel free to share your experiences in the comments section below.

The post Device Binding – Feature Guide appeared first on LeadSquared Help and Support.

With Lead 360, you can fully customize the Lead Details Page on the LeadSquared Mobile App (including fields, details, and actions). This feature is available when Casa is enabled on your account and helps you build comprehensive Lead Details Pages that give users a clear view of each lead’s journey.

• Configure the page layout with either widgets or tabs, allowing you to present lead data in a more visual way.
• Preview the page in real time before publishing it.
• Create and assign different Lead Details views to specific teams.

2. Prerequisites

• This feature is available only if Casa is enabled on your account. To enable Casa, reach out to [email protected].
• You must be an Admin to configure the Lead Details Page using Lead 360.

3. How It Works

With Casa enabled, the Lead 360 page brings together all lead information in a single, customizable view on the LeadSquared Mobile App. It is made up of three main components:

• Quick View Card – Displays key identifiers, fields, and quick actions at the top of the page for instant context.
• Page Layout – Organizes detailed lead interactions. You can choose between:
  • Classic Menu Tabs (a tab-based layout for tasks, activities, notes, etc.)
  • Custom Landing Page (a widget-based layout with tile or detailed views).
• Actions Panel – Lets you add and arrange actions (e.g., call, email, WhatsApp) for faster engagement.

Once configured, you can preview your layout and then publish it either as the default view for all users or assign it to specific teams.

4. Access Lead 360

1. On your LeadSquared Web App, navigate to Apps>Casa.
2. From the left menu, select Lead 360 under Mobile.
3. On the Lead 360 Configurations page, select Create New.

5. Customize the Quick View Card

The Quick View Card appears at the top of the page and can be customized to show key lead details. This helps users quickly identify and act on important information. In the example given below –

• Identifier –  First Name and Last Name of the lead
• Fields – Role, Lead Stage, Division, Department
• Quick Actions – Share Lead, Directions, Email Lead, Call Lead

To configure the quick view card –

1. Select Identifier – Choose the best identifier for your business use case (e.g., Name, Email).

• Click the Click To Add Field button to add the identifier for the leads.
• In the Add Lead Identifier panel, you can add upto 4 preferred identifiers and click Add. For a particular lead, if the first preference is unavailable, the system will display the next available field.
• Click the edit icon if you want to make changes to your identifier fields.

2. Display Fields – Show up to 4 lead fields on the card

• Search and select the relevant fields from the All Fields panel.
• To remove a field, click the delete icon alongside the relevant field.

• Enable the Show in List Card toggle to display the configured fields in the Smart Views and Lead list pages.

3. Configure Quick Actions – Configure up to 4 actions from the given options

• Under Card Actions, hover over the widgets to view their labels. The actions are Call, SMS, WhatsApp, WhatsApp Business, Email, Star, Change Stage or Directions.
• Select the relevant actions you want to display in the card.
• To remove a quick action, hover over the added widget and click the delete icon.

• Enable the Show in List Card toggle to display the configured actions in the Smart Views and Lead list pages.

6. Configure the Page Layout

You can customize the main Lead Details Page to display key interactions with the lead. You can configure the page in two ways:

• Classic Menu Tabs – Display lead information in a tabbed layout.
• Custom Landing Page – Use widgets for a more visual layout.

Select Page from the leftmost panel. On the Create Page panel, hover over Custom Landing Page or Classic Menu Tabs to preview how your configured page will appear with each option.

6.1 Configure Classic Menu Tabs

You can add both system and custom tabs to the page. Once added, you can scroll horizontally to navigate between them. In the example below, the configured tabs include Tasks, Details, Activities, etc.

To configure Classic Menu Tabs –

1. Click the arrow in the Classic Menu Tabs box on the Create Page panel.
2. From the Menu Items list, select the relevant tabs. The available tabs are Activities, Tasks, Notes, Documents, Social Profile, About and Approvals.

To add a custom link as a tab –

1. Click Add Custom Menu.
2. On the right side Custom Menu panel, enter a name for the tab and the link. Then, click Add.

Click the Try Widgets button to configure the page using widgets instead of tabs.

6.2 Custom Landing Page

You can add widgets from the available options or create custom widgets. You can choose to display the widgets in the Tile or Detailed view. The widgets can be configured with either an icon or an image. All widgets appear below the lead card, and tapping one navigates to the relevant screen (e.g., tapping an Opportunity widget opens the Opportunity List).

In the example shown, the image on the left is configured with Tile View while the image on the right is configured with Detailed View. This is described in the section below.

To configure widgets –

1. Click the arrow in the Custom Landing Page box on the Create Page panel.
2. Click the plus icon alongside the relevant item in the left side widgets panel.
3. On the configuration panel that opens on the right side –
   • Enter a name or label for the widget.
   • Select the Widget Type.
     • Tile View – The widgets are displayed as tiles with an icon or an image (you can upload the relevant image from your device)
     • Detailed View – Each widget shows the three most recently modified entities
   • Configure the widget as required and click Save.

To add a custom link as a widget –

1. Click Add Custom Widget.
2. On the right side Custom Menu panel, enter a name for the widget and configure the Widget Type as required.
3. Enter the relevant link and click Save.

7. Set Up Actions

You can quickly add and rearrange actions as required to engage with leads. Select Actions from the leftmost panel and begin customizing. In the example given below, the configured actions are Call, SMS, Update Location, Add Notes and Add Activity.

To configure the Actions –

1. Select the relevant items from the left side Actions panel. The action is directly added to the page.
2. To edit the name and icon of an action, hover over the relevant action on the right side Quick Actions panel and click the edit icon and make the relevant changes.
3. To delete an action, hover over it and click the delete icon.
4. Once you’ve added all the necessary actions, you can rearrange them through a drag and drop action using the icon.

8. Preview & Publish the Details Page

Once you’ve configured the details page, you can enable the Preview Mode toggle to view the card, tab, and action arrangement. If you’re satisfied, you can Publish it as the default view or assign it team-wise.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Lead 360 – Feature Guide appeared first on LeadSquared Help and Support.

This action allows you to make a call to any REST API within your UDS workflow.

Configuration Includes:

• Endpoint URL and HTTP method (GET, POST, PUT, etc.)
• Request headers, query parameters, and body
• Dynamic value mapping using variables from previous steps
• Transform data as needed using LiquidJS filters.
• Handling responses and errors

2. Prerequisites

• You must be an Administrator user, or access must be shared to you by an Admin user.
• The Universal Data Sync Connector is a paid feature. To enable it on your account, contact your account manager, or write to [email protected].
• Before creating actions, you must select a trigger for your data flow. For more information, see Select a Trigger.

3. Example Data Flow

We’ll be using a public API to set up data flows using UDS connector for an external system, but the same approach can be applied to any provider.

Action – Send leads data to an external system from LeadSquared.

4. Create an Action

1. Click + Action.
2. Under the Custom action dropdown, select Call Any API of LeadSquared.
3. Enter the name and description, then click Save & Next.

5. API Setup

This section allows you to define the API you want to call. Here, we’ll take an example API and configure it to send data from LeadSquared. This is a 3 steps process:

5.1 Input cURL

If you have a sample cURL request, you can paste it into this window. Using cURL helps automatically identify the required variables, create them, and complete the API setup for you, just in one click.

5.2 Define Variables

This section displays the list of all variables for your API. It refers to a placeholder used in an API request whose value can be dynamically assigned later.

If you’ve used a cURL in the previous step, variables are created automatically. However, you can also manually add, edit, or update existing variables as needed. In the next step (Variable Mapping), you’ll be able to assign values to these variables.

While defining a variable, you also need to select its type and Required for API.

5.2.2 Type

Choosing the correct type is important, as it determines the transformation options available during the Variable Mapping step. For example, if the variable type is set to Date, you’ll be able to configure date format transformations while mapping.

Supported Variable Types:

• String (default): e.g., "any text or value"
• Boolean:  true / false
• Number: e.g., 1, 2.5, 100
• Date: e.g., 2025-08-07, 07/08/2025
• DateTime: e.g., 2025-09-05 02:00:00
• Time: e.g., 13:01:00
• Phone: e.g., +91-98xxxxxxxx

5.2.3 Required for API

This flag gives you control over, when the API call should proceed. If enabled for a variable, and during execution the variable’s value is either missing or null, the API call will not be initiated, and the request will be marked as invalid.

5.3 API Configuration

The API Configuration interface allows you to define all the details of the API, you want to call, such as the endpoint, HTTP method, request body, headers, and query parameters.

You can replace static API parameters with variables, which makes your setup more flexible. These variables can come from:

• Steps you configured earlier in the workflow
• Global variables you’ve defined
• System variables available by default (e.g., LEAD_ID, ORG_ID, LSQ_SECRET_KEY, APPLICATION_ID, etc.)

If you used a cURL request in the earlier step, many of these fields will already be pre-populated. You can still edit or remove any of the items as needed.

Steps to Configure:

1. HTTP Method – Choose the method for your request (Supported methods: HEAD, GET, POST, PUT, PATCH, DELETE).
2. Merge Fields – In the top-right corner, click View Merge Fields to see a list of available variables and keys. You can add these parameters to your query string or request body as required.
3. Headers – Go to the Headers tab and click Add New to include additional headers. Enter the required key–value pairs.
4. Request Body – Navigate to the Body tab to review and update the request body. You can also change the format (Form Data, x-www-form-urlencoded, Raw JSON/XML, etc.). Use Merge Fields to insert additional variables wherever required.
5. Save Configuration – Once done, click Save & Close.

7. How To Do Custom Mapping With Trigger Data

When you want to map trigger data manually, you can use the JSON path of the field you need. This lets you directly access specific values from the request payload.

When you are trying to do custom mapping for variables then you can use the json path of data which you are using.

Example Trigger Data:

{
  "name": "leadsquared",
  "email": "[email protected]"
}

Here, the mapping for name would be {{ data.name }}.

In this case:

• data is the root node, because the entire request payload is stored inside a key named data.
• name is the field being accessed.
• So, {{ data.name }} will return leadsquared.

If you’re unsure about the correct JSON path for your data, you can use JSON path identifier tool (available in the interface) to quickly locate the exact path. If the path for the parameter (from the JSON Pathfinder) is x.name, pass it here as {{data.name}}

8. Transform Data

Transformation lets you manipulate mapped data before passing it to the API.

The available transformation options depend on the variable or field type you selected (e.g., String, Number, Date, etc.).

If a predefined transformation option isn’t available, you’ll get access to a playground where you can write your own LiquidJS code to transform the data as needed.

9. Response Mapping For Success

Response Mapping for Success allows you to define the structure of your API’s success response, specify which key’s value from the response should be stored in the defined variable, and set how long this value should be cached to avoid multiple calls (if required in case of time bound token expiry).

9.1 Data Key Selection

Here, you need to provide a sample response for the configured API, so the system understands the response structure. And then specify the exact key or path in the response that holds the value you want to extract and store in the global variable.

9.2 Success Criteria

This section allows you to customize what success means for your API requests. By default, any response with a 2xx status code is treated as successful.

While this works for most standard scenarios, it may not be sufficient for all APIs. In some cases, an API might return a 4xx or 5xx status code even when the operation was actually successful from your workflow’s perspective. Alternatively, the response body may contain specific keywords or flags that indicate success, regardless of the status code.

With custom success conditions, you can define logic that evaluates both the status code and content of the response. This gives you complete control over how success is interpreted within your workflow.

Example:

Let’s say your API returns following response body with response status code as 400

{
  "status": 400,
  "message": "Previous token is not expired",
  "AuthToken": "xxxxxxxxxxxxxxxxxx"
}

10. Response Mapping For Errors

This section allows you to set the definition of error for your workflow and retry logic.

By default, any response outside the 2xx status code range is considered an error.

While this works for most standard scenarios, some APIs may return a 2xx status even when the operation has actually failed. In such cases, relying solely on status codes may not accurately reflect the true outcome.

Custom Error Conditions let you define logic that evaluates both the response status code and the content. This gives you complete control over how errors are identified within your workflow.

Example: 

Lets say your API returns following response body with response status code as 200

{
  "status": 200,
  "message": "error"
}

11. Chaining Actions

In this section, we’ll demonstrate a simple example of how to use the response of a previous action in subsequent actions and handle more complex workflows.

We’ll use the LeadSquared Create a Note API to post the ID received in the response of the previous action as a note on the lead.

First, we’ll create the action and configure the API.

Next, we’ll map the response received from the previous action as the value for the NOTE field.

12. Next Steps

Now that you’ve set up an app, a data flow with actions, you can create more apps or data flows if required.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Universal Data Sync (UDS) Create Actions – API Action appeared first on LeadSquared Help and Support.

In the LeadSquared NextGen Web Experience, you may sometimes see a banner at the top of your screen and a badge in the header indicating:
“ Slow connectivity detected. This may take a little while longer.”

This feature appears whenever there’s a network drop that may slow down page loads or actions in the CRM. It’s not an error or outage – the application will continue to work as expected, just slower than its full potential.

To learn more about the new web experience, see LeadSquared NextGen – New Web Experience.

2. How it Works

LeadSquared flags network drops based on the input received from your browser, using the Network Information API (navigator.connection.downlink).

• If your reported speed drops below 5 Mbps, the system displays a slow network banner and a network badge in the header.
• The banner disappears automatically when your connection improves.
• Hover on the badge to view your connection speed.
• You can dismiss the banner, but if conditions remain poor, it will reappear.

Why you will see this banner and badge:

• On unstable Wi-Fi or mobile networks
• When your device throttles bandwidth in battery saver or data saver mode
• If there is background activity consuming bandwidth
• When using a VPN, proxy, or corporate firewall that slows real-time traffic

3. Why Speed Tests Show Different Results

You might sometimes wonder why tools like Fast.com or Speedtest show your internet as very fast, while LeadSquared still displays a slow network banner or badge.

This happens because speed tests and your browser measure different things:

• Speed test tools run short, controlled experiments to measure your maximum possible internet speed under ideal conditions.
• LeadSquared relies on your browser’s real-time network estimate (via the Network Information API), which reflects what your device can actually deliver at that moment, considering all background factors.

For example, your Internet Service provider may provide 100 Mbps internet, and a Speedtest may confirm this. But your browser could still report 2-4 Mbps due to the following reasons:

• If you have unstable connection
• Connected through a mobile hotspot
• On a weak Wi-Fi signal
• Using a VPN or proxy
• Firewall policies that might affect the bandwidth
• Device is on low battery with battery/energy saving mode preventing consumption of bandwidth

This is why you might see different results between the speed test platforms and the speed shown on LeadSquared.

4. What You Can Do

If you see the banner or badge frequently:

1. Refresh the page after a few seconds.
2. Switch to a stable Wi-Fi or wired (Ethernet) connection.
3. Close background apps or tabs that may be consuming bandwidth.
4. Disable battery saver or data saver modes on your device or browser.
5. If you’re on a corporate network, contact your IT team to check firewall or proxy restrictions.

FAQs

Q: Can I dismiss the banner?
Yes. You can close it, but if your connection stays unstable, it may reappear.

Q: Does this mean LeadSquared is down?
No. The CRM remains fully functional. The banner and badge only indicate that your internet conditions may affect responsiveness.

Q: Why don’t I see the banner and badge all the time?
They only appear when your browser detects a drop in network quality. On stable connections, they won’t show.

Q: Why do I see a warning even though Speedtest shows high speeds?
Because Speedtest measures raw bandwidth in ideal conditions, while LeadSquared uses your browser’s real-time effective speed (which factors in latency, congestion, and device limitations).

The post Network Quality Banner and Badge in LeadSquared NextGen appeared first on LeadSquared Help and Support.

The Object Types Associations feature allows you to link one Object Type with another. This helps you model real-world relationships between different entities (patients, students, dealers, invoices, loans, etc.) inside LeadSquared. This makes it easier to view and manage complex relationships across your data.

Why Use Associations?

• Healthcare: Associate a patient with a clinic, or a patient with multiple clinics.
• Education: Associate students with a high school, or multiple students with a single school.
• Manufacturing: Link dealers, distributors, wholesalers, and manufacturers together.
• Finance: Associate customers, loans, and nominees.
• Documentation: Treat invoices or purchase orders as objects, and associate them with customers, dealers, or manufacturers.

Example: If a loan is created as an object, it can be linked to both a customer and a nominee. When viewing the customer’s record, you’ll see all loans procured by that customer. When viewing the nominee’s record, you’ll see all loans linked to that nominee.

2. Prerequisites

• You must have Object Types enabled in your account. Reach out to [email protected] to get this enabled.
• You must be an Admin to set this feature up.

3. How It Works

1. Configure the Association – Create a Unidirectional or Bidirectional Association between two Object Types, depending on how you want them to interact.
2. Add the Association Field – Include the association field in the Object Form so users can link objects while creating or updating a record.
3. Add Tab in Object Details View – Ensure that the ‘Associations’ tab is configured in the Object Details View Customization.
4. Associate Objects – While adding or editing an object via forms, select the related object using the association field. Or from the object details page, add the associated object.
5. Manage Associations – Open the Details Page of any object to view its associated records. From here, you can perform actions such as adding, editing, and managing linked objects.

4. Unidirectional & Bidirectional Associations

There are 2 types of associations – Unidirectional serves most use cases, while Bidirectional is used for more complex workflows.

Unidirectional Association (Customer → Loan)

In a unidirectional association, the link is created from only one side.

How it works:

• From the customer record, you can add a new loan.
• However, from the loan record, you can’t add a new customer (since the link is Customer → Loan).

Actions users can take on each object type depend on –

• Ownership of the objects
• Permission Template settings
• Sales Group Configurations
• Object Sharing

To learn more, see Permissions for Associated Objects.

Bidirectional Association (Customer Loan)

In a bidirectional association, the relationship can be created from either side.

How it works:

• From the Customer page, you can add a new loan.
• From the Loan page, you can also add a new customer (since the link is Customer Loan).

Just like unidirectional, all actions on both objects are allowed based on the users’ permissions.

5. Create Associations

Object Type Associations can be configured as either Unidirectional or Bidirectional, depending on how you want objects to interact with each other.

To Associate Object Types –

1. Navigate to Settings>Objects>Object Types.
2. Click the Actions icon alongside the relevant object type and select Manage Associations. Let’s take Customer as the object type in a Financial Service Industry scenario.
3. On the Manage Associations popup, click Create New.

Unidirectional Associations

A unidirectional association is a one-way relationship between two object types. When you create it, the association is visible from the primary and associated object’s details pages.

1. From the Associated Object Type dropdown, select the object type you want to associate the current object type with. For instance, you select Loan object type to be associated with Customer object type.
2. Select 5 Loan object fields and an identifier among them to be displayed in the Customer details page. These are the only fields that will be mapped and displayed on the object details page.
3. Then, select 5 Customer object fields and an identifier among them to be displayed in the Loan’s details page. These are the only fields that will be mapped and displayed on the object details page.
4. Then, set the maximum number of associations that can be created.
5. Click Save.

Bidirectional Associations

A bidirectional association is established when you create associations in both directions between two object types. In other words, once you associate Customer with Loan, you also create a reverse association from Loan back to Customer. Here, both objects hold the association equally.

Once you create a unidirectional association, create the reverse association by repeating the process.

6. Create Forms & Processes

Once associations are set up, add the relevant Associated Object fields to your forms so users can link related records while filling out the form

For example, while creating a loan object, you can associate both the customer and the nominee in the same form.

1. Navigate to Workflow>Manage Forms and click Create Form.
2. Select For Inside Sales/Portal from the Choose Purpose popup.
3. Name the form and select the relevant Object Type for which you want to create the form. Click Next.
4. Choose the type and flow of the form.
5. Search and add the relevant object fields in the form. The associated object types can be added here directly.

Once the form is configured, incorporate it in the process

1. Navigate to Workflow>Process Designer and click Create Process.
2. On the popup, select At Specific Work Area.
3. Then, select the relevant object type and click Continue.
4. In the Choose starting point popup, select the relevant work area and click Save.
5. In the Process Designer, click the plus icon and select Show Form under Actions.
6. In the Show Form popup, select the relevant form and configure it as required. Click Save and select Publish on the Process Designer.

7. Configure Object Details View

Once the associations are created, add the Associations tab to the object details page.

1. Navigate to Settings>Objects>Object Details View.
2. Select the relevant Object Type from the dropdown and click Create.
3. Configure the details as required. To learn more, see Customize Object Details View.
4. Under Tabs, ensure Associations is selected. Configure the other details and click Save.
5. Then apply this view to your users.

8. View Associations on Object Details Page

On the Object Details page, you can view Associated objects in a grid format under the Associations Tab. If an object type has multiple associations, for example, if a Customer is associated with both Loan and Nominee, separate tabs will be displayed for each association. You can select a tab to view the relevant grid.

Unidirectional Associations

In a Unidirectional Association, one object acts as the child and the other as the parent. The association flows only in one direction.

Example: Customer → Loan

• From the Customer Object Type, we associate a Loan Object Type
• For Customer Sarah Adams, we associate Loan #LN123

What you see:

• On Customer Sarah Adams’ Associations tab:
  • List of Loans associated with Sarah (Loan #LN123 appears as a Primary Association).

• On Loan #LN123’s Associations tab:
  • List of Customers where Loan #LN123 is associated (Sarah Adams appears as a Secondary Association).

Bidirectional Association

In a Bidirectional Association, associated object types show up in the primary or secondary association tabs, depending on where the association was added from.

9. Add Associations on Object Details Page

You can directly associate objects from the Object Details Page. This is helpful when objects are created individually and are not associated through the form.

If you have only one associated object type, click Add Primary Association and select the relevant object. Click the checkbox alongside the relevant objects to select multiple objects from the dropdown. If you have multiple object type associations, select the relevant tab and Add Primary Associations.

10. Permissions for Associated Objects

A Sales User’s ability to view, update, or remove associations depends on their ownership of the parent record or the access provided through object sharing (lead sharing), permission templates and sales group configuration.

Access to associated objects is controlled by the permissions on the parent record:

• Users with View access can see associated objects.
• Users with Modify access can update or remove associations.
• Ownership of the parent record automatically provides full access.

In short, the higher the access level on the parent record, the more control the user has over its associated objects.

Let’s take Sales User George as an example here.

11. Actions Related to Associations from the Object Details Page

You can perform actions on an associated object directly from the Object Details Page of the object it is linked to. For example, if Loan #LN102 is associated with Sarah Adams and appears in the Associations tab, you can take actions such as editing the loan, adding tasks or activities, sending emails, making calls, and performing other supported actions on the #LN102 object directly from Sarah Adams’ details page.

To remove an existing association –

1. On the Object Details Page of the relevant object, select the Associations Tab.
2. Click the Actions icon alongside the relevant object under Primary or Secondary Associations.
3. Select Remove Associations from the dropdown.
4. On the Remove Associations popup, click Yes.

12. FAQs

1. How is this different from Activities?

Activities can only be associated with one lead or object. Associations let you link one object with multiple objects at once.

2. Can I make associations mandatory?

Yes. When adding association fields to forms, you can mark them as required.

3. How many fields can I display in the Associations tab?

You can display up to 5 fields.

The post Object Types Associations appeared first on LeadSquared Help and Support.

You can create Custom Columns in the Data Source section of SIERA reports. A custom column lets you build new fields by writing expressions that combine existing columns, apply conditions, or transform values.

This makes your reports more flexible by allowing you to model business-specific logic without altering the underlying data.

Once a custom column is created, it can be applied in multiple areas of your report:

• Row/Column Grouping → Categorize data by your custom logic.
• Values → Use them inside other custom measures using Expression Builder.
• Filters → Apply custom logic to refine report data.
• Drill-Down → Add as drillable fields for deeper exploration.
• List Report Fields → Display custom fields directly in list-style reports.

2. Prerequisites

• SIERA is a paid feature. To enable it for your account, contact your account manager or [email protected].
• For more information on building a SIERA report, refer to SIERA Report Builder.

3. Example Use Cases

Here are a few example use cases for custom columns in SIERA –

• Create a column that flags leads as High Priority if their Lead Score > 50, otherwise mark them as Low Priority.
• Combine two numeric fields (e.g., Lead Score and Engagement Score) and display one of them based on a condition.
• Build a dynamic column that returns Yes/No depending on whether a lead meets specific criteria.

4. Creating a Custom Column

Follow these steps to create custom columns –

1. In the report builder, navigate to the Data Source section.
2. Select the Custom Columns tab and click + New Column.
3. Enter a Column Name and build your Expression using the Expression Builder.
4. Click Save.
5. The new column will appear under the Custom category in the Additional Panel.

While building the expression, you can reference existing fields, apply conditions (`IF` statements), and use supported functions.

For example:

If('Leads.Lead Score' > 10, 'Yes', 'No')

This expression creates a column that outputs Yes if the Lead Score is greater than 10, otherwise No.

FAQs

1. Can I use a custom column in multiple places in the same report?
Yes. Once saved, it’s available in grouping, values, filters, drill-downs, and list reports.

2. What happens if I mix data types in my expression?
The output defaults to String unless all outputs are consistently numeric or date-time.

3. Are custom columns available in sub-queries?
Yes. You can create them inside a query, and they will be available in the main report if included in the query grouping.

4. Do custom columns affect source data?
No. They are report-level transformations and do not alter the underlying database.

The post Create Custom Columns in SIERA appeared first on LeadSquared Help and Support.

This article helps Administrators enable and customize Object Types on the LeadSquared mobile app (both iOS & Android). It also shows how field sales teams can use Object Types to organize and perform their daily workflows easily within the app.

What are Object Types?

Object Types allow you to represent and manage different business entities such as Students, Parents, Agents, Partners, and more as distinct modules within your CRM. With Object Types enabled, you can customize how leads, opportunities, tasks, activities and plans are managed for each of these entities. On the LeadSquared Mobile App, Object Types help streamline your workflow by showing only the most relevant information and actions based on the type of object you’re working with.

Why use Object Types?
With Object Types, you can:

• Avoid clutter by separating data for different entities instead of overloading the leads module
• Customize deeply with each object type having its own:
  • Forms and fields
  • Opportunity stages and pipelines
  • Activities, tasks, and Smart Views
• Give sales teams views and actions that match the object type they’re working with

2. Prerequisites

• Object Types is a paid feature. To get this enabled, reach out to [email protected].
• You must have the latest version of the LeadSquared mobile app installed on your device.
• Admins must first enable Object Types to appear on the mobile app via –
  • Mobile Navigation Settings in the side or bottom menu
  • Casa Menu Builder in the side or bottom menu
  • Casa Widgets in the homepage

Once enabled in any of the 3 specified ways, the list pages for each Object Type are displayed on the mobile app.

3. Mobile App Capabilities with Object Types

Once an Admin enables and configures Object Types, they are fully supported in the mobile app—exactly as set up by the admins.

With Object Types enabled, the following pages and features become available –

4. Dedicated List Page for each Object Type

In the mobile app, each object type has its own dedicated list page. These pages allow you to view and manage objects specific to each type.

You can view the object list pages in the mobile app by first configuring them through –

• Mobile Navigation Settings in the side or bottom menu
• Casa Menu Builder in the side or bottom menu
• Casa Widgets in the homepage

4.1 How To Configure Object List Pages via Mobile Navigation Settings

Once configured the object list pages show up in the hamburger menu on the mobile app. In the screenshot below, the object types (Manufacturer, Dealer and Distributor) are configured to be displayed on top.

To configure the hamburger menu with the object types –

1. Navigate to Settings>Mobile App>Mobile Navigation.
2. Drag and drop the relevant object type name in the Visible Menu Tabs as required. Click Save.

In the example below, the object types are Dealer, Manufacturer and Distributor.

4.2 How To Configure Object List Pages in Menus via Casa

If you have Casa enabled, you can use the Menu Builder to add My Teams to the mobile app menu.

1. Navigate to Builder (Casa) from your LeadSquared Dashboard.
2. From the left menu, select Menu under Mobile.
3. Click Create New and you will be taken to the Menu Builder page.
4. In the Menu Builder you can configure the relevant object type page to be visible in the Bottom Menu or Side Menu.

4.3 How To Add Object List Pages to the Homepage using Casa Widgets

The Object type list pages can be added to the Mobile App Homepage by configuring it in the following Casa Widgets:

• Quick Launcher
• Banner
• Image Tiles

1. Navigate to Builder (Casa) and select Homepage from the left menu under Mobile.
2. While configuring the Quick Launcher / Banner / Image Tile widget, select the relevant object type from the Navigate To dropdown.

5. Add Objects from the Object List Page

Once object type list pages are configured by the Admin and displayed on the mobile app, field sales users can easily add new object types as part of their daily workflows.

Since each object type has its own dedicated list page, adding new objects is straightforward and intuitive. You can simply navigate to the correct object type’s list page and use the default or dynamic form to add an object without the risk of mixing up types.

6. Create Object Details View

Admins can customize the Object Details page to display relevant information in an organized and meaningful way. For example, within the same account, you can create separate views for the Distributor and Customer object types, each with its own relevant tabs and actions.

To create a view for a particular object or opportunity type –

1. On your LeadSquared Web App, navigate to Settings>Mobile App>Details Customization.
2. Select Lead from the first dropdown.
3. Choose the relevant object type or opportunity type from the Choose Object Type dropdown.
4. Click Enable.
5. Create your custom view by naming it and adding the relevant tabs from the list of Available Tabs into Selected Tabs.
6. Similarly, add relevant actions from the list of Available Actions into Selected Actions. Once you’ve made the required additions, click Save View.

7. Customize Filters for Each Object Type

Configure a unique set of filters for each Object Type to ensure users can quickly find relevant information. These filters will appear in key areas of the LeadSquared Mobile App such as the Object List, Objects Near Me (when an object type chip is selected), and Journeys planning screens. This enables users to narrow down results using criteria that are meaningful to each object type.

The first screenshot displays the filters (Owner, Object Stage) configured for Customer object type and the second screenshot displays the filters (Owner, Country) configured for Manufacturer object type.

To configure and manage a distinct set of filters for each object type –

1. Navigate to Settings>Mobile App>Additional Settings.
2. Under Near Me, you will find Object Type – Custom Filter.
3. From the Object dropdown, select the relevant object type.
4. From the Custom Filter dropdown, select the relevant filters and click Save.

8. Smart Views

Lead, Activity and Opportunity Smart Views are created and managed separately for each Object Type. On the Mobile App, each Smart View will display only the relevant data for its assigned Object Type, including customized object cards and dynamic forms.

You can new object, activity or opportunity under a specific Smart View, directly from the mobile app. The following screenshot shows a Lead Smart View configured for the ‘Manufacturers’ object type.

9. Activity List and Add Activity

Field sales users can use the Object Type chips displayed on top of the Activity List page to select the desired object type. To post an activity under a specific object type, tap the Add activity icon under the relevant object type.

10. Tasks

Field Sales users can manage and organize tasks efficiently with Object Types. Object type is displayed on task cards alongside the object name in task lists, map views, and on My Trips task cards. You can also use the Object Type filter in the Tasks page to refine your task list.

When adding a task through default task forms, users will be prompted with an Object Type selection list, followed by a task type selection list ensuring that each task is linked to the correct object type. For dynamic forms, the appropriate form will automatically launch based on the selected object type from the list.

11. Casa

LeadSquared’s Casa feature lets you design homepages for your mobile application. When used with Object Types, Casa allows you to build dashboards that reflect each team’s focus area – helping sales reps, managers, and field agents see the most relevant data and actions as soon as they log in.

For example:

• A Student Enrollment Team homepage can highlight pending follow-ups, open opportunities, and a shortcut to the enrollment form.
• A Teacher Onboarding Team homepage can show tasks like document collection, a teacher list shortcut or interview scheduling specific to the Teacher object type.

To see the Casa Widgets that support Object Types, see Object Types in Casa for Mobile.

12. Near Me

LeadSquared’s Near Me feature helps users discover and manage nearby leads or objects based on their current location. When Object Types are enabled, this feature allows users to further filter, view, and add objects specific to each object type. In this section, we’ll describe how field sales users can –

• View Objects near you
• Add Objects near you
  • Add Objects from Objects Tab
  • Add Objects from Explore Tab

12.1 How To View Objects Near Me Based On Object Types

Object type chips are displayed at the bottom of the Objects tab to facilitate easier object categorization. Tap the relevant object type chip to view all the objects under it. Filters apply specifically to the chosen object type, while searches span across all object types.

12.2 How To Add Objects Under Specific Object Types from Near Me

You can add objects in Near Me quickly from the Objects and Explore tabs.

12.2.1 Add Objects from Objects Tab

You can add objects under specific object types from the Near Me page. In the Objects tab on the Near Me page, when you tap the Add Object icon, the default or dynamic form configured for the selected object type chip will be launched directly.

12.2.2 Add Objects from Explore Tab

In the Explore tab, when you tap the Add New Objects button from the More (three dots) menu, an object type selector popup appears. Once you select the object type, the configured default or dynamic form will be launched directly.

13. My Trips

My Trips is a day planning feature in the mobile app that helps you maximize productivity by optimizing your daily route. You can set your start time, start location, end time, and end location. Based on this, My Trips automatically schedules your existing appointments and tasks taking into consideration the distance and time constraints. In My Trips, you can add tasks apart from the existing ones.

When creating a new task in My Trips, you must first select the Object Type the task is associated with. This ensures the task is correctly linked and managed according to the selected object.

14. Journeys

Journeys is a field sales planning feature available on the LeadSquared Mobile App. It enables sales users to create structured visit plans by selecting specific leads and scheduling interactions over a defined time period. From Journeys, you can –

• Create Object-Based (Lead-Based) Plans
• Create and View Templates
• Create Template-Based Plans
• Approve / Reject Plans

14.1 How To Create Object-Based Plan

1. Navigate to the side menu and select My Plans on your Mobile App.
2. Tap the Create Plan icon.
3. Select the Date Range and Working Days.
4. Select Objects under Create Plan with and Tap Next.
5. Tap each day’s card to add objects categorized under object type chips.
6. Once added, tap the relevant day’s card to view the objects categorized based on the object types. You can view the task load for each day by tapping the date card.
7. Once the required objects are added across all days in the plan, click Next. You will be shown a summary of all the objects and tasks in the plan. Tap the number of objects to see a breakdown based on the object types. Then tap Submit for Approval.

14.1.1 Smart View Support for Object-Based (Lead-Based) Plans

You can filter and add objects from Smart Views in Object-Based (Lead-Based) plans. While creating or editing a plan, tap the All Objects (Smart Views) dropdown and select the relevant Smart View. The Smart Views dropdown dynamically updates based on the Object Type selected.

14.2 How To View and Create Templates

Navigate to My Templates on your Mobile App and open any template. A preview pop-up displays all objects within the template, grouped by object type. This helps you view information more effectively.

To create a new template from My Templates –

1. Click the Add Template icon.
2. Add the Template Name and a Description. Next, select a unique colour to set as the display icon for the template. Click Next.
3. Object type chips are displayed on top of the screen. Select the relevant object type and add the objects. Click Save.

14.3 How To Create Template-Based Plan

1. In My Plans, tap the Create Plan icon.
2. Select the Date Range and Working Days.
3. Select Templates under Create Plan with and tap Next and proceed further.
4. Once the required templates are added across all days in the plan, click Next. You will be shown a summary of all the objects, templates and tasks in the plan. Tap the number of objects to see a breakdown based on the object types. Then tap Submit for Approval.

14.4 How To Approve/Reject Plans

As a Manager, you can open and review plans submitted by your team, with objects grouped by Object Type. Tapping on a day’s card opens a pop-up preview displaying all planned objects under each Object Type. Tapping the date card displays all tasks grouped under each Object Type. To learn how to approve plans, see Approve Plans.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Object Types in LeadSquared Mobile App appeared first on LeadSquared Help and Support.

What are Object Types?
Object Types let you manage and track your business entities like students, parents, agents, partners, dealers, etc. as separate modules in your CRM – outside the core Leads module.

Each Object Type is fully configurable, with its own fields, forms, opportunity pipelines, and workflows. This ensures that every entity is tracked through a CRM process tailored to its real-world role – collecting only the information that’s relevant to its unique persona and business context – without cluttering your main leads module.

Why use Object Types?
With Object Types, you can:

• Separate your data – Maintain different records for different entities instead of overloading your leads module.
• Customize deeply – Each object can have its own:
  • Forms and fields
  • Opportunity stages and pipelines
  • Activities, tasks, and Smart Views
  • Email campaigns and reports
• Tailor entity workflows and user experiences – Give sales teams views and actions that match the type of object they’re working with.

Example: A training institute can manage students and agents as separate object types – each with their own forms, workflows, and stages – while keeping leads focused on inquiries.

2. Example Use Cases

Object Types can be tailored to reflect the unique business entities relevant to your industry. Below are examples of how different sectors might use Object Types:

Example: Education Industry
A Student object type might include:

• Fields – Grade, Stream, Course
• Stages – Inquiry, Application Submitted, Enrolled
• Opportunities – Test Prep Package, Summer Camp Enrollment
• Activities – Admission Form Filled, Interview Scheduled

This structure ensures that each entity follows a CRM process that reflects their real-world journey, with only the relevant data, stages, and actions.

3. Prerequisites

• You must be an admin user to create and configure object types.
• You must have NextGen enabled on your account.
• To enable Object Types in your account, reach out to [email protected].

4. How it Works

Once Object Types are enabled, you’ll see separate tabs for each object in your navigation menu – making it easy to view, track, and act on different entities like Students, Agents, or Partners.

For each object type, you can:

• Customize the Details Page (Object Details View)
  Show key information like contact details, activities, tasks, and opportunities in a layout tailored to each object type.
• Set Up Custom Forms and Processes
  Design unique forms and lead journeys – like enrolment steps for students or on-boarding for partners.
• Define Activities and Opportunities
  Create specific interaction points (e.g., “Interview Scheduled”) and sales pipelines that match the object’s real-world life-cycle.
• Assign and Track Tasks
  Set tasks for follow-ups, meetings, or documentation – based on the needs of each object type.
• Run Targeted Email Campaigns
  Send personalized emails to contacts linked to a specific object type, using their unique data.

5. Create Object Types

To create an Object type in your account –

1. Navigate to Settings>Objects>Object Types.
2. Click Create.
3. On the Create Object Type pop-up, enter the singular and plural name, then click Next.
4. Select and associate relevant object fields from Available Object Fields, select the relevant lead fields –
   • Click to add fields.
   •  Click to remove fields.
5. Choose the object fields you want to display on this object type’s Manage Objects page – this is the list view where users can track and filter records.
6. Click Publish. You can also save the object type as a draft and publish it later.

To create new lead fields, see How to Create Custom Lead Fields.

6. Customize Object Details View

You can tailor the layout of the Object Details Page to suit your team’s workflow. This includes configuring the Tabs, Actions, Buttons, and the Object VCard – giving your users a focused view of only the most relevant information for each object type.

To customize Object Details View –

1. Navigate to My Profile>Settings>Objects>Object Details View.
2. Select the relevant option from the Object Type dropdown.
3. Click Create.

On the Create Object Details View pop-up, under the Details tab, enter the following details –

• Name – A name for the view you’re creating. This is mandatory.
• Description – A description of the view you’re creating.

Then, select the relevant data to be displayed in the VCard, Tabs and as Actions and click Save.

Once the Object Details View is created hover your cursor over the actions button and click Apply to Teams.

7. Configure Object Stages

Object Stages help you track the progress of each object through its own business lifecycle, whether that’s a sales funnel, approval workflow, or onboarding process. When Object Types are enabled, you can define unique stages for each object type to reflect the journey specific to that entity.

For example:

• Customer object type can have stages like New, Engaged, and Converted
• Manufacturer object type can have stages like Shortlisted, Approved, and Partnered

By default, all object types have the existing default stages (Prospect, Opportunity, Customer) configured.

To configure stages for different object types –

1. Navigate to Settings>Objects>Object Stages.
2. Select the relevant object type from the first dropdown.
3. Under Active Lead Stages or Inactive Lead Stages, click Add and enter the name of the stage.
4. Click  to save the newly created Lead Stage. 

You can select Enable Comments on Stage Change to let your Sales Users make and read comments about the Stage change. Under Other Properties, click any of checkboxes to add the available characteristics to the Lead Stage.

8. Import Objects

You can bulk import records into a specific object type using a CSV (Comma-Separated Values) file. This is useful for onboarding large volumes of data like students, agents, or dealers into your CRM quickly and accurately.

1. Navigate to the relevant object type and select the Objects page (e.g., Dealers>Manage Dealers).
2. Click the actions button and select Import Object Type (e.g. Import Dealer) and proceed further.

9. Object Type Support in Forms and Processes

How to Create Forms for each Object Type

LeadSquared supports two types of forms – Default and Dynamic – both of which can be customized per Object Type. This ensures that each entity (like Students, Dealers, or Partners) is captured and updated using forms relevant to their unique attributes and workflows.

Create Default Forms

Default Object Forms allow you to create and manage forms directly from your web app settings to capture or updating object records. When Object Types are enabled in your account, these forms can be customized based on the specific attributes of each object type to capture relevant data.

For example, in an EdTech setup:

• Forms for the Student object type may include Class, Exam Grades, Courses Enrolled.
• Forms for the Teacher object type may include Subject Specialization, Years of Experience, Assigned Classes.

To create a new Object Form –

1. Navigate to My Profile>Settings>Objects>Object Forms.
2. Click the Select Object Type dropdown and choose the relevant object type.
3. Alongside Select Form to edit, click the dropdown and select Create Object Form.
4. You can remove/hide Lead Fields by dragging it to the Hidden Fields section on the right. You can also retrieve a particular field from the Hidden Fields by dragging it to the relevant section.
5. Reorder fields and sections by dragging them and click Save when done.

Create Dynamic Forms

Dynamic forms let you build advanced lead capture forms with rules and logic tailored to specific object types. These forms can be embedded in workflows and made available across web and mobile apps.

1. Navigate to Object Management>Workflow>Manage Forms and click the Create Form button and select the relevant purpose.
2. On the Create Form popup, you can select the object type from the Lead dropdown alongside Object Fields.
3. The lead fields relevant to the particular object type will be displayed on the Design page.
4. You can drag and drop the required fields onto your form.

Create Processes for each Object Type

After you publish your form, you can create processes for specific object types to control when and where the dynamic form appears.

1. From your LeadSquared Dashboard, navigate to Object Management>Workflow>Process Designer.
2. On the Manage Processes page, click Create Process.
3. Select At Specific Work Area. This option lets you create a button on a specific page (Manage Leads, Lead Details, etc.) to trigger the process.
4. In the popup, from the Object dropdown, select the relevant object type and proceed further.
5. In the Choose starting point popup, select work areas in the web and mobile app where your process should begin and click Save.

10. Object Types Support in Opportunities

Configure Opportunities and Create Dedicated Views for each Object Type

In LeadSquared, Opportunities represent your potential deals. When Object Types are enabled, you can associate specific opportunity types with specific object types, ensuring every deal tracks the right kind of entity and context.

For example, if a manufacturer purchases Cement Basic and expresses interest in Cement Plus or Cement Star, these would be added as cross-sell or up-sell opportunities, visible directly under the manufacturer object in your CRM.

This setup allows your teams to:

• Create targeted opportunity types per object (e.g., Customers, Dealers, Manufacturers)
• Avoid clutter by showing only the relevant opportunities for each object
• Customize how each opportunity type is viewed and managed across web and mobile

Configuring Opportunity Types

While configuring an opportunity type in the web app settings, you can associate it with one or more object types. For instance, if your object types include distributors and manufacturers, you can associate specific opportunity types like Cement Super and Cement Plus to distributors as well as manufacturers. This ensures the opportunity is only available for relevant entities, and helps teams create, manage, and report on deals specific to their business context.

1. Navigate to Settings>Opportunities>Opportunity Types.
2. Click Create and enter the relevant details.
3. From the Associated Object Types dropdown, select the relevant object types you want the opportunity type to be associated with.
4. Click Next. Once you complete the Field and Form configuration, click Save.

How To Create Opportunity Details View

Admins can customize the layout of the Opportunity Details page for each opportunity type. This includes configuring tabs, action buttons, and VCards to present information that matters most for each type of opportunity.

1. Navigate to My Profile>Settings>Opportunities>Opportunity Details View.
2. Click Create.
3. On the Create Opportunity Details View pop-up, under the Details tab, enter the following details –
   • Name – A name for the view you’re creating. This is mandatory.
   • Opportunity Type – The opportunity type for which you want to create this view.
   • Description – A description of the view you’re creating.

   Then, select the relevant data to be displayed in the VCard, Tabs and as Actions and click Save.

Once the Opportunity Details View is created hover your cursor over and click Apply to Teams.

How To Customize Opportunity Card (Mobile App)

You can configure different opportunity cards to be displayed on the mobile app for each opportunity type. In the hidden fields, only the fields associated with that particular object type will be displayed.

1. Navigate to Settings>Mobile App>Customize Opportunity Card.
2. Click Yes alongside Customize Opportunity Card.
3. Select Object Type and the associated Opportunity Type from the relevant dropdowns.
4. Then, configure the Opportunity card as required.

11. Object Types Support in Activities and Tasks

Configure and Add Activities for each Object Type

With Object Types enabled, you can assign custom activities to specific object types, ensuring that each entity (e.g., Student, Dealer, Partner) is tracked through interactions that match its role in your business process.

For example:

• A Student object might have activities like Orientation Attended or Mock Test Completed
• A Dealer might have activities like First Purchase or Contract Renewed

These activities appear only for the object types they are associated with, keeping the UI clean and relevant for your teams.

How to Configure Activities

1. Navigate to Settings>Objects>Custom Activities & Scores.
2. Click Add and enter the relevant details.
3. From the Associated Object Types dropdown, select the relevant object types you want the activity type to be associated with.
4. Enter the required details in the pop-ups and click Save.

How to Post Activities

Once you’ve created the required activity types, users can start posting them against individual objects.

1. Navigate to the relevant object type and click Activities.
2. Select the custom activity from the Activity Types list.
3. Click the Add Custom Activity button, and enter the activity, lead and opportunity details (if applicable).
4. Once you’re done, click Save & Close.

Alternatively, navigate to the relevant Object Type page (e.g., Dealers>Manage Dealers page), select the dealer and post an activity from the dealer details page.

Add Tasks for each Object Type

Tasks let you assign actionable items like follow-ups, meetings, or documentation for objects under different object types. Each task is contextually linked to the object, helping users stay focused on what needs attention.

For example:

• Schedule a Follow-up Call for a Dealer
• Assign a Document Collection Task for a Student

To create and manage tasks for specific object types –

1. Navigate to the relevant object type and click Tasks.
2. Click the Add Task button and select a task type you want to create.
3. Enter the task details on the pop-up.
4. Click Save & Close.

Alternatively, navigate to the Object Type page (e.g., Dealers>Manage Dealers), select the dealer and post a task from the dealer details page.

12. Create Targeted Email Campaigns for each Object Type

LeadSquared’s Email Campaign module allows you to run personalized outreach tailored to the sales journey of each object type.

For example:

• For Dealers, share new product launches or performance-based incentive programs.
• For Partners, schedule periodic engagement emails tied to their pipeline stage or activity history.

This ensures that every email campaign speaks directly to the recipient’s role and status in your sales process.

To create email campaigns for specific object types –

1. Navigate to Object Management>Marketing>Email Campaigns.
2. Click the dropdown alongside Create Email Campaign and select the relevant Object Type to create email campaigns for specific object types.

13. Object Types in Smart Views

Smart Views help sales teams filter and prioritize their work. When Object Types are enabled, you can create focused views for each object type to reflect their sales lifecycle. To learn more about creating a Smart Views tab, see Smart Views for Administrators or Smart Views – Feature Guide as per your role.

For example:

• A Dealer Manager might create a Smart View to track dealers at the Negotiation or Contract Sent stages.
• A Partnership Manager might view only partners with open opportunities above a certain value.

As an Admin (Creating Smart Views for Object Types)

1. Navigate to Settings>Objects>Smart Views.
2. On the Add New Tab popup, select the relevant object type from the Object Type dropdown and add other relevant details.
3. In the Select Criteria popup, build your condition with the relevant fields. You will only be shown the fields associated with the Object Type you’ve selected in the previous popup.

As a User (Creating Smart Views in the UI)

1. Navigate to Smart Views from your LeadSquared Dashboard.
2. Click the icon next to the rightmost Smart Views tab on top of the page.

14. Object Types in Casa

LeadSquared’s Casa feature lets you design tailored homepages for both your web and mobile apps. When used with Object Types, Casa allows you to build role-specific dashboards that reflect each team’s focus area – helping sales reps, managers, and field agents see the most relevant data and actions as soon as they log in.

For example:

• A Dealer Sales Team homepage can highlight pending dealer follow-ups, open opportunities, and a shortcut to the Manage Dealers page.
• An Agent Onboarding Team homepage can show tasks like document collection or interview scheduling specific to the Agent object type.

Object Types is supported in the following Casa Widgets on the Web App –

Object Types is supported in the following Casa Widgets on the Mobile App –

15. Object Types in Journeys on the Web App

Journeys is a field sales planning feature available on the LeadSquared Mobile App. It enables sales users to create structured visit plans by selecting specific leads and scheduling interactions over a defined time period.

To create a plan on the web app –

Navigate to Apps> Journeys.

Create a Template with Object Types Enabled

When Object Types is enabled, you can select objects categorized based on object types. Select the relevant object type tab to view the list of objects. To learn how to create Templates, see Create Lead Templates.

Create Template-Based Plan with Object Types Enabled

1. In Journeys, alongside Manage Plans, click Create.
2. Select the User, Date Range and Working Days.
3. Select Templates under Create Plan with and click Next.
4. Select the relevant template from the left side menu and add it to the dates.
5. Click on the template-added date to view the objects in the template categorized based on the object types.
6. Once the required objects are added across all days in the plan, click Publish.

Create a Lead-Based (Object-Based) Plan with Object Types Enabled

1. In Journeys, alongside Manage Plans, click Create.
2. Select the User, Date Range and Working Days.
3. Select Objects under Create Plan with and click Next.
4. From the right side menu, select the relevant object type tab and objects under it.
5. Once the required objects are added across all days in the plan, click Publish.

Edit a Plan with Object Types Enabled

To learn how to edit Lead-Based (Object-Based) plans, see Edit Pending or Approved Plans. While editing a plan submitted for approval, you can click the relevant object type chip on the right side menu and add or remove objects.

Approve/Reject a Plan with Object Types Enabled

To learn how to approve or reject a plan, see Approve or Reject Plans. While attempting to approve or reject plans, you can view the objects for each date categorized based on the object types.

16. Dissociating Object Field & Unpublishing an Object Type

Dissociating Object Fields

When you attempt to dissociate an object field from an object type configuration, a popup message displays all the areas where the field is currently in use. To proceed, you must first remove the field from each associated work area before dissociating it from the object type.

For example, if the Date of Birth field is used in Dynamic Form 10, you must remove it from the form before you can dissociate it from the object type.

Associated work areas could be:

• Object Details View
• Selected Automation Cards
• System and Dynamic Forms
• Lists (as the field will be available in advanced search)
• Quick Filter (as the field will be available in advanced search)
• Mobile App Object Card
• Email Campaigns
• Landing Pages

Unpublishing Object Type

When you attempt to unpublish an object type, a popup message displays the details of its associations. To proceed, you must first unpublish the associated work area before unpublishing the object type itself.

For example, if the Student object type is used in an Email Campaign, you must first delete the associated Email Campaign before you can unpublish the Student object type.

Areas where the Object Type may be associated:

• Automation
• Dynamic Forms
• Email Campaigns
• Landing Pages

17. FAQs

1. Why am I unable to import objects into the default Object Types?
Import functionality is not supported for default Object Types. You can only import custom object types from LeadSquared.

2. How can I move objects from one Object Type to another?
Currently, objects can only be moved from a default Object Type to a custom Object Type. Moving objects between two default Object Types or between custom Object Types is not supported.

3. Why can’t I see Manage Activities or Manage Opportunities for an object type?
These options will only appear if at least one Activity Type or Opportunity is associated with the object type. If none are linked, the Manage Activities or Manage Opportunities tab will not be displayed in the object type menu. To resolve this, make sure you’ve associated the relevant activity types or opportunities with that specific object type.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

The post Object Types – Feature Guide appeared first on LeadSquared Help and Support.