What is an Agent?

An Agent in Eloquent is the core unit of intelligence: a flexible, AI-driven building block that can be configured to perform tasks, interact with users, or automate processes.

Unlike simple chatbots, agents are multi-purpose, brandable, and deployable across different environments.

Why Agents matter

Most businesses struggle with AI adoption because they face a tradeoff: either use an external AI tool (and lose control of their client relationship), or build something custom (which is slow, expensive, and hard to maintain).

Eloquent agents solve this by being:

• Reusable – build once, deploy many times.
• Brand-first – always run under your logo, domain, and pricing.
• Flexible – support a wide range of interfaces and workflows.
• Scalable – optimized for production, not just experiments.

Where Agents live

An agent is not tied to one channel. You can deploy the same agent in multiple places:

• On websites
  Agents feel native on websites: lightweight, branded, and optimized for site performance. From support widgets to guided product discovery, they integrate seamlessly into the user journey.
• Inside workflows
  Agents can run behind the scenes: reading data, triggering automations, and passing information between systems. With webhooks or tools like n8n and Make, agents become part of end-to-end processes.
• For internal teams
  Agents don’t have to be client-facing. They can help staff with repetitive tasks (HR, finance, sales, ops), or serve as on-demand assistants inside your portal.

Different interfaces for different Agents

Different problems require different interfaces:

• Website interfaces – for natural Q&A, support, or discovery flows.
• Background agents – triggered by events, data streams, or workflow rules.
• Focus agents – for agents supporting internal workflows.

This makes Eloquent agents more than “bots.” They’re modular intelligence units you can adapt to any context.

Anatomy of an Agent

Every agent in Eloquent is built from six parts:

1. Prompts & Logic – define how the agent understands and responds.
2. Knowledge Base (RAG) – connect documents or data for accurate, context-rich answers.
3. Settings – adjust how creative or strict the agent should be.
4. Integrations – connect to APIs, workflows, or tools like n8n and Make.
5. Branding – your logo, colors, and domain; clients only see your brand.
6. Interface – how the user interacts with the Agent.

Together, these make each agent flexible, powerful, and fully yours.

Some example scenarios

• On a client’s website: A support agent answering FAQs, qualifying leads, and scheduling demos.
• In a workflow: An automation agent reading purchase orders from email and pushing them into a CRM.
• Internally: An HR assistant answering employee questions and updating records.