Onboarding · Smerio

From a test sender to production

A visual preview, a real test message and a production launch are three different milestones.

Start by separating the milestones

A preview shows how a message could look. A test sender lets you exercise a real messaging integration with invited test devices. A production launch enables an approved sender to reach supported users on approved networks.

These milestones answer different questions: does the experience make sense, does the integration work, and is the sender ready for the target market?

What can come from a company website?

A website can be a starting point for a sender draft: the brand name, a description, a logo and contact or policy links. Extracted information still needs customer review. A public website does not establish permission to act for a brand or consent to message its customers.

Smerio’s planned onboarding uses this distinction: suggest what can be found, show the source, and ask the customer to confirm what matters.

A real test requires an invited device

Google’s test flow requires the recipient to accept an invitation before interacting with an unlaunched agent. That makes testing useful for checking content, user interactions and events before production approval.

A preview should remain available independently of the invitation. It should not display a successful test message unless a real send has occurred. See Google’s test-device setup.

Production introduces brand and carrier approval

A production launch includes brand verification and launch approval by Google, carriers or both. Carrier-managed networks can have additional requirements. Approval is specific to the networks involved; it is not a universal switch for every country.

Choose the initial market and use case, prepare the required information, and make the current approval status visible. Google’s launch overview describes these separate steps.

Should production use a new sender?

That is a workflow decision to validate with the provider. A separate production sender can make the transition explicit, but creating a new sender should not be presented as a universal requirement. Copy only reviewed information and recheck the production requirements.

Measure time to understanding and time to delivery

Measure preview completion, invitation acceptance and the first real delivery separately. Then measure production preparation and approval time. This shows which parts of onboarding the product can improve and which depend on external review.

We’re building Smerio around these steps. Share your onboarding requirements.

What should we explain next? Send us your feedback.