Felix Beta Calls May 13

Felix Beta Calls — Daily Summary Date: Wednesday, May 13, 2026 Generated at 5:00 PM Source: Slack #felixbetacalls Executive Summary Three Felix Beta setup calls were logged today with LRG, Kittle Team, and Chris Vandervalk's team. Overall tone was strongly enthusiastic — Levi at LRG was effusive ("I don't know whether to cry or do a backflip") and Kittle's leadership was already proposing account consolidation around Felix — but every call surfaced the same exec-level theme: Felix's value is real and immediate, while CRM-integration depth and lead-routing controls remain the biggest gates to scale. Top exec takeaway: Felix is converting belief into urgency at the customer, but the next wave of work is plumbing (FUB / Sierra / Salesforce sync, multi-user warm transfers, holiday and pond-level exclusions) and a tightened pre-call account-setup playbook to prevent live troubleshooting eating the session. Cross-Call Themes (from the customer) * Felix is exceeding expectations on day one — prospects don't realize they're talking to an AI, calls are made mid-setup, and customers are surfacing new use cases (e.g., post-appointment accountability) within minutes. (LRG), (Kittle), (Vandervalk) * Tension between Felix's better outreach performance and existing ISA/agent workflows — customers want Felix to win without eroding the agent value proposition or causing collision. (Vandervalk), (LRG) * CRM-sync depth is the universal scale gate: FUB context limits and Sierra sync bugs are the live constraints, with customers consistently asking for tighter, more automated data parity. (Vandervalk), (Kittle) * Customers want more granular control surfaces — holiday blackouts, aggression by lead source, multi-user warm transfers, cash-offer routing overrides, and pond/segment-aware exclusions. (LRG), (Kittle), (Vandervalk) * 10 DLC SMS approval remains the shared near-term blocker that keeps Felix calling-only for the first week post-setup. (LRG), (Kittle), (Vandervalk) Recurring Questions, Concerns & Sticking Points * "Felix could lead to agents bypassing their internal systems, thereby eroding their business's value" — Vandervalk's lead concern, mirrored by EmpowerHome-style worries about Felix not knowing what ISAs are already doing. (Vandervalk) * "We've just had some issues with Fello syncing with Sierra lately… there's a support ticket out for that currently" — live CRM sync reliability is the customer's most concrete pain on Kittle's call, and a similar FUB-side gap blocks Vandervalk. (Kittle), (Vandervalk) * Lead-routing granularity is the most-requested control: multi-user warm transfers, cash-offer overrides, and pond-aware exclusions all came up unprompted. (Kittle), (Vandervalk) * "Is there anything for holidays or is this something that we just have to get in there and manage in real time?" — calendar/blackout controls and aggression-by-lead-source are both gaps for power users. (LRG) * Live account-setup bugs are eating session time — Vandervalk couldn't see Felix's call activity during the call and required Tom's in-flight intervention. (Vandervalk) Suggested Improvements — Call Structure & Setup * Run a pre-call account / login / permissions check (Felix dashboard access, email correctness, viewer permissions) the day before each beta setup so live troubleshooting doesn't consume the session. (Vandervalk) * Add a CRM sync-health verification step to the setup script (FUB and Sierra both): confirm assigned-user sync, tag application, and notes routing before going live; flag known support tickets up front. (Kittle), (Vandervalk) * Bring a deeper FUB / CRM context walkthrough into the agenda — what data Felix uses, why some attributes are intentionally excluded, and where signal score draws from — Chris asked for exactly this for future meetings. (Vandervalk) * Standardize a short video explainer for customers to forward to their teams so adoption doesn't bottleneck on the primary contact. * Pre-stage the warm-transfer / fallback plan (multi-user list, cash-offer routing, fallback recipient) so it isn't designed mid-call. (Kittle) Calls Logged Today Time (local) Customer / Call Headline 09:55 MDT · 60m LRG — Levi Rodgers Levi sold himself on Felix in real time, proposing scale to millions of contacts and a net-new internal accountability use case; requested holiday blackouts and lead-source aggression controls. 15:45 MDT · 61m Kittle Team — Rob Kittle Strong adoption with handoff achieved during the call; Fello-Sierra sync issues and cash-offer routing surfaced as the top product gaps, with multi-user warm transfers requested. 16:45 MDT · 85m Chris Vandervalk's team Buy-in won, but account-setup bug and FUB integration depth dominated the call; Chris flagged agent-bypass risk as the strategic concern and asked for clearer FUB-context and A/B voice testing. Voice of the Customer * Strong enthusiasm and rapid belief: "This is hot. Like I'm, my wheels are spinning. It's actually going wild… right now" and "I don't know whether to cry or do a backflip man. Like I'm I believe" — Levi is fully sold and already imagining scale to millions of contacts. (LRG) * Customers spontaneously personifying Felix and pushing it into new internal use cases — Levi suggested hiring "Felix LRG" and using Felix for post-appointment agent accountability. (LRG) * Excitement tempered by workflow-protection concerns: Chris explicitly worried Felix could erode their business's value if agents bypass internal systems to go directly to Fello. (Vandervalk) * Live-call validation moments landed hard: "He's already getting after it. Yeah, he is rob, you better put those margaritas down, man" — Felix making calls during setup is consistently the believability moment. (Kittle), (Vandervalk) * Explicit asks across calls clustered around CRM context, routing, and controls — FUB integration depth and A/B voice testing (Vandervalk); cash-offer override routing and multi-user warm transfers (Kittle); holiday blackouts and aggression by lead source (LRG). Effort * All three setups required hands-on Fello guidance through persona, business context, segments, exclusions, outreach windows, and warm-transfer configuration — LRG called the onboarding "very smooth," but Kittle and Vandervalk both consumed material Fello effort. (LRG), (Kittle), (Vandervalk) * Live troubleshooting ate session time on Vandervalk's call: Tom had to fix Chris's email/account access mid-call so he could see Felix's activity, and Ryan offered to join Andrew's follow-up to ensure ownership. (Vandervalk) * Open support tickets carried into the call on Kittle: Fello-Sierra sync issues and a condensed contacts-tab display — both acknowledged and tracked, but visible to the customer. (Kittle) * Forward effort committed: holiday-exclusion feature build (LRG), multi-user warm transfers (~1 week) (Kittle), and a deeper account-setup review for future Vandervalk meetings (Vandervalk). Journey to Thresholds * Felix went live during all three calls; LRG and Kittle are on track for the 24-hour handoff milestone (Kittle had a handoff during the call), and Vandervalk had a successful first Felix call where the prospect didn't realize they were speaking to an AI. (LRG), (Kittle), (Vandervalk) * Enrollment volume is healthy: LRG enrolled 200K marketing + 5K sales contacts; Vandervalk staged 10K contacts (5K unassigned) with a continuously-replenishing 5K working set. (LRG), (Vandervalk) * Universal near-term blocker: 10 DLC SMS approval is pending across all three (expected within ~1 week for Vandervalk; up to 10 days elsewhere) — full multi-channel engagement is gated on it. (LRG), (Kittle), (Vandervalk) * Operational sticking points: Kittle's Sierra sync affects warm-transfer assigned users; Vandervalk's account-setup bug blocked Felix activity visibility until fixed mid-call. (Kittle), (Vandervalk) * Sales agent dashboard is live (Vandervalk); Fello team is actively seeking feedback on funnel metrics and useful data — a signal the dashboard is ready for exec-level visibility. (Vandervalk) Customer Behavior * Customers are actively configuring Felix in-session — building exclusions, naming the AI, choosing personas, monitoring early activity, and curiously requesting to hear recordings; Felix is treated like a new hire being onboarded. (LRG), (Kittle), (Vandervalk) * Strategic targeting choices skew toward lower-risk pools first: Andrew is sending Felix at less-active leads with intent to expand; Vandervalk's ISA teams are seeing leads pulled into Felix because of better outreach/conversion. (Vandervalk) * Customers are already imagining operational consolidation around Felix: Rob considered merging cash-buyer and Kittle Real Estate accounts; Levi proposed a dedicated "Felix LRG" headcount. (Kittle), (Vandervalk), (LRG) * Customers are open to autonomy: Levi prefers Felix run with latitude rather than be over-scripted; teams are inviting Felix to surface leads their ISAs aren't actively engaging. (LRG), (Vandervalk) Felix Product Feedback * CRM integration depth is the biggest product theme: FUB context is intentionally limited for control / system pressure, custom attributes are planned with controlled integration, and Sierra two-way sync is unreliable with an open ticket — Tom proposed a workflow to update Sierra assigned users when Felix engages, bypassing native sync. (Vandervalk), (Kittle) * Multi-user warm transfers are the single most-requested ship-now feature on Kittle, with ETA within the week; cash-offer routing override (e.g., route directly to Teresa and Jenny) was also explicitly requested. (Kittle) * Granular control gaps surfaced: holiday-blackout dates (planned), aggression by lead source, and the ability to instruct Felix to focus on specific stages like "nurture" or "attempted contact" while excluding generic "lead" status. (LRG), (Vandervalk) * Voice / persona: A/B testing male vs. female voices is supported, but mid-conversation switching isn't ideal and current preference data is statistically insignificant; customization of Felix's self-identification at handoff is intentionally limited to preserve human-like interaction. (Vandervalk), (LRG) * UI / data accuracy: total enrollment counter is currently inaccurate during beta (fix expected); account-setup edge case bug required manual intervention to restore Felix activity visibility. (Kittle), (Vandervalk) * New use case proposed: Felix for internal post-appointment agent accountability — worth a product-side feasibility look. (LRG) Red Flags * Strategic risk: Chris explicitly worried Felix could erode their business's value if agents bypass their internal systems to go directly to Fello — needs an exec-level positioning answer, not just a feature. (Vandervalk) * CRM workflow mismatch: FUB data integration scope is narrower than the customer expected, and Sierra two-way sync is unreliable enough to impact warm-transfer assignment — both are blocking confident scale. (Vandervalk), (Kittle) * Live bug blocking core flow: Chris was unable to see Felix's call activity due to an account-setup issue and required mid-call intervention — recurrence will erode trust quickly. (Vandervalk) * Confidence in inherited account setup: Chris stated he doesn't feel great about inherited settings and regrets not starting from scratch — proactive account-health review recommended. (Vandervalk) * Routing-design mismatch: Rob's cash-offer override request and the contacts-tab display bug both indicate Felix's current design doesn't yet match the customer's desired lead routing and visibility model. (Kittle)