{"id":180486,"date":"2026-02-25T15:39:57","date_gmt":"2026-02-25T15:39:57","guid":{"rendered":"https:\/\/sinch.com\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/"},"modified":"2026-03-08T00:54:18","modified_gmt":"2026-03-08T00:54:18","slug":"arquitetura-oculta-jornadas-do-cliente-conectadas","status":"publish","type":"blog","link":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/","title":{"rendered":"A arquitetura oculta por tr\u00e1s das jornadas do cliente conectadas"},"content":{"rendered":"\n<p>AI is often heralded as being the next big thing in customer experience. But as conversation volume increases and brands add more channels, systems that worked for human-to-human interactions begin to struggle, and context can slip between touchpoints along the customer journey. Customers feel this immediately when they\u2019re asked to repeat themselves or when messages arrive without any reflection of what came before. Over time, those moments chip away at trust.<\/p>\n\n<p>What this exposes is something many organizations have underestimated: <strong>That connected customer journeys aren\u2019t sustained by channels alone, and depend on the architecture beneath the conversation.<\/strong> This includes how context is shared across systems, how regional nuance is handled, and whether trust is designed into the foundation as complexity increases.<\/p>\n\n<p>When that foundation is weak, fragmentation reveals itself as a systems problem. Our <a href=\"https:\/\/sinch.com\/pt\/blog\/previsoes-comunicacao-com-o-cliente\/\">Sinch Predictions 2026<\/a> pointed to this challenge directly. What follows is a closer look at why if a business wants to build connected customer journeys, it must first start with the architecture behind them.<\/p>\n\r\n    <nav data-content-type=\"longform\" class=\"toc-block longform-spacings px-5 py-6 px-md-6 px-lg-7 py-md-7 bg-light fs-sm rounded-lg\" aria-labelledby=\"toc-title-3780\"><p class=\"h5 m-0\" id=\"toc-title-3780\">Tabela de conte\u00fado<\/p><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">01<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#when-channel-expansion-exposes-the-cracks\">When channel expansion exposes the cracks<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">02<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#the-limits-of-omnichannel-thinking\">The limits of omnichannel thinking<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">03<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#designing-connection-into-the-system-architecture-before-automation\">Designing connection into the system: Architecture before automation<\/a><a class=\"scrollme link-body-color\" href=\"#build-the-foundation-around-the-customer\">Build the foundation around the customer<\/a><a class=\"scrollme link-body-color\" href=\"#test-whether-continuity-is-happening\">Test whether continuity is happening<\/a><a class=\"scrollme link-body-color\" href=\"#layer-automation-with-orchestration\">Layer automation with orchestration<\/a><a class=\"scrollme link-body-color\" href=\"#what-this-looks-like-in-practice\">What this looks like in practice<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">04<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#global-scale-local-relevance\">Global scale, local relevance<\/a><\/div><\/div><div class=\"d-flex mt-3\"><div class=\"w-auto fw-bold text-accent d-flex me-2\">05<\/div><div class=\"d-flex flex-column\"><a class=\"fw-bold scrollme link-body-color text-accent\" href=\"#connection-is-built-not-broadcast\">Connection is built, not broadcast<\/a><\/div><\/div><\/nav>\n<h2 class=\"wp-block-heading\">When channel expansion exposes the cracks<\/h2>\n\n<p>Many organizations already communicate across email, messaging, voice, and in-app notifications. And customers expect that flexibility: In our <a href=\"https:\/\/sinch.com\/pt\/state-of-customer-communications\/\">S<em>tate of customer communications 2025<\/em><\/a> report, 36% of consumers said they want to receive informational messages on more than one channel, and 58% want to choose their preferred channel when they opt in.<\/p>\n\n<p>The challenge emerges behind the scenes. As the number of channels increase, so does complexity. Ownership can fragment as teams operate in parallel, especially when customer context lives in different systems. This can make conversations restart instead of continuing, not because teams aren\u2019t trying to coordinate, but because the underlying structure was never meant to support them.<\/p>\n\n<p>Stefano Nicoletti of the Mobile Ecosystem Forum (MEF) <a href=\"https:\/\/sinch.com\/webinars\/sinch-predictions-2026\/\">points to this growing complexity<\/a>, especially as businesses layer in AI capabilities.<\/p>\n    <div data-content-type=\"longform\" class=\"quote hub-quote longform-spacings d-flex flex-column rounded-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 shadow-sm bg-sand\" data-theme=\"light\">\r\n\r\n        <div class=\"quote-logo mb-3\">\r\n                            <svg height=\"40\" class=\"quote-icon quote-icon-color\" aria-hidden=\"true\" data-url=\"https:\/\/sinch.com\/wp-content\/plugins\/sinch-core\/assets\/icons\/custom-icons\/quotes-right.svg\"><\/svg>\r\n                    <\/div>\r\n\r\n        <blockquote class=\"quote-content m-0\" id=\"quote-block-a84b1b4834727075fd889ff353315ea1\">\r\n            \u201cIt\u2019s a very complex ecosystem and there isn\u2019t a single rule book. There&#8217;s a set of shared needs to address identity, interoperability, and the governance framework. How does AI operate within your business? How does the AI system interact with the messaging capability? And how do we make the same conversation portable across the various channels?\u201d        <\/blockquote>\r\n\r\n                    <div class=\"d-flex gap-3 mt-5\">\r\n                                    <div>\r\n                        <img decoding=\"async\" width=\"72\" height=\"72\" class=\"rounded-lg quote-author\" src=\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Portrait-Stefano-Nicoletti.png\" alt=\"Foto de Stefano Nicoletti\">\r\n                    <\/div>\r\n                                <div class=\"d-flex flex-column align-self-center fs-sm\">\r\n                    <cite class=\"mb-0 fw-bold text-accent fst-normal\" aria-describedby=\"quote-block-a84b1b4834727075fd889ff353315ea1\">\r\n                        Stefano Nicoletti                    <\/cite>\r\n                                            <span class=\"mb-0 text-body-color\">Mobile Ecosystem Forum (MEF)<\/span>\r\n                                    <\/div>\r\n            <\/div>\r\n            <\/div>\r\n\n<p>Each new channel adds another place where context can break between touchpoints. Customers experience that gap as repetition or irrelevance, even when individual interactions appear to work. And when businesses add AI across those channels, those gaps can become much more visible.<\/p>\n\n<p>An omnichannel strategy was meant to help address this exact problem, but over time, it\u2019s become associated with presence rather than continuity.<\/p>\n\n<h2 class=\"wp-block-heading\">The limits of omnichannel thinking<\/h2>\n\n<p><br \/>For years, \u201c<a href=\"https:\/\/sinch.com\/blog\/omnichannel-customer-journey\/\">omnichannel<\/a>\u201d helped organizations move beyond single-channel thinking and acknowledge that not all customers want to communicate in the same way. Many brands thought if they could show up everywhere its customers were, connection would naturally follow. More channels meant more sophistication.<\/p>\n\n<p>But what that missed is that <strong>visibility on channels and being able to be <em>continuous <\/em>on them aren\u2019t the same thing.<\/strong> Customers expect conversations \u2013 and they expect them no matter which channel they reach out to a brand on. If those conversations fracture, having multiple channels only makes the disconnect more obvious.<\/p>\n\n<p>Our <a href=\"https:\/\/sinch.com\/pt\/state-of-customer-communications\/\"><em>State of customer communications<\/em><\/a><em> <\/em>2025 data puts numbers to that frustration: 81% of consumers have a negative reaction to repeating information during support interactions, yet only 55% of businesses say their communications are fully integrated with their tech stack.<\/p>\n\r\n    \r\n        <div class=\"row hub-data longform-spacings\">\r\n\r\n                            <div class=\"col-6 col-lg-6 my-2\">\r\n                    <div class=\"hub-data-item h-100 p-4 p-md-5 rounded-lg bg-primary\" data-theme=\"light\">\r\n                        <div class=\"h3 counter\">81%<\/div>\r\n                        <div class=\"content-body\">\r\n                            <p>of consumers have a negative reaction to repeating information during support interactions<\/p><p class=\"mb-0\"><br><\/p>                        <\/div>\r\n                                            <\/div>\r\n                <\/div>\r\n\r\n                            <div class=\"col-6 col-lg-6 my-2\">\r\n                    <div class=\"hub-data-item h-100 p-4 p-md-5 rounded-lg bg-primary\" data-theme=\"light\">\r\n                        <div class=\"h3 counter\">55%<\/div>\r\n                        <div class=\"content-body\">\r\n                            <p class=\"mb-0\">of businesses say their communications are fully integrated with their tech stack<\/p>                        <\/div>\r\n                                            <\/div>\r\n                <\/div>\r\n\r\n            \r\n        <\/div>\r\n\r\n\n<p>In reality, this is an orchestration problem. Shared context isn\u2019t enough \u2013 you also need a central layer that interprets intent and routes conversations dynamically. Without that, even thoughtfully designed journeys collapse under real-world conditions.\u00a0The solution?\u00a0<strong>Connection has to be designed into the system itself.<\/strong><\/p>\n\n<h2 class=\"wp-block-heading\">Designing connection into the system: Architecture before automation<\/h2>\n\n<p>Omnichannel expanded where brands show up. Architecture determines whether those conversations actually hold together.<\/p>\n    <div data-content-type=\"longform\"  class=\"callout px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-primary\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> <p class=\"mb-0\">The foundation for designing connected customer journeys includes:<\/p><\/div><ul class=\"mb-0 mt-3\"><li><p>A single source of truth for customer history<\/p><\/li><li><p>Systems that share context across teams<\/p><\/li><li><p>Defined rules for how journeys and handoffs work<\/p><\/li><li><p>Clear reporting on repeated contact and escalation<\/p><\/li><\/ul><div class=\"content-body mt-3\"><p>If these aren\u2019t in place, automation will only scale gaps.<\/p><\/div>\r\n    <\/div>\r\n\n<h3 class=\"wp-block-heading\">Build the foundation around the customer<\/h3>\n\n<p>Designing connection into customer journeys begins by putting the customer and their history at the center of your system.<\/p>\n\n<p>That requires having <strong>one centralized customer profile<\/strong> that holds the same underlying record of their interaction history, preferences, purchase data, open issues, and more. And when teams need context about a customer, they should be pulling from the same source of truth each time. Core systems like a CRM and enterprise resource planning (ERP) software need to be aligned and integrate into a shared communication layer. This will make it so if a customer initiates a return in a web chat, follows up via email, and later speaks to a live agent, the context of their conversation should move with them.<\/p>\n\n<p><strong>Team structure<\/strong> matters here, too. When teams operate in silos, the systems that support them often do the same. Many organizations are responding by shifting toward unified customer experience teams so that accountability aligns around the customer journey rather than departmental lines. This also makes it easier to design and manage continuity across interactions.<\/p>\n\n<p>Connection also requires <strong>shared rules<\/strong>. At a global level, organizations need clarity around how they communicate, what the brand voice represents, how compliance is handled, and more. Regional teams can adapt to local expectations, but they need to first be operating within a defined framework.<\/p>\n\n<h3 class=\"wp-block-heading\">Test whether continuity is happening<\/h3>\n\n<p>After you have a single, centralized customer profile, a unified team structure, and shared rules, you\u2019ll need to check whether continuity is actually happening. This includes signals like:<\/p>\n\n<ul class=\"wp-block-list\">\n<li>How often customers reopen cases on different channels<\/li>\n\n\n\n<li>Whether the same question is being asked multiple times in separate interactions<\/li>\n\n\n\n<li>Where escalation occurs, and why<\/li>\n<\/ul>\n\n<p>If you can\u2019t see those patterns, you won\u2019t be able to fix them. <strong>These considerations set the foundation for building connected customer journeys.<\/strong><\/p>\n\n<h3 class=\"wp-block-heading\">Layer automation with orchestration<\/h3>\n\n<p>Only after this foundation is solid should you expand automation. AI can take on repetitive questions and speed up high-volume interactions, but it won\u2019t fix structural gaps. But if your customer history is centralized and your journeys are unified, AI can become a helpful extension of the system so your human teams can focus on the complex conversations that require judgment and empathy.<\/p>\n\n<p>The same principle applies when you introduce multiple AI agents. Without coordination, you risk recreating the same fragmentation you were trying to eliminate, just in automated form. This is the principle behind conversational AI tools like <a href=\"https:\/\/sinch.com\/pt\/products\/chatlayer\/\">Sinch Chatlayer<\/a>, which help businesses design and manage chatbots and voice bots across channels.<\/p>\n    <div data-content-type=\"longform\" class=\"quote hub-quote longform-spacings d-flex flex-column rounded-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 shadow-sm bg-primary\" data-theme=\"light\">\r\n\r\n        <div class=\"quote-logo mb-3\">\r\n                            <img decoding=\"async\" class=\"quote-logo\" src=\"https:\/\/sinch.com\/wp-content\/uploads\/2024\/06\/logo-sinch.svg\" alt=\"Citar logotipo de Fernando L\u00f3pez Fern\u00e1ndez\">\r\n                    <\/div>\r\n\r\n        <blockquote class=\"quote-content m-0\" id=\"quote-block-a27c2066f5ce7617175841eac049c5dc\">\r\n            &#8220;The biggest mistake brands make is treating AI Agents as standalone chatbots. If you deploy a Sales Agent and a Support Agent without a manager, the customer is the one who has to bridge the gap.\r\nTrue scalability requires an intelligent orchestration layer. Think of it as an invisible &#8216;manager&#8217; that sits above your channels and detects customer intent in real-time, routes them to the right specialized AI agent, and ensures context travels with them. We successfully built this architecture to democratize AI for mid-market businesses, and now we see it as the standard for connected enterprise journeys.&#8221;        <\/blockquote>\r\n\r\n                    <div class=\"d-flex gap-3 mt-5\">\r\n                                    <div>\r\n                        <img decoding=\"async\" width=\"72\" height=\"72\" class=\"rounded-lg quote-author\" src=\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Portarit-Fernando-Lopez-Fernandez.png\" alt=\"Foto de Fernando L\u00f3pez Fern\u00e1ndez\">\r\n                    <\/div>\r\n                                <div class=\"d-flex flex-column align-self-center fs-sm\">\r\n                    <cite class=\"mb-0 fw-bold text-accent fst-normal\" aria-describedby=\"quote-block-a27c2066f5ce7617175841eac049c5dc\">\r\n                        Fernando L\u00f3pez Fern\u00e1ndez                    <\/cite>\r\n                                            <span class=\"mb-0 text-body-color\">Senior Product Manager, Conversational AI at Sinch<\/span>\r\n                                    <\/div>\r\n            <\/div>\r\n            <\/div>\r\n\n<h3 class=\"wp-block-heading\">What this looks like in practice<\/h3>\n\n<p>Connected customer journeys depend on this: Architecture first, shared context and governance second, and automation layered on top. They\u2019re built by putting the customer at the center, aligning teams around it, and then scaling carefully from there. Without that order, scale exposes weaknesses instead of reinforcing connection.<\/p>\n\n<p>If you want a simple way to pressure-test your approach, start here.<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Do<\/strong><\/td><td><strong>Don&#8217;t<\/strong><\/td><\/tr><tr><td><strong>Center your system around a unified customer record. <\/strong>Design your brand&#8217;s communications around the customer journey, not departmental lines.<\/td><td><strong>Don&#8217;t<\/strong> outsource to your customers the job of navigating your organizational and technical silos.<\/td><\/tr><tr><td><strong>Establish a clear governance framework<\/strong> with shared rules for communication and compliance before scaling.<\/td><td><strong>Don&#8217;t<\/strong> assume that adding more channels will automatically create a connected experience.<\/td><\/tr><tr><td><strong>Monitor interaction patterns<\/strong> to identify and fix continuity gaps, like repeated questions or escalations.<\/td><td><strong>Don&#8217;t <\/strong>assume journeys are connected without validating them.<\/td><\/tr><tr><td><strong>Layer automation <\/strong>onto a unified foundation<strong>.<\/strong><\/td><td><strong>Don&#8217;t<\/strong> rely on AI and automation for everything. Aim to automate 80% of your requests and protect the time of your employees to treat the 20% difficult or sensitive ones.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<h2 class=\"wp-block-heading\">Global scale, local relevance<\/h2>\n\n<p>How your systems are structured becomes even more important when you expand into new markets.<\/p>\n\n<p>Again, start with the customer: How do people in that region already communicate? Where do they naturally reach out when they need help?<\/p>\n    <div data-content-type=\"longform\"  class=\"callout px-5 py-6 px-md-6 px-lg-7 py-md-7 longform-spacings rounded-lg bg-primary\" data-theme=\"light\">\r\n\r\n        <div class=\"content-body\"> <p>Expanding into new markets is rarely about copying what already exists and translating it. It\u2019s about adapting to how customers prefer to interact while keeping the underlying architecture behind it connected.<\/p><\/div>\r\n    <\/div>\r\n\n<p>Take Brazil, for example, where <a href=\"https:\/\/sinch.com\/pt\/blog\/apps-de-mensagens-mais-populares-por-pais\/\">WhatsApp is a part of daily life<\/a>. If a brand enters that market and doesn\u2019t offer service on WhatsApp, it can create friction immediately.<\/p>\n\n<p>But moving into a channel like WhatsApp also changes how you design the customer journey. Features like <a href=\"https:\/\/sinch.com\/pt\/blog\/whatsapp-flows\/\">WhatsApp Flows<\/a> can let you guide customers through structured steps directly inside a conversation \u2013 but at the same time, it requires adapting the customer journey to fit the way the channel works.<\/p>\n\n<p>Successful expansion usually comes down to three fundamentals:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><strong>Understand channel preferences.<\/strong> Identify where customers already communicate and meet them there. In Brazil, that might mean WhatsApp \u2013 but in the U.S., it might mean <a href=\"https:\/\/sinch.com\/pt\/blog\/o-que-e-rcs\/\">RCS<\/a> or SMS.<\/li>\n\n\n\n<li><strong>Adapt the tone of voice.<\/strong> A brand\u2019s persona needs to feel natural in that market. That often requires local expertise to ensure style resonates.<\/li>\n\n\n\n<li><strong>Follow local rules and regulations.<\/strong> Data protection laws, opt-in requirements, and messaging rules vary by region.<\/li>\n<\/ul>\n\n<p>As you add markets, complexity increases quickly. Without clear guidelines, it\u2019s easy for teams to build solutions that are disconnected from the broader system. But when local relevance is supported by a connected foundation, conversational automation can scale across regions without losing continuity.<\/p>\n    <div data-content-type=\"longform\" class=\"quote hub-quote longform-spacings d-flex flex-column rounded-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 shadow-sm bg-primary\" data-theme=\"light\">\r\n\r\n        <div class=\"quote-logo mb-3\">\r\n                            <img decoding=\"async\" class=\"quote-logo\" src=\"https:\/\/sinch.com\/wp-content\/uploads\/2024\/06\/logo-sinch.svg\" alt=\"Citar logotipo de Robert Gerstmann\">\r\n                    <\/div>\r\n\r\n        <blockquote class=\"quote-content m-0\" id=\"quote-block-23b0f0549313d1fceb0f6ab65253b1ba\">\r\n            \u201cRegionalized communication strategies will separate global leaders from followers. So the playbook to win in a local market is really intelligent routing. To win globally, you have to master communications locally.\u201d        <\/blockquote>\r\n\r\n                    <div class=\"d-flex gap-3 mt-5\">\r\n                                    <div>\r\n                        <img decoding=\"async\" width=\"72\" height=\"72\" class=\"rounded-lg quote-author\" src=\"https:\/\/sinch.com\/wp-content\/uploads\/2024\/09\/Robert-Gerstmann.jpeg\" alt=\"Foto de Robert Gerstmann\">\r\n                    <\/div>\r\n                                <div class=\"d-flex flex-column align-self-center fs-sm\">\r\n                    <cite class=\"mb-0 fw-bold text-accent fst-normal\" aria-describedby=\"quote-block-23b0f0549313d1fceb0f6ab65253b1ba\">\r\n                        Robert Gerstmann                    <\/cite>\r\n                                            <span class=\"mb-0 text-body-color\">Chief Evangelist and Co-Founder, Sinch<\/span>\r\n                                    <\/div>\r\n            <\/div>\r\n            <\/div>\r\n\n<h2 class=\"wp-block-heading\">Connection is built, not broadcast<\/h2>\n\n<p>Connected customer journeys are often framed as a user experience problem. But in reality, they\u2019re usually built, or broken, by the systems underneath them.<\/p>\n\n<p>Adding more channels doesn&#8217;t necessarily create connection. Instead, it typically increases the number of places where context can be lost. Similarly, adding AI doesn&#8217;t create cohesion, but accelerates whatever structure already exists.<\/p>\n\n<p>If customer history lives in separate systems, if teams operate in parallel, or if regions build their own disconnected flows, expansion will expose those gaps quickly. More reach simply multiplies the problems.<\/p>\n\n<p>Connected journeys hold together when the foundation is deliberate: a shared customer record, aligned ownership across the full lifecycle, clear global guardrails, and thoughtful local adaptation. Only then can automation enhance the experience rather than strain it.<\/p>\n\n<p><strong>Connection is an architectural decision. <\/strong>Get that right, and scale strengthens the system. Get it wrong, and scale reveals every weakness.<\/p>\n\n<p>This is the reality we see every day working with organizations navigating global, multi-channel communication. Platforms built for that complexity have to solve for orchestration first. Without centralized context and shared governance, no amount of channel reach delivers continuity.<\/p>\n\n<p>If you&#8217;re rethinking how your organization scales connected customer journeys, watch Sinch\u2019s on-demand webinar, <a href=\"https:\/\/sinch.com\/webinars\/sinch-predictions-2026\/\"><em>What\u2019s in the cards for customer communications?<\/em><\/a>, to hear directly from industry leaders on how they&#8217;re preparing their teams for what comes next.<\/p>\n\r\n    <aside data-content-type=\"longform\"  class=\"banner-block longform-spacings rounded-lg shadow-lg px-5 py-6 px-md-6 py-md-7 p-lg-7 bg-light-subtle\" data-theme=\"dark\" aria-labelledby=\"banner-block-block_86b451cfde749d66ec7a1b27b3a0d001\">\r\n                    <p class=\"text-uppercase section-caption text-body-color\">\r\n                Why Sinch?            <\/p>\r\n                            <p class=\"h4 text-accent fw-bold\" id=\"banner-block-block_86b451cfde749d66ec7a1b27b3a0d001\">\r\n                Global customer communications, without the complexity.            <\/p>\r\n                            <div class=\"mb-0 text-body-color\">\r\n                                    <div class=\"content-body mb-0 text-body-color\"><p class=\"mb-0\">Sinch, the Customer Communications Cloud, powers meaningful conversations at scale across messaging, voice, and email. With direct operator connections and true global reach, you can deliver value at every step of the customer journey.<\/p><\/div>\r\n                            <\/div>\r\n        \r\n        <div class=\"text-start mt-5\"><a href=\"https:\/\/sinch.com\/pt\/por-que-a-sinch\/\"  class=\"btn btn-secondary\" >Explore the Customer Communications Cloud<\/a><\/div>\r\n    <\/aside>\r\n\r\n","protected":false},"author":85,"featured_media":180001,"menu_order":0,"template":"","meta":{"_acf_changed":false,"footnotes":""},"tags":[],"blog_category":[303],"class_list":["post-180486","blog","type-blog","status-publish","has-post-thumbnail","hentry","blog_category-insights-pt"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>The Architecture Behind Connected Customer Journeys - Sinch<\/title>\n<meta name=\"description\" content=\"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/\" \/>\n<meta property=\"og:locale\" content=\"pt_BR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Architecture Behind Connected Customer Journeys - Sinch\" \/>\n<meta property=\"og:description\" content=\"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/\" \/>\n<meta property=\"og:site_name\" content=\"Sinch\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/wearesinch\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-08T00:54:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"766\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@WeAreSinch\" \/>\n<meta name=\"twitter:label1\" content=\"Est. tempo de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/\",\"url\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/\",\"name\":\"The Architecture Behind Connected Customer Journeys - Sinch\",\"isPartOf\":{\"@id\":\"https:\/\/sinch.com\/pt\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png\",\"datePublished\":\"2026-02-25T15:39:57+00:00\",\"dateModified\":\"2026-03-08T00:54:18+00:00\",\"description\":\"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.\",\"breadcrumb\":{\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#breadcrumb\"},\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage\",\"url\":\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png\",\"contentUrl\":\"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png\",\"width\":1200,\"height\":766},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sinch.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Blog\",\"item\":\"https:\/\/sinch.com\/pt\/blog\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"A arquitetura oculta por tr\u00e1s das jornadas do cliente conectadas\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sinch.com\/pt\/#website\",\"url\":\"https:\/\/sinch.com\/pt\/\",\"name\":\"Sinch\",\"description\":\"SMS Messaging, Voice, Email, Video &amp; Verification APIs | Sinch\",\"publisher\":{\"@id\":\"https:\/\/sinch.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sinch.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-BR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/sinch.com\/pt\/#organization\",\"name\":\"Sinch\",\"url\":\"https:\/\/sinch.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\/\/sinch.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/sinch.com\/wp-content\/uploads\/2024\/09\/Thumbnail-Logo-Honey.png\",\"contentUrl\":\"https:\/\/sinch.com\/wp-content\/uploads\/2024\/09\/Thumbnail-Logo-Honey.png\",\"width\":800,\"height\":496,\"caption\":\"Sinch\"},\"image\":{\"@id\":\"https:\/\/sinch.com\/pt\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/wearesinch\/\",\"https:\/\/x.com\/WeAreSinch\",\"https:\/\/www.linkedin.com\/company\/sinch\",\"https:\/\/www.youtube.com\/channel\/UCZZ2u_B2afTxA0v-xcgfsaw\",\"https:\/\/www.instagram.com\/wearesinch\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The Architecture Behind Connected Customer Journeys - Sinch","description":"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.","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:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/","og_locale":"pt_BR","og_type":"article","og_title":"The Architecture Behind Connected Customer Journeys - Sinch","og_description":"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.","og_url":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/","og_site_name":"Sinch","article_publisher":"https:\/\/www.facebook.com\/wearesinch\/","article_modified_time":"2026-03-08T00:54:18+00:00","og_image":[{"width":1200,"height":766,"url":"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_site":"@WeAreSinch","twitter_misc":{"Est. tempo de leitura":"8 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/","url":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/","name":"The Architecture Behind Connected Customer Journeys - Sinch","isPartOf":{"@id":"https:\/\/sinch.com\/pt\/#website"},"primaryImageOfPage":{"@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage"},"image":{"@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage"},"thumbnailUrl":"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png","datePublished":"2026-02-25T15:39:57+00:00","dateModified":"2026-03-08T00:54:18+00:00","description":"Why connected customer journeys break at scale and how architecture, governance, and shared context create continuity across channels and markets.","breadcrumb":{"@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#breadcrumb"},"inLanguage":"pt-BR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/"]}]},{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#primaryimage","url":"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png","contentUrl":"https:\/\/sinch.com\/wp-content\/uploads\/2026\/02\/SI-Blog-2026-Predictions-Hidden-Architechture-Connected-Customer-Journeys.png","width":1200,"height":766},{"@type":"BreadcrumbList","@id":"https:\/\/sinch.com\/pt\/blog\/arquitetura-oculta-jornadas-do-cliente-conectadas\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sinch.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https:\/\/sinch.com\/pt\/blog\/"},{"@type":"ListItem","position":3,"name":"A arquitetura oculta por tr\u00e1s das jornadas do cliente conectadas"}]},{"@type":"WebSite","@id":"https:\/\/sinch.com\/pt\/#website","url":"https:\/\/sinch.com\/pt\/","name":"Sinch","description":"SMS Messaging, Voice, Email, Video &amp; Verification APIs | Sinch","publisher":{"@id":"https:\/\/sinch.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sinch.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-BR"},{"@type":"Organization","@id":"https:\/\/sinch.com\/pt\/#organization","name":"Sinch","url":"https:\/\/sinch.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/sinch.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/sinch.com\/wp-content\/uploads\/2024\/09\/Thumbnail-Logo-Honey.png","contentUrl":"https:\/\/sinch.com\/wp-content\/uploads\/2024\/09\/Thumbnail-Logo-Honey.png","width":800,"height":496,"caption":"Sinch"},"image":{"@id":"https:\/\/sinch.com\/pt\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/wearesinch\/","https:\/\/x.com\/WeAreSinch","https:\/\/www.linkedin.com\/company\/sinch","https:\/\/www.youtube.com\/channel\/UCZZ2u_B2afTxA0v-xcgfsaw","https:\/\/www.instagram.com\/wearesinch\/"]}]}},"_links":{"self":[{"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/blog\/180486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/users\/85"}],"version-history":[{"count":3,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/blog\/180486\/revisions"}],"predecessor-version":[{"id":180874,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/blog\/180486\/revisions\/180874"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/media\/180001"}],"wp:attachment":[{"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/media?parent=180486"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/tags?post=180486"},{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/sinch.com\/pt\/wp-json\/wp\/v2\/blog_category?post=180486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}