Operational base
Validate one priority journey with human control.
Talk to sales- One initial channel
- Knowledge and structured data
- One confirmable operation
- Inbox and human handoff
Implementation plans
Start with what matters. Expand without rebuilding the foundation.
Aipiter is configured around your operation, channels, volume and responsibilities. A generic number would ignore that real complexity.
Teams
Coordinate several processes and owners on one customer record.
Talk to sales- Multiple journeys
- Connected CRM and schedule
- Roles, alerts and assignment
- Operational reporting
Enterprise
Multi-channel deployments, tailored integrations and advanced governance.
Talk to sales- Multi-channel architecture
- Business integrations
- Advanced limits and audit
- Continuity plan
The final scope is documented before purchase. We do not activate channels or integrations before technical and security acceptance.
Frequently asked questions
Clear scope. No guesswork.
Why do the plans say “Talk to sales” instead of showing a price?
Pricing has not yet been published. A proposal depends on the process, channels, expected volume and required integrations. The three levels organise implementation scope; they are not fixed tariffs or offers with already approved commercial terms.
How do Operational base, Teams and Enterprise differ?
Operational base focuses on one priority journey with human control. Teams expands coordination across processes and owners. Enterprise covers multi-channel deployments and tailored integrations. The final proposal is documented; no plan category automatically activates an integration that is still pending.
Which costs should be clarified before signing?
The proposal should distinguish implementation, maintenance, usage and any external provider costs. It should also state what is included and what would require expanded scope. Channel, model or third-party tool fees are not assumed to be included unless agreed.
Can the scope expand later?
Yes. The approach supports adding modules and journeys on a shared foundation. Before a new process is added, its dependencies, permissions, costs and acceptance criteria are reviewed. Expanding scope means more than changing a plan name.