Prepare a calling campaign in the IllyVoIP mobile app

The IllyVoIP app’s campaign editor prepares campaign settings. Saving a campaign is separate from starting it and does not prove that contacts, agents and caller ID are ready. Plan the audience, permissions and call handling before using a campaign that can place paid calls.

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. Choose the intended campaign and mode

1. Open the campaign management area using an account with the appropriate management access.
2. Choose an existing campaign to edit or the offered creation action for a new one.
3. Confirm whether the intended mode is Power or Predictive before creating it.
4. For an existing campaign, check its current state and coordinate changes with the team using it.

The reviewed editor does not treat an existing campaign’s mode as an ordinary editable field. Do not assume that changing a label converts a Power campaign to Predictive. If you need a different operating mode, review the appropriate separate campaign setup rather than altering unrelated limits to imitate it.

2. Work through the mode’s editor steps

The reviewed app uses two steps for Power campaigns and five for Predictive campaigns. Predictive’s steps are Basics, Caller ID, Behavior, Limits and Review. Use the controls actually offered for the selected mode; do not look for every Predictive field in the shorter Power editor.

1. Enter a recognizable campaign name and the relevant basic information.
2. Review the script or guidance fields offered for the campaign.
3. Proceed through each step and correct validation messages before continuing.
4. Keep a note of intended changes when editing a campaign already used by other managers.

3. Review caller ID and behavior deliberately

Choose a caller ID that your account is permitted to use and that is appropriate for the intended destinations. The editor’s server validation remains authoritative. A value typed into a field is not proof of verification or permission to present that identity on every call.

Read the mode-specific behavior settings and decide what should happen when a contact answers, does not answer or cannot be reached. Use your organization’s authorized contact and retry policy. Do not increase retries or dialing activity merely to clear a warning without understanding what the control changes.

4. Set limits for the actual operation

1. Review the limits available for this mode against staffing and account capacity.
2. Check that the team can handle the intended answered-call workload.
3. Consider destination charges and the permitted calling schedule.
4. Avoid using a high value copied from another campaign as a default.

The editor’s accepted values do not guarantee that every attempted call will be placed or delivered. Service state, permissions, contact eligibility and runtime readiness still matter. If a control is unavailable, investigate its stated prerequisite instead of trying to bypass it with a direct API request.

5. Review and save the campaign

1. Check the name, mode, caller ID, behavior and limits together.
2. Submit the save action once and wait for the result.
3. Reopen the saved campaign and verify the intended values.
4. If the response was interrupted, inspect the existing campaign before creating another one.

A successful save means the configuration was retained. It is not an instruction to begin calling, and it does not automatically prove that contact import or agent assignment has finished. Keep setup and launch as separate decisions.

6. Complete readiness checks before launch

Review contacts and agents in their respective campaign management views. Confirm that the intended audience is authorized to be contacted, phone numbers are appropriate, agents are assigned and available where required, and the account can support the expected activity. Read any readiness or start error in full.

When you deliberately start an approved campaign, observe its actual runtime state and early outcomes. Do not repeatedly press Start after an uncertain response; first check whether it is already running. For Support, provide the campaign reference, mode, time and sanitized message. Keep contact lists and customer information out of public screenshots.

Related guides

• Prepare an outbound campaign
• Configure an inbound queue

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