[dynamic_help_sidebar root="leads"]

SIERA Report Builder – Data Sources

/2 Comments/in , /by

1. Feature Overview

To create a report using the SIERA Report Builder, admins must first select a data source. SIERA stores data separately in multiple tables, which offer the following features –

  • Designed for superior performance during report generation.
  • Simplify reporting by joining multiple tables in LeadSquared to create a mega-table, streamlining the report creation process.
  • Eliminate the need for users to concern themselves with joins, schemas, and table details, allowing for a simple drag-and-drop approach to report creation.

It’s crucial to understand the different data sources as they determine the fields that will be present in the Report Builder.

 

2. Prerequisites

SIERA is a paid feature. To enable it for your account, contact your account manager or support@leadsquared.com.

 

3. SIERA Data Sources

SIERA Reports has 6 major Data Sources –

  • Lead Data Source
    • Lead (with Lead Owner)
    • Lead (with Lead Created By)
  • Activity Data Source
    • All Activities (with Lead Owner)
    • All Activities (with Activity Creator)
  • Opportunity Data Source
    • All Opportunities (with Lead Owner)
    • All Opportunities (with Opportunity Owner)
  • Task Data Source
    • All Tasks (with Lead Owner)
    • All Tasks (with Task Owner)
  • Phone Call Data Source
    • Phone Calls (with Activity Creator)
  • Revenue Data Source
    • Revenue (with Sales Owner)

These data sources contain lead fields (custom and standard) and fields from Activities, Opportunities, and Tasks (only the standard fields) respectively. Additionally, custom data sources can be requested for specific Activities, Opportunities, and Tasks.

3.1 User Types

The user type is a metafield (Learn more on how SIERA handles metafield).

To help users map the user IDs in the report, SIERA provides ready-made templates mapped to different user types. For example, to enable users to create reports on Lead Data Sources, SIERA has 2 templates – Leads with Lead Owners and Leads with Lead Created By.

3.2 Predefined Metrics

Each template also comes with its own predefined metric. For example, lead templates come with metrics like the Number of Leads, Number of Converted Leads, etc., While users have access to create their own metrics, pre-defined metrics are a quick way of creating reports.

3.3 Example flow

Here’s an example workflow that shows how data flows in the data sources –

SIERA data flow for lead tenants

 

4. Lead Data Source

This data source contains all the lead data in your LeadSquared system. The lead along with all standard and custom lead fields (dropdown, text, date, and number type) are stored in the data source, pre-joined, and ready to be processed.

Lead data source 1

Lead Data source 2

Lead Data Source Predefined Metrics

Metric Name Logic Expression
# Leads This gives a count of leads 
Count(`Lead.ProspectID`)
# Converted Leads This gives a count of leads where the stage is the final stage as per LSQ settings 
CountIf(`Lead.ProspectStage` = Config('TenantSettings', 'LeadStages.Final'))
Converted Leads % This is the ratio of # Converted Leads and # Leads expressed in % (CountIf(`Lead.ProspectStage` in Config('TenantSettings', 'LeadStages.Final'))/Count(`Lead.ProspectID`))*100

 

5. Opportunity Data Source

This data source contains all Opportunities data in your LeadSquared system. All Opportunities created in your system, along with all standard Opportunity fields, enriched with their corresponding lead fields (from the Lead Data Source) will be stored in this data source.

opportunity data source 1

opportunity data source 2

Opportunity Data Source Predefined Metrics

Metric Name Logic Expression
Total Opportunities This gives a count of opportunities 
Count(`Opportunity.ProspectActivityId`)
# Leads with Opportunities This gives a count of leads in the opportunity data source. This will be total leads that have opportunities created on them. This will not be equal to the total leads in the system as leads with no opportunity will be missing. 
CountDistinct(`Lead.ProspectID`)
Lost Opportunities This gives a count of opportunities where the opportunity status is Lost 
CountIf(`Opportunity.Status` = 'Lost')
Lost Opportunities % This is the ratio of Lost Opportunities and Total Opportunities expressed in % 
(CountIf(`Opportunity.Status` = 'Lost')/Count(`Opportunity.ProspectActivityId`))*100
Open Opportunities This gives a count of opportunities where the opportunity status is Open 
CountIf(`Opportunity.Status` = 'Open')
Open Opportunities % This is the ratio of Open Opportunities and Total Opportunities expressed in % 
(CountIf(`Opportunity.Status` = 'Open')/Count(`Opportunity.ProspectActivityId`))*100
Won Opportunities This gives a count of opportunities where the opportunity status is Won 
CountIf(`Opportunity.Status` = 'Won')
Won Opportunities % This is the ratio of Won Opportunities and Total Opportunities expressed in % (CountIf(`Opportunity.Status` = 'Won')/Count(`Opportunity.ProspectActivityId`))*100

 

6. Activity Data Source

This data source contains all Activity data in your LeadSquared system. All activities performed in your system, along with all standard activity fields, enriched with their corresponding Lead fields (from the Lead Data Source) and Opportunity Fields (from the Lead Opportunity Source) will be stored in this data source.

activity data source 1

activity data source 2

Activity Data Source Predefined Metrics

Metric Name Logic Expression
# Activities This gives a count of activities 
Count(`Activity.ProspectActivityId`)
# Leads with Activities This gives a count of leads in the activity data source. This will be total leads that have activities created on them. This will not be equal to the total leads in the system as leads with no activity will be missing CountDistinct(`Lead.ProspectID`)

 

7. Task Data Source

This data source contains all Tasks data in your LSQ system. All activities performed in your system, along with all standard tasks fields, enriched with their corresponding Lead fields (from the Lead Data Source) and Opportunity Fields (from the Lead Opportunity Source) will be stored in this data source.

SIERA Task Data Source Flow

Task data source 1

Task Data Source Predefined Metrics

Metric Name Logic Expression
Total Tasks Count This gives a total count of tasks Count(`Task.UserTaskId`)
Pending Tasks Count Pending tasks are tasks that are yet to be completed and have not crossed their due date. StatusCode = 0 means the task is still incomplete. Along with this, we need to check the due date of the task is after today’s date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 0 and (`Task.EndDate` ≥ CurrentDateTime or `Task.DueDate` ≥ CurrentDateTime))
Overdue Tasks Count Overdue tasks are tasks that are yet to be completed and have crossed their due date. StatusCode = 0 means the task is still incomplete. Along with this, we need to check the due date of the task is before today’s date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 0 and (`Task.EndDate` < CurrentDateTime or `Task.DueDate`< CurrentDateTime))
Completed Tasks Count Completed tasks are tasks that have been marked as complete. StatusCode = 1 means the task is still marked as complete. CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 1 )
Completed Tasks Today Count Completed tasks are tasks that have been marked as complete. StatusCode = 1 means the task is still marked as complete. To get Tasks completed today, we need to check if the completed date of a task is equal to today’s date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 1 and ToDate(`Task.CompletedOn`) = ToDate(CurrentDateTime))
Due Tasks Today Count Due tasks today count is overdue tasks whose due date is today’s date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 0 and ToDate(`Task.DueDate`) = ToDate(CurrentDateTime))
Due Tasks Tomorrow Count Due tasks tomorrow count is overdue tasks whose due date is tomorrow’s date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 0 and ToDate(`Task.DueDate`) = ToDate(DurationAdd(CurrentDateTime,1,'DAY')))
Due Tasks This Week Count Due tasks tomorrow count is overdue tasks whose due date falls under the current week CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 0 and ToWeek(`Task.DueDate`) = ToWeek(CurrentDateTime))
# Tasks Completed On Time Tasks completed on time are completed tasks where the completed date is before the due date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 1 and (`Task.EndDate` ≤ `Task.CompletedOn`  or `Task.DueDate` ≤ `Task.CompletedOn` ))
# Tasks Not Completed On Time Tasks not  completed on time are completed tasks where the completed date is after the due date CountDistinctIf(`Task.UserTaskId`, `Task.StatusCode` = 1 and (`Task.EndDate` > `Task.CompletedOn`  or `Task.DueDate` > `Task.CompletedOn` ))

 

8. Revenue Data Source

This data source contains all your Revenue data which is captured in the standard Sales Activity on LeadSquared. All custom and standard Sales Activity fields, enriched with their corresponding Lead fields (from the Lead Data Source) and Opportunity Fields (from the Lead Opportunity Source) will be stored in this data source.

Revenue data source 1

revenue data source 2

Revenue Data Source Predefined Metrics

Metric Name Logic Expression
# Deals This gives a count of sales activities 
CountDistinctIf(`Activity.ProspectActivityAutoId`, `Activity.mx_Custom_2`>0)
Revenue This gives a sum of the order value Sum(`Activity.mx_Custom_2`)

 

9. Phone Call Data Source

This data source contains all your Inbound and Outbound Phone Call Activity data in your LeadSquared system. All phone calls performed in your system, along with all system phone call fields, enriched with their corresponding Lead fields (from the Lead Data Source) and Opportunity Fields (from the Lead Opportunity Source) will be stored in this data source.

phone data source 1

phone data source 2

Phone Call Data Source Predefined Metrics

Metric Name Logic Expression
# Calls This gives a count of calls (Inbound + Outbound) 
Count(`Activity.ProspectActivityId`)
# Calls Connected This gives a count of calls with status = Answered (Inbound + Outbound) 
CountIf(`Activity.Status` = 'Answered')
# Unique Leads This gives total lead counts on which calls were attempted (Inbound + Outbound) 
CountDistinctIf(`Lead.ProspectID`)
# Unique Leads Connected This gives a total lead count where call status = Answered (Inbound + Outbound) 
CountDistinctIf(`Lead.ProspectID`, `Activity.Status` = 'Answered')
# Inbound Calls This gives a count of inbound calls 
CountIf(`Activity.ActivityEvent` = 21)
# Inbound Answered Calls This gives a count of inbound calls with the status = Answered 
CountIf(`Activity.ActivityEvent` = 21 and `Activity.Status` = 'Answered')
# Inbound Missed Calls This gives a count of inbound calls with the status = Missed 
CountIf(`Activity.ActivityEvent` = 21 and `Activity.Status` = 'Missed')
# Outbound Calls This gives a count of outbound calls 
CountIf(`Activity.ActivityEvent` = 22)
# Outbound Answered Calls This gives a count of outbound calls with the status = Answered 
CountIf(`Activity.ActivityEvent` = 22 and `Activity.Status` = 'Answered')
# Outbound Unanswered Calls This gives a count of outbound calls with the status = Not Answered 
CountIf(`Activity.ActivityEvent` = 22 and `Activity.Status` = 'NotAnswered')
Total Call Duration This is a sum of call duration 
Sum(`Activity.mx_Custom_3`)
Average Call Duration This is an average of call duration 
Avg(`Activity.mx_Custom_3`)

 
# Voice Messages These are voice messages count if received 
CountIf(`Activity.Status` = 'Missed' and `Activity.mx_Custom_4` != '')
# Call Duration less than 2mins This gives a count of calls where call duration was < 2 minutes 
CountIf(`Activity.mx_Custom_3` < 120)
# Call Duration >=2mins & less than 5mins This gives a count of calls where call duration was ≥ 2 minutes and < 5 minutes 
CountIf(`Activity.mx_Custom_3` ≥ 120 and `Activity.mx_Custom_3` < 300)
# Call Duration >=5mins & less than 10mins This gives a count of calls where call duration was ≥ 5 minutes and < 10 minutes 
CountIf(`Activity.mx_Custom_3` ≥ 300 and `Activity.mx_Custom_3` < 600)
# Call Duration >=10mins This gives a count of calls where call duration was ≥ 10 CountIf(`Activity.mx_Custom_3` ≥ 600)

 

10. Report Templates in SIERA Report Builder

To make it easy to build reports, SIERA comes with predefined templates to help users create their custom reports. The templates help users create reports across entities like Leads, Tasks, Activities, Phone Calls, and Activities.

To select the correct report template, you need the following information –

  1. Scope of the data – The data source and the report template primarily depend on the scope of the data. It refers to whether the report requires solely lead data or if it also requires activity or task data.
  2. Primary user type – The report you need can also be affected by the user type. Depending on your data source, you may have one or more user types.
    • For example, in the Activity Data Source, you will find Lead and Activity Data. The user types available in this data source are –
      1. Activity Owner
      2. Activity Creator
      3. Lead Owner
Note: Presently, you can only select 1 user type while creating a report (you cannot select both Activity Owner and Activity Creator). To help you generate reports on these user types, you will find templates on multiple user types for each data source.

Example Use Case

Consider the following report requirement: “I want to view connected calls and unique leads dialed per agent“

To generate the above report, we need the following information –

  1. Data scope – The Scope of the data here is the Calling Data which is present in the Phone Call Activities. Thus, the data scope will be Activity Data Source and Phone Call Activity Data Source. As there is a specific Phone Call Activity report, we can use this Data Source.
  2. Primary user type – Because the reporting requirement is by agents who have made the call, we need the template by Activity Creator (agents).

example

 

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!

Writing Expressions using SIERA Expression Builder

/6 Comments/in , /by

1. Feature Overview

This article helps you understand the process behind writing Expression through the SIERA Expression Builder. Admins can create custom expressions that can be used to easily retrieve and manipulate data on any report.

Note: This article will only explain the expression-building process. To find a list of expressions you can use, read this article – SIERA Expression Builder.

 

2. Prerequisites

SIERA is a paid feature. To enable it for your account, contact your account manager or support@leadsquared.com.

 

3. Filter Hierarchy in SIERA

Before you start writing expressions in SIERA, it is important to understand how filters work in SIERA and their hierarchy.

SIERA supports filters at the data level. Sometimes, you might expect SIERA to execute filters in one order, but the order of operations dictates that they be executed in a different order – which gives you unexpected results.

SIERA follows the current filter hierarchy from top to bottom –

 

SIERA filter hierarchy

 

4. Example Use Case

We’ll use a couple of use cases to showcase the process –

4.1 Example 1

Build a report that gives total leads and conversions from all Sources in the last month.

Data Source – We’ll use the Lead Data Source to build our report. The Lead Data Source has all the lead information but you can’t filter the Data Source here.

Report Filter – We’ll need to filter for last month’s leads. We can use the filter of Created On (this field stores the lead created date) and set the value to Last Month. This is our 2nd level of filter and will be applied first (as there is no Data Source filter). Using this filter will bring only leads created in the last month in the query and a lead not matching the criteria will be ignored in the report.

SIERA Report Filter

Setting Dimensions – Now add Lead Source as a Row Grouping. This step adds each Lead Source as a row. This is our 3rd level of filter. This filter will be applied after the Data Source Filter and Report Filter. And, will be applied in each row. For instance, in the below screenshot, the first row is ‘Trade Show’. Any measure added will be filtered for ‘Trade Show’ in the corresponding row.

SIERA Setting Dimensions

Adding Measures – Now, in the values section let’s add our measures. We will add the following measures –

  1. Total Leads – CountDistinct(`Lead.ProspectID`)
  2. Leads Converted – CountDistinctIf(`Lead.ProspectID`, `Lead.ProspectStage` in ['Paid', 'Customer'])

The first expression has a count function and no condition (this means no filter in this expression). While the second expression has a condition of Lead.ProspectStagein ['Paid', 'Customer'](this has a filter of Lead Stage either Paid or Customer).

All of the filters applied in the data source are in the order of –

  1. Data Source Filter – No filters (all lead data)
  2. Report Filter – Leads created in the last month
  3. Dimension Filter – Each row is filtered by a Lead Source
  4. Measure Filter – The first measure has no filter while the second measure has a filter of the lead stage. This is applied at the end of each row.

 

4.2 Example 2

Let’s consider the above example, but focus on leads from India.

Let’s say this data is stored in a lead field mx_Country – to get the report we need to apply this filter. This can be applied as a Report Filter, Dimension Filter, or Measure Filter (currently custom data sources cannot be created, hence we cannot add a filter at the Data Source level).

 

5. Writing an Expression

Now that we understand the order of operation of filters, we can begin to create expressions.

Expressions in SIERA are of 3 types –

  • Aggregated Expressions – An aggregate expression uses an aggregate function to summarize a selected metric. These include expressions like Count, CountDistinct, Sum, Min, Max, and Avg.
    • For example, if we want to get a count of leads, we can use the expression Count(<field name>). 
  • Conditional Expressions – Conditional expressions use aggregate functions along with conditions.
    • For example, if you want to Count leads only if they are from Google and Facebook, using an expression of Count() will not work. In this case, we can use CountIf(<condition>).
  • Calculated Values – Calculated Values are a combination of 2 or more expressions (aggregated or conditional) on arithmetic functions like +, –, *, or /.
    • For example, if we want the percentage of leads from Google and Facebook over total leads, we can use (Countif(<condition>)/Count(<field name>))*100. Calculated Values do not support drill-down in the reports or dashboards. 

For more details on the aggregated functions supported and their syntax, you can read the Expression Builder – functions and syntax page.

 

Consider this table as an example –

siera count vs countdistinct

The table has data on Phone calls on leads. Phone calls can be of 2 types – Outbound and Inbound, and multiple calls can be done on a lead. Since each row represents one call, the values in the Activity Id column are unique – while ProspectId can be repeated (as multiple activities can be done on a lead).

Now, if we have to count the total calls made, we can use either of the following expressions –

Count(`ActivityId`) or CountDistinct(`ActivityId`)

If we want to count unique leads where the calls have been made, we will have to use Count Distinct –

CountDistinct(`Prospect Id`)

Note: Count calculates rows, while CountDistinct removes duplicates first and then counts the rows. So while counting unique leads, CountDistinct will remove the 2 instances of Dora Brown and count it as 1.

 

7. Counting Leads, Activities, Tasks and Opportunities in SIERA

  • To count leads:
    • Display name – Prospect Id
    • Data source name – Leads
    • Example – Count(`Leads.Prospect Id`)
  • To count tasks:
    • Display name – TaskId
    • Data source name – All Tasks
    • Example – Count(`All Tasks.TaskId`)
  • To count activities:
    • Display name – ActivityId
    • Data source name – All Activities
    • Example – Count(`All Activities.ActivityId`)
  • To count opportunities:
    • Display name – Opportunity Id
    • Data source name – All Opportunities
    • Example – Count(`All Opportunities.Opportunity Id`)

 

8. Metafields in SIERA

Some special fields, like metafields, need special handling – especially when writing expressions. Fields like Activity Name, Opportunity Name, User Name, and Task Type are examples of metafields.

Here’s why metafields are different –

Take an example of a field like City. Let’s say we change a dropdown option from Madras to Chennai. Changing the name will not change the field value for all the leads where City was set to Madras.

However, take Activity Type for instance. If we were to change the name of an activity from Meeting to Physical Meeting, this would change the activity name in all places where the activity was Meeting to Physical Meeting.

This happens because in the database, the value of Activity Type against each lead is not the display name, but a different field –

meta fields in siera 1

meta fields in siera

In the above example, the activity table has a field – ActivityEvent which is mapped to the display name of the Activity in a separate table. This is an example of a metafield. This is why changing the display name of the activity changes the values across the system, however, changing the value of a field like Lead Stage will not.

In the system data sources provided in SIERA, the meta fields have been handled in fields and groupings. This means, that if we search for Activity Type in an activity data source, we will find the fields.

meta fields in siera activity type

However, the metafields work differently in Expression Builder. Expression Builder works on the core database which doesn’t contain metafields display names.

Let’s say we want to write an expression that counts activities when the Activity is Auction and Interview Scheduled. As there is no field called Activity Type in the core database, we can’t use the condition of ActivityType. Instead, we need to use the condition through their metafields.

Field Name Metafield Schema Name Display Name Entity
Activity Type ActivityEvent ActivityEvent Activity
Opportunity Type ActivityEvent ActivityEvent Opportunity
Task Type TaskType TaskType Task

From the table above, we now know the metafield for Activity Type is ActivityEvent. So the expression will be –

CountDistinctIf(`Activity.ActivityId`, `Activity.ActivityEvent` in [202, 103])

We are equating ActivityEvent with 202 and 103. To get the values corresponding to each Activity Type, navigate to Settings>Lead>Custom Activities & Scores and look for the column Code against the Activity Type.

siera expressions custom scores and activities 1

Note: To get the ActivityEvents for core activities, please reach out to siera.support@leadsquared.com

Similarly for Opportunity Type, you can go to Settings>Opportunities>Opportunity Types and use the column Code for writing expressions.

siera expressions custom scores and activities 2

 

9. User Fields in SIERA

The base tables in SIERA store the user IDs. User IDs are also meta fields and similar to the above, we will have to use their meta fields while writing expressions. There are multiple user fields for an entity, for example, in the Activity Data Source you will have –

  • Lead Owner
  • Lead Created By
  • Activity Owner
  • Activity Created By
  • Opportunity Owner
  • Opportunity Created By
  • Task Owner

To write expressions with user IDs, you can use the following mapping –

Field Name Metafield Schema Name Display Name Entity
Lead Owner OwnerId Owner Lead
Opportunity Owner Owner Owner Opportunity
Activity Owner OwnerId Owner Activity
Task Owner OwnerId Owner Task
Lead Created By CreatedBy Created By Id Lead
Opportunity Created By CreatedBy CreatedBy Opportunity
Activity Created By CreatedBy CreatedBy Activity

To get the values for the user IDs, export the user data from Manage Users, and refer to the column User Id.

 

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!

LeadSquared WhatsApp Integration with Tata Tele Business Services

/0 Comments/in , /by

1. Feature Overview

Tata Tele Business Services‘s WhatsApp self-serve solutions help you engage your customers in a simple, secure, and reliable way. Tata Tele Business Services facilitates customer support and other marketing efforts through WhatsApp. To know more, visit Tata Tele Business Services.

LeadSquared offers WhatsApp integration to help users communicate with their leads. Our WhatsApp functionality supports integrations through different solution providers like Infobip, Kaleyra, WATI, Zoko and Gupshup. This article helps you set up WhatsApp messaging through your LeadSquared account using Tata Tele Business Services as your service provider.

 

2. Prerequisites

If you’re not familiar with LeadSquared’s WhatsApp integration, see WhatsApp Business Messaging Connector. For frequently asked questions, see WhatsApp Business FAQs.

  1. To enable the Tata Tele Business Services WhatsApp integration on your account, contact your account manager, or write to support@leadsquared.com.
  2. Get an Approved WhatsApp Business Number and Account.
  3. Submit Message Templates for Approval.

 

3. Installation

To know how to install the WhatsApp Business connector, refer to WhatsApp Business Messaging Connector.

 

4. Configuration

Once the connector is installed, add and configure your WhatsApp phone numbers to the connector. To do this, enter –

4.1 Basic Details

LeadSquared Gupshup integration

Field Description
WhatsApp Business Number Paste your WhatsApp business number in this field, without including any special characters such as ‘+’, etc. You will have to include the country code of the number though. An example of a number would be “9199010XXXXX”, where 91 is the country code.

Contact your Account Manager from Tata Tele Business Services to get your WhatsApp business number.
Account Name Provide a relevant name for your connector. This field is mandatory.
Allow Lead Generation on incoming message Click Slider to allow automatic lead creation when you receive messages from unknown mobile numbers.
Lead Source From the dropdown, select a lead source for your leads.

Once you’re done, click Next.

4.2 Service Provider

Then, from the available options, select Tata Tele Business Services, and click Next.

LeadSquared Tata Teleservices integration

4.3 Authentication Set-up

On this screen, enter the following details –

LeadSquared Tata Teleservices integration

Field Description
Send Message URL This is a read-only field, and no action is required from your end.
WhatsApp Number The WhatsApp number you entered in the previous section is auto populated here.
Permanent Access Token Paste your Tata Tele Business Services access token. To know how to obtain it, refer to Tata Tele Business Services WhatsApp Details.
Authentication Header Template* In this field, pass the following value – {{Token}}
Get Media URL Paste this URL here –
https://wb.omni.tatatelebusiness.com/whatsapp-cloud/media/download/{{mediaId}}
WhatsApp Business Account ID Enter your WhatsApp Business Account ID here. This is optional.

Once you’re done entering all the details, click Next.

4.4 Converse Settings

LeadSquared Converse is an instant messaging feature that allows you to have real-time conversations with your leads via WhatsApp.

LeadSquared WhatsApp Integration

To integrate LeadSquared Converse with WhatsApp, complete the following steps –

  1. On the Converse Settings tab, toggle the Enable Converse Slider slider.
  2. Under User Access, grant permissions to users who can communicate with leads through the LeadSquared Converse.
    • Based on Role – From the Search and Select Users dropdown, select the LeadSquared user roles that can send messages through LeadSquared Converse.
    • Advanced (User Level) – Based on the value present in the selected user boolean field (e.g., For user Sam, the “Is Employee” field contains “Yes”), the user will be able to send messages through LeadSquared Converse. From the Select User Field dropdown, select a relevant boolean field.
  3. Functionality – The following additional settings must be configured –
    • Approved Templates – Enable this functionality to allow your users to send approved WhatsApp templates to your leads.
    • Unapproved Templates – Enable this functionality to allow your users to send unapproved WhatsApp templates to your leads. These can only be sent if the 24-hours service window is active.
    • Notify Lead Owner* – When enabled, only lead owners will get notifications of the WhatsApp messages a lead sends. When disabled, all logged-in users will receive notifications of these WhatsApp messages.
    • Sending Rich Media – Enable this functionality to allow your users to send media files in their WhatsApp messages.

Note:

  • *Message notifications are only sent to one user, i.e., either the Lead Owner or to the user (other than the Lead Owner) that sent the WhatsApp message to the lead. When the Notify Lead Owner setting is enabled, only the Lead Owner will get notified, while the user who sent the message will not get a notification.
  • If you enable the Send Rich Media option, you must also enable the Approved Templates option. This ensures that you can add your media files to a template when messaging your leads.

LeadSquared Gupshup Integration

4.5 Advanced Settings

In this screen, you must map –

  • Activity Mapping – A LeadSquared activity field to your WhatsApp messages. This is the activity that will be posted every time a WhatsApp message is sent or received.
  • WhatsApp Opt-Out – A LeadSquared lead field to the WhatsApp opt-out functionality. Your leads can opt-in or out of receiving WhatsApp messages on the basis of this field.
  • Default WhatsApp Number Fields – The number you set as the default phone number will be automatically selected when you send a WhatsApp message to a lead. You can also select other available numbers from the “Add Another Number” dropdown.
  • Default Country Code – The default country code will be used to send messages to a phone number that’s stored in a custom field, if no country code is listed.
  • Enable HSM – Disable the Slider slider.
  • Enable Rich Media Template Support – If you want to include media files in your WhatsApp message, you must enable the Slider slider.
  • Show URL Preview in Custom Messages – Enable the sliderSlider to allow for URL previews in non-templatized WhatsApp messages.
  • Compliance Type – Here, you can select the compliance type for the WhatsApp template, by choosing either WhatsApp Opt-out or Opt-in.
  • WhatsApp Opt-out – From the dropdown, select a lead field for the WhatsApp opt-in/opt-out functionality. Your leads can opt-in or out of receiving WhatsApp messages on the basis of this field.
  • Blacklist Incoming Messages – Enable this option to blacklist incoming messages from specific numbers. This is useful when you want to block numbers that send inappropriate messages to your users. Once enabled, enter the phone numbers in the text box available on the right side of your screen. You can add phone numbers with 7-12 digits (excluding the country code). This option is available only when the Allow Lead Generation on incoming messages setting is enabled.
Note: Create a custom lead field of boolean type to map to the WhatsApp opt-out functionality. For example, you may create a custom lead field called “WhatsApp Opt Out”. Leads for whom the field is selected/checked won’t receive WhatsApp messages.

Click Save & Close when you’re done.

  • If your credentials are correct, you’ll see the success message highlighted below.
  • If they were incorrect, the integration will fail.
Note: Once you save the Advanced Settings, a webhook URL is generated. Use this URL to integrate your LeadSquared and Tata Tele Business Services accounts, as shown in the section below.

LeadSquared Tata Teleservices integration

 

5. Configure the Webhook in Tata Tele Business Services

To receive inbound messages from customers, and to capture delivery status and reports, add the webhook URL (generated in LeadSquared) to your Tata Tele Business Services account. Once the Send Message URL is generated –

  1. On your LeadSquared account, on the Configure WhatsApp Business pop-up, from the Authentication tab, copy the Notifications Webhook URL.
  2. Once you log in to your Tata Tele Business Services account, on the left panel, click Integrations, and then click the Integration tab.
  3. Here, click LeadSquared, and the click Enable.
  4. On the right panel, paste the URL.
  5. Once you’re done, click Save. This completes the integration process.

LeadSquared WhatsApp Tata Teleservices

 

6. Conversing with Leads via WhatsApp

Integrating Converse with LeadSquared’s WhatsApp connector will enable your users to have real-time conversations with your leads through WhatsApp. Using templatised messages, you’ll be able to attach and send media files (such as images, documents, etc.) in your conversations. To know more, refer to LeadSquared Converse.
LeadSquared WhatsApp Integration

 

7. Next Steps

Once the connector is successfully installed, you can proceed to add WhatsApp templates and finally message your leads. For details, see Adding WhatsApp Templates to LeadSquared.

Note: To enable link tracking for messages that contain URLs, refer to WhatsApp Link Tracking in LeadSquared.

 

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!

Convert Speech to Text on the Mobile App

/0 Comments/in /by

1. Feature Overview

Field Sales Users can add notes on their leads, opportunities, tasks, and activities on the go using the Speech to Text Converter. While adding notes, users can record themselves speaking the relevant content which will be converted to text. This text can then be edited accordingly.

 

2. Prerequisite

You must have the LeadSquared mobile app installed on your device.

 

3. Convert Speech to Text on Lead and Opportunity Detail Notes

  1. On the mobile app, navigate to the relevant Lead or Opportunity Details page.
  2. Tap Notes. On the bottom of the page, tap Add Note.
  3. On the Add Note page, tap Mic icon. Now, you can say what you need to record on the Notes. Once you’re done speaking, the speech will be converted to text on this page. You can edit your notes once the conversion is over.
  4. Once you’re done, tap Save.

LeadSquared - Convert Speech to text on Lead Details

 

4. Convert Speech to Text on Activity and Task Notes

  1. While creating an activity or a task, tap the Notes section.
  2. Now, tap the microphone icon above your keypad. You can now speak and record your speech as text.
  3. Edit your text notes as you wish and submit the form.
Note: You can only add speech to text Notes on Activities and Tasks while creating them.

LeadSquared - Convert Speech to Text on Activities

 

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!

Why Am I Still Receiving Reminders for a Task Type Even After I Disabled Reminders?

/0 Comments/in , , /by

Check when the task was created compared to when you turned off reminders. If the task was created before you turned off reminders, you might still get reminders. But if the task was created after, you shouldn’t get reminders. This helps make sure reminders match your current settings and you don’t get notified for tasks you don’t need reminders for anymore.

For more information, see How to Create Tasks and Schedule Reminders.

What Are the Maximum Number of Leads That Can Be Shared with a User?

/0 Comments/in , , /by

Using the lead share feature, you can share a maximum of 2,000 leads with a user.

To know more, see How to Share Leads with Users.

Why Is Lead Source Not Getting Updated with the Lead Capture API?

/0 Comments/in , /by

If the lead was created earlier with a previous call to the Lead Capture API, the source field won’t get updated in subsequent calls. We prevent the source field from being updated to maintain the original lead source.

To learn more, see Capture Leads API.

What Are the Maximum Number of Leads I Can Bulk Update?

/0 Comments/in , /by

You can bulk update a maximum of 25,000 leads at a go. Increasing this limit may cause performance issues, but if you require the functionality, reach out to us at support@leadsquared.com.

For more information on bulk updates, see How to Bulk Update Lead Fields.

What Are the Maximum Number of Leads That Can Be Added to the Static List? Why is the List Details Page Breaking?

/0 Comments/in , /by

A maximum of 400,000 (4 lakh) leads can be added to a static list. If you add more than 400,000 leads to a static list, the list details page may break due to a time-out error while retrieving the list of leads.

To learn more about lists, see List Management – Feature Guide.

Why Is the Sales Group Manager Unable to Edit, Mark Complete, or Delete Tasks Assigned to Members of the Same Group?

/0 Comments/in , /by

By default, even if Sales Group Managers have ‘modify lead’ privileges, they cannot alter any tasks.

If you wish to allow them to update tasks (edit, delete, mark complete) of their group members, reach out to us at support@leadsquared.com and we can enable this functionality through a back-end setting.

To learn more about Sales Groups, see Managing Lead Access through Sales Groups.

Can I use both Reporting Manager and Sales Group Hierarchy Features

/0 Comments/in , /by

No, you can use only one feature. By default, LeadSquared accounts come with the Sales Group feature enabled. If you wish to change this to the Reporting Manager feature, please contact us at support@leadsquared.com.

  • The Sales Groups feature lets you manage your sales users by organizing them into different groups based on location, business unit or any other categorization of your choice. To learn more, see Manage Sales Groups.
  • The Reporting Manager feature lets you create a hierarchy of users to reflect your organization structure. To learn more see, View User Hierarchy.

Journeys Feature Guide

/0 Comments/in /by

1. Feature Overview

Journeys is a field sales management feature built for the mobile app. It enables all sales users to create a Plan (Beat Plan, PJP etc.) in just two simple steps by defining the plan duration (i.e. Start Date & End Date) and adding the relevant leads/lead templates alongside each date in the plan duration. Users can also send plans for approval to their respective managers if required. Once a plan is published or approved, the configured To-Dos will be created against the added leads. The plan execution can then be tracked by users through My Trips, Tasks, Task Smart Views, etc., on the LeadSquared mobile app.

LeadSquared - Journeys marketing

 

2. Set Up and Configure Journeys

The Setting up Journeys on the Web App article is mainly for Admins to enable/disable high level configurations for Journeys. This is the first step in using Journeys. Once you’ve configured the Journeys settings for your account, you can start creating and managing Plans.

 

3. Manage Plans on Web App

Admins and Managers can create, approve, and reject users’ plans on the Manage Plans page. Plans can be created by selecting leads manually or through lead templates. Manage Plans on Journeys for Web Users deals with creating and managing various Plans on the web app.

 

4. Manage Plans on Mobile App

Manage Plans on the Mobile App deals with creating and managing various Plans on the mobile app. The plan execution can then be tracked through My Trips, Tasks, Task Smart Views, etc., on the LeadSquared mobile app. This allows field sales users to streamline their tasks and plan the best route possible.

 

5. Manage Lead Templates on Web App

Lead Templates are a logical group of leads created based on similar properties like geographical proximity. Manage Lead Templates on Web App details how you can use lead templates to create plans instead of manually selecting each lead.

 

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.

Can I Delete a User?

/0 Comments/in , /by

In order to preserve the integrity of your account history, we don’t allow you to delete users. However, you can deactivate users after which they’ll no longer be able to log into LeadSquared. You can even mark de-activated users obsolete and then re-use their email addresses to create new users.

To learn more, see How to Deactivate Users.

Can I increase the maximum characters for the Notes fields?

/2 Comments/in , /by

No, the maximum limit (2,000 characters) can’t be increased for the Notes Lead field or the Notes Activity field.

For more information see, How to Create a Lead Fields and How to Create an Activity Field.

Why can I see a sales user under the Modified By column in the Opportunity Settings Page?

/0 Comments/in , /by

Only admins can access the Opportunity Types Configuration page. However there are instances when sales users appear under the Modified By column on the Opportunity settings page –

LeadSquared Opportunity Management

This occurs when the allow auto update setting is enabled for a drop-down field within an Opportunity Type.
With the Allow Auto Update setting enabled, when a sales user enters a new value/option while filling the drop down field (through a form, opportunity import or API call), the opportunity type is modified and the user’s name appears under the Modified By column on the Opportunity Settings page.

LeadSquared Opportunity Management

How to Filter Duplicate Opportunities of an Opportunity Type?

/0 Comments/in , /by

There is no direct way to filter duplicate opportunities of a particular opportunity type through advanced search. However, you can export the opportunities and compare them in the CSV file.

To know more, see Export Opportunities.

Why did the Opportunity Capture API create a Lead but throw an error when creating the Opportunity?

/0 Comments/in , /by

This is the expected behaviour. In the opportunity capture flow, a lead is created first, and then an opportunity is created. So even if opportunity creation fails, a lead is still created.

To know more, see Opportunity Capture API.

Is the Opportunity Origin updated automatically like the Lead Origin Field?

/0 Comments/in , /by

No, the opportunity origin field is not updated automatically. It’s a string field that takes the value sent via the API payload or via CSV import.

For more information, see Opportunity API and Import Opportunities.

Can I update the Created On field of an Opportunity?

/0 Comments/in , /by

Yes. First, reach out to us at support@leadsquared.com to enable this feature. Once enabled, you can use the following API endpoints to updated the Created On opportunity date field –

What is the maximum character length supported for Lead and Activity fields?

/0 Comments/in , , /by

The maximum character limit for custom lead fields is 1,000 characters (for ‘Text’ type fields displayed as ‘Text Areas’). However, the Notes system lead field supports 2,000 characters.

For Activity fields of text type, the maximum limit is 200 characters.

For more information, see How to Create a Custom Lead Field and How to Create a Activity Fields.

What are the maximum export limits for Leads, Activities, Opportunities and Tasks?

/0 Comments/in , , , /by

By default, you can export a maximum of 100,000 (1 lakh) Leads, Activities, Opportunities and Tasks. This limit can be extended to 500,000 (5 lakh). To increase the limit contact us at support@leadsquared.com. Note that increasing this limit may incur additional charges due to the required infrastructure changes.

For more information, see Export your Data From LeadSquared.

What is the maximum number of Leads and Opportunities I can import?

/0 Comments/in , /by

By default, you can import a maximum of 25,000 leads or opportunities at a time. This limit can be increased to 300,000. To increase the limit, contact us at support@leadsquared.com. Note that increasing this limit may incur additional charges due to the required infrastructure changes.

For more information, see How to Import Leads and How to Import Opportunities.

Can I create more than 100 Opportunity or Activity Fields?

/0 Comments/in , , /by

No, you cannot create more than 100 Activity or opportunity fields. We suggest creating Custom Field Sets and associating them with Opportunities or Activities if you need more fields.

Setting up Journeys on the Web App

/0 Comments/in /by

1. Feature Overview

Journeys addresses sales planning and scheduling use cases like Beat Planning or Permanent Journey Planning (PJP) across industries. Sales representatives or teams are often assigned specific geographic areas or customer segments they are responsible for. Beat planning or PJP involves determining the most effective way to cover these areas to maximize sales opportunities. This includes considerations such as the location of potential clients, the density of businesses or customers in a given area, and the travel efficiency of the sales team.

Journeys enables all sales users to create a Plan (Beat Plan, PJP etc.) in just two simple steps by defining the plan duration (i.e. Start Date & End Date) and adding the relevant leads/lead templates. Users can also send plans for approval to their respective managers if required. Once a plan is published or approved, the configured To-Dos will be created against the added leads.

Note: To know more about Journeys, refer to –

 

2. Prerequisites

 

3. How It Works

Admins must first enable and configure Journeys on the Web application. Once configured, sales users can create plans on the mobile app and submit them for approval to their managers, if required. Once managers approve the plans, they will be reflected on the following pages on the mobile app –

Users can then follow their plans while performing their assigned tasks.

Note: On the web platform, users have access based on their hierarchy. Admin users and Sales managers can view the plans made by all users. Certain sales users also have access to these plans based on their hierarchy. For example, if Sales Users A and B are reporting to Sales User C, C can view the plans of A and B but not anyone else. However, sales users A and B will only be able to view their own plans.

 

4. Journeys Settings

Settings on Journeys can only be configured by Admin users.

  1. From the main menu, navigate to Apps>Journeys and on the bottom left corner of the page, click LeadSquared - journeys settings icon.
  2. On the Settings page, click Journeys.
  3. Configure the following settings and once you’re done, click Confirm.

4.1 General Settings

The look of the map and lead icons on Journeys can be customized. On your LeadSquared Web App, navigate to Apps>Journeys>Settings>General to edit these settings.

  • Map Theme Selection

To customize the Journeys map theme in your LeadSquared Web App, you need to be an Admin, Sales Manager, Sales Group Manager, or Reporting Manager. You can choose from seven pre-designed map color themes, and the selected theme will be applied across all users.

Leadsquared - Journeys Settings

  • Customized Lead Icons

As an admin, you can customize the lead icons displayed in the Journeys feature. Assign distinct shapes and colors to represent different Lead Stages or Lead Lists, making it easy to quickly identify leads within the designated territories of the users.

Leadsquared - Journeys Settings

 

4.2 Journeys Settings

  • Define Default To-Do Task Type

You must first define the default To-Do task type here. Alongside the setting, click the To-Do Task Type dropdown and select the relevant task type. Appointments are not supported as task types on Journeys since they require a specific start and end time which may clash with the other tasks of the day. Once you select a To-Do task type, you can set custom rules and define relevant task types for each lead stage/activity/territory. For example, if Lead A and Lead B are in different lead stages, they will be added to different To-Do task types based on your configuration even if they’re on the same Plan. To set custom rules –

  1. Click Add Custom Rule.
  2. Alongside Primary Lead Field, select the Lead Field you want to add conditions to. Only Mandatory Lead Fields of Dropdown Data Type lead fields will be displayed as options.
  3. Under Conditions, select the relevant value and under To-Do Task Type, select the task type you want to associate with this value.
  4. To add more rules, click Add Custom Rule.
  5. Click Save.
  6. Once you create custom rules-
    1. To delete them, click Delete icon.
    2.  To edit them, click edit.

Note:

  • Plans cannot be published until a To-Do Task type is defined by the Admin.
  • Ensure that the To-Do Task Type chosen here is not restricted for creation under Permission Templates for the Journey users. The task configured here must not be deleted from the platform settings as it may impact the task creation after plan approval.
  • You can add a maximum of 5 custom rules.

LeadSquared - Define Default To-Do Task Type

  • Enable Approvals

In the LeadSquared Web App, by navigating to Apps>Journeys>Settings>Journeys and selecting Templates and Approvals, admins can enable Approvals. If you enable this setting, all the plans created by users will be displayed to their respective managers for approval. Managers can approve or reject these plans. Only the approved plans will be added to the users’ tasks.

Additionally, admins can enable the Auto-Approve Pending Plans setting, which automatically updates plans to Approved status on both the My Plans and My Approvals pages for easy tracking. Auto-approved plans are marked with the “Auto-Approved” status, including the exact date and time of approval. Sales managers and admins can edit these auto-approved plans, with the editor’s name, date, and time of changes clearly displayed in the updated status. Joint Meetings are disabled by default in auto-approved plans to streamline workflow.

Note:

  • Admin users and Sales Managers can approve or reject the plans made by all users. Sales users also have access to these plans based on their hierarchy. For example, if Sales User X is acting as a manager to two other sales users – User Y and User Z, X can approve or reject the plans of users Y and Z, but not anyone else.
  • Approvals is an optional setting.
  • To enable Joint Meetings, you must enable Approvals.
  • Managers can only add leads to a plan if it’s a created using Lead Templates.
  • Changing the user hierarchy after setting up Journeys will result in loss of data.
  • While managers can be allowed to remove leads from plans, they cannot add leads to a plan.
  • Once enabled, Approvals cannot be disabled again.

Leadsquared - Journeys Settings

  • Enable Templates

If you enable this setting, users will be able to create Templates by grouping leads with shared attributes, which can be used to create Plans and Trips. To also allow users to add the same lead to multiple templates, alongside Allow users to add the same lead in more than one template, clickAzure checkbox. Once enabled, Templates cannot be disabled again.

Note: This setting must be enabled to access Lead Templates.
LeadSquared - Enable templates

  • Enable Joint Meetings

When this setting is enabled, users will be able to plan joint meetings with their respective managers/reportees while creating or approving a plan. To define the To-Do Task Type of this joint meeting, click the To-Do Task Type dropdown. Now, select your option.

Note: Approvals must be enabled to use this feature.
LeadSquared - Enable joint meetings

  • Define Quota & Force Minimum Quota

Within the Define Quota settings, administrators can specify the minimum number of leads a sales user must cover in a day. By default, this quota is set to 10 leads per day for all users. This flexible quota can range between 1 to 40 leads daily. Admins have the option to enforce a standard minimum lead requirement across users by enabling the Force Minimum Quota feature. The setting is disabled by default and can only be enabled once a quota is defined. While creating or editing a plan on the LeadSquared Mobile App, users can clearly see the number of leads they have added versus the minimum quota. While submitting a plan, if the users have not met the specified minimum lead quota, the system will block submission and notify the user of the shortcoming. Quotas are managed disregarding days designated as holidays or blocked.

Note: This is an optional setting.
Leadsquared - Minimum Quota Enforcement
Users can view lead chips on planned days to easily track whether their quota is being met. Plans that have met the quota will display a grey lead chip, while plans where the lead quota has not been met will show a red lead chip. The user can add leads appropriately.
Leadsquared - Minimum Quota      Leadsquared - Minimum Quota

  • Day Blocking Configuration

With this setting, you can define and manage a predefined set of reasons that users can select to block their days in a plan, such as for leave, holidays, training or other purposes. You can add a maximum of 10 reasons for day blocking here. You can also associate a To-Do task with the day blocking reason. For example, if you’re blocking a day for a Sales Meeting, you can associate a Sales Meeting task to it. Upon blocking the day, the task will automatically be created against the relevant users. To know more about using this feature, refer to Manage Plans on the Mobile App.

LeadSquared - Day Blocking Configuration

  • Restrict Overlapping Plan Date Ranges

To prevent users from creating plans with date ranges that overlap plans already published, approved, or pending, alongside Restrict Overlapping Plan Date Ranges, click the toggle.

LeadSquared - Restrict overlapping plan dates

4.3 Process Compliance Settings

This feature allows Admins to set a plan submission window, default plan duration and working days for users while creating plans on the LeadSquared Web App. On your LeadSquared Dashboard, navigate to Apps>Journeys>Settings>Journeys to enable these settings.

  • Set Monthly Plan Submission Window – By enabling this setting, the admins can specify a monthly time window during which users can submit their plans. The admins can select the start date and end date from the relevant dropdowns. This will reflect for all users. If this is enabled, any attempt to create a plan outside this window would not be acceptable.
  • Setting Default Plan Duration & Force Duration – Admins can enable Default Plan Duration for users to configure the default number of days in a plan. This can be:
    • Custom –  Selecting a value between 1 to 31 days. For instance, if 10 is entered on March 1st, then the last date of the plan will be March 10th.
    • Current Week – The default End Date would be the upcoming Sunday of the week containing the Start Date. If you select Sunday as the Start Date, the End Date will be the same.
    • Current Month – The default End Date would be the last date of the month. If the selected Start Date is already the month’s last date, it will reflect as both Start and End Date.

When a user logs into the LeadSquared Mobile App and selects a start date, the app automatically displays the end date based on the duration enabled by the admin. The user can change the end date as per their requirement. However, if the Default Plan Duration and Force Duration are enabled, the end date becomes non-editable.

  • Setting Working Days Template – Admins can enable force workday template on the LeadSquared Web App. When a user creates a plan, the app automatically displays the workday template assigned to the user and makes it non-editable. The users can modify the template if the setting is disabled.
Note: This setting is not honored when a user clones or edits a plan, allowing them to make changes to the working days template as needed.
  • Set Lead Frequency Per Plan – Admins can set a maximum lead frequency count to restrict how many times the same lead can be added to a lead-based plan from My Plans and My Approvals. Once a lead has been added the maximum number of times allowed (as configured in Journeys Settings), the Add button for that lead will be disabled during the plan creation as well as edit process.
Note: While editing a plan created before the setting was enabled, if a lead has been added more times than the new limit, those entries will be retained. However, the plan cannot be updated until the user manually removes the extra instances to meet the new limit.

Leadsquared - Journeys

4.4 Advanced Settings

On your LeadSquared Web App, navigate to Apps>Journeys>Settings>Advanced.

  • Rename Plans

To rename the Plan entity –

  1. On the Journeys page, click mobile settings icon.
  2. On the left side of the screen, under Settings, select Advanced.
  3. Under Rename Modules, alongside Plans, click edit.
  4. Enter the relevant display name and the plural term for it.
  5. Once you’re done, click Check icon.

LeadSquared - Rename Plans

 

  • User Access Hierarchy

Previously, managers in the higher positions could access all the plans created by all users under them. Now, you can define the hierarchy for accessing Plans, Templates, Trips, Approvals, and Notifications. You can either choose Direct Reporting where you can access only those who directly report to you, or All Accessible Users where you can access all users who are directly or indirectly reporting to you. To toggle between this,

  1. Navigate to Apps>Journeys>Settings>Advanced.
  2. Under User Access Hierarchy, toggle between Direct Reporting or All Accessible Users as required.
  3. Once you make the change, click Confirm on the top-right corner of the page.

Leadsquared - Journeys Settings

 

5. Add Lead Ownership Change Webhook

Create a webhook to update your pre-existing plans and lead templates according to lead ownership changes made on the LeadSquared platform. For example, if user A was assigned 10 leads and someone updates the lead owner of these leads to user B, you can automatically update this information on the platform by creating a webhook.

  1. Navigate to Settings>API and Webhooks>Webhooks and click Create. 
  2. Enter the following details –
    • Type – Webhook
    • Event – Lead Ownership Change
    • Webhook URL – https://fieldsales-in21.leadsquared.com/api/journey/v1/(EnterOrgId)/lead/owner
      • The orgid included in the URL refers to the organisation ID, which is the same as your LeadSquared Account Number. You can find this ID on the bottom of your screen.
    • Content Type – application/json
    • Execution Delay – 0 Seconds
    • Custom Header Name – Authorization
    • Custom Header Value – 
      • Navigate to Journeys>Settings>Advanced.
      • Alongside Field Sales Token for Automation, click Copy. 
      • Paste that value under Custom Header Value.
  3. Enter a description for the webhook.
  4. Click Save.

LeadSquared - Lead Owner Change Webhook

 

6. Add Lead Deletion Webhook

Create a webhook to automatically update your pre-existing plans and lead templates when a lead gets deleted on the LeadSquared platform.

  1. Navigate to Settings>API and Webhooks>Webhooks and click Create. 
  2. Enter the following details –
    • Type – Webhook
    • Event – Lead Delete
    • Webhook URL – https://fieldsales-in21.leadsquared.com/api/journey/v1/(EnterOrgID)/leads?eventType=delete
      • The orgid included in the URL refers to the organisation ID, which is the same as your LeadSquared Account Number. You can find this ID on the bottom of your screen.
    • Content Type – application/json
    • Execution Delay – 0 Seconds
    • Custom Header Name – Authorization
    • Custom Header Value – 
      • Navigate to Journeys>Settings>Advanced.
      • Alongside Field Sales Token for Automation, click Copy. 
      • Paste that value under Custom Header Value.
  3. Enter a description for the webhook.
  4. Click Save.
⚲

LeadSquared - Lead Delete Webhook

 

7. Add Journeys to Mobile App

Once you’re done configuring the Journeys settings, add it to the mobile app’s navigation menu.

  1. On the side panel of the CASA landing page, click Menu builder icon. Then, alongside the menu you want to add Journeys to, click edit.
  2. On the right side of the page, click Side Navigation.
  3. To add Journeys to the mobile app’s navigation bar, under Available Menu Tabs, alongside Journeys, click Add icon.
  4. To rearrange the tabs, drag and drop them in the desired order.
  5. Once you’re done building the menu, click Publish.

LeadSquared - Add Journeys to Mobile Navigation

 

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.