# Make connectivity feel like part of your brand. Bring a mobile service into your app, membership or customer portal. Give people a coherent experience from selecting a plan to managing it, with the commercial proposition and customer relationship shaped around your business. [Explore an embedded launch](/demo?product=esim-embedded) [Create an account for eSIM](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fesim) [Explore the eSIM platform](/products/esim) Your brand, one customer journey FIELDNOTES Data, calls and SMS, connected to your account. Compare coverage and allowance Review the price and terms before checkout. Plan · Usage · Top-ups · Help Keep the service close after the first purchase. Illustrative branded customer experience. No purchase is placed in this preview. ## Make the phone plan feel like it belongs. Start with the moment connectivity helps your customer: opening an account, booking a trip or joining a membership. Put the offer there, carry the customer’s identity into checkout and bring the service back into the account they already know. YOUR APPLICATION ### The customer relationship Your brand, account and product experience BIRD CONNECTIVITY ### The service behind it Offers, orders, installation, usage and subscriber operations ### Keep the customer’s place Return to the same order after an interrupted checkout. Make an unfinished installation easy to resume, and link a support conversation to the service the customer is trying to use. ### Make the integration your own Choose the screens and account actions your product should own. Connect them to the service contracts, while keeping private installation access and billing authority at their existing owners. [Explore the integration model](/products/esim/api) ## Connect the whole purchase experience. Match the presentation of coverage, price, taxes and renewal terms to the plan being sold. Follow the recorded order through fulfillment, then guide the customer to install the profile on the intended device. ### Choose the integration boundary Use a customer journey that fits your app and team: an integrated API experience or a branded hosted flow. Plan the return to your product after checkout and after installation. ### Keep progress visible Show whether payment, provisioning or installation needs attention. A completed checkout is one step in getting connected; the customer should be able to resume where they left off. ## Keep the service useful inside your product. Give subscribers a place to see their plan, usage observations, top-ups and upcoming changes. Connect support to the line and order, so the first purchase becomes a service your business can operate. ### Connect communication to the event Send the installation reminder, allowance update or payment notice when the relevant service event warrants it. Use your customer’s permitted channels and preferences. ### Measure the complete journey Follow selection, purchase, installation and first use as separate steps. Use their recorded outcomes to find friction and connect the original acquisition context to the resulting customer relationship. ## Build with the right reference - [Embedded connectivity guide](/docs/guides/esim/embedded-connectivity): Follow the setup, requirements and operational checks. - [Get started with eSIM](/products/esim/getting-started): Choose an offer and follow a controlled purchase-to-first-use journey. - [Plans and pricing](/products/esim/pricing): Review coverage, allowance, validity and the published terms. ## Embedded connectivity questions ### Is embedded connectivity just an affiliate link? An embedded service can keep the customer journey, branding and plan management within your product. Define the commercial and operating arrangement explicitly; a referral alone does not provide that lifecycle. ### Can we use our own checkout and app? Plan an API integration around your existing experience and payment arrangement. Agree the responsibilities for plan pricing, billing, identity and customer support before implementation. ### Can a hosted journey return customers to our app? Define the entry and return paths as part of your integration. Preserve the customer’s intended action and acquisition context without placing installation credentials in analytics or public URLs. ### What determines the integration effort? The supported markets, plan types, checkout and billing model, identity requirements and the amount of subscriber self-service you own. Prototype the full purchase-to-first-use journey before estimating only the API calls. ## Connect the complete service - [eSIM installation](/products/esim/installation): Help customers install on their device and get connected with clear guidance. - [Mobile plans](/products/esim/mobile-plans): Offer recurring data, calls and SMS with renewals and number portability. - [Connectivity operations](/products/esim/operations): Bring orders, billing, network status and support into one service history. - [eSIM resource library](/products/esim/resources): Browse practical guides, explained answers and technical references. - [Build the integration](/products/esim/api): Connect your application to catalog, purchase, installation and service operations. ## Put the next connection inside your product. Map the offer to your app, account or membership. Agree the purchase, installation, payment and support responsibilities for an embedded launch. [Build your connectivity offering](/demo?product=esim-embedded) [Map your customer journey](/docs/guides/esim/embedded-connectivity) ## Related resources - [eSIM connectivity guide](/docs/guides/esim/overview) (docs) - [What is an eSIM?](/explained/esim/what-is-an-esim) (answer) [Get an implementation brief](/learn/workspace?topic=esim)