Edit and publish a Voice Agent from the IllyVoIP app

The IllyVoIP app separates editing an agent from applying its published version. Finish changes in the main editor, follow the publish progress, then reopen the same agent to verify the result before directing customer calls to it.

These steps follow the Android app in version 1.0.46, build 272. Use your own account and the permissions assigned to it; other installed releases can have different controls.

1. Open the correct agent

1. Open Voice Agents and choose the intended agent. Check its name and current state before editing.
2. Confirm that your account has management access. A view-only screen does not authorize changing the agent.
3. Review the existing Basics, Knowledge and Call Flow information. Record the specific change you intend to make, especially for an agent already receiving calls.

Decide what should happen for an ordinary question, an unknown answer and a request for a person. Have the intended handoff destination ready. An agent’s name or website field does not prove that its knowledge is current or an external integration works.

2. Edit the appropriate part of the agent

1. Use Basics for the offered name, company, language, voice and speaking controls. Changing language does not translate the wording already saved.
2. Use Knowledge for approved facts and answers. Review enabled states and the editor’s validation before returning.
3. Open Call Flow for the caller’s path. Check both the normal branch and any no-input, failure or closed-hours path affected by the edit.
4. Finish the flow editor with its save-and-close action and return to the parent agent editor.

Returning a changed flow to the main editor is not the same as publishing it to callers. Keep the main agent editor open until you have completed the intended Update or Publish action. If you leave with edits, read the unsaved-changes prompt instead of assuming the server has retained them.

3. Review the complete change before applying it

1. Check the selected agent again and review all pending edits together.
2. Confirm the greeting and prompts use the intended words, language and voice.
3. Check configured transfer destinations and any external-service fields. Do not include credentials in spoken text or Knowledge.
4. Resolve invalid fields and outstanding knowledge-review messages before publishing.

When you publish with unsaved changes, the app first updates the agent and uses the returned version for publishing. If that update fails or does not return a usable version, publishing should not proceed. A successful update followed by a publish error therefore needs a status check, not automatic re-entry of every change.

4. Follow publishing to its result

1. Use the offered Publish action once when you intend to apply the reviewed version.
2. Watch the publishing job. Queued and running states mean work is still underway.
3. If an error appears, retain its wording and reopen the same agent to inspect its saved and published state before retrying.
4. After completion, verify the saved fields and published state. Check any audio-preparation notice separately.

A brief success message is not proof that every audio asset finished preparing or that callers can reach a transfer destination. Avoid repeated Publish taps while a job is running. Closing the progress view does not by itself cancel the server’s work.

5. Verify the affected caller experience

Only after the intended version is ready should you deliberately attach or change incoming-number routing. A published agent does not automatically move every number to it. At an agreed time, make an authorized test of the changed path: ordinary question, unknown question, handoff and after-hours behavior as relevant. Check charges first and inspect the resulting report.

If another editor changed the agent while you worked, reload the latest version and compare your intended edit before applying it again. Do not overwrite unfamiliar changes merely to clear a conflict. For Support, provide the agent reference, time and visible update or publish error, with private knowledge and integration credentials removed.

Related guides

• Prepare an AI voice agent
• Build and maintain your Voice Agent knowledge
• Connect Voice Agent flows, integrations and reports
• Read a Voice Agent call report and its usage charge

Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.