Multi-Portal Lead Engine
Apps Script pipeline parsing leads from 8+ property portals into Google Sheets, Telegram, and GHL via direct API calls.
Hi, I'm Mark Jensen A. — AI Automation Specialist and WordPress Developer. I ship workflows, integrations, and chatbots that connect your stack and turn AI into measurable ROI.
I'm Mark Jensen A. — AI Automation Specialist and WordPress Developer based in Manila. Two years shipping production websites and automation systems, with a focus on real estate and multi-niche client work.
From multi-portal lead pipelines and CRM workflows to AI chatbots, custom integrations, and full WordPress builds — I optimize for hours saved and revenue created, not features shipped.
Tools I reach for daily — from AI builds to client websites and team operations.
Reasoning agents and multi-step workflows that connect every tool in your stack.
Production websites — from custom builds to hosting, DNS, and email deliverability.
Daily-driver tools and internal-ops setups that keep teams running smoothly.
A snapshot of recent systems — each one running in production, with metrics to back it up.
Apps Script pipeline parsing leads from 8+ property portals into Google Sheets, Telegram, and GHL via direct API calls.
Replaced a paid white-label SaaS with a native GHL Conversation AI build — country-specific intents and auto-handoff.
Country-specific round-robin assignment, AI-drafted follow-ups, and SMS/email sequences across a 6-agent team.
VoIP migration with n8n-powered call logging, Telegram alerts, and CRM sync — replacing a pricey enterprise platform.
WordPress + Houzez build with automated XML feed imports for international listings — deployed on Kinsta with full CDN.
Inbox-warmed cold email infrastructure with SPF/DKIM/DMARC, dynamic personalization, and reply detection.
The full story behind the numbers — what was broken, what got built, what changed.
An international property agency was bleeding leads from 8 different portals because every email format was different and inbox handling was manual.
Inbound leads from 8 property portals arrived as differently-formatted emails. Agents copy-pasted them into the CRM by hand — frequently dropping leads on weekends. Zero analytics on which portal actually converted.
I built an Apps Script parser that watches a shared inbox, normalizes every portal's lead format into a unified schema, and pushes directly to the CRM via REST API (skipping fragile webhook layers). Country-specific round-robin assignment with instant Telegram + SMS alerts to the owning agent.
Zero leads dropped over 90 days. Average time-from-lead-to-first-contact dropped from 4 hours to under 30 seconds. Booking rate climbed 3.4× as agents could act on leads while still warm.
A growing business was paying monthly for a third-party AI nurturing tool — but locked out of customization and bottlenecked by their pricing tiers.
The white-label nurturing SaaS was opaque: no way to tune intent classification, no clean handoff to human agents, and a roadmap that didn't match the team's needs. Cost grew with every contact added.
Migrated to a native GHL Conversation AI build with country-specific intent flows, custom data tags, and a confidence-threshold escalation model that hands off to the right rep with full context preloaded.
Recurring SaaS bill eliminated. Full ownership of prompts, data, and the upgrade path. Handoff quality measurably improved — agents stopped re-asking questions the AI had already answered.
Every engagement starts with a problem worth solving. Here's where I plug in.
End-to-end automation: trigger → reasoning → action. Orchestrated across your full stack with monitoring and graceful failure modes.
Domain-trained AI agents for support, sales, or internal ops. RAG-backed, multi-turn, with human handoff when it matters.
Custom connectors when off-the-shelf tools fall short. Bidirectional sync, retry logic, and clean schemas you can build on.
I audit your existing stack, find the manual loops, and replace them — measured against the hours-saved metric you actually care about.
No mystery. No bloated discovery decks. Four steps, designed to ship.
Map your current stack, surface bottlenecks, agree on the metric we're moving.
Architect the system on paper first — flow diagrams, tool choices, fallback paths.
Ship in tight iterations. Real data, real edge cases, real users — from day one.
Measure, refine, expand. The system gets smarter every month it runs in production.
A few words from teams I've shipped automation for.
The lead-routing system paid for itself in the first month. We finally stopped losing leads on weekends, and our agents now spend their time selling instead of copying spreadsheets.
I expected a chatbot. I got a support team that doesn't sleep. Resolution rate jumped past 60% within two weeks of launch — and the handoffs to my human agents are seamless.
Rare combo: deeply technical and weirdly business-minded. Every system shipped came with a clear ROI story. We've now automated four workflows we didn't even think were automatable.
Tell me what's eating your team's hours. I'll come back within one business day with a clear path forward — or an honest "this isn't a fit."