CRM Manager interview questions

Lifecycle marketing uses customer data and timely messages to help people progress through their relationship with a product or brand.

• It covers stages such as onboarding, activation, retention, loyalty, lapse, and win-back rather than isolated promotional sends.
• It selects a relevant audience, channel, timing, and message from customer events and profile attributes.
• Its outcomes are measured through behavior such as activation, repeat purchase, or retention, not only opens and clicks.

These stages describe the path from attracting a prospect to creating lasting customer value.

• Acquisition brings a person into the audience or product through a signup, lead, install, or first purchase.
• Onboarding teaches the next steps, while activation is the measurable moment when the person first experiences core value.
• Retention means the customer continues returning, purchasing, or using the product over a defined period.

They address different parts of the customer journey and therefore need different primary outcomes.

• Acquisition is commonly evaluated by new leads, new customers, conversion rate, and customer acquisition cost.
• Retention is commonly evaluated by repeat behavior, retention rate, churn, purchase frequency, and customer value.
• Applying an acquisition metric such as raw signup volume to retention can hide whether existing customers actually stay active.

Onboarding is the guided process, while activation is the customer behavior that proves initial value was reached.

• An onboarding sequence may explain setup, recommend actions, and remove friction across several messages.
• An activation event must be product-specific, such as completing a first project or making a first successful order.
• Finishing every onboarding message does not prove activation if the customer never performs the value-bearing action.

Retention describes continued behavior, while loyalty describes a stronger preference that can support that behavior.

• A retained customer may repeat because of convenience, a subscription, or switching costs without feeling loyal.
• Loyalty can appear through repeat purchases, referrals, direct preference, or engagement with a rewards program.
• A loyalty campaign should still be judged by observable behavior because positive sentiment alone does not guarantee retention.

They describe declining activity, loss, and an attempt to restore a valuable customer relationship.

• A customer is lapsed after passing an inactivity threshold based on the product's normal usage or purchase cycle.
• Churn is the defined loss event, such as cancellation or failure to remain active during a measurement window.
• Win-back targets eligible lapsed or churned customers and succeeds only when they return to the desired behavior.

Lifecycle-stage segmentation groups customers by their current relationship with the product or brand.

• Typical stages include prospect, new customer, activated customer, repeat customer, loyal customer, lapsed customer, and churned customer.
• Stage rules use observable events and time windows, such as first purchase completed or no activity for 60 days.
• It prevents sending a generic message when a new customer needs guidance and a lapsed customer needs a reason to return.

RFM segments customers using recency, frequency, and monetary value of their purchases.

• Recency measures how recently the customer purchased, frequency counts purchases in a defined period, and monetary value totals or averages spend.
• Each dimension is commonly scored into bands, then combined to identify groups such as recent high-value buyers or inactive one-time buyers.
• RFM reflects purchase history, so it should not be treated as a complete explanation of intent, satisfaction, or future value.

Behavioral segmentation uses actions, while profile segmentation uses relatively stable customer attributes.

• Behavioral inputs include product views, logins, purchases, feature use, and message clicks within a defined time window.
• Profile inputs include location, language, plan, stated interests, or customer type when those fields are collected lawfully.
• Behavior often signals current intent more directly, while profile data supplies context but can become stale or incomplete.

Attribute-based segmentation is useful when a known customer property changes message relevance or eligibility.

• Language can select localized content, product ownership can prevent irrelevant recommendations, and plan type can control onboarding instructions.
• Attributes need clear allowed values, update rules, and a fallback for missing data before they drive campaign logic.
• The main risk is using outdated, inferred, or sensitive data in a way that produces wrong targeting or violates customer expectations.

Exclusions and suppressions keep ineligible or inappropriate recipients out of a campaign even if they match its target segment.

• Legal suppressions remove people who opted out or cannot receive a channel under the applicable consent rules.
• Business exclusions can remove recent purchasers from an abandonment offer or employees and test accounts from reporting.
• Deliverability suppressions can exclude hard bounces, complaints, and persistently unengaged addresses from email sends.

Overlapping segments can make one customer eligible for conflicting or excessive messages at the same time.

• A person may qualify as both high-value and lapsed, so separate campaigns could send different offers without priority rules.
• Global frequency caps, campaign priorities, and mutual exclusions control which eligible journey wins.
• Segment counts alone do not reveal overlap, so audience logic should be checked at the customer level before launch.

Email is a consent-based channel suited to detailed, durable, and relatively low-cost lifecycle communication.

• It can carry onboarding guidance, recommendations, receipts, post-purchase education, and win-back content with more depth than push or SMS.
• Email identity usually depends on an address, while relevance depends on linking that address to current customer events and attributes.
• Its reach is limited by inbox placement, attention, consent, and list quality, so a send is not the same as a seen message.

Email supports richer content, while push is better for short and timely prompts on opted-in devices.

• Email can explain several steps and remain searchable, but recipients may read it long after the relevant moment.
• Push can reach the screen quickly and deep-link into an action, but space is limited and permission can be revoked.
• The choice should follow message urgency, content depth, device context, consent, and likely customer value rather than channel availability alone.

Mobile push reaches an installed app, while web push reaches a browser or supported web environment after separate permission.

• Mobile push can use app events and deep links to open a specific screen within the installed application.
• Web push can reach visitors without an app, but browser and operating-system support affects permission and delivery.
• A customer's mobile-push consent does not automatically grant web-push consent, and device tokens must be managed separately.

An in-app message is most appropriate when guidance is useful while the customer is actively using the product.

• It can explain a feature, confirm progress, or suggest the next action in the exact screen where that action is possible.
• It does not reach customers who never open the app or site, so it cannot replace an external re-engagement channel.
• Display rules should use current session context and stop after completion so the message does not obstruct repeated use.

SMS offers fast visibility but has stricter consent expectations, direct cost, and limited space.

• It suits concise and time-sensitive messages such as a requested alert or an urgent service update when the customer has opted in.
• Each send usually costs money and can feel intrusive, so low-value reminders can damage trust faster than email.
• Opt-out instructions, quiet-hour rules, country requirements, and channel-specific consent must be respected before sending.

Shared context keeps email, push, in-app, and SMS from acting like unrelated campaigns.

• A purchase event should stop cart reminders across every channel, not only in the channel where the purchase was observed.
• Channel eligibility and preference should determine the next valid touch instead of repeating the same message everywhere.
• Cross-channel frequency should be counted together because customers experience total contact volume, not separate platform calendars.

An automated lifecycle campaign responds to customer eligibility or behavior, while a broadcast sends at a planned time to a selected audience.

• Automation commonly starts from an event or state change and can continue with delays, conditions, and exits for each entrant.
• A broadcast commonly delivers one campaign, such as a newsletter, to everyone matching a segment at send time.
• Automation is not automatically more relevant because poor triggers, stale data, or missing exits can repeat the wrong message at scale.

An event records that something happened at a time, while an attribute describes the customer's current known state.

• An event can be product_viewed with a timestamp and product ID, or order_completed with an order value.
• An attribute can be preferred_language, loyalty_tier, or last_order_date and is usually overwritten when the state changes.
• Events support sequences and recency logic, while attributes support current-state filters, so replacing all events with attributes loses history.