Description
Summary We have a production multi-channel AI reception system ("GAEL") already live, built on n8n + Claude API (Anthropic). It currently runs three channels — voice (LiveKit + Deepgram + ElevenLabs), a website chat widget, and email (IMAP/SMTP) — all feeding into a shared qualification and routing engine: Claude-based lead scoring and multi-program routing (leads are routed to one of several qualification tracks with dedicated nurture sequences) ActiveCampaign as CRM — contact creation, tagging, nurture automation PostgreSQL (self-hosted, EU server) as the system of record for conversations A "thin lead" recovery system for incomplete/low-signal contacts A follow-up email scheduler for leads that haven't converted We want to add WhatsApp as a fourth channel, fully integrated into this existing architecture — not a standalone bot. WHAT WE NEED WhatsApp Business API integration (your recommendation: Meta Cloud API direct vs. a provider like Twilio/360dialog — please state your preferred approach and why in your proposal) n8n workflow(s) to receive and send WhatsApp messages, following the same pattern as our existing email workflow (single workflow routes by client config, not hardcoded per client) Claude API integration for message classification and response generation, matching tone/logic already used on the email channel Messages and outcomes feed into the same qualifier/scoring/routing logic already in place — WhatsApp leads should land in the same ActiveCampaign tagging structure and nurture tracks as the other channels Conversations logged to the existing PostgreSQL store, consistent with voice/chat transcript logging Handles the 24-hour session window and template-message requirements of the WhatsApp Business API correctly (for messages sent outside the customer-initiated window) Should work with the existing thin lead recovery and follow-up scheduler logic where applicable to WhatsApp conversations WHAT STAYS THE SAME (DO NOT REBUILD) Voice, chat widget, and email channels — untouched Qualification scoring logic and multi-program routing — reused, not duplicated ActiveCampaign tagging structure — reused Client config file architecture — WhatsApp config (number, API credentials, templates) should live in the same per-client config file pattern, no hardcoded values WHAT WE PROVIDE Access to the existing n8n instance and relevant workflows for reference Claude API key ActiveCampaign API access WhatsApp Business Account / Meta Business Manager access (or guidance on what you need us to set up) WHAT TO INCLUDE IN YOUR PROPOSAL Your recommended WhatsApp API approach (direct Meta Cloud API vs. BSP provider) and why Fixed price quote Estimated timeline Relevant experience integrating WhatsApp Business API with n8n and/or Claude/LLM-based agents Any open questions you'd need answered before finalizing the quote DELIVERABLES Working WhatsApp channel integrated end-to-end into the existing system n8n workflow(s) exported as JSON Brief documentation: how the WhatsApp flow works, config fields, template message setup Short handover call if needed