[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"integration-servicetitan":3},{"id":4,"category":5,"dataDelivered":6,"extension":18,"faq":19,"hero":38,"howItWorks":42,"meta":59,"seo":60,"setup":62,"slug":71,"stem":72,"tagline":73,"tier":74,"tool":75,"whoItsFor":76,"whyItMatters":77,"__hash__":78},"integrations\u002Fintegrations\u002Fservicetitan.yaml","Field Service Management",{"intro":7,"fields":8,"toolMapping":17},"Every webhook payload from Leaddi carries the full qualified-lead context:",[9,10,11,12,13,14,15,16],"Customer name and phone number","Issue description and job type hint (plumbing, HVAC, electrical, etc.)","Urgency level (emergency, same-day, this-week, flexible)","Service address","Preferred appointment window","Photos the caller shared (linkable URLs)","Full SMS conversation transcript","Source tag: Leaddi","ServiceTitan users typically land Leaddi leads as Booking records or Customer + Job opportunities, with Lead Source = Leaddi. Because ServiceTitan setups vary widely (custom job types, business units, tag taxonomies), most customers run the webhook through a thin middleware layer or Zapier step to match their internal taxonomy exactly.","yaml",[20,23,26,29,32,35],{"question":21,"answer":22},"Is the ServiceTitan integration included in all Leaddi plans?","Yes. The webhook connector is included on Essential ($229\u002Fmo), Growth ($399\u002Fmo), and Scale ($629\u002Fmo). For enterprise-scale ServiceTitan deployments with custom middleware, the Scale plan offers direct onboarding support.",{"question":24,"answer":25},"Does Leaddi overwrite anything in ServiceTitan?","No. Leaddi only creates new records via webhook — never updates or deletes existing customers, jobs, or opportunities. Duplicate detection and customer merging stay in your ServiceTitan workflow or middleware layer.",{"question":27,"answer":28},"What if our ServiceTitan setup uses custom job types, business units, or lead sources?","Common setup. The webhook payload is flexible — during setup we can match Leaddi fields (issue, urgency, etc.) to your ServiceTitan taxonomy. Most Scale-tier ServiceTitan customers use a thin Zapier or middleware layer to translate Leaddi's generic payload into their specific ServiceTitan IDs.",{"question":30,"answer":31},"How long does setup take?","5 minutes for the standard mapping; 10-20 minutes if you need to match a custom ServiceTitan taxonomy (job types, business units, lead source IDs).",{"question":33,"answer":34},"Can we turn off the ServiceTitan integration if we don't want it?","Yes. Toggle the webhook off in Leaddi's Settings → Integrations. Leads keep flowing to your Leaddi dashboard; they just don't land in ServiceTitan.",{"question":36,"answer":37},"Does Leaddi respect ServiceTitan's zone, tag, and business-unit routing?","Leaddi qualifies every missed caller regardless of zone — we assume you want every lead visible. Your ServiceTitan side (or a middleware step) handles zone-based routing, business-unit assignment, and tagging based on the address and issue data we deliver.",{"eyebrow":39,"headline":40,"subheadline":41},"Leaddi + ServiceTitan Integration","Leaddi + ServiceTitan — Never Lose a Lead to a Missed Call","Leaddi connects to ServiceTitan via outbound webhook, so every qualified lead from a missed call lands in your ServiceTitan pipeline the same moment it hits your phone. No double-entry, no disrupted CSR workflow — leads show up where your dispatchers already work.",[43,47,51,55],{"title":44,"description":45,"icon":46},"Missed call detected","Leaddi sees the missed call within seconds and the AI texts back from your business number.","i-lucide-phone-missed",{"title":48,"description":49,"icon":50},"AI qualifies over SMS","In about 30 seconds, the AI captures customer, issue, urgency, address, preferred window, and photos where relevant.","i-lucide-message-square",{"title":52,"description":53,"icon":54},"Lead delivered via webhook","When the lead is qualified, Leaddi fires an outbound webhook with the full lead payload to your ServiceTitan endpoint.","i-lucide-zap",{"title":56,"description":57,"icon":58},"CSRs and dispatchers act in ServiceTitan","The lead lands as a new booking opportunity tagged source=Leaddi. Your CSRs confirm and dispatch in their normal flow.","i-lucide-truck",{},{"title":39,"description":61},"Leaddi connects to ServiceTitan via webhook — qualified missed-call leads land as booking opportunities with Lead Source=Leaddi. Included on every plan.",{"timeEstimate":63,"steps":64,"docsHref":70},"5-15 minutes",[65,66,67,68,69],"In ServiceTitan, identify the endpoint you want new leads to land at — the ServiceTitan public API, a Zapier connector, or an internal middleware","In Leaddi, go to Settings → Integrations → Webhooks → Add ServiceTitan","Paste your endpoint URL and any required auth headers","Map Leaddi fields to your ServiceTitan taxonomy (job types, business units, lead source ID)","Send a test webhook from Leaddi to confirm the lead lands in ServiceTitan","#","servicetitan","integrations\u002Fservicetitan","Leaddi connects to ServiceTitan via outbound webhook — qualified leads land as new opportunities the same moment they're delivered to your phone.","webhook","ServiceTitan","Mid-market and enterprise home-service operators running on ServiceTitan — multi-location plumbing, HVAC, electrical, and garage-door shops processing thousands of calls a month. If you have a CSR team and a dispatch board inside ServiceTitan, Leaddi recovers the calls your CSRs never got to pick up.","ServiceTitan is built for operators who take their call volume seriously. Every missed call is a CSR seat that couldn't pick up in time — and at typical HVAC or plumbing volumes, that can be 50-200 lost opportunities a month. Leaddi recovers those calls before the customer dials a competitor, qualifies them with vertical-specific questions, and hands the booking to your CSRs and dispatchers inside ServiceTitan. The result: higher booked-call rate without adding headcount.","ecmiYLVIjMsAQ5q8RTiPWhQWi4BAa3c7FMEyFkNb9ZQ",1776888301168]