How Bigbox went live on Customer.io in 15 days with Hyppo 

Bigbox and Hyppo, a Buenos Aires-based data & growth agency and official Customer.io partner, stood up a complete, production-ready Customer.io setup across five countries in fifteen days, then built a multi-country messaging operation on top of it.

• Bigbox ran email and WhatsApp internally, with no platform tying its five countries together
• Bigbox and Hyppo prioritized full technical onboarding before launching a single campaign
• The Customer.io setup went live across five countries in 15 days
• One flow library, built in Design Studio, replicated across five markets
• New phone-capture, churn, and A/B testing work followed two months later
• The next phase is deeper personalization and automation across the lifecycle

Bigbox is one of Latin America's largest experience-gift companies, with a strong presence across Argentina, Chile, Uruguay, Peru, and Mexico. Email and WhatsApp were already running, handled internally through a mix of tools operated by the product team, and the core flows worked. What the business didn't have was a platform built to match its ambition: lifecycle logic that treats new buyers, loyal customers, and churned users as distinct audiences, replicated cleanly across every country Bigbox operates in.

That's the gap Bigbox closed by moving its messaging onto Customer.io, with Hyppo brought in to lead the build.

The brief Bigbox and Hyppo set together was specific, and it wasn't the usual one. Most onboardin is a race to start messaging the full base as fast as possible. Bigbox and Hyppo optimized for something else first: get fully onboarded and technically operational, across every market, in fifteen days.

That meant every integration connected to Customer.io, all five country workspaces built inside it, data syncing correctly, sender domains and phone numbers validated, and the first flow live and checked against the existing system, before anything else got built. The goal was a Customer.io foundation solid enough to build on with confidence, not a quick demo.

The fifteen-day build moved in tight, overlapping stages, all inside Customer.io.

Days 1–5: While contracts, the DPA, and billing were coordinated with Bigbox's finance team, Hyppo set up Bigbox's Customer.io domain and mapped the work ahead: sync queries for attributes and formats, the per-country workspace structure, email deliverability testing, template creation, the first flow build, and event tracking through GTM feeding into Customer.io.

Days 6–10: Hyppo used Customer.io to replicate Regalendario, one of Bigbox's signature features, which lets users save important dates and get reminded ahead of time with relevant offers. Rebuilding it inside Customer.io was the natural starting point once data access was established and the sync queries were running.

Days 11–15: The WhatsApp sending number was validated inside Customer.io, the Regalendario campaign was switched on and confirmed to be running correctly, and Bigbox retired its own version of the flow on the next deploy. Fifteen days after kickoff, Bigbox had a Customer.io setup that was connected, validated, and live in production, across all five countries.

In the weeks after, the same discipline continued inside the platform: additional country phone numbers were validated for WhatsApp one by one, GTM event tracking was refined, and the team began wiring up real-time event data inside Customer.io for the campaigns that came next.

Once the Customer.io foundation was live, Hyppo made a deliberate choice: build a focused set of things and get them right, rather than launch broadly and fix issues later.

Every template was built in Design Studio, Customer.io's HTML email builder, to a high standard. Hyppo started by replicating what Bigbox already had, buyer onboarding, recipient onboarding, and one-off campaigns for occasions like Mother's Day and Father's Day, so results could be measured against the previous system before anything expanded.

Because every one of the five workspaces runs the same flow library inside Customer.io, an improvement made in one market carries cleanly to the others. Replication became a repeatable process inside the platform rather than five separate builds from scratch.

Two months after going live, the work shifted from replication to creation, all built on the Customer.io foundation Hyppo had put in place. The core flows now run across all five countries, and new work in progress includes flows to capture phone numbers from more users, dedicated strategies for churned users built around how each audience behaved while active, and brand-education onboarding for the full user base.

The team is also testing more sophisticated mechanics inside Customer.io: split branches, A/B tests, and calibrating the right volume of WhatsApp messages and discounting for each audience.

None of this is outsourced and forgotten. Hyppo works alongside Bigbox's growth function as an extension of the team, inside Customer.io, on integrations, on existing flows, and on everything new. Bigbox brings the growth expertise, Hyppo builds and executes alongside it, and Customer.io is the platform both teams build on.

The direction from here is deeper impact at every stage of the customer lifecycle: more campaigns, more measurement, more automation, and more personalization, tuned to how Bigbox's business actually works. The fifteen-day foundation Hyppo built inside Customer.io is what makes that next phase possible.

• 15 days from kickoff to a connected, validated Customer.io setup live in production
• 5 country workspaces: Argentina, Chile, Uruguay, Peru, and Mexico, each running the same flow library
• 3 channels live: email, in-app, and WhatsApp, built in Design Studio and validated market by market
• 1 flow rebuilt: Regalendario, replicated inside Customer.io, matched against the previous system, and switched on in production