Klaviyo build

Built in Klaviyo, live on a yes

The approved emails, built inside the client’s own Klaviyo with the plan’s triggers and timings, read back and checked, and switched off until you say yes.The approved emails, built inside your own Klaviyo with the plan’s triggers and timings, read back and checked, and switched off until you say yes.

Start free

Your part: say yes when you want it live, one flow or all of them.

Klaviyo build workspace with illustrative account data
Product walkthrough · Illustrative account data.View full size

Between your yes and a live flow

Built exactly as approved, and checked again before it can send.

Every approval is tied to the exact version you saw. If anything changes after it, the approval no longer counts and the email comes back to you.

  1. Klaviyo’s APIThe approved email becomes a template

    Only an email you approved, in the exact version you approved.

  2. Klaviyo’s APIIts pictures move into Klaviyo

    So the email does not depend on InboxSmith to load.

  3. CheckedRead back and compared

    The template is read back from Klaviyo and compared with the approved version.

  4. CheckedIts links and code are tested

    A fault stops the build instead of reaching a customer.

  5. InboxSmith’s browserOne-time codes are created

    In the client’s Klaviyo, before any email that carries one is built.

  6. Our teamThe flow is wired

    Klaviyo’s API cannot create flows, so our team wires the templates into the flow from the approved plan.

  7. Klaviyo’s APICampaigns are prepared

    With their audience, subject and sender, and no send time.

  8. Your yesIt goes live

    Nothing is scheduled or switched on until you say so. Campaigns are then scheduled for you.

AutomaticIn InboxSmith’s browserBy our teamYour decision
Continue the workflow

Campaigns

A calendar, audience and purpose for every send.

Explore campaigns

Take the tenth client the way you took the first.See what your email really earns.

Start free