Fix each feature where it stands.
An earlier pass on September 23 replaced all three workflows with a six-question intake, which removed the forwarding, callbacks, texts and call summary that make up the product. On September 24 the snapshot was rebuilt instead: the three original workflows were restored and repaired, three contact fields and the Company Name variable were created, and the temporary intake was removed.
Every source finding has a disposition.
The recovery workflow listens to inbound calls only, removes the missed lead tag before anything else and makes at most two callbacks before creating a task. Callback calls are outbound, so they cannot start it again.
The two numbers imported from Votel's account are gone. Both forwarding steps use one rule, Monday to Friday 8 to 5, with a [Team Phone Number] placeholder that Votel flags until the owner sets it.
All five team emails go to the account's support address. The caller only ever receives texts.
Email steps stay in place and are flagged until a sender is connected.
Four texts: message received, callback coming (held until business hours), sorry we missed you, and we got cut off. The cut-off text is driven by a new hung-up-early output on the AI summary.
The call workflow starts on inbound calls to this agent's number only.
Basement-waterproofing claims, the Iowa service area and the caller-as-business contact details were removed. The prompt forbids inventing prices, hours, service areas or guarantees.
One variable, Company Name (default "our office"), replaces the ten missing ones and is used only in scripted lines.
Scripted greeting added; copy cleaned; Sara kept as an editable persona.
The business-hours decision had empty conditions; the end step looped back into the conversation; callback calls handed off to a workflow in another account; contact lookup used an old variable format; the fourth question was not saved; stored model was GPT-4o Mini; a wait step was saved in a format the editor could not read.
The same design, now able to run.
Text version of this diagram
In the source, any ended call, inbound or outbound, checked for the missed lead tag. If the tag was present a callback was placed; when that callback ended it started the same check again, and the tag was never removed. Otherwise the call went to the AI action summary.
Text version of this diagram
Before: the workflow started on any chat, text or call and then ran phone-only steps; calls were forwarded to two numbers from Votel's own account; team notifications were emailed to the caller; the callback workflow could re-trigger itself because it listened to every ended call and never removed the missed lead tag; the promised callback text did not exist; and the prompt described a basement-waterproofing company in Iowa. After: the workflow starts on inbound calls only; forwarding goes to the owner's team line in business hours; a six-question message is saved to the contact and team notices go to the account's support address; the recovery workflow listens to inbound calls only, removes the tag first and makes at most two callbacks before creating a task; four texts cover message received, callback coming, missed call and cut-off call; and the prompt is neutral.
Text version of this diagram
An inbound call finds or creates the caller by phone number, and Sara greets them with the business name. The call is then forwarded to the owner's team line. If the team answers, the team gets a call-connected email. If nobody answers during business hours, or the call comes in outside business hours, the workflow marks which case it is and Sara takes a message: first name, last name, best phone number, reason for the call, whether it is urgent and the best time to call back, all saved to the contact. The contact is tagged missed lead, the team gets a missed-call or after-hours email with the details, and Sara confirms the message and says a text is coming before the call ends.
Text version of this diagram
When an inbound call ends, the workflow checks what happened. If the caller left a message (tagged missed lead), the tag is removed, the caller gets a message-received text, then a callback-coming text held until business hours, then up to two callback calls five minutes apart. An answered callback is noted and the callback conversation takes over; if both callbacks fail, a task asks the team to call back manually. If the call itself was missed, busy, sent to voicemail or failed, the caller gets a sorry-we-missed-you text and the team gets a task. Otherwise an AI step reads the transcript: if the caller hung up before giving their details they get a we-got-cut-off text and the team gets a task; if the call produced next steps the team gets them by email; if neither, a note records that no follow-up is needed.
Text version of this diagram
When a callback call is answered, Sara says she is returning the caller's call and tries the team line. If the team answers, the connection is noted. If nobody answers or it is outside business hours, Sara confirms the reason for the call and the best time to reach the caller, emails the team that the callback did not connect, confirms, and ends the call.
Checked in the editor and the simulator.
44 steps and 49 links survive a save in Votel's editor with no dangling links. Every branch ends in a close, note, task or email.
With forwarding bypassed for the test, eight simulator conversations (cooperative and rambling callers) scored 78 to 96 and ran 7 to 13 steps to the first email without a sender. The 78 ran out of simulator turns mid-questions.
17 paths generated. The simulator cannot set a call status or tags, so every run takes the no-follow-up branch, which executes correctly. The other branches are owner acceptance tests.
No invented facts, no callback time promises, 911 for emergencies, no card or password details, stop-contact requests respected. The miss is a transfer request, which needs the workflow.
Need a phone line, SMS number, sender and account balance; listed as owner acceptance tests.
Remediation complete.
The rebuilt account is ready for final acceptance and master snapshot generation.
Open final audit →