Five problems, five working systems.
Client names are withheld; the problems and the solutions are real. Each one was built for a multi-brand consumer products company running Zoho alongside AWS and third-party messaging vendors.
-
Challenge: A holding company launching several consumer brands needed SMS marketing that would survive TCPA and 10DLC scrutiny, with each brand texting from its own number and contacts able to subscribe to more than one brand.
Solution: A hybrid architecture: Zoho Creator as system of record and admin UI, AWS for the compliance-critical edges, and the SMS vendor for delivery. Built in AWS CDK (TypeScript) with Lambda, EventBridge, an append-only DynamoDB consent log with point-in-time recovery, SSM-secured credentials, and CloudWatch/SNS alerting.
Result: Consent is captured at the source and tagged by origin (form, keyword, waitlist, import). Opt-out suppression is authoritative at the infrastructure layer, keyed by E.164 phone. Adding a brand spins up its own sync path with no hand-built code. Designed for a dozen-plus brands from day one.
-
Challenge: A no-code Zoho Flow integration between the SMS platform and Zoho Marketing Automation was blocked by an opaque vendor error.
Solution: Re-platformed to AWS Lambda with a single controlled write path, per-brand numbers for carrier-scoped STOP handling, and a DynamoDB consent/send log. Established a working webhook payload contract and resolved the original Flow failures along the way.
-
Challenge: The SMS reseller couldn’t isolate opt-outs per brand, a hard compliance requirement once customers could join several brands.
Solution: Evaluated plan changes, separate workspaces, and alternative providers; negotiated a direct vendor contract with the required opt-out add-on; coordinated legal, finance, and CFO sign-off. Planned the cutover with full contact and list backups, message history preserved, and numbers and 10DLC registration ported last to avoid campaign disruption. Voice service stayed with the original partner to protect that relationship.
-
Challenge: Every brand’s customers received support email from a single corporate identity, and a form-based follow-up flow was reopening closed tickets.
Solution: Branded send-from addresses for six brands with DNS (SPF/DKIM) and mailbox routing coordinated with IT; a ticket-level Brand attribute driving templates, workflows, and reporting; branded auto-replies and closed-ticket emails in five languages using SLA-safe workflow alerts instead of autoresponders; the email-to-form flow rebuilt so submissions against closed tickets create new ones, tested in parallel before cutover; and an issue-type model built for dozens of incoming brands without breaking legacy reporting.
-
Challenge: Marketing ran a flavor-vote SMS campaign with no way to measure responses.
Solution: A scheduled Zoho Flow + Deluge sync pulling messages from the SMS platform’s API (48-hour lookback, idempotent upsert) into Zoho Analytics, with query tables and a live vote dashboard. Tallied roughly 137 unique respondents for the launch, then generalized to serve multiple brands from one flow. Built low-code on purpose so the team wasn’t waiting on engineering capacity.