The system is ambitious. Its stop conditions and data contracts are not ready.
Votel’s template demonstrates a genuinely useful acquisition architecture: outbound calls, long-term SMS follow-up, seller qualification, booking, tasks, pipeline updates, and appointment notifications. But the installed version can continue calling after an answered call, repeat one SMS campaign across five number fields, and send private information to hard-coded destinations. Treat it as a reference design, not a switch-on-and-run snapshot.
Broad architecture
One inactive agent, five connected workflows, 112 real nodes, 156 edges and one pipeline.
Stop conditions
An answered call can enter the next-day retry loop; SMS waves have no visible number deduplication.
Data contract
Workflow stages do not exist in the installed pipeline, and appointment actions reference other workflows.
One agent orchestrates five distinct jobs.
GPT-5.4 Mini, Jacqueline by Cartesia, en-US, no active channels, 251-word prompt.
Multi-number call sweeps, SMS reply gate, pipeline update, daily waits, response-workflow handoff.
Interest routing, seven qualification questions, calendar, pipeline, email and task.
Forty-four SMS actions across nine delayed waves and five contact-number fields.
Inbound intent, seller qualification, calendar booking and pipeline state.
Unconfigured appointment source followed by four immediate notification actions.
Five named installed stages; workflow updates target different stage names.
No knowledge base, widget, custom tools, or enabled built-in tools.
How the five flows work together.
The structure below reconstructs the installed system without exposing account-specific contact or destination data.
Workflows
OUTBOUND CALLOUTBOUND RESPONSESMS OUTREACHSMS FLOWAPPOINTMENT NOTIFICATIONS1 · OUTBOUND CALL
Twenty-two call nodes rotate through phone, mobile, work, home and secondary numbers. The final answered outcome enters a one-day retry loop.
2 · OUTBOUND RESPONSE
The qualification sequence is strong, but one answer maps to the wrong field type and the calendar/email destinations are unresolved.
3 · SMS OUTREACH
The campaign spans one day through three months. It needs a preferred-number rule, consent controls, deduplication and a stop-on-response contract.
4 · SMS FLOW
Qualification values remain local to the workflow, and the unbound calendar has no error fallback.
5 · APPOINTMENT NOTIFICATIONS
This is an immediate notification flow, not a timed reminder flow. Its trigger source, senders, recipients and appointment fields require remapping.
The installed workflows and pipeline do not speak the same language.
Installed pipeline stages
Plus Votel’s system No Column bucket.
Workflow target stages
These names are not present in the installed pipeline, and the same negative state uses two capitalization variants.
The prompt and messages use an unavailable global variable.
Notification email references unavailable custom contact fields.
A text answer is mapped to the contact Owner user field.
Notifications reference calendar and trigger outputs from different workflows.
Four seller answers are not persisted to contact fields or activity.
Fourteen findings, prioritized by launch risk.
Activation could notify the wrong person.
Private seller information is routed outside the intended team.
Duplicate outreach, cost and consent risk without a preferred-number guard.
A successfully reached contact can keep receiving daily calls.
Workflow target stages do not exist in the installed pipeline.
Recipient and time values can be empty or stale.
Senders are absent and the internal email has no recipient.
Both booking paths can strand the prospect.
A text answer conflicts with a user-assignment field.
Prompt and notification copy contain unresolved values.
All four actions run immediately after scheduling.
Seller intelligence is not reusable after the run.
The prompt promises a connection that no action implements.
Amy and company-specific wording reduce portability.
Repair safety first, then delivery, then experience.
- 1Remove every hard-coded destinationSafety
Replace phone and email values with verified required setup fields.
- 2Normalize one preferred contact numberSafety
Add deduplication, consent, stop-on-response and frequency caps.
- 3Fix every retry exitSafety
Answered calls must leave the calling campaign permanently.
- 4Rebuild one pipeline stage contractRequired
Make every workflow target an installed, consistently named stage.
- 5Bind every delivery dependencyRequired
Phone, SMS, email, calendars, appointment source and recipients.
- 6Use the appointment event payloadRequired
Remove cross-workflow output references and add actual reminder timing.
- 7Repair the seller data modelRequired
Create occupancy fields and persist qualification data deliberately.
- 8Add error and human-handoff pathsRequired
Recover failed booking and implement the senior-specialist promise.
- 9Resolve identity and variablesRequired
Parameterize Amy/company copy and supply every missing field.
- 10Test with synthetic data onlyTest
Generate and run every simulator path before attaching live channels.
Real Estate Seller Prospecting audit complete.
The snapshot is installed, inventoried, traced, scored, sanitized for public review, and added to the first-party comparison and defect matrices.
Return to the Snapshot Library →