808enzo

@808enzo source repo

35 skills
0 followers
4 hours ago last updated

▌
Contact Orchestration · 808enzo bundle
Control how many messages one person gets across every channel and every sending system, and decide what happens when two messages want the same person at the same time. Use when building a contact policy, setting or deriving a frequency cap, ordering message priority, setting quiet hours, deduplicating the same pitch across channels, working out why unsubscribes rise while each individual campaign looks fine, or auditing total load before adding a channel. Not the construction of one flow, one segment or one channel program, and not consent capture.

0 installs
▌
Program Audit And Ops · 808enzo bundle
Notice when something you launched has stopped working, and decide what to do about it. Use when a flow goes quiet, a send goes out twice or to the wrong list, an export stops refreshing, a promo pool runs dry, a metric sags with no obvious cause, or nobody can say which of your forty mechanics are still earning their place. Covers the duty roster and its slot, alerting, incident response, message recall and correction sends, and the periodic audit that decides what stays running. Not the design of a flow, not the definition of a metric, and not proof that a change caused a result.

0 installs
▌
Loyalty Program Design · 808enzo bundle
Design what a loyalty program is made of and what it costs. Use when choosing between a discount, a points currency and paid access, writing the earn and burn rules, setting redemption depth and expiry, building a tier ladder and pricing each tier, sizing a referral reward and protecting it from abuse, or changing rules that are already promised to a live base. Not the launch project, not enrollment, not discount depth on a single order, and not the day to day running of a program.

0 installs
▌
Loyalty Program Launch · 808enzo bundle
Take a loyalty program from a signed design to a running one, and get people into it. Use when deciding whether the program is worth launching at all, checking that the design can actually run at the till, sequencing the build, sizing a pilot, rolling out by location or channel, migrating members off an old program, removing friction from enrollment, getting store staff to ask, or reading the first months before any effect is readable. Not the earn-and-burn model, not reward value or tiers, not discount depth, and not the day-to-day operation of a program that is already live.

0 installs
▌
Subscription Retention · 808enzo bundle
Keep a paid subscription from ending without the person's decision, and end it cleanly when the person decides. Use when a renewal charge fails and nobody knows how long the person keeps access or when they count as gone, when the cancel screen holds a discount and a legal team asks where the cancel button is, when annual renewals produce refund requests and "cancelled recurring" disputes, when subscriptions billed through an app store get your dunning emails, or when a paused subscription never resumes. Covers the notice calendar, the recovery case after a declined charge (decline classes, retry window, access, deadline), and the exit request with one alternative, one offer, the effective date and the pause. Not the general form of churn, not the signals before a lapse or the win-back after it, not the contract renewal handled by an account manager, not the trial's activation, not the depth of a discount, not the class of a service message.

0 installs
▌
Welcome And Activation · 808enzo bundle
Run the first weeks after somebody arrives, from the moment a contact is recorded to a first purchase or a first use of the product. Use when a signup gets no messages at all, when one welcome series serves six different entry points, when a person who just bought is still being asked to buy, when somebody resubscribes and gets greeted as a stranger, when a trial ends without the product being used, when nobody can say who owns a contact after the welcome series finishes, or when you need to know how long the series should be and how many touches go in it. Covers entry points and their promises, the target action, the window computed from your own data, touch spacing, send and skip conditions, activation events and how to pick one, the setup step before it, the four ways a series ends, and what a second arrival does. Not the capture form, not the message copy, not the second purchase, not winback.

0 installs
▌
Consent And Preferences · 808enzo bundle
Decide on what basis the program may write to a person, in which channel and for what, what the person chose afterward, how far and how fast a withdrawal takes effect, and which uses of their data beyond sending (selection, scoring, inferred attributes) rest on which basis. Use when a base was imported with a "subscribed" flag and no record behind it, when a person unsubscribes and keeps getting texts from another system, when a checkout ticks the marketing box for everyone, when a segment is built on a purchase that reveals a health condition, or when somebody wants to re-permission the whole base by email. Covers the basis record and its proof, confirmed opt in, basis lifetime, the preference center, withdrawal scope and propagation, special categories, and erasure that keeps the suppression entry. Not the capture form, not the merge of records, not the cap, not the envelope, not the class check of a service message, and not legal advice.

0 installs
▌
Transactional Messaging · 808enzo bundle
Decide which service messages a person gets about something they set in motion (an order, a booking, a payment, an account request), what triggers each one, what it has to contain, how fast and through which channel it has to arrive, what it may carry besides, and how to tell whether the set does its job. Use when people keep asking support where their order is, when a delay notice arrives after the promised date, when a sign-in code arrives after the person gave up, when somebody wants a cross-sell block in the order confirmation, or when service messages are judged on revenue. Covers the service register and status map, the four kinds (access, confirmation, progress, exception), promise timers, the content contract, channels and failover by kind, and testing without withholding required messages. Not the trigger machinery of marketing flows, not the cap, not the sending identity, not the review request, not the order handling process itself.

0 installs
▌
Experiments And Holdouts · 808enzo bundle
Design a comparison a decision can rest on. Use when writing a testable hypothesis, choosing what to randomize, sizing a test and deciding how long to run it, building a local or global control group, sizing a holdout and pricing what it costs, checking whether a running test is still valid, reading a result without over-reading it, or answering whether a mechanic produces anything at all beyond what customers would have done on their own. Covers A/B design, holdouts drawn from flow entries, verifying an exclusion, incremental measurement of an added cascade step, the evidence ladder, and the test log. Not the metric formula, not the dashboard, not the attribution model.

0 installs
▌
Personalization · 808enzo bundle
Decide what changes inside a message or on a page from one person to the next, where each value comes from, and what happens when it is missing. Use when a message ships with an empty name in the greeting or a raw template token, when a recommendation block shows the same items to everybody, when a cart reminder arrives describing an empty cart, when a personalized campaign performs like a generic one, when nobody can say how many personalization rules are running or who owns them, when a block recommends what somebody bought last week, or when you need to decide whether a message should go at all once the personal part cannot be built. Covers the four source classes, the moment a value is resolved, format contracts, the three level fallback ladder, the anchor ladder and cold start, algorithm classes and catalog constraints, short fill, the register of live rules and how to switch one off. Not the copy, not the segment, not the display rule, not the discount economics.

0 installs
▌
Repeat Purchase · 808enzo bundle
Work out when somebody's next purchase is due, move a first time buyer to a second purchase, and decide what may be offered alongside an order. Use when a replenishment reminder arrives after the customer already restocked elsewhere, when nobody can say where the reminder date comes from, when a buyer with one purchase gets a win-back message that assumes an interval they do not have, when first time buyers are handed nothing after the welcome series ends, when a recommendation block offers a second mattress to somebody who bought one yesterday, or when average order value rises while margin per order falls. Covers the four sources of an interval and the ladder between them, the advance for decision and delivery, recompute and retraction, the cohort window, the five outcomes, the three moments for an add on and the exclusion lists. Not the trigger itself, not discount depth, not the recommendation algorithm, not loyalty economics.

0 installs
▌
Lapse And Winback · 808enzo bundle
Decide who counts as lapsed, catch the ones heading that way before they go, and run one finite attempt to bring back the ones already gone. Use when nobody can say how many days without a purchase makes somebody lapsed, when a win-back message reaches people who bought yesterday in the store, when the lapsed segment only ever grows, when a re-engagement campaign has no end and no outcome, when returns happen but only ever with a discount attached, when customers leave and the team finds out at renewal, or when you need to know whether an attempt to win somebody back is worth making at all. Covers the qualifying action and the threshold derived from your own interval, the two axes of absence, the out of scope classes, retrospective signal building, scoring and validation, the sequence and its escalation, the channel cascade, the declared end and the five outcomes. Not the churn formula, not the tier cadence, not deletion, not discount economics.

0 installs
▌
Voice Of Customer · 808enzo bundle
Ask customers about an experience and act on the answer. Use when setting up a post-purchase, post-delivery, post-conversation, post-cancellation or lapse survey, when a low score arrives and nobody knows who owns it or by when it must be answered, when the biggest store always looks worst on complaint counts, when a review incentive or a survey-based segment is proposed, or when nobody can say whether a change made "because customers said so" worked. Covers the judging point and sampling, one overall question and the branch by score, the per-person ration, the route to the owner and the timer from the answer, coding verbatims into themes, the readable floor per cell, verification after the change, and the message back to the people who raised the theme. Not the metric formula, not test design, not the display rule of a widget, not the conversation itself, not product discovery research, not reputation management.

0 installs
▌
Crm Program Design · 808enzo bundle
Decide what the CRM program is for, which single number it is judged on, who answers for each part of that number, what gets built first when nothing exists yet, and when the whole set is re-cut. Use when a business is starting lifecycle work from scratch, when there are many live mechanics and no one can say what they add up to, when two people claim the same result, when the queue of things to build is ordered by enthusiasm, or when goals were set a year ago and nobody has looked at them since. Covers the goal and the metric system, the ownership map, team shapes and promo budget split, the first launch queue and its dependencies, and the point where build order hands over to the roster. Not the design of any single mechanic, not the roster of mechanics, not the definition of a metric, and not permission to send.

0 installs
▌
Messaging Channels · 808enzo bundle
Build and run the channels where a carrier or a messaging platform stands between the sender and the person, such as SMS, RCS, WhatsApp and similar messaging apps. Use when deciding which registered number or name a message leaves from, when a template needs approval and a category, when a template gets paused or a number's limit stops a campaign, when an order update and a promotion share one number, when STOP has to work on every system that texts, when a send is billed per segment or per delivered message, or when a cascade has to know what "sent" and "delivered" mean. Covers the origin and its registration, the reply window and the template regime, segment budgets and encoding, cost before the send, statuses and the no-receipt class, and keyword handling. Not the order of channels in a cascade, not the cross-channel cap or quiet hours, not the lawful basis for texting, not the conversation after a reply, not the class of a service message.

0 installs
▌
Metric Definitions · 808enzo bundle
Write down what a metric actually is, so two people quoting it mean the same thing. Use when two dashboards disagree, when a metric is about to become a target, when you need the numerator, denominator, window and attribution method of a lifecycle metric written so someone else can reproduce it, when you are reconciling a number across two systems, or when you are deciding which metrics a program reports on and who owns them. Covers message and channel metrics, customer and money metrics, the definition-change protocol, and the self-baseline you build when no citable benchmark exists. Not the dashboard, not the attribution model, not the proof that a difference is real.

0 installs
▌
Push Notifications · 808enzo bundle
Decide who can be reached by push, through which endpoint, and what each send does to the permission the channel depends on. Use when planning how and when to ask for notification permission on iOS, Android or the web, when opt-in looks fine but the channel keeps shrinking, when nobody knows how many people the push base reaches, when notifications get switched off and nobody notices, when one promotion lights up every device a person owns, when an offer arrives after it ended, or when deciding which endpoints a message should go to. Covers the ask budget of each platform, the pre-permission screen, provisional authorization, marketing opt-in apart from display permission, the endpoint registry and token staleness, the fan-out rule, interruption levels, expiry and collapse keys. Not the trigger, not the cross-channel cap or quiet hours, not consent as a lawful basis, not in-app messages.

0 installs
▌
Triggered Messages · 808enzo bundle
Build flows fired by a customer event rather than by a person pressing send. Use when deciding which events deserve a message, writing a trigger definition someone else can reproduce, setting the delay, shaping the chain of steps and the channel cascade, deciding when a flow stops, or untangling two dozen live flows that collide on the same person. Covers abandoned cart, browse and checkout, catalog events such as back in stock, price drop and low stock, date events such as birthdays, anniversaries and expiry dates, and recorded states such as a delivered order. Not the welcome series, not winback, not the message copy, not the cross-channel contact cap.

0 installs
▌
In Product Messaging · 808enzo bundle
Decide what the product shows a person who is already inside it, on which screen, in what form, how often, which message wins the screen when several want it, and how those displays connect to the email and push about the same thing. Use when every launch opens with a modal, when in-app messages come from three systems that do not see each other, when an offer shows after it ended, when the same pitch reaches a person by email, push and in-app in one day, when the pre-permission screen, a rating request and a survey all want the same screen, or when a feature is announced to people who already use it. Covers the slot inventory, protected screens, eligibility as state, expiry and the queue, the session budget, precedence, displays as touches in a cascade, the inbox, and the holdout. Not the trigger, not the cross-channel cap, not the site's widgets, not the conversation, not the content of a personalized block.

0 installs
▌
Segmentation · 808enzo bundle
Cut a customer base into segments that hold up in use. Use when deciding which attribute to split on, writing a segment definition someone else can reproduce, sizing a segment, setting how often it recomputes, resolving people who land in several segments at once, deciding what happens to everyone who lands in none, or retiring a segment that has stopped separating. Not RFM or behavioral scoring, not what goes inside the message, not contact collection, and not metric formulas.

0 installs
▌
B2b Lifecycle · 808enzo bundle
Carry a business account from the first known contact to the buying group's decision. Use when leads go to sales and nobody records whether sales accepted them, when sales says "these leads are junk" and marketing says "sales never calls", when an account sits in a sales stage for months with no recorded next step, when three people at one company get the same email in one week, when a champion answers every message and the deal still dies at the budget holder, or when a lost deal is archived with "no decision" and never comes back. Covers fit and decaying intent on the account, the handoff threshold agreed with sales and acceptance by a promised time, stage ownership, the account cadence, buying roles from your own won deals, next steps with promised times, loss codes with a re-entry date, and the record a won deal hands to retention. Not lead generation, not cold outreach, not the sales conversation itself, not trial activation, not renewal.

0 installs
▌
B2b Retention · 808enzo bundle
Carry a business contract billed by invoice from the won deal to the customer's decision about renewing it. Use when you track renewals by end date and notices of non-renewal keep arriving "too late", when a contract renewed automatically and the customer disputes the invoice, when the account manager opens a renewal without knowing what the sale promised, when you sign an expansion weeks before the customer gives notice, or when an invoice stays unpaid and nobody can say when the customer counts as gone. Covers the success plan and QBRs, the contract register, the decision point and the renewal case, the protective notice and the holdover, renewal notices required by law, amendments, true-up and contraction, and the collection case. Not the scoring of churn signals or the win-back, not a subscription on a card or an app store, not the deal before signature, not the general form of revenue retention, not the depth of a concession.

0 installs
▌
Chat And Bots · 808enzo bundle
Decide whether a bot or a human answers a person who writes in, how their matter reaches someone who can settle it and stays with that person until it is done, what they are told while nobody answers, and when the conversation counts as finished. Use when a bot is being planned or already traps people, when handoffs lose context and people repeat themselves, when conversations bounce between agents or shifts, when the chat promises a reply time it does not keep, when first response time looks fine and people still say nobody answered, or when deciding what a bot may answer on its own. Covers the issue as the unit, bot scope by the cost of a wrong answer, the exit to a human and the handoff contract, one assignee per issue, shift boundaries, closure and returns, staffing to arrivals, the promised wait, and off-hours mode. Not lead capture, not lead qualification, not messaging platform rules, not surveys, not in-app messages.

0 installs
▌
Crm Reporting · 808enzo bundle
Build the regular report a lifecycle program gives the business, read change over time on cohorts rather than on the whole base, and report money so that credit and effect are not confused. Use when somebody asks for a CRM dashboard, when a number went up in the deck and nobody can say compared to what, when repeat purchase share improved in the month acquisition was cut, when the newest cohorts look worse than the old ones, when channel tools claim more orders than the business took, or when attributed revenue keeps rising and the holdout does not move. Covers a comparison base and a noise band for every line, counterweights, freeze dates and restatement notes, the cohort table by age, splitting a base-wide change into mix and within-cohort change, the attribution model and window per decision, and the register of vanity metrics. Not the metric definition, not test design, not pipeline monitoring, not paid acquisition analytics.

0 installs
▌
Email Program · 808enzo bundle
Run email as a standing program rather than as one-off sends. Use when planning what goes out and to whom, setting a sending rhythm per engagement tier, building a slot calendar, deciding who is excluded from a given send, or diagnosing a channel whose returns are falling. Covers program design, recipient selection, and recovery. Not for writing or designing a single email, not for authentication and inbox placement, not for event-triggered flows, and not for the cross-channel contact cap.

0 installs
▌
List Building · 808enzo bundle
Build a contact base worth sending to, and keep it that way. Use when you need to know where your records come from, which attributes the base should carry and in what order to ask for them, why one person exists in the base three times, which record wins when two of them disagree, and when a contact has stopped being worth keeping. Covers the intake register and provenance, the attribute plan and the ladder for filling it, identity keys and merge conflicts, decay and hygiene, and the split between the active base and the record you keep longer. Not the design of a capture form, not segment definitions, and not what you send.

0 installs
▌
Martech Stack · 808enzo bundle
Decide where the facts your program runs on actually live, which system owns each one, how fresh the events are, and how to change platform without losing the program. Use when two systems disagree and nobody can say which is right, when you are deciding what to send into a marketing platform and what to leave behind, when a segment stopped filling and nobody changed it, when you need to know how long after an action an event becomes visible to a trigger, or when you are choosing, buying, or moving to a new platform. Covers the register of facts and their owners, field formats, the event plan, freshness classes, event retention, and the order of a migration. Not segment design, not trigger design, not deliverability, and not consent as a lawful basis.

0 installs
▌
Deliverability · 808enzo bundle
Decide how your mail identifies itself to a mailbox provider, how it earns the right to send volume, and what to do when a provider stops letting it through. Use when mail stops arriving at one provider while the rest look fine, when response falls after a platform move or a change of sending IP, when a domain or IP lands on a public blocklist, when bounces or spam complaints cross a provider's threshold, when a new domain or subdomain is about to send for the first time, or when a program wants more volume than the audience currently carries. Covers sending identities, SPF, DKIM, DMARC and alignment, one-click unsubscribe, shared against dedicated IPs, the warmup ladder per provider, the ordered diagnosis of a placement failure, blocklist delisting, and the four classes of an unreachable address. Not what goes out or to whom, not the fate of a record, not consent as a lawful basis, not templates, and not a list of spam words.

0 installs
▌
Onsite Capture · 808enzo bundle
Turn anonymous site traffic into people the program is allowed to contact. Use when placing or auditing pop-ups, subscription forms, quizzes and other capture points, deciding what to ask for and what to give in return, setting the rule that governs when a widget may appear, fixing a site that shows three overlays at once, working out why captured contacts never buy, or connecting a form to what happens next. Not the content of a widget that asks for nothing, not the welcome series, and not consent as a lawful basis.

0 installs
▌
Promo Calendar · 808enzo bundle
Decide what happens when in the year, and what a peak does to the weeks around it. Use when building or rebuilding the promotional calendar for a cycle, working out whether a season is real or self made, deciding which occasions earn a place and which do not, preparing and running a peak window, placing windows so they do not collide with each other or with promises already issued, filling a trough, or explaining why a sale that looked good left the year smaller. Covers the index of a period and the separation of season from trend, the admission test for an occasion, the window register, the issuance cutoff, lead time and the message and channel ladders, the freeze window, the extended window a verdict is read on, and the three directions demand can be shifted. Not discount depth, not the channel's own calendar, not the frequency cap, not copy or design.

0 installs
▌
Email Copy · 808enzo bundle
Decide what one email says, what it promises, what it asks for, and how you know the words were the reason it worked. Use when a message has to be written or rewritten, when a subject line has to be chosen, when nobody can say in one sentence what a send is for, when a message carries two jobs at once, when clicks land on navigation instead of the offer, when a promise made at signup has to be kept in words, when a substitution can come out empty, or when a draft is about to go out and somebody has to decide whether it can. Covers the message brief, inherited promises, claim discipline, the sender name, subject and preheader, body order, the single call to action, fallback wording, link roles, and the review that blocks a send. Not who receives the message, not when it fires, not the economics of the offer, not the template, and not a list of spam words.

0 installs
▌
Email Design · 808enzo bundle
Decide what a reader sees when a message opens in their environment, and whether the template holds the job, the action and the required elements in places the author never looked. Use when a template is being built or changed, when a message looks right in the editor and broken in somebody's inbox, when images are off or the reader is in dark mode, when a long message is clipped and the unsubscribe link falls below the cut, when a product block can come out short or empty, when a countdown, an animation or an interactive part is proposed, or when clicks fall in one mail app while the rest hold. Covers the template frame and block library, the base layer and the layers above it, template versions and release, the environment matrix built from your own base, live checks against emulated previews, block states at assembly, and the interactive layer with its fallback part. Not the words, not inbox placement, not where a personal value comes from, and not a table of which client supports which property.

0 installs
▌
Offer Design · 808enzo bundle
Decide what you promise a customer in exchange for a purchase, down to the form of the benefit, how deep it goes, what it is conditional on, how long it lives, what carries it, and what happens when several promises land on one order. Use when somebody has decided to "send a discount" and nobody has said how much, when a promo code leaks, when two promotions stack into a loss, when a code stops working while the message promising it is still in inboxes, when you are pricing a game or prize mechanic, or when you want to cut discounting without losing the base. Covers benefit form, depth against margin, entry thresholds, redemption windows, exclusions, unique against shared carriers, issuance limits, prize funds, arbitration between offers, and the fate of a promise you can no longer honor. Not loyalty program construction, not the promotional calendar, not which mechanic sends the message.

0 installs
▌
Rfm Segments · 808enzo bundle
Cut your base by recency, frequency and money using boundaries computed from your own distribution rather than from somebody's article, collapse the resulting grid into groups a person can actually work, and keep the groups honest as people move between them. Use when somebody hands you a 27 cell RFM table and asks which cells to message, when you need to decide where a band boundary goes, when the same three digit code means opposite things in two documents, when a winback message reached somebody who bought yesterday, or when a large part of the base has no purchase history and no route. Covers the three axes and the direction of the scale, quantile and business fact cuts, collapsing cells into working groups, the customers the grid cannot place, the recompute ritual, and transitions read as occasions. Not what the group gets sent, not the metric formulas, and not permission to send.

0 installs
▌
Scenario Map · 808enzo bundle
Decide which mechanics your program runs at all, which one gets built first when you cannot build them all, and which one leaves. Use when nobody can list what is currently running, when somebody hands you an industry list of scenarios and asks which to launch, when a new mechanic is requested and you need to know whether it earns a slot, when much of the set has not fired since launch, or when a review says a mechanic should be switched off and nobody knows who decides that. Covers the roster of mechanics, the admission test, the build order and its dependencies, the four verdicts of a review, and the order a mechanic is retired in. Not the construction of one flow, not the design of the program, and not monitoring what already runs.

0 installs

35 published skills