← All work
Case StudyTier AProductionMar 2025
Batch Messaging Delivery System
Personalized SMS batching through an Android phone/SIM gateway with normalization, structured logs, retries, and rate controls.
ProductAutomationTechnical
Evidence
~5,000 personalized sends
Context
Mar 2025 · Real campaign use · Maturity: Production.
Problem
A real campaign required sending personalized messages to thousands of contacts while controlling rate, failures, and data quality.
Users
Campaign operators and message recipients.
My Role
Personal automation/product — design and implementation.
Product Decisions & Responsibilities
- Defined batch/retry behavior and operational observability.
- Connected contact preparation to messaging execution.
Technical Approach
- Built Python REST integration, batching, normalization, logging, retry, and rate-limiting workflows.
PythonREST APICSV/ExcelDockerLoggingRate limiting
Constraints
- Gateway API queue status did not equal carrier delivery confirmation.
- Phone/SIM gateway throughput required controlled sending.
Product Flow
- Load contacts
- Normalize/personalize
- Batch & rate-limit
- Send through gateway
- Log/retry
Outcome
- Personalized sends to ~5,000 contacts in a real campaign.
What I Learned
- Operational status semantics must be precise; queued is not delivered.
Evidence Boundary
What this does — and does not — prove
No final carrier-delivery rate is claimed because API “Pending” represented queue status.
Next Iteration
Extend the product only after the next decision can be tied to stronger user, operational, or business evidence rather than adding features for their own sake.