How to Build a Custom AI Customer Support Agent in Embage: Step-by-Step Guide
A complete walkthrough on creating a customer support AI receptionist: building knowledge bases, datastores, sub-agents, integrations, and database isolation.
Deploying an AI customer support receptionist used to require complex backend coding, managing custom state machines, and manually stitching together APIs.
Embage changes all of that. With Embage's no-code agent builder, you can construct, configure, test, and deploy a production-ready AI voice and chat agent in minutes.
This guide walks you through building a fully working customer support agent from scratch inside the Embage dashboard.
![Embage AI Agent Builder Dashboard Overview]
Why Enterprise Database Isolation Matters
Before building your agent, it is essential to understand how Embage protects your business and customer data.
Most generic AI chatbot platforms store all customer records and chat logs inside a single, shared multi-tenant database. This creates a risk of cross-tenant data leakage or prompt injection attacks exposing private company data.
Embage enforces strict Database Isolation.
Every organization on Embage receives its own completely isolated database vault. Your knowledge base documents, customer support tickets, and chat transcripts live in a dedicated environment. There is no technical path for one company's data to appear in another organization's agent response. You get enterprise-grade data privacy out of the box without having to manage or configure any database infrastructure.
Step-by-Step: How to Build a Working Support Agent
Here is the exact 6-step workflow to build an automated AI support agent in Embage:
For a detailed breakdown of platform capabilities, explore our Platform Features, read about Real-World Use Cases, or see how we compare in our Platform Comparison.
Step 1: Create the Primary Agent (/app/agents/add)
The Primary Agent acts as the conversational "brain". It handles real-time Voice-to-Voice audio streams and Web Chat interactions, maintaining the conversation context and evaluating when specialized help is needed.
![Step 1: Create Primary Agent]
- Go to Agents (
/app/agents) and click Add New Agent. - Select the Customer Support use case preset to pre-fill optimal tone and safety constraints.
- Configure your agent's persona, welcome message, and response constraints (e.g. "Empathetic tone, clear instructions, no unverified discount promises").
- Choose your preferred AI model size (e.g., Gemini Flash) for sub-second voice and chat response speed.
Step 2: Upload Your Knowledge Base (/app/kb)
An AI support agent must answer from verified facts rather than general training guesses. The Knowledge Base gives your agent instant access to your company's official documentation.
![Step 2: Upload Knowledge Base]
- Navigate to Knowledge Base (
/app/kb) in the sidebar. - Upload your product manuals, FAQ PDFs, policy documents, or website URLs.
- Embage automatically vectorizes and indexes your files. Whenever policies change, simply update your Knowledge Base documents — your agent instantly reflects the changes across all channels with zero retraining.
Step 3: Create a CRM Datastore (/app/datastore)
Every resolved or escalated support interaction should leave structured business data behind. CRM Datastores allow your agent to log support tickets, leads, feedback, or product bug reports automatically.
![Step 3: Create CRM Datastore]
- Navigate to Datastores (
/app/datastore) and click Create Datastore. - Define your desired schema fields (for example, a Support Tickets store with fields:
ticket_id,customer_email,category,urgency, andissue_summary). - Save the datastore schema. Your agent will now be able to populate these fields automatically during or after customer chats.
Step 4: Add Third-Party Integrations (/app/integrations)
Extend your agent's capabilities by connecting it to your existing software stack.
![Step 4: Connect Integrations]
- Go to the Integrations library (
/app/integrations). - Choose from popular platforms including Gmail, Shopify, Slack, Zendesk, HubSpot, or Salesforce.
- Click Connect to complete 1-click OAuth authorization safely.
Step 5: Build Specialized Sub-Agents (/app/subagent)
In Embage, specialized tasks are delegated to Sub-Agents ("the hands"). Sub-agents keep prompt sizes small, token costs low, and execution accurate.
![Step 5: Create Sub-Agents and Tools]
- Navigate to Sub-Agents (
/app/subagent) and click New Sub-Agent. - Give your sub-agent a specific role (e.g., Knowledge Searcher, Ticket Creator, or Gmail Email Sender).
- Open the Tools dialog and attach targeted tools:
knowledge_base: For retrieving document answers.add_to_datastore: For writing records to your CRM datastore.integration_3p: For executing actions in connected tools like Gmail or Shopify.
- Select the execution mode: General Worker (for live mid-chat calls) or Post-Conversation Workflow (triggers automatically upon session end).
Step 6: Connect Sub-Agents to Your Main Agent Using Skills
The final step is binding your specialized sub-agents to your primary agent as active Skills.
- Return to your Primary Agent settings or step 4 of the Agent Builder (Agent Capabilities & Skills).
- Under Active Agent Skills, select your created Sub-Agents and expose their tools as skills (e.g., "Search Knowledge Base", "Create Support Ticket", "Send Gmail Follow-up").
- Save your agent configuration.
Your customer support agent is now fully live and operational!
Conclusion
Building a production-ready AI customer support receptionist doesn't require weeks of backend engineering. With Embage's modular architecture:
- Primary Agents govern conversation.
- Knowledge Bases provide grounded facts.
- CRM Datastores capture structured business records.
- Integrations & Sub-Agents execute third-party workflows.
- Database Isolation protects your data privacy.
Ready to automate customer support? Start building on Embage Platform today.