Failure PatternDecision layer

Why Agencies Fail With Alhena in Multi-Client Retainers

Symptom: Client invoices spike unexpectedly when conversation volumes cross plan limits, turning a fixed retainer into a variable cost that erodes margin. Root cause: Alhena's pricing is conversation-based (e.g., 200 conversations/mo on Essentials at $199/yr, up to 1,200/mo on Scale at $999/yr), so agencies that don't forecast per-client volume face unpredictable overage costs.

By InnovaAI ResearchPublished Updated

How do you recognize it?
  • Client invoices spike unexpectedly when conversation volumes cross plan limits, turning a fixed retainer into a variable cost that erodes margin.
  • Support teams report that the AI concierge gives outdated or incorrect product answers because the knowledge base wasn't refreshed after catalog changes.
  • Agency dashboards show low adoption of the shopping assistant module, with clients only using the support concierge and ignoring upsell features.
  • Clients complain about inconsistent brand tone in AI responses, especially when multiple AI profiles are configured without centralized governance.
  • Renewal conversations stall because the agency cannot clearly tie Alhena's conversation analytics to revenue or CSAT improvements.
Why does it happen?
  • Alhena's pricing is conversation-based (e.g., 200 conversations/mo on Essentials at $199/yr, up to 1,200/mo on Scale at $999/yr), so agencies that don't forecast per-client volume face unpredictable overage costs.
  • The platform's multi-product architecture (shopping assistant, support concierge, voice AI) tempts agencies to bundle everything into one retainer, but clients often only need one module, leading to wasted spend and misaligned expectations.
  • Alhena's AI training relies on client-specific knowledge bases and product catalogs; if agencies don't establish a refresh cadence, the AI degrades as inventory and policies change.
  • With up to 5 AI profiles on Essentials, agencies can easily create conflicting configurations across client sub-brands or regions without a shared prompt or tone guideline.
How do you fix it?
  • Audit each client's monthly conversation usage in the Alhena dashboard and set up alerts at 80% of plan limits to avoid overage surprises.
  • Create a standard operating procedure for updating client knowledge bases and product SKUs in Alhena after every catalog change, and assign a dedicated owner.
  • Review the AI Visibility audit report to identify which modules are actually driving value, then re-scope retainers to drop unused features.
  • Centralize AI profile management by defining brand tone templates and enforcing them across all client profiles in the Alhena admin panel.