01
Which modules you deploy
Mira Reach, Engage, Growth and Core can be scoped around the Customer Lifecycle capabilities your organization needs. Not every deployment needs to begin with every module.
How a Mira deployment works
Mira is one agent platform for the entire Customer Lifecycle, delivered as a deployment shaped around your organization. We define where Mira connects, what it operates, and where governance, approval and human oversight apply across Acquire, Engage, Retain and Grow.
[ What drives scope ]
Four things shape a Mira deployment
Every organization operates its Customer Lifecycle differently. Scope reflects the systems, channels, workflows and volume required to connect Mira to yours.
02
Which systems we connect
Each system Mira connects to becomes part of how agents gather context and execute actions. The number and complexity of those connections are a primary driver of scope.
03
How many channels go live
Each channel has its own requirements, formats and workflows. Scope reflects where your customer relationships happen and which channels Mira needs to operate across.
04
What volume runs through it
Customer volume and the level of activity across your Customer Lifecycle determine the infrastructure and capacity required for your deployment.
[ The path ]
Two phases from platform to connected execution
We separate deployment into two phases because establishing Mira inside your environment and connecting it to your organization involve different requirements.
Scoping conversation
We start by understanding how your Customer Lifecycle operates today, where relationships live, which systems and channels are involved, and where autonomous execution can create the most value.
Phase one, the platform
Mira is deployed inside your environment with the foundation required to run securely under your organization's control.
Phase two, the connections
Mira is connected to the data, systems, workflows and channels required to acquire, engage, retain and grow customer relationships. This is where the deployment is shaped around how your organization actually operates.
Production, with control from the start
Autonomy begins within the boundaries your organization defines. Those boundaries can evolve as workflows are validated and your organization becomes comfortable expanding autonomous execution.
[ Where it runs ]
Inside your infrastructure, from the first day
Mira is deployed inside your organization's environment, keeping customer data and deployment specific context under your control. No usage data or telemetry returns to Here AI. You hold the encryption keys, and your data is not used to train a shared Here AI model serving other customers. These principles apply from deployment through production.
The next step is a scoping conversation
Tell us how your Customer Lifecycle operates today and where you want to begin. Together, we define how Mira connects to your organization and what it takes to bring Acquire, Engage, Retain and Grow into one agent platform.