RootLogic Lead Pipeline
Lead Pipeline

I accidentally moved a lead to the wrong column. How do I fix it?

How you fix a misplaced card depends on which column it landed in — a wrong drag to Hot Lead is harmless, but a wrong drag to Consult Booked needs immediate action.

1
Moved to Hot Lead by accident? Just drag it back
Hot Lead has no automation attached to it. If a card landed there by mistake, simply drag it back to Lead Received. Nothing fired, nothing broke. The lead is still in the automated nurture sequence and nothing needs to be corrected beyond moving the card back to the right column.
2
Moved to Consult Booked by dragging instead of booking? Act immediately
This is the more serious situation. First, drag the card back to Lead Received or Hot Lead. The incorrect position caused no automation to fire (that's the problem — nothing fired), so moving it back doesn't create new problems. You're resetting the visual state. The card sitting in Consult Booked without a real booking is inaccurate and must be corrected right away.
3
If there IS a real consult booked, create the appointment through the calendar now
Open the contact record, click the Appointments tab, and create the actual appointment for the date and time the patient agreed to. Save it. The automation will fire — confirmation text, email, reminder sequence — and the card will move back to Consult Booked on its own. The patient will now receive the confirmation and reminder communications they should have gotten the first time.
4
If no consult is actually booked, leave the card in Lead Received and add a note
If the card got dragged to Consult Booked but there's no real appointment, just leave it in Lead Received after dragging it back. Add a note explaining what happened so there's no confusion later. The 45-day nurture sequence is still running for that lead. No VMMG notification needed for a simple drag error — just correct it and move on.
Important: If a lead was in Consult Booked incorrectly for more than a day or two, let your VMMG account manager know. The conversion data may have already been reported inaccurately and they may need to correct it on the ad platform side.