How to Use Vici Dialer Step by Step

Here is how to use vici dialer, following Ohio State’s agent workflow: log in, select a campaign, handle calls, and save dispositions. This guide separates VICIdial® agent tasks from administrator setup, then walks through a practice session before you call real leads. (chrr.ohio-state.edu)

Key takeaways

• Get separate phone and agent credentials from your administrator.
• Test customer audio before joining a production campaign.
• Practice accurate outcomes, callbacks and transfers before increasing dialing pace.
• Test do-not-call controls, not just the wording in your script.
• Reconcile the practice calls against saved results before approving an agent for live work.

What do you need before logging in?

If you are learning how to use vici dialer as an agent, skip server configuration. Ask your supervisor for an approved agent URL, phone credentials, user credentials, campaign name and headset setup.

Administrators have a different job. The VICIdial Group’s white paper distinguishes agent screens from administrative screens for configuration, reporting and data exports. Keep those roles separate during training. (vicidial.com)

Before starting, get written answers to these operational questions:

• Which campaign am I assigned to?
• Which outcomes should I use, and which must never be retried?
• Who receives qualified calls?
• What happens if that destination is unavailable?
• Which time zone does our callback screen use?

For owners still evaluating infrastructure, use the open-source dialer operating-cost guide separately. A daily agent tutorial should not double as an installation project.

How should an administrator prepare the campaign?

Start with a training campaign and numbers controlled by your team. Matt Florell’s official getting-started presentation establishes the basic setup order: user group, agent user, phone, campaign and list. Its screenshots are historical, so use your installation’s help for current field details. (vicidial.org)

Prepare and verify the lead list

Dial Fusion’s lead-loading documentation documents creating a list, assigning its campaign, choosing its active state and loading a file through Load New Leads. Use that workflow with these checks: (docs.dial-fusion.com)

1. Create a clearly named training list under the intended campaign.
2. Prepare a small CSV containing approved test destinations and identifiable lead names.
3. Select the intended list in the loader and map the file’s columns.
4. Review duplicate-check options rather than accepting them without inspection.
5. Inspect imported records, especially phone numbers, country codes and location fields.
6. Activate the list only when you are ready to test it.

Do not import a production file merely to discover whether the loader works. Prove the mapping first.

Choose the dialing method deliberately

The project’s VICIDIAL.txt process documentation, mirrored on GitHub, distinguishes manual, ratio and adaptive dialing. The recommendations below are training choices, not universal production settings. (github.com)

Learning how to use vici dialer starts with a controlled campaign, not a higher dial level. Approve the caller ID, callable statuses, retry rules and calling windows before enabling automatic calls.

How to use vici dialer for your first shift?

Use this start-of-shift sequence. Ohio State’s archived training manual documents separate phone and campaign logins, the agent session call, preview dialing and customer hangup controls. Follow your own deployment’s screen order if it differs. (chrr.ohio-state.edu)

1. Open the approved agent page. Use the address supplied by your administrator, not an unfamiliar public demo. Keep administrator credentials out of agent onboarding sheets.
2. Connect the assigned phone. Open the configured browser phone or softphone. Check the headset input and output, and allow microphone access when required.
3. Enter phone credentials. Fill the phone-login fields with the workstation’s assigned details. Do not assume the phone password matches your agent password.
4. Enter agent credentials and select the campaign. Read the campaign name before submitting. Stop if the expected campaign is missing.
5. Join the agent session. Answer the session call where your phone setup requires it. Keep this connection open while working, using the agent screen to end customer calls.
6. Inspect the screen before dialing. Locate availability, customer details, script, comments, hangup, transfer and disposition controls. Ask your trainer to identify any customized buttons.
7. Make a controlled test call. Confirm that both participants can hear each other. Finish the call and save its result before enabling production work.

The VICIdial pause-code documentation identifies login pause time and system pause reasons, including lost agent-screen communication. My rule is simple: confirm your availability state before expecting calls or leaving the desk. (vicidial.org)

I treat browser access, the agent-phone connection and customer audio as separate acceptance checks. A successful web login is not my permission to start dialing.

How do you handle calls and save the right outcome?

The project’s VICIDIAL.txt workflow describes Dial Next Number for manual calling and availability controls for automatic calling. In automatic mode, greet the customer as soon as the live call reaches you. (github.com)

Use this call-handling routine:

1. Review the lead’s name, location and previous notes.
2. Follow the approved introduction and qualification script.
3. Update information during the conversation rather than reconstructing it afterward.
4. Confirm any requested callback details before ending the call.
5. End the customer call through the agent interface.
6. Save the outcome that actually happened.

According to the VICIdial Group’s white paper, agent scripts and external customer-record screens can be configured within the workflow. Save any separate form before leaving it. For bot-generated results, our guide to moving call results into a CRM explains the available handoff options. (vicidial.com)

Which disposition should you choose?

The official VICIdial status definitions distinguish these outcomes. Your campaign may expose different labels or additional custom statuses. (vicidial.org)

VICIdial’s status documentation says a DNC outcome also adds the lead to its DNC list if configured. Test that behavior; do not treat a comment saying “stop calling” as proof of suppression. (vicidial.org)

How do callbacks, transfers and logout work?

The official VICIdial Agent API documentation distinguishes scheduled callbacks, agent availability, transfer commands and logout. These are separate actions, even when customized screens place their controls together. (vicidial.org)

Schedule a callback someone can actually make

The Agent API documentation supports callbacks assigned to a specific user or anyone eligible. Choose according to your campaign’s staffing policy. (vicidial.org)

1. Confirm the customer’s date, time and time zone.
2. Select the campaign’s scheduled-callback outcome.
3. Enter the schedule and callback owner.
4. Write a short reason and relevant context.
5. Reopen the callback record to verify it saved correctly.

Do not promise a personal callback during an agent’s unstaffed hours.

Practice the exact transfer route

The Agent API documentation distinguishes blind transfer, closer routing and conference-related actions. Use the configured destination, not a number copied from an old training sheet. (vicidial.org)

For a supervised consultation, ask the trainer to demonstrate placing the customer on hold, reaching the receiving person and completing the handoff. Then practice failure recovery when nobody answers.

Test a three-party conference separately if your floor uses one. Confirm who can hear whom before sharing private notes. Human consultation and AI live-transfer workflows are not interchangeable procedures.

Finish the shift cleanly

The Agent API documentation defines logout separately from hanging up a customer call. Finish the last disposition, pause, use Logout, then close the phone and browser. Do not use a closed tab as your logout procedure. (vicidial.org)

What does a complete practice session look like?

When teaching how to use vici dialer, require a complete result trail, not just a successful connection.

Hypothetical worked example: prepare six controlled test records. Have colleagues simulate these outcomes:

1. A qualified conversation transferred to the designated closer.
2. A callback requested for an agreed time.
3. A person who is not interested.
4. A person requesting no further calls.
5. An answering machine greeting.
6. A call that is not answered.

Using the official VICIdial status definitions, the expected results are XFER, scheduled CALLBK, NI, DNC, A and N. These are test expectations, not performance benchmarks. (vicidial.org)

Now reconcile the exercise:

• Every test attempt has a saved outcome.
• The transferred lead reached the correct destination with usable notes.
• The callback has a verified time and owner.
• The DNC destination fails your controlled eligibility check for future calls.
• Notes match what the colleague actually said.

In this hypothetical example, one transfer divided by six attempts equals about 16.7%. One transfer divided by four human conversations equals 25%. Label the denominator before comparing agents or campaigns.

Why am I logged in but getting no usable calls?

Use this diagnostic order rather than changing several settings together:

1. Missing campaign: ask the administrator to verify your account’s campaign access.
2. Session not connected: check the assigned phone and repeat the controlled audio test.
3. No automatic calls: verify your availability and the campaign’s dialing method.
4. No eligible leads: inspect the active list, lead statuses, calling windows and hopper.
5. Calls without usable audio: collect a test-call timestamp and involve the telephony administrator.
6. Transfers fail: test the destination directly, then test the complete campaign route.

The VICIDIAL.txt process documentation describes the hopper as the lead-staging step before automatic dialing. An uploaded file alone does not prove that the campaign has eligible leads ready. (github.com)

For escalation, record the campaign, agent, lead identifier, timestamp, visible status and expected action. Never include passwords in screenshots. Avoid bulk status resets while diagnosing a problem.

What must you check before production or AI calling?

For covered U.S. telemarketing calls, the FTC’s Telemarketing Sales Rule guide generally restricts residential calling to 8 a.m. through 9 p.m. at the recipient’s location, absent prior consent otherwise. The FTC also explains DNC obligations and abandoned-call requirements. (ftc.gov)

The FTC’s abandoned-call safe harbor includes more than a 3% threshold: connection timing, ringing, identification-message and recordkeeping conditions also matter. Do not equate a dialer’s displayed drop percentage with legal compliance. (ftc.gov)

Before automation, have qualified counsel review the artificial-voice consent requirements in 47 CFR § 64.1200, published by Cornell LII, alongside applicable state rules. Our TCPA controls overview describes product controls, not permission to call. (law.cornell.edu)

Where do outbound bots fit?

VoiceOI’s AI voice bots for VICIdial handle first-contact qualification and pass qualified calls to human closers. They appear as VICIdial remote agents, with outcomes written back to the dialer. (voiceoi.com)

The VICIdial AI integration setup guide explains team-led onboarding, including the server connection, IP allow-listing, campaign setup and bot users and phones. VoiceOI does not provide predictive dialing for human representatives. (voiceoi.com)

Keep people on calls requiring negotiation, sensitive judgment or unsupported languages. Do not add bots to compensate for unverified consent, broken routing or inconsistent dispositions. Pass the controlled practice session first.

Cover photo by LumenSoft Technologies on Unsplash.

Sources

• VICIdial Group: Contact Center Software White Paper
• VICIdial: Agent API documentation
• VICIdial: Status definitions
• VICIdial: Agent pause codes
• Matt Florell: Getting Started With ViciDial
• FTC: Complying with the Telemarketing Sales Rule
• Cornell LII: 47 CFR § 64.1200
• VICIDIAL.txt project documentation, mirrored by Inktel on GitHub
• Ohio State CHRR: Archived agent training manual
• Dial Fusion: Manually Loading Leads From File