> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/wprowadzenie/obslugiwane-kanaly.md). # Supported channels ## Application launch channels and contexts The Eximee platform was designed with flexible handling of processes in various customer and bank employee contact channels in mind. As a result, applications created on the platform can operate consistently across the entire banking environment - regardless of where they are launched. ### Technical channels A technical channel defines the environment in which the front-end part of the application is launched - e.g. a form, a task screen, or a customer panel view. It is the technical channel that determines how the application is embedded and displayed to the user. Typical technical channels are: * **online banking** (desktop), * **mobile app**, * **CRM system or internal employee portal**, * **partner channel** (e.g. external agent), * **public bank portal** (for unauthenticated customers). Thanks to component unification and visual adaptation to the hosting channel, Eximee provides a consistent user experience across all these environments. ### Business contexts (business channels) In addition to the technical channel, the application always operates within a specific business context. This context includes: * **user identity and role** (e.g. customer, advisor, partner), * **operating conditions** (logged in/not logged in, acting with customer or own permissions), * **scope of available data and functions**. The combination of the technical channel and the operating context creates the so-called **business channel**. Examples of business channels: * an individual customer logged in to online banking, * bank employee in CRM handling an application on behalf of a customer, * a customer filling out a form on the bank's public website (without logging in), * a user authorizing an instruction in the mobile app, * an external partner initiating a process on behalf of a customer. Defining business channels allows for precise control of logic, permissions, component visibility, and data available within the process - depending on the situation in which the application is launched. ### Multichannel and omnichannel It is worth distinguishing between two approaches to designing applications across multiple channels: * **Multichannel** (multichannel):\ The same form or process is available in multiple technical channels - e.g. a mobile app and online banking - but operates independently in each of them. The user must complete the case in the same channel in which it was started. * **Omnichannel** (omnichannel):\ The application enables the continuation of the same process across different channels and contexts. A customer can start an application in online banking, finish it in the mobile app, and finally approve it together with an advisor in the branch - all within the same case, while preserving full context and history. Eximee supports both approaches, and the platform architecture and central data repository enable effective implementation of omnichannel solutions - with synchronization of progress, tasks, and information between channels. ### Summary By distinguishing between technical and business channels, the Eximee platform allows you to create flexible, contextual, and consistent banking applications operating across the institution's entire ecosystem. Application designers can precisely control application behavior in different environments and adapt it to the role and needs of the end user. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/wprowadzenie/obslugiwane-kanaly.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.