# NC SQUARED - SMART ROUTING & SCHEDULING FOR SALESFORCE


## COMPANY OVERVIEW


NC Squared are the team behind Distribution Engine and Booking Engine. They provide smart routing and scheduling solutions for Salesforce. The company delivers no-code automation that gets the right work to the right rep, right away. Over 20,000 users worldwide trust NC Squared's solutions to optimize routing efficiency across various sectors including technology, financial services, healthcare, education, media, and real estate.


### Core Mission
NC Squared automates the assignment work that connects businesses to their customers. The company focuses on leveling up Salesforce when out-of-the-box tools and custom code don't cut it anymore - providing no code, no hassle solutions that rapidly route leads, meetings, cases and other Salesforce objects so their clients can deliver a responsive customer experience.


---


## NC Squared Products


- [Distribution Engine](https://nc-squared.com/products/distribution-engine): Intelligent lead and case routing for Salesforce that automatically distributes Leads, Opportunities, Contacts, Cases, and custom objects to the right rep at the right time using rules-based logic for territory, skills, availability, workload balancing, round-robin, and SLA enforcement—all 100% native to Salesforce with no-code configuration. One of the original and most trusted routing solutions on the market, with an average rating of 4.89 out of 5 stars on the Salesforce AppExchange. 


- [Booking Engine](https://nc-squared.com/products/booking-engine): Making it effortless for your customers and team to schedule meetings, with Salesforce updates and admin handled for you. Let customers book meetings directly in your calendar with sharable booking links that sync with your availability and automatically update Salesforce. Meeting routing solution that empowers outbound agents to check team availability, schedule the next meeting on the spot, and automatically assign meetings based on availability, territory, or account ownership while seamlessly handing off between SDRs and Sales teams.


---


## DISTRIBUTION ENGINE IN DETAIL


### What Problems It Solves


**The Salesforce Routing Challenge:**
Out-of-the-box Salesforce routing only gets you so far. Native Salesforce lacks comprehensive round-robin routing capabilities and struggles with complex assignment scenarios. Assignment Rules, Queues, and Flows handle straightforward situations, but when requirements get more complicated, speed to response matters, these solutions fall short.


**Common Pain Points Addressed:**
- Uneven lead and case distribution creating feast-or-famine workloads
- High-quality leads going cold before initial contact
- Loss of visibility into ownership clarity
- Lack of audit trail on where and why leads and cases were routed
- Manual routing destroying speed-to-lead
- Territories overlapping causing confusion
- Leads routing to inactive users or out-of-office reps
- Complex routing logic requiring constant developer or admin intervention
- Lack of fairness and transparency in distribution


### How Distribution Engine Works


Distribution Engine operates on clear, foundational principles:


**1. Clarity Trumps Complexity**
Every rule executes one function: "If X, then Y." If explanations require a complex flowchart, it's overengineered.


**2. Automation Trumps Reaction**
Manual routing destroys speed-to-lead. Distribution Engine assigns ownership the instant a lead enters your system and reassigns if the SLA is breached.


**3. Fairness Builds Trust**
Balanced lead distribution translates to engaged reps and faster follow-up. Burnout degrades performance for everyone.


**4. Visibility Drives Accountability**
Without performance metrics, management operates blind. Dashboards aren't optional - they're mission-critical infrastructure.


** 5. Routing Solution For The Entire Customer Journey**
Ensure every customer interaction gets the speedy follow-up it deserves. Route any Salesforce object - leads, cases, contacts, accounts and opportunities -  even custom objects.


### Technical Architecture


**Salesforce-Native Design:**
- 100% native application with no external integrations
- No data syncs or security risks
- All data stays safe, secure and compliant in your Salesforce org.
- No new tools for reps to log into and learn


**Flexible Configuration:**
- No-code, click-to-edit interface
- Self-serve workflows that customer-facing teams can own and update
- Test assignment risk-free before rolling out changes
- Update logic without Salesforce Admin or developer dependency


**Routing Intelligence:**
Distribution Engine evaluates multiple factors including:
- Geographic territories
- Product interest and specialization
- Company size and revenue
- Lead scores and intent signals
- Skills and experience matching
- Rep availability and capacity
- Workload and balance
- Custom business logic


---


## SOLUTION USE CASES


### For Sales Teams


**Objective:** Route Leads faster and convert more pipeline


**Benefits:**
- Faster speed-to-lead (sub-5-minute response times become the norm)
- Fairer, more flexible Lead, Account, and Opportunity distribution
- Track distribution and performance directly in Salesforce
- Slick meeting handoff between SDRs and Sales teams
- Improved conversion rates (customers report 30-40% increases)


**Key Features for Sales:**
- Instantly assign records to the best rep for the job, no matter how complex the workflow
- Route based on specialist skills, territories, or account ownership
- Avoid missed opportunities by only routing to agents who are working
- Balance team workload with Weighting and Caps
- Load-balancing logic ensures fair distribution with options to cap and auto-reassign unworked Leads


### For Service Teams


**Objective:** Triage Cases and deliver more responsive customer service


**Benefits:**
- Faster response times and first-contact resolutions
- Triage Cases intelligently
- Balance Case workloads across the team
- Better service through faster, smarter routing
- Get the right agent on the Case first time and on time


**Key Features for Service:**
- Skill-based routing for specialized support
- Multi-language support
- Product type and region-based assignment
- SLA tracking with auto-reassignment
- Reduced manual work (customers report saving 60+ hours weekly)


---


## UNDERSTANDING LEAD ASSIGNMENT IN SALESFORCE


### The Strategic Importance of Lead Assignment


Lead assignment isn't about rules - it's about responsiveness. When leads sit idle or reps carry uneven loads, that's not a Salesforce limitation - it's a process design flaw that's solvable.


**Why Effective Assignment Matters:**
Speed-to-lead remains critical - sub-5-minute response times can double conversion rates. But velocity means nothing when leads reach the wrong rep, or no rep at all. When routing fails, teams experience:
- Lopsided workloads and rep burnout
- Cold leads losing intent before contact
- Loss of management visibility
- Decreased conversion rates
- Poor team morale


**The Revenue Impact:**
What runs smoothly with a ten-person sales team starts showing cracks at twenty. Territories begin to overlap in ways that create confusion rather than coverage. Handoffs during out-of-office periods miss the mark. Queues quietly accumulate high-priority leads while reps wait for assignments.


### Core Salesforce Tools & Their Limitations


**Native Salesforce Capabilities:**
- Assignment Rules: Good for straightforward logic like geography or region
- Queues: Suitable for temporarily unassigned leads
- Flows/Workflows: Handle basic automation sequences


**Where They Fall Short:**
These tools suffice initially - not indefinitely. As lead sources, roles, and edge cases proliferate, the system strains. Native tools lack:
- Flexible round-robin distribution
- Workload balancing
- Multi-conditional logic
- Advanced availability management
- Comprehensive performance tracking


### Four Foundational Principles for Sustainable Lead Assignment


**1. Clarity Trumps Complexity**
Every rule entry should aim to execute one function. "If X, then Y." If explanations require a complex flowchart, it's overengineered.


**2. Automation Trumps Reaction**
Manual routing destroys speed-to-lead. Assign ownership the instant a lead enters your system.


**3. Fairness Builds Trust**
Balanced lead distribution translates to engaged reps and faster follow-up. Burnout degrades performance for everyone.


**4. Visibility Drives Accountability**
Without performance metrics, management operates blind. Dashboards aren't optional - they're mission-critical infrastructure.


### Common Routing Pitfalls


**Scalability Limits:**
Out-of-the-box rules reach scalability limits. They lack flexibility. Once you need round-robin distribution, workload balancing, or multi-conditional logic, you're layering workarounds indefinitely.


**Workload Imbalances:**
Territory-based routing alone creates dramatic rep imbalances - some overwhelmed by incoming leads, others idle.


**Missing Fallback Logic:**
Leads route to inactive users or salespeople who are out-of-office, then languish unnoticed.


**Visibility Gaps:**
Without metrics tracking queue duration or response velocity, you're operating on assumptions, not data.


### Lead Assignment Best Practices


**Automate Early, Audit Regularly:**
Start simple, then review quarterly. Routing logic degrades quickly as teams evolve, markets shift, and territories reorganize.


**Balance Workloads Strategically:**
Fairness protects revenue and maintains lead management. Implement workload caps or rotation logic to maintain lead velocity and rep morale simultaneously.


**Match Skills & Availability:**
Route inbound leads to the right person in a position to close - by expertise, region, or active hours. Don't send EMEA leads to an offline US rep.


**Monitor Response Velocity:**
Track pickup times via dashboards. Bottlenecks typically indicate unclear ownership or missing fallback protocols.


**Reroute Idle Leads Automatically:**
Establish SLAs, then reassign leads that sit untouched. No exceptions.


---


## SLA-BASED LEAD ROUTING


### The Hidden Revenue Leak


Leads die not from apathy, but from systems that fail to enforce real ownership and accountability. A qualified lead hits Salesforce, gets classified and passed to a sales rep, but that rep has a full plate. Before you know it, days pass, the lead isn't touched, and $25K of potential opportunity has gone cold.


The culprit isn't lack of effort - it's the absence of systematic accountability.


### SLAs as Operational Rhythm


Think of SLAs less as bureaucratic red tape and more as operational rhythm. Your funnel requires consistent velocity - not sporadic bursts of activity.


**Key Components:**
Each stage needs defined time boundaries:
- Leads contacted within hours
- Cases acknowledged within minutes
- Opportunities followed up before momentum stalls


SLAs make these boundaries explicit and measurable.


**Behavioral Impact:**
When a rep knows reassignment happens at the 90-minute mark, behavior changes. When managers see breach rates in dashboards, they can coach proactively rather than reactively.


### Why Most SLA Frameworks Fail at Scale


Most SLA initiatives fail at the execution layer, not the strategy layer. Three typical breakpoints:


**1. Manual Dependency:**
Someone needs to monitor timestamps or send reminders.


**2. Rigid Logic:**
One-size-fits-all rules that ignore timezone differences or workload variation.


**3. Hidden Metrics:**
No real-time visibility when breaches occur.


### The Automation Advantage


Effective SLA frameworks live inside your operational systems. Distribution Engine embeds SLA tracking directly into the workflow:
- Monitoring response times automatically
- Triggering alerts as breaches approach
- Handling reassignments automatically if the SLA isn't met
- The system enforces your rules of engagement


**Context-Aware Intelligence:**
Distribution Engine adds intelligence that maintains fairness and flow:
- Route only to reps who are online and available
- Exclude users at capacity
- Adjust timers by priority level or geographic region
- Handle reassignments instantly based on actual conditions


### Anatomy of Effective SLAs


The strongest implementations share three characteristics:


**1. Clear Ownership:**
Every record has a single accountable person.


**2. Real-Time Visibility:**
SLA timers and dashboards live in Salesforce where the work happens.


**3. Automated Enforcement:**
The system escalates or reassigns as deadlines approach.


**Practical Example:**
- New inbound lead enters Salesforce
- SLA target: 2-hour first response
- At 90 minutes: automated alert fires
- At 2 hours: auto-reassignment to next available rep


This creates fair, consistent enforcement without emotional escalations or manual tracking.


### Cross-Functional Alignment


Mature RevOps teams use SLAs to define clear accountability across Marketing, Sales, and Customer Success:
- Marketing: Deliver MQLs within 10 minutes of capture
- Sales: Respond to MQLs within 2 hours
- Success: Resolve customer cases within 24 hours


These create measurable handoff points across functions. When something slips, you can diagnose where in the process - not who to blame.


### Measurable Impact on Revenue Velocity


Across NC Squared implementations:
- Lead response SLAs compressed from 12+ hours to minutes
- Conversion uplifts can be 30-40%
- Response times that double conversion rates
- Predictable, compounding conversion gains


Real-world examples:
- 360 Learning: Automated lead follow-up, reduced response times to under 10 minutes, achieved 97% routing accuracy and 40% conversion increase
- Aetna: Reclaimed 8 hours daily of manual case assignment work with SLA-driven routing
- Shutterstock: Multi-language, skill-based routing across 20 countries, saving 60 hours weekly


---


## ROUND ROBIN ROUTING


### What is Round Robin Routing?


Round robin routing is a routing method that assigns incoming records to a group in a repeating order. Lead 1 to Rep A, lead 2 to Rep B, lead 3 to Rep C, then back to Rep A. Equal-share across reps. No cherry-picking. No "first come, first served" chaos.


**The Salesforce Gap:**
Short of doing nothing, round robin is routing at its most basic. But strangely enough, Salesforce Sales Cloud doesn't have this function built in out-of-the-box. You can build it yourself with clunky formulae and coding, but it comes with significant drawbacks and requires constant manual reconfiguring.


### Benefits of Round Robin Routing


**1. Faster Speed-to-Lead**
Leads receive allocation with the next available agent without pooling behind the busiest person. Spikes don't stall queues and response times stay consistent.


**How Distribution Engine Enhances It:**
- Combine with Active Caps to limit how many hot leads each rep is working
- SLA auto-reassign pulls idle records back to the pool
- First-Action SLA (e.g., 5 minutes) with Auto-Reassign after that window
- Distribution hours so after-hours arrivals wait for a live pool


**Measure:** Average time to first action; % of records actioned within SLA; conversion-to-meeting within 24 hours.


**2. Fairness & Boosted Morale**
Even distribution removes cherry-picking and queue hoarding. Fewer disputes and burnouts; less context switching.


**How It Works:**
Each record goes to the next eligible rep, skipping anyone out of office, offline, or capped. Weights smooth the loop without favoritism. Distribution Engine's Availability feature allows instant toggling of reps on and off from round robin.


**Measure:** Assignments per active hour by rep; variance between top and bottom rep (<10-15%); rep CSAT on fairness.


**3. Predictable Capacity**
Real throughput replaces guesswork. Forecasting and staffing get easier. A steady rotation exposes how many records a rep can action per hour when work is evenly fed.


**Quick math:** Required reps/hour ≈ inbound volume/hour ÷ target assignments/rep/hour. Add 15-20% buffer for breaks and meetings.


**Measure:** Planning accuracy (forecast vs actual); utilization (% of time on routed work); backlog growth during peaks.


**4. Safer Ramp for New Hires**
New reps contribute earlier without drowning; seniors protect focus. Weightings allow less for rookies while skills build, more to keep experienced reps busy.


**Example:** 0.5 weight for new, 1.0 for mid-level, 2.0 for senior.


**Measure:** New-hire time-to-first-action vs team median; 30/60/90-day conversion trend; time to full quota of assignments.


**5. Cleaner Coaching Data**
Apples-to-apples performance comparisons. Coaching plans target real gaps, not routing luck. With even distribution, you remove selection bias.


**Measure:** Conversion by rep on matched segments; talk-time-to-booked-meeting; lift after targeted coaching.


### How to Implement Round Robin with Distribution Engine


**Step 1: Create Your Team and Membership**
Create a Team and add eligible users. Configure their working hours. Use tags (role, product, language, territory) to make membership and filtering dynamic.


**Step 2: Set Availability and Hours**
Enable the online/offline widget for reps. Configure distribution hours for the team and sync Salesforce Calendar so PTO and meetings pause assignments automatically.


**Step 3: Define Caps and Weights**
Set time-based caps (hourly or daily) and an Active Cap to limit concurrent hot leads. Apply weights to smooth ramping.


**Step 4: Build the Distributor**
Create a Distributor with Method = Round Robin. Set the Source and apply a Team Member Filter using tags for skills, product, or region.


**Step 5: Configure Ownership and Fallback**
Turn on sticky/related owner where appropriate, then define a backup queue or distributor for cases when no one is eligible.


**Step 6: Log Every Assignment**
Distribution Engine writes an assignment record for each action with who, what, when, and why. Keep this object visible for audits.


**Step 7: Protect Speed with SLA and Auto-Reassign**
Set an SLA policy for first action. If a record is untouched after X minutes, trigger auto-reassign back to the pool or to a supervisor path.


**Step 8: Monitor and Tune**
Track assignments per rep, time to first action, SLA adherence, reassign rate, and distribution balance. Review caps, weights, and membership monthly.


### Common Pitfalls & Quick Fixes


**Fuzzy Membership:**
Drive filters with tags and run a weekly report of Active users with zero assignments.


**Out of Office Leaks:**
Use calendar sync plus the online/offline widget so PTO and meetings pause routing.


**Uneven Load:**
Start with equal caps, then adjust weights using time-to-first-action and conversion data.


**No Fallback Path:**
Always set a backup distributor or queue for "no eligible rep."


**Quiet Failures:**
Turn on SLA alerts and watch auto-reassign events as an early warning signal.


---


## COMPREHENSIVE GUIDE TO LEAD ROUTING


### What is Lead Routing?


Lead routing or lead assignment directs an inbound lead to the best-fit salesperson the moment it's created. The goal isn't clever rules - it's reliability, speed, and accountability.


**Simple Use Cases:**
Round robin across the Sales Development Team.


**Complex Use Cases:**
UK healthcare leads interested in Product A go to the EMEA health team; if capacity is hit, overflow to a backup pool; if state is missing, infer it from dial code so nothing stalls.


### Why Lead Routing Matters


**Speed Shapes Everything:**
Quick replies lead to better first calls. Better first calls lead to shorter cycles and more qualified leads. The compound effect shows in pipeline quality and forecast confidence.


**The Human Side:**
- Reps work real opportunities instead of fixing ownership
- Managers' workflows allow for coaching instead of refereeing fairness debates
- Workloads feel fair because they are
- Result: momentum in both conversion rates and morale


Teams that tighten speed-to-lead and match leads to specialists often set sub-10-minute response times as the norm, not the exception.


### The Cost of Poor Lead Distribution


When assignment lags:
- Good leads cool off
- Sales reps burn time on reassignments or chase wrong targets
- Incoming leads get two follow-up calls, or none
- Uneven distribution eats at trust: some reps drown while others feel left out


Distribution Engine helps by balancing load and respecting capacity. Caps prevent overload. Overflow rules keep queues moving when a team hits its limit.


### Core Components of Effective Lead Routing


**1. Lead Capture and Qualification**
Great routing starts with great inputs. Standardize the fields you depend on (geo, segment, product interest, account size) and enrich early so the first owner has context.


**2. Defined Lead Routing Rules**
Clarity beats complexity. Build rules around territory, product, company size, lead score, language, skills, and availability. You need freedom to update logic without code when territories shift, new products launch, or teams reorganize.


**3. Automated Routing**
Manual triage doesn't scale. Automated lead routing assigns in real time, applies fairness controls (round-robin, caps, availability windows), and can auto-reassign if a lead sits untouched past an SLA.


**4. Performance Monitoring**
"Set and forget" is how systems decay. Logs, dashboards, and SLA tracking let RevOps see what's happening, tune rules, and prove impact.


### Lead Routing Strategies & Best Practices


**Geographic Routing: Meeting Prospects Where They Are**
Assign leads by geographic location (country, state, or region) so reps with local knowledge handle local prospects, aligning with time zones, local norms, and regulations.


Distribution Engine uses territory classifiers that can fill in gaps (such as state from dial codes) to keep assignments accurate without manual cleanup.


**Industry/Niche Routing: Specialization Builds Trust**
Healthcare to healthcare. Finance to finance. Matching buyers with someone fluent in their world shortens discovery and raises confidence on both sides.


**Company Size/Revenue Routing: Aligning Complexity with Expertise**
SMB prospects move faster and need different handling than large enterprises. Routing by company size ensures smaller accounts go to speed-oriented reps, while enterprise deals land with senior account executives who can manage longer, complex cycles.


**Skill-Based Routing: Leveraging Strengths**
Some leads require specific skills - like language fluency, technical depth, or strong negotiation experience. Routing by skill ensures the right conversations happen from the start.


**Lead Score Routing: Prioritizing High-Intent Prospects**
Not all leads are equal. Prospects showing high intent or perfect fit for your ICP should go straight to top reps who can close them, while lower-score leads may go to SDRs for nurturing.


**Round-Robin Routing: Keeping It Fair**
Spread leads evenly to keep the team motivated and avoid cherry-picking. Distribution Engine enhances this classic model with workload caps and performance tags.


**Capacity-Based Routing**
Assign new leads to the best-fit rep only when they've got room to work them. Distribution Engine checks real-time workload, then applies caps you define. If a rep hits their cap, the next qualified rep gets the record.


**Availability-Based Routing**
Route leads to reps who are available and ready to respond right away. Factor in vacations, sick leave, and shift patterns. Stop leads going unworked.


**Hybrid Models**
Most organizations mix two or more strategies. For example, leads might first be sorted by territory, then by product interest, and finally assigned round-robin within the qualified pool.


### Micro-Examples You Can Copy


**EMEA Enterprise Overflow:**
Overflow to NA Enterprise during campaign weeks to keep SLAs green.


**ICP Score + Product:**
A-scores interested in Product B go to senior AEs; B-scores to SDRs for qualification.


**SLA Safety Net:**
If untouched after 10 minutes, reassign to "rapid response" queue for a first touch.


### Measuring Success with KPIs


**Response Time (Speed-to-Lead):**
How fast reps follow up after the lead comes in. The quicker the reply, the higher the chance of qualifying and converting.


**Conversion Rate:**
Proof your logic works. Right leads in the right hands close more often.


**Sales Cycle Length:**
Optimized routing doesn't just lift win rates - it shortens the path to closed-won. Faster cycles mean revenue sooner.


**Team Productivity:**
Routing should cut admin, not add to it. Time reinvested in selling.


**Customer Satisfaction:**
When prospects meet the right rep instantly, they gain confidence fast. That strong first impression shapes the relationship.


---


## SALESFORCE TERRITORY MANAGEMENT


### Territory Chaos = Pipeline Chaos


Uneven or outdated territories lead to unfair workloads, slower response times, and unreliable forecasts. Your West Coast team drowning in inbound while East Coast reps refresh dashboards waiting for leads. Your forecast shows $2.3M, but nobody trusts it because ownership keeps changing. Three different reps claiming the same account.


Territory chaos doesn't announce itself with sirens. It just slowly wrecks everything downstream - your response times, your forecasts, your team's trust in the system.


### Salesforce Territory Management Provides Structure


Territory management isn't organizational housekeeping. It's foundational pipeline architecture. When designed properly, it delivers three critical outcomes:


**1. Fairness:**
Workload distribution that gives every rep a legitimate path to quota attainment.


**2. Speed:**
Clear ownership that enables immediate response without routing debates.


**3. Forecast Accuracy:**
Predictable coverage that makes pipeline planning reliable.


**Native Capabilities:**
Salesforce gives you the framework - defining ownership by geography, industry, or customer size, improving visibility, fairness, and forecasting.


**The Gap:**
Salesforce Territory Management lacks built-in automation. You still need something to actually move leads, cases, and opportunities through that framework in real time.


### Automation is the Missing Piece


Distribution Engine adds the operational layer to Salesforce's structural layer, assigning leads, opportunities, and accounts in real time based on criteria you define:
- Availability
- Capacity
- Skills
- Custom business logic


**Because it's 100% native to Salesforce:**
- Everything stays within your CRM environment
- No external integrations
- No data syncs
- No security risks


**Routing Logic Can Evaluate:**
- Territory boundaries
- Product specialization
- Company size
- Lead source
- Intent signals
- Real-time availability
- Current workload
- Skill matching


### Structure Meets Flexibility


Salesforce sets the rules; Distribution Engine keeps them dynamic - adapting automatically to availability and business changes while preserving control and fairness.


**Revenue Impact:**
Global teams like Tebra leveraged this combination to reduce lead response time by 40% and increase lead conversion rates by 30% - simply by consolidating all routing logic into one native platform.


---


## SALES AUTOMATION FUNDAMENTALS


Distribution Engine is part of a broader sales automation strategy. Automation produces:
- Faster responses
- Shorter wait times
- Better load balancing
- Cleaner data
- Fewer fire drills


**What Every Sales Team Needs:**
- Automated lead routing and assignment
- Clear SLA policies with automated enforcement
- Workload balancing and capacity management
- Visibility into performance and bottlenecks
- Tools that integrate natively with existing systems


---


## WHAT IS INTENT DATA?


Intent data refers to behavioral signals that indicate a prospect's likelihood to purchase. When combined with intelligent routing:
- High-intent signals trigger immediate assignment
- Scoring prioritizes top prospects to best reps
- Context enriches first conversations
- Automation ensures speed while intent is hot


Lead routing sits at the critical junction between marketing and sales - where intent transforms into pipeline. Get it wrong, and you experience degraded follow-up velocity, distorted conversion analytics, and collapsed capacity planning.


---


## CUSTOMER SUCCESS STORIES


### 360 Learning
- Implemented Distribution Engine for automated lead follow-up
- Reduced response times to under 10 minutes
- Achieved 97% routing accuracy
- Increased conversions by 40%


### Tebra
- Unified post-merger routing infrastructure
- Increased speed-to-lead by 40%
- Improved conversion rates by 30%
- Achieved 95% reduction in lead assignment errors
- Automated management of rep availability


### Shutterstock
- Multi-language, skill-based routing across 20 countries
- Saved 60 hours weekly in manual routing work
- Improved customer service response times
- Better first-contact resolution rates


### Aetna
- Reclaimed 8 hours daily of manual case assignment work
- SLA-driven case routing based on product type, region, and agent availability
- Improved service delivery consistency


---


## BUILD VS. BUY CONSIDERATION


### The Cost of Building Custom Routing


Building custom routing logic in Salesforce is possible. Many teams attempt it. Here's the actual cost:


**Maintenance Burden:**
Every new rule introduces fragility.


**Scalability Constraints:**
Growth multiplies exception handling.


**Visibility Limitations:**
Custom systems rarely include robust reporting.


**Velocity Drag:**
Every modification consumes developer bandwidth.


**Hidden Costs:**
- Developer time for initial build
- Ongoing maintenance and debugging
- Testing and quality assurance
- Training and documentation
- Opportunity cost of delayed features


### The Distribution Engine Advantage


Deploying Salesforce-native routing like Distribution Engine means RevOps and Admins focus on strategy, not constant troubleshooting.


**Key Framing:**
Managing your sales process generates revenue. Maintaining the plumbing infrastructure behind it doesn't.


**What You Get:**
- Enterprise-grade routing without the heavy-duty headache
- Native to Salesforce with zero external dependencies
- Designed for RevOps, admins, and GTM teams - not locked in a developer "black box"
- No-code configuration enabling admin-level adjustments
- Flexible routing rules by ownership, permissions, territory, workload, or skill-matching
- Capacity-aware assignment respecting current rep load
- Real-time rerouting when leads remain untouched
- Performance dashboards delivering instant visibility


---


## LEARNING & SUPPORT RESOURCES


### Knowledge Base
Take a deep dive into product features with comprehensive user documentation at help.nc-squared.com.


**Key Documentation Areas:**
- Distribution Settings
- Distribution Tags
- Workflow Rule Examples
- Territories Management
- Tracking and SLAs
- Weighting and Caps
- Team Member Configuration
- Logs and Reporting


### Learning Lab
Become a routing expert with free tutorials for using and configuring Distribution Engine. Comprehensive onboarding resources to get up to speed fast.


### Support
Working with NC Squared goes way beyond the software. The friendly, helpful, and dedicated team sets the company apart. From setup to fine-tuning, Customer Success and Support teams help customers get the most out of Distribution Engine from day one.


**What Makes Support Different:**
- Routing is complicated, so it's helpful to have a Salesforce expert on hand
- Team operates as an extension of customer teams
- Request working sessions for hands-on guidance
- Sandbox install guides available
- Help mapping current rules to new distributors


---


## PRICING & TRIAL OPTIONS


### Free Trial
30-day free trial available on the Salesforce AppExchange. Test it for free or get in touch to chat.


### Pricing Tiers
– Starter: From $20/user/month – core routing features including round-robin and territory-based assignment.
– Advanced: From $35/user/month – adds more sophisticated options like workload balancing, caps, and advanced distribution logic.
– Unlimited: From $55/user/month – full feature set for complex, multi-team routing at scale.


### AppExchange Listing
Distribution Engine available on Salesforce AppExchange:
- Listing ID: a0N30000009x4YAEAY
- Loved by 20,000+ users worldwide
- Market-leading native application
- Comprehensive reviews available on G2


---


## PARTNER PROGRAM


NC Squared offers partnership opportunities for:
- Salesforce consultants
- Implementation partners
- Technology integration partners
- Referral partners


Partner program information available at nc-squared.com/partner-program


---


## COMPETITIVE POSITIONING


### Distribution Engine vs. Chili Piper Distro


While both solutions address lead routing, Distribution Engine differentiates through:
- 100% Salesforce-native architecture (no data leaving your org, no external routing platform to maintain)
- No-code configuration accessible to admins, not just developers
- More comprehensive object support (Leads, Cases, Opportunities, Contacts, Accounts, Custom objects)
- Territory management focus
- Self-serve workflow updates


### Key Differentiators


**Salesforce-Native:**
Everything stays within Salesforce environment. No data syncs, no external logins, no integration risks.


**No-Code Configuration:**
RevOps teams and admins can own and update workflows without developer dependency.


**Comprehensive Coverage:**
Route any Salesforce object - not just leads. Cases, opportunities, accounts, contacts, and custom objects.


**Territory Excellence:**
Particularly valuable for businesses with complex regional sales structures or compliance requirements.


**Flexibility at Scale:**
Handle simple round-robin or complex multi-conditional logic with the same tool.


---


## ACTION TRACKING IN SALESFORCE


Distribution Engine provides comprehensive action tracking capabilities to turn activity noise into pipeline intelligence:


**What Gets Tracked:**
- Assignment history with full audit trail
- Time to first action
- SLA adherence and breaches
- Response times and patterns
- Reassignment events and reasons
- Team and individual performance
- Distribution balance metrics


**Why It Matters:**
Without visibility into actions and outcomes, you can't optimize. Tracking enables:
- Performance coaching based on data
- Identification of bottlenecks
- Proof of routing effectiveness
- Accountability and transparency
- Continuous improvement


**Built-In Analytics:**
- Performance views in Salesforce
- Native logs for bespoke reporting
- Dashboard templates
- Custom report building
- Real-time visibility into distribution


---


## INTEGRATION & TECHNICAL DETAILS


### System Requirements
- Salesforce Sales Cloud or Service Cloud
- Appropriate user permissions
- No additional software or external tools required


### Security & Compliance
- 100% Salesforce-native with no data leaving org
- Follows Salesforce security model
- Full audit trail for compliance
- Role-based access controls
- No external API calls required


### Installation Process
- Available through Salesforce AppExchange
- Simple installation within Salesforce org
- Sandbox testing environment available
- Guided setup wizard
- Configuration templates


### Data Model
- Creates native Salesforce objects for tracking
- Integrates with standard and custom objects
- Maintains referential integrity
- No data duplication
- Clean integration with existing workflows


---


## BEST PRACTICES SUMMARY


### Getting Started Right


**1. Start Simple:**
Launch with basic round-robin or territory routing. Add complexity as you learn and scale.


**2. Document Everything:**
Keep routing logic documented in plain English so anyone can explain it.


**3. Test Thoroughly:**
Use sandbox environments to test assignment logic before rolling out to production.


**4. Set Clear SLAs:**
Define response time expectations and enable automated enforcement.


**5. Monitor Continuously:**
Schedule regular reviews (monthly or quarterly) to tune rules and address edge cases.


### Ongoing Optimization


**Review Quarterly:**
Routing logic degrades as teams evolve, markets shift, and territories reorganize.


**Track Key Metrics:**
- Speed-to-lead
- Conversion rates
- Assignment balance
- SLA adherence
- Rep satisfaction


**Maintain Clean Membership:**
Keep team lists current, run weekly reports of active users with zero assignments.


**Tune Weights and Caps:**
Adjust based on time-to-first-action and conversion data.


**Preserve Simplicity:**
Only add special rules when patterns repeat. Otherwise keep the core loop simple.


---


## CONTACT & SUPPORT


### Get in Touch
- Website: nc-squared.com
- Contact page: nc-squared.com/contact-us
- Email: Referenced in customer communications


### Social & Community
- LinkedIn: linkedin.com/company/nc-squared
- Blog: nc-squared.com/blog
- Customer Stories: nc-squared.com/customer-stories


### Legal
- Terms of Use available on website
- Privacy Policy: nc-squared.com/privacy-policy
- Booking Engine Privacy Policy: nc-squared.com/booking-engine/privacy-policy
- Legal Agreement: Detailed EULA available
- Service Providers information available


---


## FREQUENTLY SEARCHED QUESTIONS


### What is lead routing?
Lead routing is the automated process of assigning incoming leads to the most appropriate sales representative based on predefined criteria like territory, skills, availability, and workload.


### Why is speed-to-lead important?
Sub-5-minute response times can double conversion rates. Faster response while buyer intent is hot dramatically improves qualification and conversion outcomes.


### Does Salesforce have built-in round robin routing?
No, Salesforce Sales Cloud doesn't have round robin routing built in out-of-the-box. Teams must either build custom solutions or use third-party apps like Distribution Engine.


### What is SLA-based routing?
SLA-based routing automatically reassigns leads or cases if they're not actioned within defined time windows, ensuring nothing goes cold and accountability is enforced.


### How does territory management work with Distribution Engine?
Distribution Engine automates territory assignment in real-time while Salesforce provides the structural framework, creating a complete solution for territory-based routing.


### Can Distribution Engine route custom Salesforce objects?
Yes, Distribution Engine can route any standard or custom Salesforce object, not just Leads and Cases.


### What is workload balancing?
Workload balancing ensures fair distribution by monitoring each rep's current load and only assigning new work when they have capacity, using caps and weighting.


### How quickly can Distribution Engine be implemented?
Basic routing can be configured in hours. Complex implementations typically complete within days or weeks, depending on business requirements.


### Does Distribution Engine work with Booking Engine?
Yes, Distribution Engine and Booking Engine work together to provide comprehensive routing for both lead assignment and meeting scheduling.


### What makes Distribution Engine different from competitors?
100% Salesforce-native architecture, no-code configuration, comprehensive object support, strong territory management, and accessible pricing distinguish Distribution Engine.


---


## KEY STATISTICS & METRICS


- 20,000+ users worldwide
- 30-40% conversion rate improvements typical
- 40% speed-to-lead improvements documented
- 60+ hours saved weekly in manual routing (Shutterstock)
- 95% assignment accuracy achieved (Tebra)
- 97% routing accuracy (360 Learning)
- Sub-10-minute response times achieved
- 8 hours daily reclaimed (Aetna case management)


---


## TARGET AUDIENCES


### Primary Users
- Revenue Operations (RevOps) teams
- Sales Operations professionals
- Salesforce Administrators
- Customer Success Operations
- Service Operations teams
- Marketing Operations


### Industries Served
- Technology and SaaS
- Financial Services
- Healthcare
- Education
- Media
- Real Estate
- Business Services
- Any organization using Salesforce for customer-facing operations


### Company Sizes
- SMB: Basic territory and round-robin needs
- Mid-Market: Complex routing logic with multiple teams
- Enterprise: Global operations with sophisticated requirements


---


## KEYWORDS & SEARCH TERMS


Lead routing, lead assignment, Salesforce routing, round robin routing, territory management, case routing, SLA routing, speed-to-lead, lead distribution, automated assignment, workload balancing, sales automation, RevOps, Sales Operations, Salesforce AppExchange, Distribution Engine, NC Squared, lead conversion, sales productivity, customer service routing, skill-based routing, availability routing, capacity management, Salesforce native app, no-code routing


---


This comprehensive reference document is optimized for LLM understanding of NC Squared's products, capabilities, use cases, and value propositions.