Installed snapshot · independent audit

Inside the Pool Removal & Landscaping snapshot.

What actually appears after installation, not just the library description. This report traces the agent, all three workflows, the connected pipeline, node dependencies, placeholders, and the work required before launch.

Votel library v2.1Reviewed Sep 23, 2026Immutable source recordSanitized for publication
VOTEL SNAPSHOT AUDIT01 / HOME SERVICES

AI Pool Removal &
Landscaping Receptionist

Installed agent1
Agent workflows3
Workflow nodes18
Pipeline stages9
Launch statusNeeds setup
1AI receptionist
3Connected workflows
18Canvas nodes
9Pipeline stages
0Active channels
01 · Executive verdict

A strong operating skeleton, not a finished business system.

The install is more substantial than the library card suggests. It creates a structured voice receptionist with lead lookup, qualification, data capture, pipeline routing, an external webhook, team-message handling, and two stage-driven follow-up workflows. It is intentionally installed inactive and still contains business-specific placeholders.

Installed

Core system

One agent, three workflows, one Sales pipeline, branching conversations, contact capture, email, API and hangup actions.

Configure

Business details

Replace company placeholders, experience claims, pool counts, team routing, notification destinations and the webhook.

Test first

Channels & delivery

The agent is inactive with zero active channels. No knowledge base or website widget is attached.

What this means: you are not buying a one-click finished receptionist. You are buying a thoughtfully connected starting system that can save meaningful build time once it is customized and tested.
02 · Installed asset inventory

Everything the snapshot placed in the account.

Votel’s library discloses one agent and one pipeline. The account audit reveals the operating detail inside those two assets.

Pool and Landscaping source inventory: one AI receptionist, three workflows, 18 source nodes and nine Sales stages, leading to the corrected data contract
Installed source at a glance. The blue nodes are the immutable v2.1 inventory; the green nodes preview the corrected data layer documented in report two.
AssetStatusVerified detail
AI Pool Removal & Landscaping ReceptionistInactive

Agent v1 in the account; OpenAI GPT-5.4 Nano; Skylar voice; en-US; zero active channels.

Inbound CallConnected

Conversation start → contact lookup → existing/new decision → service routing → qualification → save fields → webhook → call completion.

Why Client PassedTrigger only

Triggered when a contact moves to the Sales pipeline’s Pass stage. The installed trigger leads to an empty placeholder; no follow-up action is connected yet.

Google ReviewsTrigger only

Triggered when a contact moves to the Sales pipeline’s Completed stage. The installed trigger also leads to an empty placeholder.

Sales pipelineInstalled

Nine stages: Lead, Contact, Proposal, Resolved, Qualified, Completed, Won, Pass and Lost.

Shared knowledgeNone

No knowledge base is selected. FAQs currently live in the agent prompt rather than an attached source library.

Website widgetNone

No website widget is configured.

Built-in tools0 / 17

No built-in conversational tools and no custom tools are enabled in the agent’s Tools tab.

Scope rule: the account also had a Social integration visible, but the snapshot library only claims one Agent and one Pipeline. This report does not attribute account-wide integrations to the snapshot unless the installed workflow explicitly uses them.

The 12-question lead intake

The main Ask & Save node uses AI-generated delivery, allows interruptions, and loads existing contact values. Eleven questions are always visible; the landscaping-interest question appears only when the project type is Pool removal.

QuestionTypeSaved destination
First nameText

First Name

Last nameText

Last Name

Construction project typeDropdown

custom_project_type

Phone numberPhone

Phone

Email addressEmail

Email

Street addressText

Mailing Street

ZIP codeNumber

Mailing Postal Code

How did you hear about us?Text

custom_how_did_you_hear_about_us

Landscaping after pool removal?Conditional

custom_landscape · shown when project type = Pool removal

Residential or commercial?Dropdown

custom_project_type

Other contractor estimates?Dropdown

custom_bidsyet

Message for the Demo ProsTextarea

custom_note

Field-mapping warning: both “Construction project type” and “Residential or commercial?” save to custom_project_type. Test whether the second answer overwrites the first. This is exactly the kind of conflict a complete snapshot audit should reveal.
03 · Sanitized screen view

What the installed workflow looks like.

This publication-safe reconstruction preserves the visible Votel canvas structure while removing the account name, personal contact data, and the external webhook identifier.

AI Pool Removal & Landscaping Receptionist
● INACTIVE

Agent workflows

Inbound CallWhy Client PassedGoogle Reviews

Capabilities

Prompt BuilderTools & IntegrationsShared Knowledge
INBOUND CALL · FLOW 1
Conversation StartedVoice, chat or SMS entry
Contact LookupMatch phone number; create contact when absent
Existing contact?Yes / No decision
Set Pipeline StageSales → Lead
Service routePool removal or landscaping
Ask & Save12 questions → contact fields
Submit customer infoPOST JSON → external workflow
End callConfirmation and handoff
Sanitized canvas reconstruction. Based on the installed Votel workflow reviewed in the account. It is not a stock illustration; labels and connections come from the live installed asset.
Why the raw screen is not published: the canvas contains an account-specific company value and a private external workflow URL. The documentation should show the system without leaking implementation details.
04 · Node-level connection map

How the pieces hand work to one another.

There are 18 visible workflow nodes across the three installed flows. The primary route is a real operating chain, not a collection of disconnected examples.

Source inbound call structure showing contact lookup, new and existing contact branches, service routing, guided intake, team handoff and safe completion
Source workflow reconstruction. This Mermaid diagram reflects the verified installed graph without exposing the private account canvas.

Inbound qualification path

Conversation started→Phone lookup→Existing / new decision→Sales · Lead
Pool or landscaping?→Full or partial removal?→12-question Ask & Save→POST customer data→Hang up

Passed-lead workflow

Sales stage = Pass→Empty placeholder

The flow name suggests follow-up, but only the stage trigger is wired. Its action path still needs to be designed.

Completed-job review workflow

Sales stage = Completed→Empty placeholder

The trigger exists, but there is no connected review-request action chain. Treat this as a build prompt, not a launch-ready automation.

Node typeCountWhat it contributes
Conversation nodes7

Greeting, routing, qualification context, confirmations and fallback responses.

Triggers3

Conversation started, Sales → Pass, and Sales → Completed.

Data & routing5

Two Ask & Save nodes, contact lookup, decision and pipeline assignment.

Delivery actions3

Email, API POST and hangup. Together they hand the captured lead to the team.

05 · Installed CRM structure

The snapshot’s Sales pipeline.

The workflow does not merely collect information. It writes leads into a dedicated pipeline and uses pipeline movement as the starting signal for two unfinished automations.

LeadContactProposalResolvedQualifiedCompletedWonPassLost
Connectivity proof: Inbound Call assigns new contacts to Sales → Lead. Two additional workflows listen for Sales → Pass and Sales → Completed, but both currently stop at an empty placeholder. This is the exact distinction a snapshot report should make visible.
06 · Launch checklist

What must be configured before this can take calls.

Installation gives you the system. Launch readiness requires business decisions, destination connections, and safe testing.

  • 1
    Replace every placeholder

    Company name, experience, number of completed removals, team-member references and any bracketed copy.

    Required
  • 2
    Review the 12 saved questions

    Confirm field names, required answers, property type, project type, address, ZIP and attribution questions.

    Required
  • 3
    Replace or approve the external webhook

    The installed API node points to an external Zoho Flow destination. Verify ownership, payload and failure behavior.

    Security
  • 4
    Set real notification recipients

    Confirm who receives passed-lead messages and what happens when email delivery fails.

    Required
  • 5
    Attach phone or other channels

    The agent is inactive and currently shows zero active channels.

    Required
  • 6
    Add business knowledge if needed

    No shared knowledge base is selected; FAQs currently depend on the prompt.

    Recommended
  • 7
    Finish the Google Reviews path

    The Completed-stage trigger is present, but the visible action path still needs to be built or verified.

    Required
  • 8
    Simulator test every branch

    Use synthetic contacts only. Test existing/new callers, both service types, Pass, Completed, API failure and message fallback.

    Required
07 · Framework check

The same report structure works for Dental, but exposes different risks.

The Dental AI Receptionist was reviewed as a comparison. It also installs one inactive agent and one pipeline, but it is significantly larger and much more dependent on calendars, email delivery and location-specific setup.

Pool & Landscaping · v2.1

Focused lead qualification and routing system.

  • 3 workflows
  • 18 visible nodes
  • 12-question lead intake
  • 9-stage Sales pipeline
  • External webhook dependency

Dental AI Receptionist · v33

Complex multilingual appointment and front-desk system.

  • 2 workflows
  • Booking, rescheduling, cancellation and confirmation
  • Multiple appointment email paths
  • Several calendar nodes currently show “No calendar”
  • Appointment triggers show “Source: Not configured”
Why this matters: counting assets alone is not enough. A useful snapshot audit must document dependencies and unfinished connections. The Dental install looks powerful, but its calendars, appointment sources, email destinations and one agent-forwarding reference must be remapped before launch.

The immutable source audit is complete.

The next report shows every defect-to-fix decision made in the isolated private baseline.

Open the remediation report →
Audit method: read-only review of the installed assets in a Votel agency account, finalized September 23, 2026. No agent was activated, no message or call was sent, and no live contact data was used for testing. Votel can update snapshots after this review.