If you've built complex ManyChat automations — not just "comment LINK to get the freebie" but real multi-step flows with external requests, custom fields, conditional logic, and API integrations — this is your job. What You'll Do Per new client: - Build the full ManyChat flow from our architect's flow map and our copywriter's copy - Configure all triggers — keyword triggers, comment triggers, DM ad triggers, story reply triggers - Set up custom fields for lead tracking — buyer stage, objection history, qualification status, conversation state - Wire up External Requests to our AI API — send lead messages out, receive AI responses back, route them correctly - Configure the async webhook pattern — our API processes messages and pushes responses back through ManyChat's Send API - Set up conditional logic and branching — route leads based on classification, custom field values, and conversation state - Build escalation paths — when the AI flags a lead for human handoff, it routes to the right place - Configure compliance triggers — required disclaimers get inserted at the right points - Test every single path end to end before launch — every branch, every edge case, every fallback - Document what you built — if someone else needs to maintain it, they can follow your docs Ongoing: - Implement architecture updates when our review cycle identifies changes needed - Swap in new copy when our copywriter delivers refreshed scripts - Build A/B test variants — duplicate flows with variations, set up split testing - Troubleshoot issues — if a flow breaks or a webhook stops firing, you fix it fast - Maintain and update custom fields and tags as the system evolves - Stay current on ManyChat platform updates — new features, deprecations, API changes What We Need Must have: - Deep ManyChat Pro experience — you've built real flows, not followed YouTube tutorials. You know the platform's quirks and limitations. - External Request / webhook experience — you've connected ManyChat to external APIs and handled JSON responses - Custom fields and conditional logic — you can build branching flows that route based on multiple conditions - Instagram and Facebook DM automation — you know the platform-specific rules and limitations (24-hour window, messaging policies, etc.) - Attention to detail — one wrong connection in a flow means leads get the wrong message or hit a dead end. That can't happen. - Fast turnaround — when we hand you a flow map and copy, we need the build done in 2-3 business days, not two weeks Nice to have: - GHL (GoHighLevel) experience — Phase 2 of our system adds SMS and email flows through GHL - Basic API/JSON understanding — you don't need to be a developer, but you should be able to read a JSON response and map fields correctly - Experience with ManyChat's AI Step and ChatGPT integration — you've used their native AI features - Zapier or Make experience for supplementary automations - Experience in regulated industries — understanding that some messages need disclaimers and some responses need guardrails What You're Not Doing - Designing the conversation strategy or flow architecture (our conversation architect does that) - Writing copy (our copywriter does that) - Configuring the AI engine or writing prompts (our GM and engineer handle that) - Managing client relationships - Analyzing conversation data or making strategic decisions about what to change You build what we design. You build it perfectly. You build it fast. How This Role Works - Contract / per-client basis to start - Remote - Starts with 1-3 client builds while we establish the workflow together - Each new client build is roughly 2-3 days of focused work - Ongoing maintenance is lighter — a few hours per client per month for updates and fixes - As we scale to 10+ clients, this likely becomes a full-time role What a Typical Week Looks Like When onboarding a new client: - Day 1: Receive flow map + copy. Set up the ManyChat account, create custom fields, configure triggers. - Day 2: Build the full flow. Wire up External Requests to our API. Implement all branching logic. - Day 3: Test every path. Fix edge cases. Document. Hand off for final review. Steady state (existing clients): - Implement flow updates from architecture reviews (1-2 hours per client per review cycle) - Swap in new copy when delivered - Monitor for and fix any flow issues flagged by the team - Build A/B test variants as needed