Documentation Index
Fetch the complete documentation index at: https://docs.nedzo.ai/llms.txt
Use this file to discover all available pages before exploring further.
Nedzo supports three agent types, each designed for a different channel. All agent types share the same prompt, actions, and knowledge base configuration — the differences are in how they communicate.
Voice agents
Voice agents handle phone calls using AI. They can make outbound calls or answer incoming ones.
Call direction
- Outbound — The agent makes calls to your contacts. Used for lead qualification, appointment reminders, follow-ups, and outreach campaigns.
- Inbound — The agent answers incoming calls. Used for customer support, reception, and intake.
You can change the direction at any time from the agent’s Prompt tab.
Phone number assignment
Voice agents need a phone number to make or receive calls. Assign one from the Settings tab under Telephony.
Purchased numbers — Phone numbers you own in your workspace. Both inbound and outbound agents can use these. Each inbound agent needs its own number — two inbound agents can’t share the same number.
Some countries require a regulatory bundle before you can purchase a number. When buying a number for one of these countries, you’ll see a prompt to create a regulatory bundle first, with a button that takes you to the Trust Center with the country pre-filled.
Verified Caller IDs — Numbers you’ve verified for outbound use only. Useful when you want calls to show your existing business number. Not available for inbound agents.
Call settings
| Setting | Range | Default | Description |
|---|
| Max call duration | 1–60 min | 30 min | The call ends automatically after this time |
| Ring duration | 1–60 sec | 30 sec | How long to ring before marking as “No Answer” |
| Background sound | On/Off | On | Plays subtle office ambience to make the call feel natural |
Voicemail
Enable voicemail detection from the Settings tab. When turned on:
- The agent detects when a call goes to voicemail
- It leaves your configured voicemail message
- The call is logged with a “Voicemail” disposition
You can customize the voicemail message. The default is: “Hi, could you please call me back?”
HIPAA compliance
Enterprise plans can enable HIPAA compliance mode. When enabled, call recordings, transcriptions, and logs are not stored. This is configured in the Settings tab under Security & Compliance.
Chat agents
Chat agents handle text-based conversations across multiple messaging channels. They respond automatically and show all conversations in Unibox.
Channels
Enable the channels you want from the Settings tab under Channels.
| Channel | Status | Description |
|---|
| SMS | Available | Responds to incoming text messages |
| Instagram | Available | Responds to Instagram DMs |
| Messenger | Available | Responds to Facebook Page messages |
| Email | Available | Responds to inbound emails on a per-agent address |
| WhatsApp | Coming soon | — |
Email channel
Once Email is enabled, set a per-agent local part (the part before the @). Inbound emails sent to that full address are routed to this agent’s conversations.
| Setting | Description |
|---|
| Inbound email address | The local part of the address. Combined with your verified sending domain to form the full address (e.g. support@mail.yourdomain.com). |
- Lowercase letters, numbers, dots, hyphens, and underscores only
- Max 64 characters
- No leading, trailing, or consecutive dots
- Must be unique within a workspace — two agents in the same workspace can’t share the same local part
Requirements:
- A verified sending domain on the workspace — set up under Settings > Integrations > Email. Without one, the inbound address input is hidden because there’s no domain to attach to.
- The Email channel must be enabled on the agent.
How it works:
- Inbound emails to the agent’s address create or continue a conversation in Unibox under that agent.
- The agent generates AI replies using its prompt, knowledge base, and configured actions — same engine that powers SMS, Instagram, and Messenger.
- Replies sent automatically by the agent or manually from Unibox come from the agent’s own inbound address, not from a generic notifications address.
- Each agent’s email conversations are scoped to that agent — two agents on the same workspace can have parallel email threads with the same contact.
Channel-aware replies
Chat agents know which channel each incoming message came from and adjust their replies accordingly. You write one prompt — Nedzo layers channel-specific guidance on top automatically.
| Channel | Default tone | Default length |
|---|
| SMS | Direct, conversational | 1–2 short sentences (designed to fit a single SMS segment) |
| Email | Polished, structured | Multi-paragraph with greeting and sign-off where appropriate |
| Web chat | Friendly, helpful | 1–3 sentences, links allowed |
| Instagram | Casual, light | Short, can use emoji |
| Messenger | Conversational | Short, can use emoji |
| WhatsApp | Conversational | Short — optimized for mobile |
Response timing
Set a delay (0–60 seconds) before the agent responds. A short delay makes conversations feel more natural. Configure this in the Settings tab.
Manual message behavior
When you or your team sends a manual message, you may want the AI to pause so it doesn’t respond over a human.
- Pause AI after manual message — Stops the agent from responding after a team member sends a message
- Auto-reactivate after — Optionally resume AI responses after a set time (minutes, hours, or days)
Message limits
Set a maximum number of AI messages per conversation to prevent runaway conversations.
When the limit is reached, you can optionally send a final message — for example: “Thanks for chatting! A team member will follow up with you shortly.”
Leave the limit blank for unlimited messages.
Post-event behavior
- Pause after escalation request — Stops the agent when a contact asks to speak to a human
- Pause after appointment booked — Stops the agent after a calendar booking is made
- Idle timeout — How long to wait before the pause takes effect (60–3600 seconds, default 300)
Auto-close abandoned conversations
Close a conversation automatically when a customer stops replying. Once closed, the conversation moves out of the Open view in Unibox and the same finalization pipeline runs as a manual close: AI summary generation, Conversation ended workflow trigger, post-conversation webhook, and cost rollup.
Configure it from the Settings tab → Auto-close abandoned conversations.
| Setting | Default | Description |
|---|
| Close conversations when customers stop replying | Off | Master toggle. When off, no auto-close timer is armed. |
| Timeout value | 15 | How long to wait for a customer reply before closing. |
| Timeout unit | minutes | minutes, hours, or days. |
chat_agents.auto_close_timeout_value and chat_agents.auto_close_timeout_unit directly. The Settings UI shows custom values as “Custom: N unit” — picking a preset overwrites the custom value.
How it works:
- When the agent sends an outbound reply, a timer is armed for the configured duration.
- A customer inbound message cancels the timer — the conversation stays open.
- If the timer expires without a customer reply, the conversation closes automatically with
closed_by set to null (system close).
- A customer reply on a system-closed conversation re-opens it and the agent resumes responding. Manually-closed conversations (closed by an operator from Unibox) stay closed even if the customer replies — operator decisions are not overridden.
Scope:
- Available on Chat agents only — covers SMS, Instagram, Messenger, and Email channels.
- Not available on Voice agents (calls have their own duration limits) or Web Agents.
Protection keywords
Add keywords that trigger an escalation when a contact uses them. For example: “manager”, “human”, “complaint”. You can add up to 50 keywords.
When a contact sends a message containing one of these keywords, the agent pauses and the conversation is flagged for human review.
Web Agent
Web Agents let you embed an AI assistant directly on your website. Visitors can chat, talk, or both.
- Voice — Visitors can speak to your agent through their browser
- Chat — Text-based conversation
- Both — Visitors choose between voice and chat
Set the mode in the Settings tab.
Appearance
| Setting | Options | Default |
|---|
| Position | Bottom Right, Bottom Center, Bottom Left, Center Right, Center Left, Top Right, Top Left | Bottom Right |
| Theme | Light, Dark | Light |
| CTA text | Any text (max 25 characters) | “Talk to an agent” |
| Avatar | Upload PNG, JPEG, SVG, or WebP (max 2 MB) | Gradient default |
Branding
- Show branding — Toggle the branding footer on/off
- Branding text — Customize the text shown in the footer
Visitor context
The widget automatically captures context about website visitors to give your agent and team more information:
- Page URL — The page the visitor was on when they started the conversation. This shows up in Unibox so your team can see what the visitor was looking at.
- Name extraction — The agent extracts the visitor’s name from the conversation automatically. Once identified, the contact record is updated with their name.
Markdown rendering
AI responses in the chat widget render basic markdown formatting:
- Bold and italic text
- Hyperlinks — links open in a new tab
User-typed messages are displayed as plain text. Markdown rendering works in both the embedded widget and the chat simulator.
Multilingual support
Web Agents respond in the visitor’s language automatically. If a visitor writes in Spanish, the agent replies in Spanish — regardless of the language set in the Prompt tab.
The language setting on the Prompt tab controls the agent’s default language and voice. The multilingual behavior applies to chat mode only.
Embedding on your site
After configuring your widget, copy the script tag from the Settings tab and paste it into your site’s HTML, just before the closing </body> tag.
<script src="https://cdn.nedzo.ai/widget.js" data-agent-id="your-agent-id"></script>
