How Surface Labs Works With Salesforce

Your sales team lives in Salesforce. Your pipeline is in Salesforce. Your reporting runs on Salesforce. Nobody is ripping that out — and nobody should.

Surface doesn't replace Salesforce. It fixes the layer Salesforce was never built to handle: the real-time capture, qualification, routing, and response that happens in the first 60 seconds after a lead fills out a form. Surface handles that layer and pushes a clean, qualified, routed lead into Salesforce — ready for your team to work.

What Surface handles

Smart form capture. Surface forms replace your current form tool (native web forms, HubSpot forms, Typeform) on high-intent pages. Multi-step conditional logic, qualifying questions, and embedded scheduling built in.

Real-time qualification. The lead is scored and segmented at the moment of form submission — based on form responses and enrichment data. No waiting for a Salesforce Flow to process, no batch scoring overnight.

Attribute-based routing. The lead is matched to the right rep before it enters Salesforce. Territory, deal size, product interest, and availability are evaluated in real time. The lead arrives in Salesforce already assigned to the correct owner.

Instant response. A personalized message fires within 60 seconds — referencing the lead's stated interest, introducing the assigned rep, and including a scheduling link. The lead is already engaged before the Salesforce notification reaches the rep.

Embedded scheduling. The lead books on the matched rep's calendar during the form flow. By the time the lead record appears in Salesforce, there's often already a meeting on the calendar.

What Salesforce handles

Everything it already handles:

Lead and contact records. Surface creates the lead or contact record in Salesforce with all data populated — form responses, qualification score, enrichment data, and routing assignment.

Opportunity management. Once a deal is created from the Surface-generated lead, Salesforce manages the pipeline — stages, forecasting, collaboration, approvals.

Reporting and dashboards. Salesforce's reporting continues to work. Surface-created leads carry full attribution data (source, campaign, UTM parameters) so your Salesforce reports reflect the impact of every channel.

Flows and automation. Existing Salesforce Flows triggered by lead creation or field updates continue to fire. They just receive better inputs — pre-qualified, pre-routed leads with complete data.

Einstein and AI features. If you're using Salesforce Einstein for scoring or next-best-action, it benefits from the richer data Surface provides at the lead level.

How the data flows

Surface can create Leads or Contacts depending on your Salesforce data model. For teams using the Lead object → conversion flow, Surface creates Leads. For teams that skip Leads and go straight to Contacts + Opportunities, Surface creates Contacts with an associated Account.

The Salesforce routing problem Surface solves

Salesforce's built-in lead assignment rules are limited. They evaluate one criterion at a time, they can't check real-time rep availability, and modifying them requires a Salesforce admin.

Most teams that outgrow basic assignment rules move to Salesforce Flows — but Flows for routing quickly become complex. A routing flow that evaluates territory + deal size + product interest + availability requires multiple decision elements, loops, and custom Apex if the logic gets sophisticated enough. It's powerful but brittle — changes take days, testing is manual, and failures are silent.

Surface replaces this with a dedicated routing engine that evaluates multiple variables simultaneously, checks real-time availability, handles fallbacks automatically, and can be modified by ops teams without a Salesforce admin. The CRM receives the routing output — a lead already assigned to the right owner — and doesn't need to make the routing decision at all.

What changes for your team

For reps: Nothing. Leads appear in Salesforce in their queue, assigned to them, with full data. The experience is the same as today — except leads arrive faster, with more context, and more of them have meetings already booked.

For Salesforce admins: Routing logic moves out of Salesforce Flows and into Surface. This simplifies the Salesforce org — fewer Flows to maintain, fewer failure points, fewer support tickets about leads going to the wrong person. The admin still manages post-routing automation (deal creation, task assignment, approval processes) in Salesforce.

For ops: Surface becomes the place where capture and routing rules are managed. Changes take effect immediately without a Salesforce deployment. The Salesforce integration is configure-once — Surface handles field mapping during setup and maintains the sync automatically.

Setup timeline

Day 1: Connect Surface to Salesforce via OAuth. Map fields — Surface auto-detects standard objects and creates custom fields for qualification data. Configure your first form.

Day 2: Build routing rules in Surface. Test with sample submissions — verify lead records appear correctly in Salesforce with the right owner, right data, and right custom field values.

Day 3: Deploy on your high-intent pages. Monitor the first day of live leads.

No Salesforce package installation required. No custom Apex. No managed package dependencies.

Where Surface fits

Surface is the real-time layer that Salesforce needs but doesn't have. Fast capture, instant qualification, intelligent routing, and sub-60-second response — pushing the result into Salesforce where your team works.

If your Salesforce lead assignment rules or routing Flows have become a maintenance burden, and your speed-to-lead is measured in hours instead of seconds, Surface fixes both problems without changing how your team uses Salesforce.