{"id":1189,"date":"2026-02-25T10:37:22","date_gmt":"2026-02-25T10:37:22","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/"},"modified":"2026-02-25T10:37:22","modified_gmt":"2026-02-25T10:37:22","slug":"identifying-actors-in-customer-journey-bpmn","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/","title":{"rendered":"Identifying Actors: Customers, Frontline Staff, and Back Office"},"content":{"rendered":"<p>Every journey begins with a person \u2014 and every process is shaped by those who touch it.<\/p>\n<p>When I work with teams who say, \u201cWe don\u2019t know who\u2019s doing what,\u201d I start by asking: \u201cWho\u2019s actually responsible for the next step?\u201d<\/p>\n<p>That question cuts through the fog. In customer journey BPMN, identifying actors isn&#8217;t just about labeling lanes \u2014 it\u2019s about clarifying ownership, accountability, and the human element behind every step.<\/p>\n<p>This chapter shows you how to distinguish between customers, frontline staff, and back-office teams \u2014 not just in theory, but in the way you draw them in BPMN.<\/p>\n<p>You\u2019ll learn how to map roles clearly, avoid common confusion between internal and external actors, and design diagrams where the customer stays visible \u2014 even in complex operations.<\/p>\n<p>By the end, you\u2019ll be able to translate real-world roles into BPMN pools and lanes with confidence, using patterns that reflect how people actually work \u2014 and how customers experience it.<\/p>\n<h2>Why Actors Matter in Customer Journey Modeling<\/h2>\n<p>Too many BPMN models start with a blank canvas and an abstract \u201cprocess.\u201d But a customer journey isn&#8217;t abstract. It\u2019s lived \u2014 and felt \u2014 by real people.<\/p>\n<p>When you fail to define actors, you lose accountability. You end up with a diagram where \u201csomeone\u201d handles the next step \u2014 and no one takes ownership.<\/p>\n<p>Clarity around roles isn\u2019t just about structure. It\u2019s about empathy. It means knowing: who\u2019s on the frontlines? Who\u2019s behind the scenes? And who\u2019s actually experiencing the journey?<\/p>\n<p>Here\u2019s a truth I\u2019ve learned after 20 years: the most broken processes aren\u2019t the ones with poor logic \u2014 they\u2019re the ones where roles are ambiguous or invisible.<\/p>\n<p>With that in mind, let\u2019s look at the three core types of actors in customer journey BPMN.<\/p>\n<h3>1. The Customer: The Heart of the Journey<\/h3>\n<p>The customer is not a role \u2014 it\u2019s the reason the journey exists.<\/p>\n<p>They\u2019re the only actor who must always be visible in the model, even if they\u2019re not directly interacting at every step.<\/p>\n<p>Always represent the customer as a separate pool or lane. This is non-negotiable.<\/p>\n<p>If the customer isn\u2019t in the diagram, you\u2019ve already lost the experience perspective \u2014 and that\u2019s why so many process improvements fail.<\/p>\n<h3>2. Frontline Staff: The Face of Service<\/h3>\n<p>These are the people who interact directly with customers \u2014 call center agents, retail associates, support reps, sales consultants.<\/p>\n<p>They\u2019re often the first point of contact when a customer reaches out. Their actions \u2014 whether it\u2019s resolving a query or escalating a complaint \u2014 shape the customer\u2019s perception of quality.<\/p>\n<p>In BPMN, frontline staff should be in their own lane, within the same pool as the customer or in a separate pool for internal operations.<\/p>\n<p>They act as intermediaries \u2014 carrying customer requests forward, relaying feedback, and managing expectations.<\/p>\n<p>Remember: frontline staff are not just executors. They are decision-makers in real time \u2014 and their role should reflect that.<\/p>\n<h3>3. Back Office Teams: The Hidden Engine<\/h3>\n<p>Behind the scenes, back office teams handle what frontline staff can\u2019t \u2014 account setup, policy checks, fraud validation, billing, data entry.<\/p>\n<p>These roles are often invisible to customers, but they\u2019re critical to whether a journey succeeds.<\/p>\n<p>In BPMN, back office teams should be in a separate lane \u2014 typically under a \u201cBack Office\u201d pool or within a subprocess.<\/p>\n<p>They don\u2019t need to be labeled \u201cadmin\u201d or \u201csupport.\u201d Be specific: \u201cCredit Risk Analyst,\u201d \u201cPolicy Validation Team,\u201d \u201cInvoice Processing Unit.\u201d<\/p>\n<p>Why? Because ambiguity breeds delay. If a step says \u201cbackend checks,\u201d who\u2019s doing it? What are the rules?<\/p>\n<p>Clear role definition ensures that handoffs are precise and expectations are shared.<\/p>\n<h2>Mapping Roles to BPMN Pools and Lanes<\/h2>\n<p>Now that we\u2019ve defined the roles, let\u2019s turn to the model.<\/p>\n<p>Use pools to represent major organizational entities. The customer is always in a pool of their own.<\/p>\n<p>Internal teams \u2014 frontline and back office \u2014 belong in pools or lanes within a larger process pool.<\/p>\n<p>Here\u2019s a simple but powerful pattern:<\/p>\n<ul>\n<li><strong>Pool 1:<\/strong> <strong>Customer<\/strong> \u2014 always visible, always primary.<\/li>\n<li><strong>Pool 2:<\/strong> <strong>Frontline Operations<\/strong> \u2014 includes call center, retail, or service agent roles.<\/li>\n<li><strong>Pool 3:<\/strong> <strong>Back Office<\/strong> \u2014 includes systems, validation, processing, and data teams.<\/li>\n<\/ul>\n<p>Each pool can have multiple lanes \u2014 for example, \u201cCall Center Agent,\u201d \u201cField Technician,\u201d or \u201cDocument Review Team.\u201d<\/p>\n<p>Use this structure to show not just what happens, but who is responsible for it.<\/p>\n<p>Let\u2019s take a real example: a customer service request via phone.<\/p>\n<p>The customer initiates the journey by calling. That request lands in the Frontline Operations pool. The agent logs the issue and decides: is it simple? Can it be resolved now?<\/p>\n<p>If yes \u2014 done. If no \u2014 the request moves to the Back Office pool, where a specialist reviews the case. Once approved, the solution flows back to the frontline, who communicates it to the customer.<\/p>\n<p>This structure makes responsibilities clear \u2014 and makes it easy to spot where delays happen.<\/p>\n<h3>Patterns for Distinguishing Internal vs. External Actors<\/h3>\n<p>Not all actors are internal. Some are partners, vendors, or third parties.<\/p>\n<p>To maintain clarity, use consistent visual cues:<\/p>\n<ul>\n<li><strong>Customer:<\/strong> Always outside the organization \u2014 typically on the left.<\/li>\n<li><strong>Frontline Staff:<\/strong> Inside the organization \u2014 in the first internal pool.<\/li>\n<li><strong>Back Office:<\/strong> Deeper into the organization \u2014 often in a separate pool.<\/li>\n<li><strong>External Partners:<\/strong> Represented with a dashed border or a different color \u2014 e.g., \u201cThird-Party Payment Processor.\u201d<\/li>\n<\/ul>\n<p>Why does this matter? Because when a customer waits for a payment to be approved by an external partner, that wait isn\u2019t on your team\u2019s clock \u2014 but it\u2019s on the customer\u2019s.<\/p>\n<p>Make that visible.<\/p>\n<h2>Defining Roles for Customer Journeys: A Step-by-Step Guide<\/h2>\n<p>Here\u2019s how I help teams define roles with precision:<\/p>\n<ol>\n<li><strong>Start with the journey narrative.<\/strong> What does the customer do? What triggers each step?<\/li>\n<li><strong>Ask: Who does this step?<\/strong> Don\u2019t assume. Interview the people who do it.<\/li>\n<li><strong>Group roles by function:<\/strong> frontline, back office, partners, or customer.<\/li>\n<li><strong>Label lanes explicitly:<\/strong> Use job titles \u2014 not \u201cTeam A\u201d or \u201cDepartment B.\u201d<\/li>\n<li><strong>Map handoffs clearly:<\/strong> Use message flows to show communication between pools.<\/li>\n<li><strong>Validate with stakeholders:<\/strong> Ensure no one says, \u201cThat\u2019s not my job.\u201d<\/li>\n<\/ol>\n<p>This process isn\u2019t about perfect labeling \u2014 it\u2019s about removing ambiguity.<\/p>\n<p>When you can answer, \u201cWho will do this next?\u201d with confidence, you\u2019ve made progress.<\/p>\n<h3>Common Pitfalls and How to Avoid Them<\/h3>\n<p>Even experienced modelers fall into traps. Here are the most common:<\/p>\n<ul>\n<li><strong>Blurring frontline and back office:<\/strong> Don\u2019t mix \u201cagent\u201d and \u201cmanager\u201d in the same lane. Keep them separate.<\/li>\n<li><strong>Overloading lanes:<\/strong> Don\u2019t list every job in one lane. A \u201cSupport\u201d lane with 10 roles is unreadable. Split into sub-lanes or use a subprocess.<\/li>\n<li><strong>Ignoring the customer\u2019s role in handoffs:<\/strong> If a customer must confirm something \u2014 show it. Even \u201cwaiting for customer response\u201d is a state.<\/li>\n<li><strong>Using vague labels:<\/strong> \u201cSomeone,\u201d \u201cthe system,\u201d or \u201cthe team\u201d are not roles. Be specific.<\/li>\n<\/ul>\n<p>Remember: a clear lane is not a busy lane.<\/p>\n<h2>Frontline vs Back Office in Processes: A Practical Comparison<\/h2>\n<p>Understanding the difference between frontline and back office roles is key to modeling experience accurately.<\/p>\n<p>Here\u2019s how they differ \u2014 and why it matters in BPMN:<\/p>\n<table>\n<thead>\n<tr>\n<th>Aspect<\/th>\n<th>Frontline Staff<\/th>\n<th>Back Office Teams<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Interaction with Customer<\/strong><\/td>\n<td>Direct: phone, chat, in-person<\/td>\n<td>Indirect: via system or request<\/td>\n<\/tr>\n<tr>\n<td><strong>Decision-making Speed<\/strong><\/td>\n<td>Real-time: resolves issues on the spot<\/td>\n<td>Delayed: may take hours or days<\/td>\n<\/tr>\n<tr>\n<td><strong>Visibility<\/strong><\/td>\n<td>High: customer sees them<\/td>\n<td>Low: customer rarely knows<\/td>\n<\/tr>\n<tr>\n<td><strong>Role in BPMN<\/strong><\/td>\n<td>Executes steps directly; often in a separate lane<\/td>\n<td>Handles complex, non-urgent work; often in a subprocess<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use this table to guide your modeling decisions.<\/p>\n<p>When you see a step like \u201cverify identity,\u201d ask: is this handled by a frontline agent who sees the customer, or a back office team who reviews documents?<\/p>\n<p>That distinction changes how you model it \u2014 and how the customer experiences it.<\/p>\n<h2>Case Study: Resolving a Delayed Refund<\/h2>\n<p>Let\u2019s say a customer reports a wrong charge on their account.<\/p>\n<p>Step 1: Frontline agent receives the complaint. They verify the transaction and determine it\u2019s a billing error.<\/p>\n<p>Step 2: The agent submits a refund request to the back office.<\/p>\n<p>Step 3: The back office team validates the claim, checks policy, and approves or denies.<\/p>\n<p>Step 4: If approved, the refund is processed and notified back to the frontline agent.<\/p>\n<p>Step 5: The agent contacts the customer with the update.<\/p>\n<p>Without clear roles, this model would show \u201csomeone approves the refund.\u201d<\/p>\n<p>With clear roles? You see the delay \u2014 not in the process, but in the handoff.<\/p>\n<p>The back office team is swamped. The customer waits. But now, the bottleneck is visible \u2014 and measurable.<\/p>\n<p>That\u2019s what happens when you model customers and staff in BPMN with intention.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why can\u2019t I just use \u201cCustomer\u201d and \u201cTeam\u201d as lanes?<\/h3>\n<p>Because \u201cTeam\u201d is not a role \u2014 it\u2019s a label. You need to know who\u2019s actually performing the work. If you don\u2019t, handoffs become black boxes, and accountability vanishes.<\/p>\n<h3>Should the customer be in their own pool or in a lane?<\/h3>\n<p>Always in their own pool. It preserves their journey as a first-class participant. If you put them in a lane within a business pool, you risk making them part of the process \u2014 not the driver.<\/p>\n<h3>How do I represent a self-service journey with no frontline staff?<\/h3>\n<p>Still include the customer as a pool. Represent the self-service system as a lane within the customer pool or a separate \u201cDigital Channel\u201d pool. Use message flows to show interactions \u2014 like \u201cuser submits form\u201d \u2192 \u201csystem validates\u201d \u2192 \u201cresponse sent\u201d.<\/p>\n<h3>Can one person hold multiple roles in a BPMN model?<\/h3>\n<p>Yes \u2014 but only if it\u2019s accurate. A call center agent who both receives the call and submits a refund request can be in two lanes. But never label a lane \u201cAgent\u201d and assume it covers everything. Break it down by responsibility.<\/p>\n<h3>What if the back office is outsourced?<\/h3>\n<p>Treat them as an external partner. Use a separate pool with a dashed border. Label clearly: \u201cThird-Party Fraud Reviewer.\u201d This keeps the flow visible and avoids confusion.<\/p>\n<h3>How do I handle roles that change during a journey?<\/h3>\n<p>Use a subprocess or a message flow to show the transition. For example, \u201cCustomer submits form \u2192 Frontline reviews \u2192 Back Office validates.\u201d The role changes \u2014 but the ownership stays traceable.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every journey begins with a person \u2014 and every process is shaped by those who touch it. When I work with teams who say, \u201cWe don\u2019t know who\u2019s doing what,\u201d I start by asking: \u201cWho\u2019s actually responsible for the next step?\u201d That question cuts through the fog. In customer journey BPMN, identifying actors isn&#8217;t just [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1186,"menu_order":2,"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-1189","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>Identifying Actors in Customer Journey BPMN<\/title>\n<meta name=\"description\" content=\"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.\" \/>\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\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Identifying Actors in Customer Journey BPMN\" \/>\n<meta property=\"og:description\" content=\"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/\",\"name\":\"Identifying Actors in Customer Journey BPMN\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:37:22+00:00\",\"description\":\"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Modeling Customer Journeys with BPMN\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Foundations of Customer Journey Thinking\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Identifying Actors: Customers, Frontline Staff, and Back Office\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Identifying Actors in Customer Journey BPMN","description":"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.","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\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/","og_locale":"pl_PL","og_type":"article","og_title":"Identifying Actors in Customer Journey BPMN","og_description":"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"9 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/","name":"Identifying Actors in Customer Journey BPMN","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:37:22+00:00","description":"Learn how to identify and map customers, frontline staff, and back-office actors in BPMN to create clear, customer-centric process models that improve experience and alignment across teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/identifying-actors-in-customer-journey-bpmn\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Modeling Customer Journeys with BPMN","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/"},{"@type":"ListItem","position":3,"name":"Foundations of Customer Journey Thinking","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/modeling-customer-journeys-with-bpmn\/customer-journey-foundations\/"},{"@type":"ListItem","position":4,"name":"Identifying Actors: Customers, Frontline Staff, and Back Office"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1189","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1189\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1186"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1189"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}