The graph is easy to learn from; the installed configuration is not safe to activate.
The snapshot shows a strong compact pattern: contact lookup/create, call-forwarding outcomes, shared Ask & Save capture, contact notes and inbound-only post-call notification. But it ships two forwarding destinations, emails lack a sender, and its basement-services persona abruptly switches into an unrelated SaaS demo script.
Call pattern
Lookup → notify → forward → capture on failure → note and email.
Forwarding safety
Two destination numbers ship configured in a reusable snapshot.
Prompt contract
Basement repair copy switches to Acme SaaS qualification and promises absent booking.
Two small workflows with one clean, reusable failure pattern.
GPT-5.4 Mini, Janet by ElevenLabs, 199-word prompt and zero active channels.
Contact lookup/create, lead email, offer transfer, forwarding, shared capture, message email, note, FAQ and hangup.
Inbound-only trigger → recording email. Direction filter avoids outbound self-reentry.
One shared block serves No Answer and Outside Hours and stores caller details.
They target the support-email variable but have no selected sender.
The FAQ has no knowledge base and the prompt’s demo-booking promise has no calendar node.
Forwarding failures converge into one capture sequence.
Workflows
BASEMENTS FLOWCALL ENDEDAgent
Prompt BuilderShared KnowledgeForwarding outcomes
Post-call
Ten findings, led by unsafe forwarding and a cross-niche prompt.
Reusable installs can forward calls to unintended external recipients.
Basement service suddenly becomes Acme SaaS demo qualification.
Non-voice sessions can enter forwarding and hangup nodes.
Existing and newly created contacts both notify before qualification.
The agent can improvise unsupported service answers.
Lead and recording notifications cannot send.
No calendar or appointment action exists.
Every inbound call status can cause recording delivery without visible governance.
The reusable business identity is unavailable after install.
Sara, Acme and the selected Janet voice are not aligned.
Repair safety and truthfulness before adding polish.
- 1Clear and remap forwardingImmediate
Remove both source destinations and require a verified setup value plus failure fallback.
- 2Replace the entire prompt contractRequired
Use one basement/foundation persona whose promises match installed actions.
- 3Restrict channel scopeRequired
Run the call workflow only for inbound voice or branch safely before phone-only nodes.
- 4Fix notificationsRequired
Notify only for new/qualified leads and configure approved senders and recipients.
- 5Govern knowledge and recordingsSafety
Attach approved service content and define consent, status filters and retention.
- 6Run synthetic QATest
Test existing/new caller, answered, no answer, outside hours, FAQ uncertainty and post-call handling.
AI Home Solutions audit complete.
The installed assets, flow topology, external dependencies and defects are documented.
Return to the Snapshot Library →