{"id":1195,"date":"2026-02-25T10:37:25","date_gmt":"2026-02-25T10:37:25","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/"},"modified":"2026-02-25T10:37:25","modified_gmt":"2026-02-25T10:37:25","slug":"self-service-vs-assisted-journeys-in-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/","title":{"rendered":"Capturing Self-Service and Assisted Journeys"},"content":{"rendered":"

Most teams approach customer journey modeling with a binary mindset: either the customer acts alone, or they rely on a human agent. But real interactions are rarely so clean. What if your customer can start self-serving online, then escalate to live support mid-process? That\u2019s not a flaw\u2014it\u2019s a reality. The real challenge isn\u2019t in the user\u2019s behavior but in how we model it.<\/p>\n

I\u2019ve seen teams build separate diagrams for self-service and assisted flows, only to struggle when a single journey crosses both paths. The result? Misaligned expectations, duplicated work, and confusion between teams. The answer isn\u2019t to choose one or the other. It\u2019s to model them together, using BPMN\u2019s power to unify experience and execution.<\/p>\n

Here, you\u2019ll learn how to capture both self-service and assisted journeys in a single, coherent BPMN diagram\u2014without losing clarity. You\u2019ll see how gateways, lanes, and subprocesses can reflect the complexity of real-world customer behavior while keeping the model understandable for stakeholders across CX, IT, and operations.<\/p>\n

This approach isn\u2019t about over-engineering. It\u2019s about modeling truthfully, with empathy, and with a clear path to improvement. You\u2019ll walk away with patterns you can apply immediately, whether you’re redesigning an account management flow or streamlining a support process.<\/p>\n

Why Separate Diagrams Fail in Practice<\/h2>\n

Many teams create two diagrams: one for self-service, one for assisted. At first glance, this seems logical. But it quickly breaks down.<\/p>\n

Consider a customer who logs in via a web portal, tries to update their address, hits a system error, and then calls support. The journey wasn\u2019t \u201ceither\/or.\u201d It was both.<\/p>\n

When you split the process, you lose visibility into how customers transition between paths. You can\u2019t measure how often self-service fails, or where handoffs happen. You can\u2019t analyze the impact of delays across channels.<\/p>\n

Worse, it leads to duplication. The same customer action\u2014updating an address\u2014appears in two places. One version says \u201cuser does it online.\u201d The other says \u201cagent handles it via CRM.\u201d But the reality? The same data, same outcome, different channel.<\/p>\n

That\u2019s the cost of fragmentation. It undermines alignment. It hides performance metrics. It weakens your ability to improve the customer experience.<\/p>\n

Unifying Journeys: The BPMN Approach<\/h2>\n

Instead of splitting the journey, let\u2019s build it as one. The key is to treat self-service and assisted paths as alternative routes within the same process\u2014connected by decision points and shared data.<\/p>\n

Use a **gateway** to represent the moment a customer chooses a path. This isn\u2019t a technical choice\u2014it\u2019s a behavioral one. The gateway reflects the customer\u2019s intent: \u201cI can do this myself,\u201d or \u201cI need help.\u201d<\/p>\n

Structure the diagram with **swimlanes** to show who does what. The customer lane stays central. One lane holds \u201cWeb Self-Service,\u201d another \u201cCall Center Support,\u201d and a third \u201cBack Office Processing.\u201d This makes responsibility clear and avoids confusion.<\/p>\n

Then, use **subprocesses** to encapsulate complex flows. For example, a \u201cSelf-Service Update\u201d subprocess can include login, form validation, error handling, and confirmation. If an error occurs, the subprocess can trigger a transition to a \u201cSupport Escalation\u201d path.<\/p>\n

Key Patterns for Hybrid Journey Modeling<\/h3>\n

Here are the core patterns I use when modeling hybrid journeys:<\/p>\n

    \n
  1. Use a decision gateway after the first customer action<\/strong>. Ask: \u201cCan the user complete this step without help?\u201d If yes, route to self-service. If no, route to assisted.<\/li>\n
  2. Model shared data as a single source of truth<\/strong>. Whether the user logs in or an agent updates the profile, data flows through the same system. Make that visible.<\/li>\n
  3. Use event-based triggers for escalation<\/strong>. A \u201ctimeout\u201d or \u201cerror count threshold\u201d can trigger a handoff to support, even within a self-service flow.<\/li>\n
  4. Visualize handoffs with message flows<\/strong>. When a self-service form fails, show a message flow to the support team. This clarifies the transition.<\/li>\n
  5. Group similar paths under one swimlane using sub-processes<\/strong>. This reduces visual noise while keeping logic clear.<\/li>\n<\/ol>\n

    These aren\u2019t rigid rules\u2014they\u2019re flexible patterns. You\u2019ll adapt them based on complexity, audience, and tooling. But the goal remains the same: keep the customer in view, and make the journey transparent to everyone involved.<\/p>\n

    Practical Example: Account Update Journey<\/h2>\n

    Let\u2019s walk through a simple but realistic example: a customer updating their address.<\/p>\n

    Start with a Start Event<\/strong> labeled \u201cCustomer initiates address update.\u201d Then, add a Gateway<\/strong> with two outcomes:<\/p>\n

      \n
    • \u201cUser selects self-service\u201d \u2192 proceeds to subprocess \u201cUpdate via Web Portal\u201d<\/li>\n
    • \u201cUser requests live support\u201d \u2192 proceeds to subprocess \u201cEscalate to Call Center\u201d<\/li>\n<\/ul>\n

      The \u201cWeb Portal\u201d subprocess includes steps like login, form entry, validation, and confirmation. If validation fails more than twice, a Boundary Event<\/strong> triggers a \u201cEscalate to Support\u201d message flow.<\/p>\n

      The \u201cCall Center\u201d subprocess includes agent login, lookup, update, and confirmation. Both subprocesses end in a shared End Event<\/strong>: \u201cAddress updated successfully.\u201d<\/p>\n

      Now, both paths are visible, traceable, and share the same outcome.<\/p>\n

      Comparing Self-Service and Assisted Patterns<\/h3>\n\n\n\n\n\n\n\n\n
      Feature<\/th>\nSelf-Service BPMN Patterns<\/th>\nAssisted Service BPMN Models<\/th>\n<\/tr>\n
      Primary Interaction<\/strong><\/td>\nCustomer via web or app<\/td>\nCustomer via agent<\/td>\n<\/tr>\n
      Key Gateway<\/strong><\/td>\n\u201cCan user complete alone?\u201d<\/td>\n\u201cDoes customer need help?\u201d<\/td>\n<\/tr>\n
      Handoff Trigger<\/strong><\/td>\nForm errors, timeouts, or user choice<\/td>\nAgent decision, escalation rules<\/td>\n<\/tr>\n
      Responsibility<\/strong><\/td>\nCustomer + system<\/td>\nAgent + system<\/td>\n<\/tr>\n
      Shared Outcome<\/strong><\/td>\nYes \u2014 data update<\/td>\nYes \u2014 data update<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Notice how both paths share the same data and goal. The difference is in who controls the flow\u2014and that\u2019s what the model should make visible.<\/p>\n

      When to Use Each Approach<\/h2>\n

      Not every journey needs a hybrid model. Use a single path when the customer either always self-serves or always uses support. But when the journey is fluid\u2014when the customer might start one way and finish another\u2014hybrid modeling is essential.<\/p>\n

      Here\u2019s a checklist to guide your choice:<\/p>\n

        \n
      • Does the customer have a real choice between channels?<\/li>\n
      • Are there documented cases where self-service fails and support is needed?<\/li>\n
      • Do both paths lead to the same outcome with shared data?<\/li>\n
      • Do stakeholders need a unified view to measure performance?<\/li>\n<\/ul>\n

        If three or more answers are \u201cyes,\u201d build a hybrid model. You\u2019ll gain clarity, improve alignment, and unlock better insights.<\/p>\n

        Common Pitfalls and How to Avoid Them<\/h2>\n

        Even with the right structure, modeling hybrid journeys can go sideways. Here\u2019s what to watch for:<\/p>\n

          \n
        • Overloading the gateway<\/strong>: Don\u2019t use more than three outgoing flows. If you have more, split the process or use a sub-process.<\/li>\n
        • Confusing swimlane ownership<\/strong>: Assign clear roles. Don\u2019t let \u201cCustomer\u201d do work that only an agent or system can do.<\/li>\n
        • Ignoring data continuity<\/strong>: If the customer updates their address in self-service, make sure the support system reflects that change. Use shared data objects.<\/li>\n
        • Missing escalation triggers<\/strong>: Ensure error thresholds or time limits trigger handoffs. Otherwise, customers stay stuck.<\/li>\n<\/ul>\n

          These aren\u2019t just technical details\u2014they\u2019re customer experience decisions. Every misplaced gate or missing event can mean longer wait times, frustration, or lost trust.<\/p>\n

          Final Thoughts: One Journey, Two Paths, One Model<\/h2>\n

          Self-service and assisted journeys aren\u2019t opposites. They\u2019re complements. The best customer experiences don\u2019t force a choice\u2014they make both options available, seamless, and intuitive.<\/p>\n

          Modeling them together in BPMN isn\u2019t about complexity. It\u2019s about clarity. It\u2019s about showing the real journey, not a simplified myth.<\/p>\n

          You\u2019re not building separate models. You\u2019re building a single, shared understanding\u2014one that spans channels, roles, and decisions. That\u2019s where true customer experience improvement begins.<\/p>\n

          Start by identifying one journey where customers switch between self-service and support. Apply these patterns. Then, ask your team: \u201cDoes this reflect how people actually behave?\u201d If yes, you\u2019re on the right track.<\/p>\n

          Frequently Asked Questions<\/h2>\n

          How do I show escalation from self-service to support in BPMN?<\/h3>\n

          Use a boundary event on a self-service subprocess\u2014triggered by \u201cerror threshold reached\u201d or \u201ctimeout.\u201d Then route the event to a message flow to the support lane. This makes the handoff visible and traceable.<\/p>\n

          Can I use the same subprocess for both self-service and assisted flows?<\/h3>\n

          Yes, but only if the logic is identical. For example, a \u201cdata validation\u201d subprocess can be reused. But if the steps differ\u2014like agent verification vs. automated validation\u2014model them separately to avoid confusion.<\/p>\n

          What if the customer path is unpredictable?<\/h3>\n

          Use a flexible gateway with \u201cdecision points\u201d at key stages. Annotate with notes like \u201ccustomer may choose to self-serve or call.\u201d This keeps the model usable while acknowledging real-world variability.<\/p>\n

          How do I measure performance across both paths?<\/h3>\n

          Attach KPIs to the subprocesses: \u201caverage self-service completion time,\u201d \u201csupport handoff rate,\u201d \u201csuccess rate per path.\u201d Use BPMN\u2019s annotation or attributes to document these without cluttering the diagram.<\/p>\n

          Do I need to model every possible path?<\/h3>\n

          No. Focus on the most frequent paths and high-impact exceptions. Use \u201cother\u201d or \u201cexception\u201d lanes for rare cases. The goal is clarity, not completeness.<\/p>\n

          Is hybrid modeling suitable for complex enterprise systems?<\/h3>\n

          Absolutely. In fact, it\u2019s essential. When a customer updates a profile via a website, then calls support to verify a change, you need a model that reflects both. BPMN\u2019s flexibility allows you to scale from simple flows to enterprise-grade journeys.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Most teams approach customer journey modeling with a binary mindset: either the customer acts alone, or they rely on a human agent. But real interactions are rarely so clean. What if your customer can start self-serving online, then escalate to live support mid-process? That\u2019s not a flaw\u2014it\u2019s a reality. The real challenge isn\u2019t in the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1191,"menu_order":3,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1195","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nSelf-Service vs Assisted Journeys in BPMN<\/title>\n<meta name=\"description\" content=\"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Self-Service vs Assisted Journeys in BPMN\" \/>\n<meta property=\"og:description\" content=\"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/\",\"name\":\"Self-Service vs Assisted Journeys in BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:37:25+00:00\",\"description\":\"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Designing Customer-Centric BPMN Models\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Capturing Self-Service and Assisted Journeys\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Self-Service vs Assisted Journeys in BPMN","description":"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/","og_locale":"ru_RU","og_type":"article","og_title":"Self-Service vs Assisted Journeys in BPMN","og_description":"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"8 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/","name":"Self-Service vs Assisted Journeys in BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:37:25+00:00","description":"Learn how to model self-service and assisted journeys in BPMN without siloed diagrams. Use gateways, lanes, and subprocesses to unify customer experience flows.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/self-service-vs-assisted-journeys-in-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Designing Customer-Centric BPMN Models","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/modeling-customer-journeys-with-bpmn\/designing-customer-centric-bpmn-models\/"},{"@type":"ListItem","position":4,"name":"Capturing Self-Service and Assisted Journeys"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1195","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1195\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1191"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=1195"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=1195"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}