LeadSquared

The LeadSquared connector uses LeadSquared's Universal Telephony Connector. Edesy posts call logs and live popups to URLs that LeadSquared gives you, and LeadSquared sends click-to-call requests and dispositions to URLs that Edesy gives you. If you don't see the Universal Telephony Connector in your account, ask LeadSquared support to enable it.

What you get#

• Click2Call: an agent clicks a lead's number, their mapped phone rings first, then the lead.
• Call logs on the lead as phone-call activities: direction, start and end time, duration, status (Answered, Missed or Voicemail), agent and the recording link.
• Agent Popup: the lead's record opens for each mapped agent whose phone an inbound call is ringing.
• Call Disposition: the outcome and notes the agent picks in LeadSquared are stored on the call.
• Ring the lead owner first (with API keys): a known lead's owner rings before the rest of the team.

Set up#

1. In LeadSquared, open Apps → Apps Marketplace → Universal Telephony Connector and add an instance of type Generic Telephony Connector.

2. Copy its Call Log URL and Agent Popup URL into Edesy: Settings → CRM integrations → Connect LeadSquared. If the connector shows an extra authentication header, copy that too. Choose the number your calls show.

3. In LeadSquared, open the instance's Click2Call settings and paste the values from the connection's Set up tab:

   LeadSquared field	Value from Edesy
   URL	The Click-to-call URL
   Method	POST
   Header	X-Edesy-Hook-Token with its value
   Data template	The JSON template shown on the Set up tab
   Response keyword	Success

4. Paste the Call Disposition URL into the instance's Call Disposition setting.

5. On the connection's Users tab, map each LeadSquared user to the phone they answer calls on. See Map Your Users.

6. In LeadSquared, turn on Show Phone Call Popup for those users.

7. Click to call a lead. Your phone rings, then the lead's. The call is logged on the lead with its recording.

The hook token is a secret for your workspace. If it leaks, disconnect and connect again to get a new one.

Optional: API keys#

Add an administrator's Access Key and Secret Key (in LeadSquared: My Account → Settings → API and Webhooks) and your API host, for example api-in21.leadsquared.com. With keys you can:

• pick users from a list instead of adding each by email,
• add recordings that arrive after the call was logged,
• ring the lead owner first.

The keys are sent in request headers, never in a URL.

Ring the lead owner first#

With API keys added, tick Ring the lead owner first on the connection. When a lead calls one of your forwarding numbers:

1. Edesy asks LeadSquared who owns the caller's lead.
2. If the owner is a mapped user, their phone rings first, then the forwarding rule's usual numbers.
3. If LeadSquared doesn't answer within 1.5 seconds, or the owner isn't mapped, the call rings as usual.

A number LeadSquared returns is never dialled unless you mapped it to a user.

High call volume#

LeadSquared accepts about 25 requests every 5 seconds per account. Edesy stays under that per connection; above it, calls wait a few seconds before they are logged. To log bursts straight away, add LeadSquared's asynchronous Call Log URL and its x-api-key under High call volume on the connection. Waiting for the rate limit does not use up a call's retry attempts.

Troubleshooting#