LeadSquared Field Mapping

Start with a small, explicit field map. The integration should create or resolve one contact, attach call context, and map only the qualification values your sales process actually uses.

Recommended object flow

1. 01

   Resolve the contact

   Match on a stable external id when available. Use phone normalization only as a controlled fallback.

2. 02

   Create the contact when needed

   Store source, consent context, and the originating call id according to your approved data model.

3. 03

   Attach call activity

   Create a completed-call activity with status, disposition, duration, and an authorized link to the call record.

4. 04

   Map qualification fields

   Write normalized budget, timeline, financing, locality, and intent values to approved custom fields.

5. 05

   Create the follow-up

   Create tasks only for explicit commitments such as a requested callback or site visit.

Default mapping

Conflict handling

• Use source timestamps and update precedence rather than last-writer-wins for every field.
• Keep phone changes in a review queue when consent or ownership may have changed.
• Do not overwrite manually maintained sales stages with inferred values.
• Map unknown values to an explicit unmapped state for observability.