Zendesk Sell on your landing pages
A franchise kit request or a B2B quote is worth the most on the day it's made. If it reaches Zendesk Sell the next morning through an import, the rep calls someone who has already moved on. Sending your LanderLab leads to Sell creates each lead as it's submitted, tagged with its campaign, with the answers that qualify it in fields the team filters on.
It fits sales teams on Zendesk who pay for their pipeline: franchise development teams running Meta and Google, B2B service firms quoting from a demo page, agencies sending leads into a client's Sell. LanderLab's webhook calls Sell's API directly, so there's no connector or Zap in the middle.
Zendesk Sell leads from every submit
Each submit becomes a lead in Sell with the person's name, email, mobile, a short description and the tags and custom fields you choose. Sell needs a last name or an organization name to save a lead, which a franchise or B2B form asks for anyway.
Every submit makes a new lead, so a person who fills your page twice appears twice. Reps merge the repeat in Sell, and the second submit tells them the person is still interested.
Tags and custom fields your reps filter on
Tags don't need to exist in Sell beforehand: send landing-page and the campaign name and Sell creates them. A filtered lead list on a tag gives each rep or each territory its own queue of new leads.
Answers land in Sell custom fields, so a capital band like $150k+ becomes something reps sort and filter by, not a line buried in a note.
Campaign and variant on every Sell lead
Fill a UTM Campaign and a Page Variant custom field from hidden fields and LanderLab's LL Variant ID. A Sell report on leads by campaign, then on the deals they became, tells you which ad sets bring candidates who sign, not just the ones who download the kit.
Send Sell only the candidates who qualify
Franchise development teams don't want leads below the capital minimum taking up call time. In LanderLab Workflows (beta), an If node on the liquid capital answer sends qualified candidates to Sell through an HTTP Request node and leaves the rest in LanderLab's Leads tab. When a rep asks why a lead never arrived, the Runs view shows the path it took.
