Documentation Index
Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt AI agents and IDE assistants can connect to the docs MCP server at: https://dialnexa.com/docs/mcp Use this file to discover all available pages before exploring further.
September 2026 update summary
DialNexa changelog for September 2026
7th September, 2026
Agent Builder build path and agent type recommendation
Create agent now opens a build path choice. Proceed to Agent Builder collects Goal & Context, Call Playbook, and Personality, then suggests an agent type you can override. Manual Build starts from a template or a blank configuration. Agent Builder can draft Single Prompt, Conversational Flow, Speech to Speech, and IVR agents.Agent type selection moved to Manual Build
The Dynamic Agents and Static Agents tabs have been replaced. Manual Build shows Single Prompt, Conversational Flow, and Speech to Speech cards, and Show the IVR agent reveals the IVR Agent card, still marked Beta.Prompt size limits and the editor meter
Single Prompt and Speech to Speech editors show an estimated token count with green, yellow, and red states. Every selectable model now has an enforced ceiling, and with a fallback enabled the tighter of the two applies. Save and publish are blocked above the ceiling.IVR handoff variables and branch labels
Each Connect To Agent node needs a non-empty fallback for every variable in its target’s published prompt, welcome message, voicemail message, and default map. Branches show their digit on the connecting line, and publishing warns about missing fallbacks. IVR calls record only the conversational portion after a handoff.Agent exports and imports drop phone bindings
Exports strip inbound and outbound phone bindings, including nested phone-provider objects, and import ignores bindings in older JSON files. IVR menu graphs are preserved. Assign phone numbers explicitly in the destination workspace after publishing.Workflow lead tags
Tag a lead cohort from the upload dialog or a reserved tags column. Tags are combined, lowercased, trimmed, and deduplicated, with at most 20 tags per lead and 40 characters per tag. Calls placed by the workflow copy the lead’s tags into the call record for Call History filtering.End Call is platform-managed
End Call appears automatically on new agents and cannot be edited or deleted. It does not on its own disable predictive preprocessing or require a tool-calling model. Those rules apply once you add callable functions.Recipient column mapping and duplicate rules
Two mapped columns cannot resolve to the same field name, and a mapped column wins over an unmapped source column of the same name. Duplicate removal uses the phone column you selected, and numeric Excel phone cells are converted to strings before validation.Batch retry count corrected to four
The retry count range is 0 through 4, so a recipient is called at most five times. The retry interval is in minutes, from 0 to 1440. The previous guidance said 5, which the API has never accepted.Knowledge base document API
Upload a PDF or TXT document to a knowledge base with an API key, and list a knowledge base’s documents. A knowledge base outside your workspace returns 404 rather than confirming the ID exists, because document listings carry each file’s full text.Public API reference expanded to 72 operations
Added API key validation, IVR transfer helper reads, agent version and function reads, agent type recommendation, and knowledge base documents. Every operation was checked against DialNexa’s own API definition, so the reference covers exactly the endpoints the platform publishes, with request fields, response envelopes, and errors. Endpoints the platform treats as internal are deliberately absent.Batch reads for API key callers
Get Batch Call Details and Update Batch Call Status return an empty object to API key callers because batch detail fields are filtered from the response. Use List Batch Calls for status and List Calls with batch_call_id for call records, or set export=true on the detail endpoint.Batch retry and filter parameters in the reference
Create Batch Call now listsnumber_of_retries and interval_between_retries as request fields with their accepted ranges, and Get Batch Call Details lists the is_ivr, tags and tags_match filters. The endpoints already accepted all five; only the reference was missing them. List Organization Folders gained export and Search Available Numbers gained region for the same reason.