Skip to content

CRM Suite pricing

Customer Support

Choose a tier, compare scope, then configure the plan for your rollout.

Standalone plans for Customer Support

Revenue team reviewing commercial work before customer commitment.
Customer Support starts with people trying to make the right call. It starts with a person trying to get customer support work done without losing context. They need the next action to be clear, but they also need confidence that the platform has checked the risk, evidence, permissions and downstream impact.

Plan fit

Understand the commercial shape before choosing a tier

Standalone plans for Customer Support

Flexible pricing

Choose your plan

Select a starting tier and configure users, billing and commercial details on the quote page.

Starter

Core app capability.

$35
user/month

What's included:

  • Customer Support

Usage limits:

StarterEntry volume / limited features
BusinessRecommended volume / operational features
EnterpriseEnterprise volume / governance and support review

Plan details:

Base package1 user included
Base amount$35/month
Additional user$35 per user/month
Payment termsMonthly prepaid
Billing modeluser/month
RolloutAvailable as part of a phased rollout
Configure plan

Enterprise

Advanced controls, integrations, and support.

$119
user/month

What's included:

  • Customer Support

Usage limits:

StarterEntry volume / limited features
BusinessRecommended volume / operational features
EnterpriseEnterprise volume / governance and support review

Plan details:

Base package15 users included
Base amount$1,785/month
Additional user$119 per user/month
Payment termsMonthly prepaid
Billing modeluser/month
RolloutAvailable as part of a phased rollout
Configure plan
Revenue team reviewing commercial work before customer commitment.
Where Customer Support becomes real work people can trust. The person is no longer carrying the full burden alone. Agents assemble context, route specialist checks, pause when judgement is required and record what happened so Customer Support work feels calmer, faster and accountable.

Compare plans

Compare Plans

Detailed scope comparison to help you choose the right plan.

Capability StarterBusinessEnterprise
Commercial scope
Monthly price $35$119
Annual prepaid equivalent $30/mo equiv.$102/mo equiv.
Billing basis user/monthuser/month
Base included 1 user included15 users included
Included apps 11
User scale IncludedIncluded
Storage IncludedIncluded
Integrations IncludedIncluded
Support IncludedIncluded
Billing options annual-prepaid, monthly-prepaidannual-prepaid, monthly-prepaid
Recommended NoNo

Included apps

Apps in this Plan

The plan is composed from Advanze product capabilities, so teams can adopt a focused plan without creating another silo.

Customer Support

Included capability in this plan.

Related products

Explore related pricing paths

Compare adjacent products and suites in the same pricing group.

Why this pricing path matters

Customer Support pricing should be understood through the work it helps govern.

It starts with a person trying to get customer support work done without losing context. They need the next action to be clear, but they also need confidence that the platform has checked the risk, evidence, permissions and downstream impact.

What makes it harder in the real world: Customer support work looks straightforward until it crosses people, systems, policies, approvals and customer impact. In practice, the work may require the right customer or employee context, policy checks, data quality, approvals, exception routing, integration updates and a clear audit trail.

What Advanze changes: Customer Support turns customer support activity into governed execution by connecting lead, opportunity, customer, campaign and service context to agents, workflow, permissions, approvals and audit evidence before work is completed.

Customer Support Intake AgentClassifies new customer support work, identifies intent, urgency, context requirements and the likely execution path.
Customer Support Context AgentGathers related records, history, documents, messages, policies, metrics and system state needed for customer support decisions.
Customer Support Processing AgentPrepares the recommended action, draft update, workflow step or system change for customer support work.
Guardrail AgentChecks permissions, policy thresholds, sensitive data, financial exposure, compliance implications and approval requirements.
Workflow Orchestration AgentRoutes reviews, manages approvals, records evidence and coordinates safe system updates after approval.
Challenge

Customer Support starts as a single app experience, but the real work usually depends on context from other teams, policies, data and systems.

Orchestration

Advanze treats Customer Support as part of a governed execution fabric. The app captures the work, agents gather context, workflow routes approvals and the control model determines what can safely happen next.

Success

Customer Support becomes more than a screen. It becomes a reliable path from intent to controlled action, with people still responsible for judgement and the platform carrying evidence.

Revenue team reviewing commercial work before customer commitment.
Commercial review 16Revenue teams aligning customer, proposal, commercial and delivery context before action.
Revenue team reviewing commercial work before customer commitment.
Commercial review 1Revenue teams aligning customer, proposal, commercial and delivery context before action.
Revenue team reviewing commercial work before customer commitment.
Commercial review 2Revenue teams aligning customer, proposal, commercial and delivery context before action.

Control model

Useful AI execution needs pricing, permissions and governance to move together.

Customer Support is valuable when it participates in the Advanze control model: identity, permissions, workflow, policy checks, data context, audit evidence and human approval boundaries sit inside the execution path.

  • Customer Support work needs the right lead, opportunity, customer, campaign and service context before an agent or user can act with confidence.
  • The process often crosses handoffs, approvals, exception paths, SLAs and downstream system updates.
  • Different actions need different permission levels: read, draft, update, approve, send, pay, create, close or escalate.
  • The business needs evidence of what was requested, what was checked, who approved, what changed and why.
Revenue team reviewing commercial work before customer commitment.
The outcome is not just automation. It is confidence in what happens next. The person is no longer carrying the full burden alone. Agents assemble context, route specialist checks, pause when judgement is required and record what happened so Customer Support work feels calmer, faster and accountable.

Next step

Review another pricing path or involve sales

Go back to pricing categories when you want to compare alternatives, or contact sales to combine this plan with other suites, services and enterprise controls.