{"id":1199,"date":"2026-02-25T10:37:26","date_gmt":"2026-02-25T10:37:26","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/"},"modified":"2026-02-25T10:37:26","modified_gmt":"2026-02-25T10:37:26","slug":"support-journey-bpmn-issue-resolution","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/","title":{"rendered":"Support Journey: From Issue to Resolution and Follow-Up"},"content":{"rendered":"<p>\u201cStart with the customer\u2019s first point of contact and move step by step.\u201d This advice appears everywhere. But in practice, it often leads to tangled, overly detailed models that miss the real pain points.<\/p>\n<p>When you model support journeys, the real challenge isn\u2019t capturing every step. It\u2019s identifying where the gaps are\u2014where delays happen, where handoffs break down, where empathy fades.<\/p>\n<p>My years building BPMN models for support teams taught me this: a solid support journey BPMN doesn\u2019t just map actions. It reveals who\u2019s responsible, when time matters, and how decisions affect experience.<\/p>\n<p>You\u2019ll walk through how to model the full lifecycle of a support issue\u2014across self-service, chat, and phone\u2014using BPMN to highlight touchpoints, decision gates, escalation paths, and follow-up loops. You\u2019ll learn to balance clarity with realism, so your model becomes a tool for improvement, not just documentation.<\/p>\n<p>This chapter turns abstract concepts into clear, actionable diagrams. You\u2019ll see exactly how to represent the <strong>customer support process BPMN<\/strong>, track a single ticket through escalation paths, and model outcomes that matter: resolved, unresolved, or repeated.<\/p>\n<h2>Mapping the Full Support Journey: From Issue to Resolution<\/h2>\n<p>Every support journey begins with a friction point: a failed login, a missing shipment, a confusing error message. The moment the customer reaches out, a new process begins\u2014not just a sequence of actions, but a path where experience is shaped by response time, clarity, and care.<\/p>\n<p>Start by defining the journey\u2019s scope. The trigger is clear: a customer reports an issue. The end? A confirmed resolution, a follow-up, or a closure with feedback. But the path between is where things diverge.<\/p>\n<p>Use BPMN to model the customer as a first-class participant. Place them in their own pool or lane, clearly separated from internal teams. Then, map the channels they use: self-service help, live chat, phone support.<\/p>\n<p>Each channel has its own rhythm and outcome. Self-service resolves simple cases fast, but can leave customers feeling stuck. Chat offers real-time help but may delay escalation. Phone support builds trust but can introduce delays.<\/p>\n<h3>Modeling Multi-Channel Support Entry Points<\/h3>\n<p>Begin with a message flow from the customer pool to a central support lane. Use a gateway to route the case based on channel.<\/p>\n<p>Here\u2019s a practical structure:<\/p>\n<ul>\n<li><strong>Self-Service Path:<\/strong> Customer searches a help center. If resolved, the journey ends. If not, they can escalate to a chat or phone ticket.<\/li>\n<li><strong>Chat Path:<\/strong> A support agent responds in real time. If resolved, close the ticket. If not, escalate via message flow to the next level.<\/li>\n<li><strong>Phone Path:<\/strong> The agent logs the issue, checks the system, and determines next steps. If unresolved, the ticket is escalated.<\/li>\n<\/ul>\n<p>Use <strong>send\/receive tasks<\/strong> to represent interactions. For example:<\/p>\n<pre><code>Customer \u2192 [Send: Issue Report] \u2192 Support Lane\nSupport Lane \u2192 [Receive: Issue Report] \u2192 Triage<\/code><\/pre>\n<p>Keep the customer visible throughout. Even when they\u2019re waiting, their presence should be implied through time-based events or wait states.<\/p>\n<h2>Decision Logic: Triage, Escalation, and Resolution Paths<\/h2>\n<p>At the heart of any support journey BPMN model is decision-making. The ability to route tickets correctly determines how fast and fairly customers are served.<\/p>\n<p>Use gateways to model branching logic. The first decision is <strong>triage<\/strong>:<\/p>\n<ul>\n<li>If issue is common and documented \u2192 Route to self-service or knowledge base.<\/li>\n<li>If issue is complex or high-risk \u2192 Escalate to Tier 2.<\/li>\n<li>If issue is time-sensitive \u2192 Flag for immediate attention.<\/li>\n<\/ul>\n<p>Now, model the <strong>ticket escalation journey<\/strong>. This is where many models fail: they assume escalation is a single path. In reality, it\u2019s a decision tree with multiple conditions.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Escalation Trigger<\/th>\n<th>Response<\/th>\n<th>BPMN Pattern<\/th>\n<\/tr>\n<tr>\n<td>Unresolved after 48 hours<\/td>\n<td>Auto-escalate to Tier 2<\/td>\n<td>Timer event + gateway<\/td>\n<\/tr>\n<tr>\n<td>High-priority label<\/td>\n<td>Immediate assignment to senior agent<\/td>\n<td>Message event with priority flag<\/td>\n<\/tr>\n<tr>\n<td>Customer escalates via email<\/td>\n<td>Reopen and re-route<\/td>\n<td>Boundary event (exception)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use <strong>boundary events<\/strong> to capture exceptions: a customer sending a hostile message, a response time exceeding SLA, or a repeated issue from the same user.<\/p>\n<p>These events don\u2019t just signal failure. They trigger recovery actions: reassurance, management review, or a service recovery protocol.<\/p>\n<h3>Modeling Resolved, Unresolved, and Repeated Issues<\/h3>\n<p>Not all issues end in resolution. Some remain open. Some get reopened. A good <strong>issue resolution BPMN model<\/strong> must reflect these outcomes.<\/p>\n<p>After resolution, include a <strong>follow-up task<\/strong>:<\/p>\n<ul>\n<li>Wait 48 hours<\/li>\n<li>Send customer satisfaction survey (CSAT)<\/li>\n<li>Evaluate feedback<\/li>\n<li>If CSAT is low \u2192 Reopen ticket and escalate to quality team<\/li>\n<\/ul>\n<p>Use a loopback to previous steps if the customer reports the issue persists. This isn\u2019t a flaw\u2014it\u2019s a feature. It shows the journey isn\u2019t linear.<\/p>\n<p>Here\u2019s a simple loop logic:<\/p>\n<pre><code>Resolution \u2192 [Wait: 48h] \u2192 [Send Survey]\nSurvey \u2192 [CSAT \u2265 4] \u2192 [Close Ticket]\nSurvey \u2192 [CSAT &lt; 4] \u2192 [Reopen Ticket] \u2192 [Escalate to Quality]<\/code><\/pre>\n<p>Reopening isn\u2019t a mistake. It\u2019s a signal the process needs improvement.<\/p>\n<h2>Integrating KPIs and SLAs into the Model<\/h2>\n<p>Every BPMN model should answer: what does success look like?<\/p>\n<p>Attach SLAs to key steps:<\/p>\n<ul>\n<li>First response: within 4 hours<\/li>\n<li>Resolution: within 3 business days<\/li>\n<li>Follow-up: within 48 hours<\/li>\n<\/ul>\n<p>Use <strong>timer events<\/strong> to represent time limits. If a task exceeds SLA, a boundary event triggers an alert.<\/p>\n<p>Label each activity with a KPI. For example:<\/p>\n<ul>\n<li>\u201cTriage: Average time: 1.2 hours (KPI: SLA 4h)\u201d<\/li>\n<li>\u201cEscalation: Average time: 2.4 hours (KPI: SLA 48h)\u201d<\/li>\n<\/ul>\n<p>These annotations aren\u2019t decorative. They turn the BPMN model into a performance dashboard.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced modelers fall into traps. Here are the most frequent:<\/p>\n<ol>\n<li><strong>Overloading the diagram:<\/strong> Too many gateways, nested subprocesses, or too many lanes. Simplify. Use subroutines for repeated logic.<\/li>\n<li><strong>Hiding the customer:<\/strong> When the customer isn\u2019t in the model, it becomes a back-office flow. Always keep the customer lane visible.<\/li>\n<li><strong>Missing exception paths:<\/strong> A \u201chappy path\u201d model doesn\u2019t reflect reality. Always include escalations, complaints, and reopens.<\/li>\n<li><strong>Ignoring time:<\/strong> Waiting states, response delays, and SLAs are part of the customer experience. Use timers and annotations to reflect them.<\/li>\n<\/ol>\n<p>Remember: the goal isn\u2019t to document every detail. It\u2019s to reveal where improvements are needed.<\/p>\n<h2>Final Thought: The Model as a Tool for Change<\/h2>\n<p>When you\u2019ve built a support journey BPMN model that includes all channels, decisions, escalations, and follow-ups, you\u2019re not done. You\u2019ve just begun.<\/p>\n<p>This model becomes a shared language. Product teams see where friction occurs. Support leads understand bottlenecks. CX leaders can measure impact.<\/p>\n<p>A strong support journey BPMN isn\u2019t just about process. It\u2019s about responsibility, empathy, and continuous improvement. And it all starts with a single decision: to put the customer at the center of every line of code, every handoff, every task.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I represent self-service and live chat in the same BPMN model?<\/h3>\n<p>Use a gateway to split the flow based on channel. Create separate lanes for \u201cSelf-Service,\u201d \u201cLive Chat,\u201d and \u201cPhone Support,\u201d but keep the customer pool connected across all. Use message flows to show escalation between lanes.<\/p>\n<h3>What\u2019s the best way to model ticket escalation in BPMN?<\/h3>\n<p>Use a decision gateway after triage. Include triggers like time elapsed, priority level, or customer feedback. Then use timer events and boundary events to capture SLA breaches or exceptions.<\/p>\n<h3>Can I model repeated issues in a BPMN diagram?<\/h3>\n<p>Absolutely. Use a loopback from the follow-up step to resolution if the customer reports the issue persists. Label it clearly: \u201cReopen if issue not resolved.\u201d This shows the journey isn\u2019t linear.<\/p>\n<h3>Should I include the customer in every BPMN diagram?<\/h3>\n<p>Yes, especially when modeling the end-to-end support journey. Represent them as a separate pool or lane. This keeps the focus on experience, not just operations.<\/p>\n<h3>How do SLAs and KPIs fit into BPMN?<\/h3>\n<p>Use annotations or labels on activities. For example: \u201cResolution: Target 48h (SLA).\u201d Use timer events to trigger alerts if time limits are exceeded. This turns BPMN into a performance tracker.<\/p>\n<h3>What if my support team uses different tools across channels?<\/h3>\n<p>Don\u2019t model the tools. Model the process. Use a single \u201cSupport\u201d lane and annotate it with channel-specific steps. The tool is irrelevant\u2014what matters is the handoff, response time, and resolution outcome.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u201cStart with the customer\u2019s first point of contact and move step by step.\u201d This advice appears everywhere. But in practice, it often leads to tangled, overly detailed models that miss the real pain points. When you model support journeys, the real challenge isn\u2019t capturing every step. It\u2019s identifying where the gaps are\u2014where delays happen, where [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1197,"menu_order":1,"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-1199","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>Support Journey BPMN: From Issue to Resolution<\/title>\n<meta name=\"description\" content=\"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.\" \/>\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\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Support Journey BPMN: From Issue to Resolution\" \/>\n<meta property=\"og:description\" content=\"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/\",\"name\":\"Support Journey BPMN: From Issue to Resolution\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:37:26+00:00\",\"description\":\"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"End-to-End Journey Examples in BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Support Journey: From Issue to Resolution and Follow-Up\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Support Journey BPMN: From Issue to Resolution","description":"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.","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\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/","og_locale":"de_DE","og_type":"article","og_title":"Support Journey BPMN: From Issue to Resolution","og_description":"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/","name":"Support Journey BPMN: From Issue to Resolution","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:37:26+00:00","description":"Master the support journey BPMN model to visualize issue reporting, triage, escalation, resolution, and follow-up across self-service, chat, and phone channels. Optimize customer experience with clear, actionable process design.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/support-journey-bpmn-issue-resolution\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"End-to-End Journey Examples in BPMN","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/modeling-customer-journeys-with-bpmn\/end-to-end-journey-examples-in-bpmn\/"},{"@type":"ListItem","position":4,"name":"Support Journey: From Issue to Resolution and Follow-Up"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1199","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1199\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1197"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1199"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}