The Challenge
No Bulk SMS API
Google Voice does not expose a bulk messaging API. The only interface for sending SMS is the web UI at voice.google.com. Each message requires navigating to the compose screen, entering a phone number, typing the message, and clicking send. For a client doing outreach at any meaningful volume - 50, 100, 200+ contacts - this is hours of repetitive manual work per batch.
Personalization Requirement
The client was not sending identical messages. Each contact received a personalized message with their name and context-specific content. This ruled out any simple copy-paste approach and required a CSV-driven system that could read per-contact messages.
Mixed Technical Team
The client's team included both developers (comfortable with terminal and Node.js) and non-technical operators (comfortable with browsers but not code). A single delivery format would leave half the team unable to run the automation independently.
Google's Anti-Automation Measures
What We Did
Two-Version Architecture
The system was delivered as two independent, fully functional automation solutions that share identical CSV input format and interaction patterns but use different execution environments:
Version A: Playwright (Node.js) for developers, CI/CD integration, and high-volume use.
Version B: UI.Vision (Chrome Extension) for non-technical operators, quick setup, and ad-hoc use.
The Results
Browser Automation for API-less Platforms
When a service does not offer an API (or the API does not support the needed functionality), browser automation fills the gap. This pattern is directly repeatable for any web-based workflow: CRM data entry, social media posting, form submissions, report downloads, invoice generation from vendor portals.
Dual-Track Delivery (Code + No-Code)
Wonkrew does not just build for developers. Delivering both a code-based and no-code version of the same automation ensures the entire client team can operate independently. This is a repeatable delivery model for any automation project where the end users have mixed technical backgrounds.
Key Takeaway
Browser Automation for API-less Platforms
When a service does not offer an API (or the API does not support the needed functionality), browser automation fills the gap. This pattern is directly repeatable for any web-based workflow: CRM data entry, social media posting, form submissions, report downloads, invoice generation from vendor portals.
Dual-Track Delivery (Code + No-Code)
Wonkrew does not just build for developers. Delivering both a code-based and no-code version of the same automation ensures the entire client team can operate independently. This is a repeatable delivery model for any automation project where the end users have mixed technical backgrounds.