salesforce elevenlabs project
Budget: $250 – $750 USD
OVERVIEW
Both projects use ElevenLabs (Twilio-backed) to automate outbound calls from Salesforce. They share the same org and Phone_Number__c custom object but have independent codebases and agents.
Project A (elevenlabs-salesforce): An LWC on the Contact record lets users trigger a live AI call or drop a personalized cloned-voice voicemail.
Project B (elevenlabs-verify): An LWC lets users bulk-verify Contact phone numbers. An AI agent calls them, determines the status, and updates Salesforce via webhook.
CURRENT STATUS
Project A: Live calls work and log as Tasks. However, the core voicemail drop feature is broken (selecting a VM script incorrectly routes to the live agent).
Project B: The end-to-end verification loop (LWC, Apex, Webhook, ElevenLabs Agent) is fully functional for both sequential and parallel modes.
REMAINING WORK
Project A (High Priority):
1. Fix VM Drops: Create a VM Drop Agent, enable voicemail detection, and fix routing logic in Apex.
2. Security: Move hardcoded API credentials to Custom Metadata.
3. Personalization: Inject Ascendix property data into VM scripts.
4. Polish: Customize prompts, remove deprecated Flow, add Jest tests, and improve UI errors.
Project B (Lower Priority):
1. Security: Move hardcoded API credentials to Custom Metadata.
2. Enhancements: Add List View bulk verification, auto-retry for "No Answer", upgrade to Platform Events, and refine prompts.
REQUIREMENTS & ACCESS
Skills: Salesforce Apex, LWC, REST APIs/Webhooks, ElevenLabs AI, and Twilio. Nice to have: SFDX, Jest, and Ascendix.
Access: You will receive Admin access to the Production org, full ElevenLabs dashboard access, and GitHub repo access.
ARCHITECTURE & FLOW
Project A: LWC calls Apex -> Apex POSTs to ElevenLabs -> Twilio Call -> Task logged.
Project B: LWC calls Apex -> Apex POSTs to ElevenLabs -> Call -> Webhook to Salesforce Site -> Apex HMAC Validation -> DB Update -> LWC refresh.
Agents: Each project uses distinct Agent IDs, Phone Numbers, and Phone Number IDs. Only Project B utilizes a webhook URL.
KNOWN ISSUES & GOTCHAS
Security: API keys and weak webhook secrets are hardcoded and must be secured immediately.
Deployments: You must use RunSpecifiedTests during deployment due to unrelated org errors.
Testing: Neither project currently has LWC Jest tests.
Data: Do not overwrite the existing Phone_Number__c object during deployment.
Permissions: The webhook runs without sharing; the Site Guest User needs CRUD on Phone_Number__c.
Both projects use ElevenLabs (Twilio-backed) to automate outbound calls from Salesforce. They share the same org and Phone_Number__c custom object but have independent codebases and agents.
Project A (elevenlabs-salesforce): An LWC on the Contact record lets users trigger a live AI call or drop a personalized cloned-voice voicemail.
Project B (elevenlabs-verify): An LWC lets users bulk-verify Contact phone numbers. An AI agent calls them, determines the status, and updates Salesforce via webhook.
CURRENT STATUS
Project A: Live calls work and log as Tasks. However, the core voicemail drop feature is broken (selecting a VM script incorrectly routes to the live agent).
Project B: The end-to-end verification loop (LWC, Apex, Webhook, ElevenLabs Agent) is fully functional for both sequential and parallel modes.
REMAINING WORK
Project A (High Priority):
1. Fix VM Drops: Create a VM Drop Agent, enable voicemail detection, and fix routing logic in Apex.
2. Security: Move hardcoded API credentials to Custom Metadata.
3. Personalization: Inject Ascendix property data into VM scripts.
4. Polish: Customize prompts, remove deprecated Flow, add Jest tests, and improve UI errors.
Project B (Lower Priority):
1. Security: Move hardcoded API credentials to Custom Metadata.
2. Enhancements: Add List View bulk verification, auto-retry for "No Answer", upgrade to Platform Events, and refine prompts.
REQUIREMENTS & ACCESS
Skills: Salesforce Apex, LWC, REST APIs/Webhooks, ElevenLabs AI, and Twilio. Nice to have: SFDX, Jest, and Ascendix.
Access: You will receive Admin access to the Production org, full ElevenLabs dashboard access, and GitHub repo access.
ARCHITECTURE & FLOW
Project A: LWC calls Apex -> Apex POSTs to ElevenLabs -> Twilio Call -> Task logged.
Project B: LWC calls Apex -> Apex POSTs to ElevenLabs -> Call -> Webhook to Salesforce Site -> Apex HMAC Validation -> DB Update -> LWC refresh.
Agents: Each project uses distinct Agent IDs, Phone Numbers, and Phone Number IDs. Only Project B utilizes a webhook URL.
KNOWN ISSUES & GOTCHAS
Security: API keys and weak webhook secrets are hardcoded and must be secured immediately.
Deployments: You must use RunSpecifiedTests during deployment due to unrelated org errors.
Testing: Neither project currently has LWC Jest tests.
Data: Do not overwrite the existing Phone_Number__c object during deployment.
Permissions: The webhook runs without sharing; the Site Guest User needs CRUD on Phone_Number__c.