Raw, Capped AI Agent Pricing: Why Embage Avoids Per-Session Flat Fees

Most AI chatbot vendors make pricing appear deceptively simple by charging flat per-session or per-conversation fees. At first glance, a "$0.50 per chat" price tag sounds straightforward. In practice, per-session pricing is a trap that penalizes businesses for basic customer inquiries while creating unpredictable monthly bills.

Embage takes a fundamentally different approach. We do not bill chat as a single flat session. Instead, chat-based sessions are priced per AI credits (200 credits on Starter, 800 on Pro, and 2,000 on MAX), while voice-based sessions are priced per session with dedicated monthly minute pools.

---

The Flaw in Flat Per-Session Chat Pricing

Per-session pricing obscures the true infrastructure cost of an AI interaction. Consider two completely different website visitors:

1. Visitor A (Simple FAQ): Asks "What are your store hours?" The agent answers in a sentence.
2. Visitor B (Complex support): A 20-message troubleshooting session that searches your docs, checks an order, creates a support ticket, and sends a Gmail follow-up.

Under flat per-session pricing, your business pays the exact same high rate for both interactions. The tiny FAQ question subsidizes the complex enterprise workflow. Worse still, if a bot or viral surge triggers thousands of simple 1-message chats, your monthly bill explodes unexpectedly.

---

How Embage Pricing Works: AI Credits for Chat + Per-Session Voice

Embage decouples conversation handling into transparent, measurable operational components:

+-----------------------------------------------------------------------+
|                      Embage Monthly Operating Envelope                |
+-----------------------------------------------------------------------+
  |
  +--> 1. AI Credits Pool (200 Starter / 800 Pro / 2,000 MAX for chat)
  |
  +--> 2. Voice Sessions & Minutes (talk-time on voice calls)
  |
  +--> 3. Knowledge Base Search Cap (lookups in your docs)
  |
  +--> 4. AI Form Write Cap (CRM lead, ticket, feedback, & review logs)
  |
  +--> 5. Integration Call Cap (3rd-party SaaS execution)

1. AI Credits for Chat-Based Sessions

Covering the intelligence behind chat replies (200 on Starter, 800 on Pro, 2,000 on MAX). A simple FAQ uses a tiny slice of a credit instead of a full session fee.

2. Knowledge Base Search Quota

A search counts only when the agent looks something up in your uploaded PDFs, docs, or website content. A simple greeting does not use this quota.

3. AI Form Write Quota

A write counts only when the agent saves a structured record into your AI Forms — like a support ticket, qualified lead, review, or piece of feedback.

4. Integration Call Quota

A call counts when the agent does something in an app you connected, such as Gmail, Slack, Google Calendar, HubSpot, Salesforce, or Shopify.

5. Voice-to-Voice Minute Allotments

Voice calls use a monthly minute pool. Searches, AI Form writes, and app actions during a call still count against the same action caps.

---

A Side-by-Side Comparison

Let's compare how two interactions are billed in Embage:

Interaction Type	Actions Triggered	Embage Billing Impact
Simple FAQ Chat "Are you open on weekends?"	• None	• Uses a small amount of AI credits. • 0 action caps used.
Full Support Workflow "I was double billed on invoice #8812"	• 1 Knowledge Search • 1 AI Form Ticket Write • 1 Gmail Integration Call	• Uses AI credits for the replies. • 1 Knowledge Search. • 1 AI Form write. • 1 Integration call.

---

Why Hard Monthly Caps Protect Your Business

In Embage, limits are hard monthly caps, not hidden overage penalties.

If you hit a monthly cap — for example, integration calls — that action pauses until the next billing cycle or an upgrade. The agent can still answer questions from your Knowledge Base and use any remaining actions.

This design guarantees two major operational benefits:

1. Predictable Expenses: No surprise $5,000 credit card bills from unexpected traffic spikes.
2. Value-Aligned Billing: You only pay for high-value business outcomes (leads captured, tickets logged, emails sent) rather than idle chit-chat.

---

Further Reading

• Explore Embage Platform Features — Knowledge base, AI Forms, sub-agents, and integrations.
• AI Agent Orchestration for Customer Support — How sub-agents minimize token usage.
• Gmail AI Agent Workflows — Automated follow-up setup guide.
• Shopify AI Agent Product Lookup — E-commerce support automation.