--- title: "Automated Salesforce Lead Routing | Ortoo Orchestrator" description: "Automated Salesforce Lead Routing with Q-assign on Ortoo Orchestrator. Route every lead by territory, capacity, qualification and SLA in real time, without custom code." lang: en json-ld: | [ { "@context": "https://schema.org", "@type": "Organization", "name": "Ortoo", "url": "https://ortooapps.com/", "logo": "https://ortooapps.com/ortoo-logo-square.png", "parentOrganization": { "@type": "Organization", "name": "Ascendx" } }, { "@context": "https://schema.org", "@type": "WebSite", "name": "Ortoo", "url": "https://ortooapps.com/" }, { "@context": "https://schema.org", "@type": "Article", "headline": "Automated Salesforce Lead Routing", "description": "Automated Salesforce Lead Routing with Q-assign on Ortoo Orchestrator. Route every lead by territory, capacity, qualification and SLA in real time, without custom code.", "dateModified": "2026-07-18", "datePublished": "2026-07-18", "author": { "@type": "Organization", "name": "Ortoo" }, "publisher": { "@type": "Organization", "name": "Ortoo" }, "mainEntityOfPage": "https://ortooapps.com/resources/pillar/lead-routing-salesforce" }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://ortooapps.com/" }, { "@type": "ListItem", "position": 2, "name": "Resources", "item": "https://ortooapps.com/resources" }, { "@type": "ListItem", "position": 3, "name": "Automated Salesforce Lead Routing", "item": "https://ortooapps.com/resources/pillar/lead-routing-salesforce" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How do I automate lead routing in Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Start with native lead assignment rules for the first match, then automate the rest with a routing layer: capacity, territory changes, SLA follow-up, and the SDR-to-AE handoff. Q-assign, on Ortoo Orchestrator, is configured in Salesforce setup, point and click, no code, and runs on top of the assignment rules already in place." } }, { "@type": "Question", "name": "Does Salesforce have a built-in round-robin lead assignment feature?", "acceptedAnswer": { "@type": "Answer", "text": "Standard Salesforce assignment rules assign leads based on field criteria, not by equitable distribution across available reps. Round-robin logic requires custom Apex, a Flow workaround, or a third-party routing tool. Ortoo Orchestrator includes round-robin and capacity-aware assignment as configured options, without custom code. For how this approach compares to standalone routing tools, see Ortoo Orchestrator vs routing tools." } }, { "@type": "Question", "name": "What is Salesforce lead routing?", "acceptedAnswer": { "@type": "Answer", "text": "Salesforce Lead Routing is the complete process of moving every inbound lead from capture to a qualified sales conversation. It governs enrichment, scoring, assignment, outreach, SDR-to-AE handoff, and SLA escalation as one coordinated workflow, rather than leaving each step to separate tools or manual practice." } }, { "@type": "Question", "name": "What is the difference between Salesforce lead routing and Salesforce lead assignment?", "acceptedAnswer": { "@type": "Answer", "text": "Salesforce Lead Assignment is the single match step that puts a lead on a queue or user based on field criteria. Salesforce Lead Routing is the end-to-end process that governs every stage from capture to qualified handoff, including capacity, territory changes, SLA follow-up, and the SDR-to-AE handoff. Assignment is one step inside routing." } }, { "@type": "Question", "name": "How does Ortoo Orchestrator route leads differently from native Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Ortoo routes based on real-time conditions: capacity, territory state, qualification tier, and SLA. Native assignment rules match against fixed field values at creation. Ortoo also governs what happens after assignment, outreach initiation, SDR-to-AE handoff, SLA escalation, as part of the same workflow." } }, { "@type": "Question", "name": "Can Ortoo Orchestrator work alongside our existing assignment rules?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Ortoo Orchestrator adds a coordination layer above assignment rules without replacing them. Existing rules remain in place and continue to fire. Ortoo handles the routing decisions and lifecycle steps that the existing rules do not cover." } }, { "@type": "Question", "name": "How does Ortoo handle routing when a rep is out of office or at capacity?", "acceptedAnswer": { "@type": "Answer", "text": "Ortoo evaluates capacity at the moment of assignment. A rep flagged as unavailable or at workload threshold is skipped. The lead routes to the next eligible rep by territory and qualification match. This happens automatically, without a manager redistributing manually." } }, { "@type": "Question", "name": "What happens to leads that do not get a response within the SLA window?", "acceptedAnswer": { "@type": "Answer", "text": "Ortoo Orchestrator runs the SLA clock from assignment. If the response threshold is not met, the workflow escalates automatically: to a senior rep, to a manager notification, or to a re-routing step, depending on the configuration. Escalation is built into the workflow rather than depending on someone monitoring response times." } }, { "@type": "Question", "name": "How long does it take to configure lead routing in Ortoo Orchestrator?", "acceptedAnswer": { "@type": "Answer", "text": "Most teams have a first lead type routing accurately within a few weeks. Configuration is done in the Ortoo UI without code, using the existing Salesforce environment. There is no platform migration and no development sprint required. Existing assignment rules remain in place throughout." } }, { "@type": "Question", "name": "Does Ortoo Orchestrator support both SDR-led and AE-direct routing models?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Routing models are configured, not hardcoded. SDR-led routing, AE-direct assignment, and hybrid models with territory-based splits are all supported. The SDR-to-AE handoff definition, including context transfer, acceptance criteria, and escalation path, is configured as part of the same workflow." } } ] } ] --- [Skip to main content](#main-content) [Support](/support)[Contact](/contact) [![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-gradient-C54UkOOH.webp)](/) Ortoo Orchestrator Solutions Why Ortoo Resources About [Pricing](/pricing) [Map your workflow](/contact?intent=workflow-mapping)[Book a demo](/contact?intent=demo) [Book a demo](/contact?intent=demo) On this page 1. [01 What is Salesforce lead routing?](#what-lead-routing-involves) 2. [02 Why does lead routing break down in Salesforce orgs?](#where-routing-breaks) 3. [03 What does modern Salesforce lead routing look like?](#what-handled-looks-like) 4. [04 One Salesforce lead routing workflow from routing readiness to successful assignment](#capture-to-close-diagram) 5. [05 What does Ortoo Orchestrator change for the RevOps team?](#what-changes-for-revops) 6. [06 How does Ortoo Orchestrator compare to native Salesforce lead routing?](#ortoo-vs-native-routing) 7. [07 How do you automate Salesforce lead routing?](#how-to-start) Salesforce lead routing # Automated Salesforce Lead Routing Salesforce Lead Routing is the process of matching every inbound lead to the right sales representative based on territory, capacity, qualification and response SLA from the moment the record is created. Salesforce provides lead assignment rules: deterministic filters that match leads to a queue or owner on fixed criteria. What assignment rules do not do is reflect operational conditions in real time. A rep at full capacity is assigned the same way as one with an open slot. A territory restructured last month still routes by last month's rules until someone updates them. High-intent leads that arrive out of hours wait for someone to notice.  Q-assign, powered by Ortoo Orchestrator, automates Salesforce Lead Routing with multi-factor matching and real-time routing decisions that adapt to territory, capacity and SLA changes without custom code. [Book a demo](/contact?intent=demo)[Map your workflow](/contact?intent=workflow-mapping) Definition ## What is Salesforce lead routing? Not a single step. A sequence from capture to qualified handoff, each stage with a defined owner and a defined output. Salesforce Lead Routing is more than assigning a lead to a sales rep. It is the process of evaluating every inbound lead and routing it to the right representative based on territory, capacity, qualification and SLA. Effective Lead Routing uses enrichment, scoring and qualification as routing inputs before making the routing decision. Routing is one stage inside [the complete lead-management lifecycle](/resources/pillar/salesforce-lead-management), which governs capture, qualification, engagement, conversion and recycling around the routing decision. Most Salesforce environments handle some of these steps. Few govern routing decisions as a single, observable workflow. Salesforce provides assignment rules that match leads to queues or users based on field values. They evaluate records only when the rule runs and cannot continuously adapt to operational changes such as capacity, territory updates or SLA risk. They do not adapt to what is happening in the team at the moment of assignment: who is at capacity, which territory was restructured last week, which lead source has an agreed two-hour SLA. That context lives outside the rule, and someone has to apply it manually when the rule gets it wrong. A practical test: can your team answer three questions about any open lead right now? Who owns it.  What stage of the routing workflow it is in.  What should happen next and when.  If any of those answers require checking with a person rather than reading a record, your lead routing workflow is incomplete. Why standard setups stall ## Why does lead routing break down in Salesforce orgs? Four patterns. Each manageable in isolation. Together, they produce a revenue cost that compounds with volume. Salesforce Lead Routing breaks down between workflow steps, not within the assignment rule itself. The assignment rule fires correctly. The problem is what happens when the assignment is wrong, when the rep does not respond, when the territory no longer reflects the team structure, or when routing decisions no longer reflect operational reality. ### Static assignment rules Rules match against field values at the moment of assignment. They cannot reflect capacity: a rep at 100% workload receives the same volume as one with open slots. When a territory changes, the rule reflects the old structure until someone updates it. The result is a steady flow of misroutes that SDRs and managers redistribute manually, without measuring the cost. ### Ownership drift between SDR and AE Routing gets the lead to an SDR. Nothing governs the handoff from SDR to AE. The qualification conversation is not attached to the record in a structured form. If the SDR who owned the lead moves on, or the lead goes cold and reactivates, the context that existed at first contact is gone. Ownership drifts because routing ends at assignment instead of governing reassignment and escalation. ### Speed-to-lead that degrades as volume grows When lead volume is low and the team is small, manual coordination keeps pace. As volume increases, the manual steps compound. High-intent and low-intent leads enter the same queue with the same priority. First response time rises. The team adds headcount or asks managers to triage, both absorb cost that a governed routing layer would eliminate. ### Territory logic that lags the business Territory structures change. Regions are split, accounts are reassigned, new verticals open. Updating assignment rules to reflect those changes requires a platform owner or admin. Until the update ships, routing reflects last quarter's structure. High-value accounts reach the wrong rep, and someone in RevOps corrects it after the lead has already aged. The five stages ## What does modern Salesforce lead routing look like? Five stages, each with a defined owner and a defined output. None of them dependent on who is watching the queue. Lead Routing in Salesforce is the process of matching every inbound lead to the right representative and ensuring that assignment remains correct as workload, territory and SLA conditions change. Native assignment rules make the first match on fixed criteria. Modern Lead Routing extends native assignment rules with capacity awareness, territory management, SLA monitoring and automatic re-routing when conditions change. Effective Salesforce Lead Routing governs every stage from capture to qualified handoff rather than relying on manual coordination between teams. Ortoo Orchestrator governs five stages. The same coordination model applies to case management, claims intake, and other operational workflows running on the same platform. For the category argument in full, see [why teams choose Ortoo Orchestrator](/why-ortoo-orchestrator), and for a side-by-side against point solutions see [how Ortoo compares to standalone routing tools](/why-ortoo-orchestrator/vs-routing-tools). ### Routing readiness The lead contains the minimum information required to make an accurate routing decision, including territory, source, qualification signals and ownership context. Missing routing data is identified before assignment. ### Routing evaluation Qualification signals, territory rules, capacity and business priorities are evaluated before routing. These factors determine who should receive the lead without requiring manual intervention. ### Routing and assignment Every lead is routed to the right representative using territory, capacity, qualification and SLA instead of static assignment rules. A rep at full capacity is skipped. A territory change takes effect without a platform redeploy. Round-robin, skills-based, and capacity-aware assignment are configured options, not custom Apex. Every routing decision is logged. ### Assignment and response The assigned representative receives the lead with the required context. Response SLAs begin immediately, and missed response targets trigger workflow actions automatically. ### Re-routing and exceptions If workload, availability or SLA conditions change, the workflow can re-route the lead automatically. Routing remains accurate throughout the assignment lifecycle rather than ending after the initial match. End to end ## One Salesforce lead routing workflow from routing readiness to successful assignment Ortoo Orchestrator orchestrates every stage of the Salesforce Lead Routing workflow above the Salesforce assignment rules and Flows already in place. 1. 01 Capture Clean record, source attributed 2. 02 Enrichment ICP tier and intent assessed 3. 03 Routing Territory, capacity, SLA matched 4. 04 Outreach Context transferred, SLA clock running 5. 05 Qualification MQL to SQL governed, audit complete For the revenue operations team ## What does Ortoo Orchestrator change for the RevOps team? What the coordination layer changes in practice. What stays exactly as it is. Existing assignment rules, Flows, and queue structures remain in place. Ortoo Orchestrator orchestrates lead routing across those layers. The boundary is precise. ### What stays in Salesforce - Assignment rules and queue structures already configured. - Flows and process automations running today. - Territory hierarchy, account ownership, and CRM data model. - Existing reports, dashboards, and revenue attribution. - Agentforce agents and enrichment tools already in the stack. ### What Ortoo Orchestrator owns - Routing decisions based on real-time capacity, territory, and qualification tier. - SDR-to-AE handoff definition: context transfer, acceptance criteria, escalation path. - SLA enforcement: response time, follow-up cadence, escalation on no-response. - AI steps applied at enrichment and scoring stages, within defined boundaries. - Audit trail across every routing decision, reassignment and escalation. - Visibility into where every lead is in the workflow, in real time. The net result: routing reflects how the team actually works today, not how it worked when the assignment rules were last updated. RevOps changes routing logic in the Ortoo UI without a platform deploy cycle. Territory changes propagate to routing immediately. Every routing decision is auditable. What modern Salesforce lead routing looks like ## Real outcomes from automating Salesforce lead routing Near 100% Routing accuracy from first assignment Equativ [See the Equativ story](/case-studies/enhancing-case-assignment-at-equativ-with-q-assign) 120,000+ Records processed through governed routing in 3 months Assent Compliance [Browse case studies](/case-studies) Weeks Typical time from decision to first routing workflow in production Comparison ## How does Ortoo Orchestrator compare to native Salesforce lead routing? Revenue operations teams typically choose between three approaches: extend native assignment rules, adopt a point-solution routing tool, or add a coordination layer that governs the full lead lifecycle. Here is what each approach delivers in practice. Capability Ortoo Orchestrator Native Salesforce with manual coordination Salesforce lead routing capabilities Territory, capacity, qualification tier, SLA state, evaluated at the moment of assignment. Field-value matching at time of rule fire. No real-time capacity or SLA awareness. Territory adaptability Territory changes propagate to routing immediately. No deploy cycle required. Assignment rules reflect the territory structure at the time they were last updated. Round-robin and capacity-aware assignment Configured option. Skips reps at capacity. Equitable distribution across available team members. Not natively supported. Requires custom Apex or Flow workaround. SDR-to-AE handoff governance Defined in the workflow. Context transfers. Acceptance criteria and escalation path configured. Managed by informal agreement. Context transfer depends on individual practice. SLA and no-response escalation SLA clock starts at assignment. No-response triggers escalation automatically within the workflow. Requires manual monitoring or a separate alert. Escalation depends on someone noticing. Audit trail Step-level, complete. Every routing decision, criteria matched, rep assigned, timestamp, is logged. Partial. Standard lead history captures field changes, not routing decision rationale. Cost of change RevOps adjusts routing logic in the Ortoo UI. No admin or developer required. Rule changes require platform owner or admin involvement. Admin backlog introduces delay. How does Ortoo Orchestrator compare to native Salesforce lead routing? Capability Ortoo Orchestrator Native Salesforce with manual coordination Salesforce lead routing capabilities Ortoo Orchestrator Territory, capacity, qualification tier, SLA state, evaluated at the moment of assignment. Native Salesforce with manual coordination Field-value matching at time of rule fire. No real-time capacity or SLA awareness. Territory adaptability Ortoo Orchestrator Territory changes propagate to routing immediately. No deploy cycle required. Native Salesforce with manual coordination Assignment rules reflect the territory structure at the time they were last updated. Round-robin and capacity-aware assignment Ortoo Orchestrator Configured option. Skips reps at capacity. Equitable distribution across available team members. Native Salesforce with manual coordination Not natively supported. Requires custom Apex or Flow workaround. SDR-to-AE handoff governance Ortoo Orchestrator Defined in the workflow. Context transfers. Acceptance criteria and escalation path configured. Native Salesforce with manual coordination Managed by informal agreement. Context transfer depends on individual practice. SLA and no-response escalation Ortoo Orchestrator SLA clock starts at assignment. No-response triggers escalation automatically within the workflow. Native Salesforce with manual coordination Requires manual monitoring or a separate alert. Escalation depends on someone noticing. Audit trail Ortoo Orchestrator Step-level, complete. Every routing decision, criteria matched, rep assigned, timestamp, is logged. Native Salesforce with manual coordination Partial. Standard lead history captures field changes, not routing decision rationale. Cost of change Ortoo Orchestrator RevOps adjusts routing logic in the Ortoo UI. No admin or developer required. Native Salesforce with manual coordination Rule changes require platform owner or admin involvement. Admin backlog introduces delay. How to start ## How do you automate Salesforce lead routing? One lead type. A defined routing workflow for it. Nothing existing changes on day one. 1. Map the current routing path for your highest-volume lead source. Identify every point where a human steps in to reassign, qualify, or escalate manually. 2. Define the routing criteria for that lead type: territory, capacity threshold, qualification tier, and response SLA. Write down how routing actually works today, not how the rule was written. 3. Configure the Salesforce Lead Routing workflow in Ortoo Orchestrator above the existing assignment rules. The existing rules remain in place. Ortoo adds the coordination layer above them. 4. Run the new routing layer in parallel for one week. Compare first-touch assignment accuracy against the manual correction log from the same period. 5. Enable automated Salesforce Lead Routing once accuracy is confirmed. Shift additional lead types from the same foundation, one at a time. 6. Add the next routing condition as a new Function Instance: a second territory tier, a new qualification signal, a capacity threshold for a growing team. Most teams have one lead type routing accurately within a few weeks. Assignment rules have not changed. The coordination layer above them is now handling what manual practice was handling before. Related reading ## Continue reading [ Salesforce routing The routing category across leads, cases, and any object: how routing works in Salesforce and where native routing stops. ](/resources/pillar/salesforce-routing)[ Salesforce lead assignment How Ortoo matches leads on skills, capacity, territory, and SLA, and what changes when routing is governed. ](/use-cases/lead-assignment-in-salesforce)[ Salesforce lead distribution Fair, value-aware, capacity-aware allocation of inbound leads. ](/use-cases/salesforce-lead-distribution)[ Q-assign: Salesforce lead and case routing The routing engine on Ortoo Orchestrator. ](/solutions/q-assign)[ Revenue workflow orchestration ](/solutions/revenue-workflow-orchestration)[ Operational workflow management in Salesforce ](/resources/pillar/operational-workflow-management-salesforce)[ Salesforce lead assignment rules, explained ](/resources/blog/lead-assignment-rules-salesforce)[ Why Ortoo Orchestrator The category argument: coordination layer above the automation Salesforce already provides. ](/why-ortoo-orchestrator)[ Ortoo Orchestrator vs routing tools Side by side with standalone point routing tools. ](/why-ortoo-orchestrator/vs-routing-tools) Frequently asked ## Common questions How do I automate lead routing in Salesforce? Start with native lead assignment rules for the first match, then automate the rest with a routing layer: capacity, territory changes, SLA follow-up, and the SDR-to-AE handoff. Q-assign, on Ortoo Orchestrator, is configured in Salesforce setup, point and click, no code, and runs on top of the assignment rules already in place. Does Salesforce have a built-in round-robin lead assignment feature? Standard Salesforce assignment rules assign leads based on field criteria, not by equitable distribution across available reps. Round-robin logic requires custom Apex, a Flow workaround, or a third-party routing tool. Ortoo Orchestrator includes round-robin and capacity-aware assignment as configured options, without custom code. For how this approach compares to standalone routing tools, see [Ortoo Orchestrator vs routing tools](/why-ortoo-orchestrator/vs-routing-tools). What is Salesforce lead routing? Salesforce Lead Routing is the complete process of moving every inbound lead from capture to a qualified sales conversation. It governs enrichment, scoring, assignment, outreach, SDR-to-AE handoff, and SLA escalation as one coordinated workflow, rather than leaving each step to separate tools or manual practice. What is the difference between Salesforce lead routing and Salesforce lead assignment? Salesforce Lead Assignment is the single match step that puts a lead on a queue or user based on field criteria. Salesforce Lead Routing is the end-to-end process that governs every stage from capture to qualified handoff, including capacity, territory changes, SLA follow-up, and the SDR-to-AE handoff. Assignment is one step inside routing. How does Ortoo Orchestrator route leads differently from native Salesforce? Ortoo routes based on real-time conditions: capacity, territory state, qualification tier, and SLA. Native assignment rules match against fixed field values at creation. Ortoo also governs what happens after assignment, outreach initiation, SDR-to-AE handoff, SLA escalation, as part of the same workflow. Can Ortoo Orchestrator work alongside our existing assignment rules? Yes. Ortoo Orchestrator adds a coordination layer above assignment rules without replacing them. Existing rules remain in place and continue to fire. Ortoo handles the routing decisions and lifecycle steps that the existing rules do not cover. How does Ortoo handle routing when a rep is out of office or at capacity? Ortoo evaluates capacity at the moment of assignment. A rep flagged as unavailable or at workload threshold is skipped. The lead routes to the next eligible rep by territory and qualification match. This happens automatically, without a manager redistributing manually. What happens to leads that do not get a response within the SLA window? Ortoo Orchestrator runs the SLA clock from assignment. If the response threshold is not met, the workflow escalates automatically: to a senior rep, to a manager notification, or to a re-routing step, depending on the configuration. Escalation is built into the workflow rather than depending on someone monitoring response times. How long does it take to configure lead routing in Ortoo Orchestrator? Most teams have a first lead type routing accurately within a few weeks. Configuration is done in the Ortoo UI without code, using the existing Salesforce environment. There is no platform migration and no development sprint required. Existing assignment rules remain in place throughout. Does Ortoo Orchestrator support both SDR-led and AE-direct routing models? Yes. Routing models are configured, not hardcoded. SDR-led routing, AE-direct assignment, and hybrid models with territory-based splits are all supported. The SDR-to-AE handoff definition, including context transfer, acceptance criteria, and escalation path, is configured as part of the same workflow. See it on your lead workflow ## Automate Salesforce lead routing Bring the lead type that generates the most manual routing decisions, reassignment or SLA exceptions. We'll show you how to automate Salesforce lead routing using your existing Salesforce configuration. [Book a demo](/contact?intent=demo)[Map your workflow](/contact?intent=workflow-mapping) ![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-C6Mjw-cG.svg) Workflow orchestration in Salesforce, executed by specialized agents under controlled AI. PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) ## PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) ## WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) ## RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) ## USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) ## COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) ## LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) © 2026 Ortoo. An Ascendx Company. All rights reserved. [](https://www.linkedin.com/company/ortooapps/)[](https://x.com/OrtooApps)