Real-Time Campaign Notes for DTC Consumer Goods Brands: Keeping CX and Marketing in Sync

You don’t know what changed when a product launches and then months later as CX you start to feel the changes and by then everyone else knows what happened.

The sync problem that slows DTC consumer goods brands down

A campaign goes live on a Tuesday morning. Paid social pushes traffic. Email hits inboxes. The landing page is live, the offer is real, and customers are already clicking.

By 9 a.m., your CX queue is full of questions about it.

Your CX team has no idea the campaign launched.

And manual intervention is exactly what breaks under pressure.

Why manual campaign handoffs keep failing DTC CX teams

The standard playbook looks like this: a marketing manager drafts a campaign brief, attaches it to a Notion page or a Slack message, @-mentions the CX lead, and marks the item done. The @CX lead then reads it once and files it somewhere and the rest of the team is counting on them to know what to do when the calls and tickets start coming in.

There are at least four places that breaks.

The brief doesn’t travel where the questions land. While CX agents may work from a support platform, the brief remains rooted to a project tool or that chat thread from three weeks ago. No one has time to hop between two locations while a queue builds.

The brief goes out and then things change! The promo codes may change, stock levels may change, an offer may be extended for a week. So your original brief is now out of date in terms of the current offer.

Agents/Temps lack necessary context to deal with calls. New seasonal agent has been with the company for last month. He has no idea where the company stores its campaign information or if it is current. He has to wing it, customer gets upset.

It does not scale with launch cadence. Manual handoffs of this nature are okay when you’re launching a campaign every few months but not when you’re launching weekly (new launches, flash sales, rotating bundles to include with other products for a promotion). The costs of coordination will rise exponentially as will the potential for error (wrong discount, wrong return policy, incorrectly inform customer of feature that was not included in shipment with promised features, etc.). Eventually someone will mess up in a big way and cause significant problems for the company.

90% of sales and marketing professionals agree that aligned initiatives and messages have a positive impact on customer experience. The main difference between having knowledge to perform tasks and actually achieving them is operational. Many tools lack integration, knowledge is not transferable between teams, and thus those executing tasks have to put in non-scalable additional work.

What a real-time knowledge layer does for DTC campaign operations

Much of the campaign knowledge exists within the campaign management tools and as these systems were never designed to auto-integrate, lack of discipline exists within the team executing the campaigns.

HubSpot holds the campaign structure. Slack holds the launch announcement thread. A Google Doc holds the brief. Salesforce holds customer history. None of these systems automatically send the CX agent the information pertaining to the campaign that was launched as they are not all connected to a pool of shared knowledge that would automatically push information to the agents’ work queues.

Knowledge layers basically change the architecture of a team. Campaign data that has hitherto resided in siloed tools such as spreadsheets or CRM is ingested, organized and then released on demand to both AI and human team members.

LemonLime helps DTC consumer goods brands build a knowledge layer on top of the tools they already use to run their business. No migration, no scripts, no setting up of IT. A campaign goes live in HubSpot? All that information gets pulled into the knowledge layer for the brand. A brief gets posted in Slack? That information gets automatically ingested into the knowledge layer for the brand as well. A product variant gets updated in Stripe or a bundle of products gets updated in another part of a company’s tech stack, the knowledge layer refreshes with the new information.

CX agents stop working from memory and start working from the current and structured information that they have at hand. Instead of throwing questions at the AI they interact with to get a correct answer from correct data, they get the right answer from the right data as the AI retrieves the information for them from the current sources of information that they use, rather than from stale documentation.

The layer evolves as the business evolves. Each new tool or application added to the mix adds more signal to the layer. Every new campaign launched adds more context to the layer. The layer is unlike a wiki which stalls a fast moving business.

What good campaign sync looks like for a DTC consumer goods brand

Picture a brand that sells functional beverages. They run a new flavor launch with a limited-time bundle offer in the first two weeks: buy two, get one free, with a specific SKU code.

CX was notified in Slack of the change a few days prior to the launch of the campaign. By day three of the campaign agents who had not read the notification were referring to the standard pricing in customer interactions with customers that had read the email. These customers were confused and resulted in escalations.

Here’s a comparison with knowledge-layer approach. In knowledge-layer approach, campaign brief would go into HubSpot, promo details into Stripe and launch announcement into Slack. Ingesting that in LemonLime would automatically happen in each of those three places. For example, customer calls CX and asks whether bundle will apply to his active subscriptions. The agent would instantly retrieve the info to respond. Here’s the offer. Here are the terms. Here are the answers to the questions of whether the bundle applies.

No digging. No "let me check with the team." No wrong answer delivered confidently.

Now extend that to a brand running multiple launches in a single month, with different SKUs, different regions, and different promotional windows. The knowledge layer deals with this increased complexity in the same way as it did with the simple launch above – it doesn’t get tired and it always sends the right brief.

"We used to spend the first few days of every launch putting out fires because CX and marketing weren't working from the same information. That's just not how it works for us anymore.", head of growth at a DTC personal care brand.

How DTC consumer goods brands can start connecting marketing to CX today

The LemonLime path does not have to be a technical project. You can cover most of the path with just three steps.

Link to campaign knowledge tools. For this campaign I use HubSpot for running it, Slack for communication with my team, Google Docs & Google Sheets to set up the required information to run the campaign and then Salesforce for storing information of customers. Logging into the corresponding tools to start the ingestion process.

Let the knowledge layer take shape. LemonLime organizes found information about campaign details, product information, promotion terms and support history in a knowledge layer that’s been optimized for AI retrieval. Organized signal as opposed to a document dump.

Exposing the layer where CX actually functions. Once you have set up the knowledge layer, you can then build AI on top of it. That AI can answer any CX related questions directly off of the campaign data of that AI while it is live – as opposed to gathering the information first and then reading a human written briefing document.

Test connecting 1 tool, launching 1 campaign and reviewing all the answers from the AI on launch day after having no prior setup for the AI. The large gap between what the AI knows and what it is guessing is the operational problem that you are trying to solve.

LemonLime is currently accepting waitlist applications at lemonlime.ai. If you launch frequently enough (i.e. more frequently than your teams can coordinate manually) then this is where to start.

Frequently Asked Questions

Why does my CX team always seem behind on campaign details? We have many different marketing tools that the marketing team can run campaigns from, but those campaigns don’t automatically pull information into the Customer Experience tools that are used on a daily basis by the agents. Campaign briefs are created in project management tools, are stored in different Slack channels or shared documents, and as agents are too busy to search for campaign information while answering calls in a queue a knowledge layer that automatically ingests information and stays up to date with both marketing and Customer Experience tools is needed to eliminate manual forwarding of campaign briefs.

How can I stop campaign details from going stale before my CX team uses them? Static documents don't get updated because they're not hooked up to the places where the real updates happen. So changing a promo code or extending a bundle offer should update the layer that your CX is pulling from. The same layer that your chatbots and self-service and other CX channels are pulling from. LemonLime ingests continuously from connected tools like HubSpot, Slack, and Stripe, which means the knowledge layer reflects current campaign terms rather than the version that existed when someone last updated a wiki page.

What happens to my CX quality when my DTC brand runs a high-volume launch month? The first point of failure in manual coordination is scale. As you run more launches per month, the cost of briefing CX starts to skyrocket as the number of campaigns scales. Agents will be flying blind or with outdated information, and the potential for miscommunication with CX increases exponentially with each additional brief. A knowledge layer, on the other hand, can handle a high cadence of launches the same way it would handle a single launch. Information is automatically ingested by the layer and does not equal increased work for the layer as launches scale.

Does connecting marketing tools to a knowledge layer require an IT project? Not with LemonLime. Connecting tools like HubSpot, Slack, Salesforce, Google, and Stripe happens through sign-in, with no data migration, no scripts, and no IT setup required. Tools such as HubSpot, Slack, Salesforce, Google and Stripe.

How does a knowledge layer help my CX agents answer questions on launch day? That campaign information will be available to answer the customer’s question as their very first contact with the organization. Information that the agent and/or AI assisting the agent needs to answer the customer’s question will be set up in the knowledge layer (offer terms and conditions, SKU information, current promotions, etc.). The agent will not have to search for a brief to answer a customer’s simple question to confirm information, nor will they have to ask marketing for that information. Launch day is no longer the worst day for the Customer Experience.

Is my campaign data secure with LemonLime? That's worth checking before you connect anything. The full details on how LemonLime handles your data are at lemonlime.ai/security. Please note the page you are being redirected to is currently live, so will display latest data and configuration. Therefore it is best to first view specifics against your own use case before linking up tools.