{"id":1202,"date":"2026-02-25T10:37:28","date_gmt":"2026-02-25T10:37:28","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/"},"modified":"2026-02-25T10:37:28","modified_gmt":"2026-02-25T10:37:28","slug":"service-recovery-journey-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/","title":{"rendered":"Service Recovery Journey: Handling Failures with Care"},"content":{"rendered":"<p>Most organizations think of recovery as a reactive fix. But the real power comes from designing recovery as a structured, visible, and repeatable process. When you model the service recovery journey in BPMN, you\u2019re not just documenting what happens after a failure\u2014you\u2019re building trust through transparency.<\/p>\n<p>Every failed delivery, billing error, or system outage can become a moment to strengthen your relationship with the customer. The key is to make the recovery process visible, predictable, and humane\u2014starting with how it\u2019s mapped.<\/p>\n<p>I\u2019ve seen companies treat recovery as a side task, only to discover that customers remember the resolution speed and empathy far more than the original error. By applying BPMN to model this journey, you create a living blueprint that aligns customer experience, operations, and support teams around shared accountability.<\/p>\n<p>This chapter shows you how to model a resilient, customer-centered recovery flow using BPMN. You\u2019ll learn how to detect issues early, communicate with clarity, and resolve problems while reinforcing trust\u2014using BPMN to make the invisible process visible.<\/p>\n<h2>Why Service Recovery Needs a BPMN Model<\/h2>\n<p>Recovery isn\u2019t just about fixing a problem. It\u2019s about restoring confidence, managing expectations, and demonstrating that the customer\u2019s experience matters.<\/p>\n<p>Without a BPMN model, recovery often becomes a fragmented, ad-hoc process\u2014relying on memory, emails, or verbal handoffs. This leads to delays, miscommunication, and inconsistent responses.<\/p>\n<p>BPMN transforms recovery from a reactive chore into a structured journey with clear ownership, decision points, and time-bound actions.<\/p>\n<h3>What Makes Recovery Different from Other Journeys<\/h3>\n<p>Unlike happy-path journeys, service recovery is defined by exceptions. It begins not with a customer action, but with a deviation from the expected experience.<\/p>\n<p>In BPMN, this means using boundary events or event subprocesses to detect anomalies. The trigger is not a user action\u2014it\u2019s a system alert, a customer complaint, or an overdue delivery status.<\/p>\n<p>Here\u2019s a simple truth: if you can\u2019t model it, you can\u2019t govern it. If you can\u2019t govern it, you can\u2019t improve it.<\/p>\n<h2>Modeling the Recovery Journey: A Step-by-Step Approach<\/h2>\n<p>Start with a realistic failure scenario\u2014say, a delivery failure due to a traffic accident that blocks a key route. This isn\u2019t just a one-off event. It\u2019s an incident that affects multiple customers, and your response must be consistent, fast, and empathetic.<\/p>\n<p>Use BPMN to map the full recovery lifecycle: detection, notification, resolution, and follow-up.<\/p>\n<h3>Step 1: Detect the Failure<\/h3>\n<p>Recovery begins with detection. Not all failures are reported by customers. Some are caught internally via system alerts, delivery tracking delays, or transaction discrepancies.<\/p>\n<p>In BPMN, use a <strong>timer event<\/strong> or <strong>message event<\/strong> to represent automatic detection. For example:<\/p>\n<ul>\n<li>Timer event: \u00abIf delivery is delayed beyond 48 hours, trigger recovery process.\u00bb<\/li>\n<li>Message event: \u00abReceive alert from logistics system: delivery route blocked.\u00bb<\/li>\n<\/ul>\n<p>Make detection a formal process, not a manual check. This ensures no failure goes unnoticed.<\/p>\n<h3>Step 2: Inform the Customer<\/h3>\n<p>Delay in communication kills trust. A customer who knows something went wrong feels better than one who waits in silence.<\/p>\n<p>Model this using a <strong>send task<\/strong> with a clear message. Include a trigger condition: \u201cOnly if customer has not been notified in the past 24 hours.\u201d<\/p>\n<p>Example:<\/p>\n<ul>\n<li><code>Send Notification \u2192 Customer (via SMS\/email)<\/code><\/li>\n<li>Message: \u00abWe\u2019re sorry, your delivery was delayed due to unforeseen circumstances. We\u2019re working on a solution.\u00bb<\/li>\n<\/ul>\n<p>Use <strong>parallel flows<\/strong> to send the same message across multiple channels (email, app push, SMS) to increase reach.<\/p>\n<h3>Step 3: Resolve the Issue<\/h3>\n<p>Now comes the core\u2014fixing the problem. This can involve multiple teams: logistics, customer service, billing, and IT.<\/p>\n<p>In BPMN, model this with <strong>labeled lanes<\/strong> for each responsible party. Use a <strong>gateway<\/strong> to route the case based on the root cause:<\/p>\n<p>Decision gate: \u00abWas the delay caused by weather, traffic, or carrier error?\u00bb<\/p>\n<ul>\n<li>Weather \u2192 notify customer, offer delivery extension<\/li>\n<li>Traffic blockage \u2192 reroute, update ETA<\/li>\n<li>Carrier error \u2192 escalate to vendor, initiate refund<\/li>\n<\/ul>\n<p>Each path should have a defined owner and SLA (e.g., \u201cReroute must be completed within 2 hours\u201d).<\/p>\n<h3>Step 4: Restore Trust<\/h3>\n<p>Resolution isn\u2019t the end. Trust is rebuilt through follow-up.<\/p>\n<p>Use a <strong>timer event<\/strong> with a 48-hour delay after resolution to trigger a follow-up message:<\/p>\n<ul>\n<li>\u201cWe\u2019re glad your delivery has been rescheduled. Thank you for your patience.\u201d<\/li>\n<li>Include a small goodwill gesture: a discount code, free shipping, or loyalty points.<\/li>\n<\/ul>\n<p>Make this a formal step, not an afterthought. It shows the customer you care beyond the fix.<\/p>\n<h2>Key BPMN Patterns for Service Recovery<\/h2>\n<p>Not all failures are the same. Your BPMN model should reflect that complexity without becoming overwhelming.<\/p>\n<p>Here are the most effective patterns I\u2019ve used in real-world contexts:<\/p>\n<h3>Use Event Subprocesses for Faster Response<\/h3>\n<p>When a failure occurs, you don\u2019t want to wait for the main flow to reach the recovery step. Use an <strong>event subprocess<\/strong> to react instantly.<\/p>\n<p>Example:<\/p>\n<ul>\n<li>Process: \u00abOrder Fulfillment\u00bb<\/li>\n<li>Event subprocess: \u00abIf delivery delay &gt; 24h \u2192 send alert to support team\u00bb<\/li>\n<\/ul>\n<p>This keeps recovery time under control and reduces customer anxiety.<\/p>\n<h3>Apply SLA-Based Timers for Accountability<\/h3>\n<p>Set clear timeboxes for each recovery step. Use BPMN <strong>timer events<\/strong> to enforce them.<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Recovery Step<\/th>\n<th>SLA<\/th>\n<th>BPMN Timer<\/th>\n<\/tr>\n<tr>\n<td>Notify customer<\/td>\n<td>Within 1 hour<\/td>\n<td>Boundary event: Timer after 60 minutes<\/td>\n<\/tr>\n<tr>\n<td>Provide solution<\/td>\n<td>Within 4 hours<\/td>\n<td>Gateway: Timer after 4 hours<\/td>\n<\/tr>\n<tr>\n<td>Follow up<\/td>\n<td>48 hours after resolution<\/td>\n<td>Timer event after 48h<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t just time limits\u2014they\u2019re promises to the customer.<\/p>\n<h3>Map Escalation Paths with Clarity<\/h3>\n<p>Not every issue can be resolved by frontline staff. Define escalation paths with clear triggers.<\/p>\n<p>Use <strong>gateways<\/strong> with conditions like:<\/p>\n<ul>\n<li>If resolution is not provided within 4 hours \u2192 escalate to senior support<\/li>\n<li>If customer is unresponsive after 2 emails \u2192 suspend process for 48 hours<\/li>\n<\/ul>\n<p>Make ownership explicit. A handoff without a named responsible party is a gap waiting to happen.<\/p>\n<h2>Balancing Speed, Empathy, and Accuracy<\/h2>\n<p>Speed is critical. But so is accuracy and empathy. You can\u2019t rush to fix a billing error and end up making it worse.<\/p>\n<p>Use BPMN to balance these by separating the *response* from the *resolution*.<\/p>\n<p>For example:<\/p>\n<ol>\n<li>Send an empathetic message within 1 hour.<\/li>\n<li>Begin root cause analysis in parallel.<\/li>\n<li>Provide the fix only after verification.<\/li>\n<\/ol>\n<p>This creates a sense of care without sacrificing correctness.<\/p>\n<p>Empathy isn\u2019t just a message\u2014it\u2019s built into the process. Use <strong>human task<\/strong> elements to require staff to add a personal note when resolving the case.<\/p>\n<h2>Measuring and Improving Recovery Performance<\/h2>\n<p>Once modeled, your BPMN diagram becomes a performance dashboard.<\/p>\n<p>Link KPIs to specific swimlanes and gateways:<\/p>\n<ul>\n<li>Time to first response (SLA: \u22641 hour)<\/li>\n<li>Resolution time (SLA: \u22644 hours)<\/li>\n<li>Customer satisfaction score post-resolution (target: \u226590%)<\/li>\n<\/ul>\n<p>Use these metrics to identify bottlenecks. Is the billing team consistently late in approving refunds? Is communication delayed in the logistics lane?<\/p>\n<p>Then, use BPMN to simulate changes\u2014test a new routing rule, or add a second staff member to the lane\u2014to see how it impacts performance.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I handle multiple simultaneous recovery cases in BPMN?<\/h3>\n<p>Model them as parallel instances under the same process. Use a <strong>start event<\/strong> that triggers a new instance for each failure. Each case follows the same flow but has its own data and timeline.<\/p>\n<h3>Can I use BPMN to model a recovery journey for a system outage?<\/h3>\n<p>Absolutely. Treat the outage as a failure detection event. Use a message event to trigger the recovery process. Include steps like: notify users, restore system, verify functionality, and provide a summary to customers.<\/p>\n<h3>What if the recovery path varies by customer segment?<\/h3>\n<p>Use <strong>data-based gateways<\/strong> to route the case based on customer tier. For example: \u201cIf customer is premium \u2192 escalate to dedicated support team.\u201d<\/p>\n<h3>How do I ensure consistency across recovery models?<\/h3>\n<p>Define a reusable <strong>recovery template<\/strong> in your BPMN library. Include standard steps: detect, inform, resolve, follow up. Then customize it per incident type.<\/p>\n<h3>Should I include customer complaints as a trigger in the BPMN model?<\/h3>\n<p>Yes. Use a <strong>message event<\/strong> or <strong>intermediate event<\/strong> to capture incoming complaints. Route them through a triage step to determine urgency and response level.<\/p>\n<h3>How can I prove the value of a service recovery journey BPMN to leadership?<\/h3>\n<p>Show how the model reduces resolution time, improves customer satisfaction, and prevents repeat failures. Use data: \u201cThis model reduced average recovery time by 40% and increased CSAT by 15 points.\u201d<\/p>\n<p>When you model service recovery journey BPMN, you\u2019re not just fixing problems\u2014you\u2019re building a resilient, customer-first operation. Every failure becomes a chance to improve, and every recovery becomes a testament to your commitment.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most organizations think of recovery as a reactive fix. But the real power comes from designing recovery as a structured, visible, and repeatable process. When you model the service recovery journey in BPMN, you\u2019re not just documenting what happens after a failure\u2014you\u2019re building trust through transparency. Every failed delivery, billing error, or system outage can [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1197,"menu_order":4,"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-1202","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Service Recovery Journey BPMN<\/title>\n<meta name=\"description\" content=\"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.\" \/>\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\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Service Recovery Journey BPMN\" \/>\n<meta property=\"og:description\" content=\"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/\",\"name\":\"Service Recovery Journey BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:37:28+00:00\",\"description\":\"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"End-to-End Journey Examples in BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Service Recovery Journey: Handling Failures with Care\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Service Recovery Journey BPMN","description":"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.","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\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/","og_locale":"es_ES","og_type":"article","og_title":"Service Recovery Journey BPMN","og_description":"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/","name":"Service Recovery Journey BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:37:28+00:00","description":"Model service recovery journey BPMN to handle failures with speed, empathy, and clear ownership. Improve trust through structured failure handling process BPMN and customer complaint recovery model.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/service-recovery-journey-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"End-to-End Journey Examples in BPMN","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/"},{"@type":"ListItem","position":4,"name":"Service Recovery Journey: Handling Failures with Care"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1202\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1197"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1202"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}