Integration · Welcome Call
AI Video KYC and Identity Verification for Solar Financing Deals
Call Pilot's AI-powered video KYC verifies a solar customer's identity against a government-issued ID using facial recognition — producing lender-compliant documentation stored on the SubcontractorHub proposal record. Built for solar contractors whose financing partners require identity verification beyond e-signature.
What Connects Between Call Pilot and SubcontractorHub
The specific data flows that eliminate double entry and keep both systems current without extra work from your team.
Post-Signature KYC Trigger
When a solar customer signs a SubcontractorHub proposal that requires identity verification, Call Pilot automatically initiates the video KYC session via an SMS link sent to the customer's mobile number. The customer completes the verification on their own device — photographing their government ID and completing a facial liveness check — without rep involvement. Automated KYC trigger eliminates the rep coordination step that creates delays and gaps in identity verification completion.
Facial Recognition Against Government ID
Call Pilot's AI compares the customer's live selfie to their submitted government ID photo and produces a verification confidence score — the result and the supporting documentation (ID image, selfie, match score) store permanently on the SubcontractorHub proposal record. Lenders requiring KYC documentation for solar loan approval receive a complete verification package from the SubcontractorHub record without additional steps. Identity verification failure flags are immediately visible on the proposal for rep follow-up.
Lender Compliance Documentation Package
Call Pilot's verification output — ID scan, liveness check video, match score, and verification timestamp — is formatted to meet the Know Your Customer documentation standards required by regulated solar financing partners. The compliance package attaches to the SubcontractorHub proposal and is retrievable by lenders via secure link or direct API push to the loan origination system. Having pre-formatted lender-compliant KYC documentation on the SubcontractorHub record reduces per-deal review time at the lender by an average of two to three business days.
Verification Status on Proposal Timeline
Call Pilot syncs verification status updates to SubcontractorHub in real time — not started, link sent, in progress, completed (pass/fail) — so the finance coordinator can see KYC status alongside proposal signature status on the same project record. Deals where KYC is incomplete are visible in SubcontractorHub's pipeline view without requiring a separate Call Pilot dashboard check. Pipeline stage progression can be gated on KYC completion status for contractors whose workflow requires verification before permit submission.
How to Connect Call Pilot with SubcontractorHub
Connect Call Pilot Account
In SubcontractorHub integrations, select Call Pilot and authenticate using your Call Pilot business account credentials to establish the API connection.
Set KYC Trigger Rules
Configure which SubcontractorHub proposal types (by financing product or lender) trigger a Call Pilot KYC session automatically after signature.
Customize Verification Flow
In Call Pilot, configure which ID types are accepted, the verification language (English/Spanish), and the lender-specific documentation format required.
Test End-to-End Flow
Complete a test verification using a team member's ID to confirm the full workflow — SMS trigger, verification completion, documentation storage on SubcontractorHub proposal record — before using with customers.
Ready to connect Call Pilot?
Book a 30-minute demo — we'll show you exactly how the integration works and walk you through setup for your account.
Who Uses the Call Pilot Integration
High-Fraud-Risk Market Identity Verification
Solar contractors operating in markets with documented solar contract fraud — where third parties sign customers up without their knowledge — use Call Pilot's liveness check to confirm the person completing the verification is present and consenting, not signing remotely using someone else's information. The liveness detection video, stored on the SubcontractorHub proposal record, is a meaningful deterrent and documentation tool against fraudulent contract claims. Identity fraud exposure is a significant legal and financial risk for solar contractors that KYC verification directly mitigates.
Streamlining Mosaic and Other KYC-Requiring Lenders
Certain solar loan products require customers to complete a KYC step before loan funds are released. Without integration, this means the finance coordinator emails the customer a separate KYC link, tracks completion in a spreadsheet, and manually informs the lender when it's done. Call Pilot's SubcontractorHub integration automates the trigger, tracking, and documentation in one workflow — reducing finance coordinator time per deal from 20 minutes to under two minutes. At 30 deals per month, that's 9 hours per month recovered for higher-value work.
Spanish-Language KYC for Bilingual Markets
A solar company serving Spanish-speaking homeowners in Southern California uses Call Pilot's Spanish-language verification flow to conduct KYC in the customer's primary language — ensuring the verification is fully understood and legally defensible rather than completed by a customer who didn't fully understand the English-language instructions. Spanish-language KYC reduces verification failure and abandonment rates in bilingual markets where English-only workflows create friction and compliance risk.
Lender Direct API Push for Fast Funding
A solar company working with financing partners that have direct Call Pilot API integrations uses the SubcontractorHub–Call Pilot connection to push verified customer documentation directly to the lender's origination system the moment verification is complete — without finance coordinator involvement. Lenders with direct document intake process these deals in hours rather than days compared to email submission. Fast funding cycle improvement is one of the most impactful operational benefits in high-volume solar installation businesses.
Common Questions About the Call Pilot Integration
How does Call Pilot differ from SCH Welcome Call?
SCH Welcome Call is a verbal agreement verification — the AI avatar confirms the customer understands what they signed. Call Pilot is identity verification — it confirms the person who signed is who they say they are, by checking their face against a government ID. Some lenders require both: proof of agreement (welcome call) and proof of identity (KYC). They serve complementary but distinct compliance purposes and can both be active on SubcontractorHub simultaneously.
What government IDs does Call Pilot accept for verification?
Call Pilot accepts U.S. and Canadian driver's licenses, state-issued ID cards, and passports. Foreign national IDs may have limited acceptance depending on the issuing country and the lender's specific requirements. The accepted ID types are configurable in Call Pilot's verification settings — contractors whose financing partners have specific ID requirements configure those restrictions in the Call Pilot portal.
What happens if a customer's identity verification fails?
A failed verification flags the SubcontractorHub proposal record immediately and creates a follow-up task for the finance coordinator. The coordinator reviews the failure reason (ID couldn't be read, facial match below threshold, liveness check failed) and works with the customer to retry or obtain alternative verification documentation. Lenders are not notified of failed attempts — only successful verifications are pushed to lender documentation packages.
Is the customer's ID image stored permanently in SubcontractorHub?
Call Pilot stores verification documentation according to their data retention policy, which is configurable per your Call Pilot account settings. SubcontractorHub stores only the verification result summary (pass/fail, timestamp, verification ID) and a reference link to the full documentation in Call Pilot — the actual ID image and video are stored in Call Pilot's compliant document vault, not in SubcontractorHub. This limits sensitive identity document exposure to the minimum necessary systems.
Does Call Pilot work in all 50 states or are there regulatory restrictions?
Call Pilot operates across all 50 U.S. states. Biometric data collection laws in Illinois (BIPA) and Texas require specific consent language before facial recognition processing — Call Pilot's verification flow includes compliant consent screens for those states automatically. Contractors in Illinois and Texas should confirm their Call Pilot account is configured for state-specific compliance before activating KYC verification for customers in those states.
Connect Call Pilot with SubcontractorHub
Your team keeps working in the tools they know. SubcontractorHub ties them together so nothing falls through the cracks.
Book a Free Demo