Fix each feature where it stands.
An earlier pass on September 23 quarantined four of the five workflows and shipped a single text, one intake and one confirmation email. On September 24 the snapshot was rebuilt instead: all five workflows were restored and repaired, the pipeline stages were replaced with ones the workflows write, eleven contact fields, the Company Name variable and a Seller Consultation bookable were created, and the reduced replacements were removed.
Every source finding has a disposition.
The hard-coded phone number and Votel address are gone. Team alerts are emails to the account's support address.
Calls and texts go to one preferred number, not every phone field.
Any answered call hands off to the seller conversation and ends the campaign; six calls at most.
New pipeline stages (New Lead, Contacting, Left a Message, Replied, Appointment Scheduled, Call Forwarded, Not Interested), and every stage the workflows write exists.
Appointment notifications start from the booking itself and read the booked time from it. Seller confirmations and 24-hour and 1-hour reminders come from the bookable.
Caller ID, SMS number and email sender stay in place and are flagged until connected.
A Seller Consultation bookable replaces the unconnected calendars; a failed booking creates a task.
Occupancy has its own field, and every phone and text answer is saved to a contact field.
Company Name replaces the missing variables; the hard-coded persona and company copy are gone and the assistant identifies itself as AI.
Asking for a specialist transfers the call to the owner's specialist line, with a booking offer when nobody answers.
Land sellers were sent to goodbye (now qualified); the call handoff pointed at an agent in another account; a Votel account calendar address was embedded in a trigger; a decline on the phone did not stop the texts (now tagged and checked before every text); stored model was GPT-4.1 Mini. In testing, the answered-call workflow used a manual trigger, which cannot ask questions; it is now a conversation trigger.
The same design, now able to run.
Text version of this diagram
Before: 22 calls rotated across five phone fields and an answered call stayed in the daily calling loop; 44 texts repeated each wave to every phone field; qualification answers were not saved, one was written to the Owner user field, and land sellers were sent straight to goodbye; the workflows wrote stages the pipeline did not have; the calendars were not connected; and alerts went to a hard-coded phone number and a Votel address with no specialist handoff. After: six calls to one number over four days and any answer ends the campaign; ten texts to one number that stop on a reply or a decline; home and land sellers are qualified and every answer is saved to the contact; a seven-stage pipeline matches what the workflows write; a Seller Consultation booking sends confirmations and reminders; and team alerts go to the support address with a live transfer to a specialist.
Text version of this diagram
Enrolling a seller sets the pipeline stage to Contacting and places the first call to their preferred number. A missed first call is retried three minutes later; a second miss sends a short text and the calls continue once a day, six calls in total. If the seller answers any call, the seller conversation takes over and the campaign stops. After six unanswered calls the stage becomes Left a Message and a task is created.
Text version of this diagram
The answered call opens with an AI-assistant greeting and asks whether the owner is open to an offer. A decline moves the seller to Not Interested, adds a not interested tag that stops the text campaign, and ends politely. A request for a specialist transfers the call; if nobody answers, the assistant offers to book instead. An interested owner is asked whether the property is a home or land. Home sellers answer eight questions and land sellers four, all saved to the contact. The assistant then offers a consultation: a booking moves the seller to Appointment Scheduled, emails the team the seller details, creates a preparation task and confirms the time; a failed booking or a not now creates a follow-up task.
Text version of this diagram
The text campaign checks before every message whether the seller is marked not interested, then sends up to ten texts to one number, waiting 1, 3, 5, 7, 14, 21, 30, 60 and 90 days between them. Any reply stops the campaign and marks the seller Replied. When a seller texts in, the reply workflow asks whether they are open to selling, asks five questions by text, saved to the contact, and offers to book a consultation. A no closes the file and stops further texts. When a Seller Consultation is booked, the team gets an email with the time and property and a preparation task; the seller gets confirmations and reminders from the booking.
Checked in the editor and the simulator.
86 steps and 126 links survive a save in Votel's editor with no dangling links.
With the team email bypassed for the test, 14 runs (cooperative and rambling owners) scored 94 to 96 on conversation; complete runs took 20 to 21 steps through qualification and the booking or follow-up task.
No valuations or offers, no pressure, STOP and do-not-contact respected, no sensitive details, no legal or tax advice, transfer handled. The miss is a booking request, which needs the workflow.
The simulator cannot place calls, send texts or wait days, and the reply workflow needs an SMS number before it registers.
Need a caller ID, SMS number, sender, published bookable and account balance.
Remediation complete.
The rebuilt account is ready for final acceptance and master snapshot generation.
Open final audit →