How to move emailed leads to another list by disposition

Say an agent handles an inbound email, marks it a sale, and you want that record to land in a follow-up list so quality control can call the customer back in a few days. VICIdial can do that move for you automatically, based on the Disposition the agent picked. The trick is to point the email group's Dispo Email URL at a small script that moves leads between lists.

How it works

Dispo Email URL fires a silent web request every time an email is statused. Instead of pointing it at your own system, you point it at the dispo_move_list script that ships with VICIdial. The request carries the lead and the disposition, the script checks whether that disposition matches a status you care about, and if it does, it moves the Lead into the list you named.

The address looks like this, with the standard variable markers VICIdial fills in at run time:

http://serverIP/agc/dispo_move_list.php?lead_id=--A--lead_id--B--&dispo=--A--dispo--B--&user=--A--user--B--&pass=--A--pass--B--&new_list_id=XXXXX&sale_status=SALE

Walking the key parameters:

• lead_id, dispo, user, pass are the standard variables, filled in for each email.
• new_list_id is the list you want matching leads moved into.
• sale_status is the disposition that triggers the move. Set it to SALE, or whatever status you want to act on.
• reset_dialed=Y clears the dialed flag so the lead can be called again from the new list.
• log_to_file=1 writes a log so you can confirm the move happened.

Sending different statuses to different lists

You are not limited to one rule. To send STATUS 1 to list A and STATUS 2 to list B, you add a second set of parameters with _1 on the end of each name. The next set takes _2, then _3, and so on. You can fan out to as many as 99 different lists from a single Dispo Email URL.

The flow end to end

flowchart TD
  A["Agent statuses an email"] --> B["Dispo Email URL fires"]
  B --> C["dispo_move_list script runs"]
  C --> D{"Does dispo match a sale_status"}
  D -->|no| E["Lead stays put"]
  D -->|yes, set 1| F["Move to list A, reset dialed"]
  D -->|yes, set 2| G["Move to list B, reset dialed"]
  F --> H["Log the move"]
  G --> H

Because the move keys off the Disposition, it only runs when the agent actually picks the status you named. Everything else is left alone. A common pattern: SALE leads go to a verification list for a callback later, while XFER leads go to a separate queue for a Closer to finish.

A couple of habits will save you headaches. Turn on log_to_file=1 while you are testing so you can open the log and confirm each move actually happened, then leave it on if you want an ongoing record. Decide up front whether reset_dialed should be Y for each rule: set it when the lead needs to be dialed again from its new home, and leave it off when you just want the record filed away. And before you point the field at the script in production, run it once with a single test lead so you can see exactly where that record lands.

This approach scales nicely. Because one Dispo Email URL can carry up to 99 numbered rule sets, a single email group can route every meaningful outcome to its own list without any extra wiring. Sales go one way, transfers another, complaints a third, and so on. Each rule is just another bundle of parameters with the next number on the end.

Set this up on the same field described in the Dispo Email URL field, and for the full email queue setup see the inbound email and chat guide. If running these scripts on your own box sounds like a chore, our pricing page covers managed VICIdial hosting where the box is live in under 40 seconds.