Make connectivity part of the customer journey.
eSIM Copilot for Salesforce is now in early access. It lets teams add mobile connectivity to the moments Salesforce already helps manage: trips, events, onboarding, offboarding, and life changes.
Connectivity is rarely the headline of a customer journey. The headline is the thing a person is trying to do: arrive at an event, start a new role, move abroad, onboard as a partner, activate a connected product, or get help from support when their existing connection is broken.
Salesforce is already where many of those moments are understood. It knows who the person is, what stage they are in, which team owns the relationship, and what should happen next. That makes it a natural place for connectivity to become part of the experience, not a separate add-on that someone has to remember later.
What changes
eSIM Copilot brings mobile activation and management into Salesforce so an authorised team can connect someone at the moment the need is known. The customer does not experience connectivity as another product to chase. The team does not experience it as another portal to reconcile.
The useful part is the fit. Search the right plan, activate it, send the install link, see whether it was installed, check usage, support the person, and stop access when the journey ends. The mobile plan follows the customer context.
The moments that matter
The strongest use cases are not abstract telecom workflows. They are ordinary business and life moments where being connected changes the quality of the experience.
Events and trips
Confirmed attendees, travelling customers, brand ambassadors, or field teams can receive connectivity before they arrive instead of hunting for Wi-Fi on site.
Campaign journeys
A campaign can include connectivity as a useful next step, especially when the customer experience depends on an app, a QR code, a venue, or a destination.
Onboarding
New customers, partners, staff, contractors, or distributors can be connected as part of the same welcome journey that introduces the service.
Offboarding
When someone leaves a programme, role, project, or partner relationship, mobile access can be stopped as part of the same closing journey.
Life moments
Moving abroad, studying overseas, relocating for work, or joining a premium service can include connectivity from day one instead of a separate support exchange.
Support
When someone says they cannot get online, support can see install state, usage, plan status, and the history of what has already been sent.
Why Salesforce is the right place
Salesforce has the context that mobile providers usually lack: the relationship, the consent, the segment, the owner, the service case, the trip, the campaign, the onboarding state, the renewal risk, and the next best action. Connectivity becomes more useful when it is attached to that context.
That is the important shift. The question is not "can this person buy an eSIM?" The better question is "at this point in the journey, should this person already be connected?"
Better journey questions
What early access should prove
The first rollout should answer one business question: does adding connectivity inside Salesforce make this journey measurably better? That is more useful than testing every possible telecom feature on day one.
Choose a journey with a promise.
Pick a moment where being connected is part of the customer promise: ready before the trip, online at the event, connected on move-in day, or equipped before work starts.
Define the trigger and owner.
Decide what should cause connectivity to appear, who is allowed to activate it, what the customer sees, and when access should stop.
Track the thing that used to break.
Measure the old pain directly: people arriving offline, support chasing install status, manual fulfilment emails, unused plans, or access that stayed live too long.
Early access
Want to make connectivity part of your Salesforce journeys?
We are opening the Salesforce integration with selected customers. Tell us which customer moment you want to improve first and we will help map the right activation, usage, support, and access-control path.