23 Oct 2026, 12:52 UTC · 5 questions · ID 93665e83118b
Who asked
Persona
CMO (Chief Marketing Officer)
Company
Whirlpool Corporation
Industry
Manufacturing
Pages visited (35)
/
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/
/chat-response
/chat-response
/chat-response
/chat-response
/chat-response
/
/chat-response
/chat-response
/
/chat-response
/chat-response
/
/chat-response
/chat-response
/chat-response
/
/chat-response
/chat-response
/
/chat-response
/chat-response
/
/chat-response
/chat-responseQuestions 2 and 4 asked here
/Questions 1, 3 and 5 asked here
Question 1
“If we move our brands onto Hourglass, what happens to our SAP and product-registration data, and can my team still personalize from it?”
Answer
Partly answered
The site covers two-way syncs with ERPs, custom objects for products, segments built on any record field, and personalized pages. It never names SAP as a supported ERP and never covers product-registration data or personalizing marketing across brands from it.
No ERP system is named; SAP is never mentioned as a ready-made sync.
It doesn't say which ERP objects, such as customers, orders or products, come across in a sync.
Where
Update this section: add a list of named ERP systems under the "Ready-made syncs for warehouses, ERPs and billing" line of the "Two-way syncs, without custom code" card.
Related sections
The tools in Data Hub
What to do
Confirm with engineering which ERP systems, including SAP, have ready-made two-way syncs and which objects each one syncs.
Add the confirmed ERP names and synced objects to the card, linking to the integrations listing if one exists.
Done when: /products/data names each supported ERP system, and whether SAP is one of them, in the two-way syncs card.
Add product registrations and brand marketing to /solutions/manufacturing
Who needs it: Manufacturing (this visitor: Whirlpool Corporation)
What is missing
Product-registration data and how it reaches the customer record are not covered.
It doesn't show how marketing segments and personalizes across several brands from ERP and registration data.
Where
Update this section: add a third card beside "Quotes from your real price lists" and "Service history on every ticket".
Related sections
Segments that update themselves · Personalized pages · Custom objects
What to do
Confirm with product how product-registration data is brought into Hourglass, for example as a custom object or through a sync.
Add a card covering registration data on the account and owner record, and marketing segments and personalized pages built from it, by brand.
Link the card to /products/data and /products/marketing.
Done when: /solutions/manufacturing has a card explaining how product-registration and ERP data are used for multi-brand marketing. Depends on: “Name the supported ERP systems on /products/data”
Answer full page
Hourglass syncs your SAP data and other sources, like product registrations, into one customer record through two-way syncs and custom objects, so nothing is left behind when your brands move. Your marketing team can then build segments that update themselves and personalize pages from that same record. This page shows how the data connects and how marketing uses it.
“If I ask our CFO to fund consolidating every brand onto one platform, what will they push back on, and what's my best answer?”
Answer
Partly answered
The site covers the arguments: one price instead of several subscriptions, no setup fees, phased team-by-team moves with history kept, many brands on one platform and marketing reporting tied to revenue. It gives no payback period, total cost of ownership or savings figures from consolidating tools, and Enterprise pricing for many brands is only 'priced for your organization'.
Add cost savings results to manufacturing stories on /solutions/manufacturing
Who needs it: Manufacturing (this visitor: Whirlpool Corporation)
What is missing
The Suzuki story says three legacy systems were retired but gives no cost saved or payback time.
No manufacturing story shows the financial result of consolidating brands onto one platform.
Where
Update this section: Add a cost or payback metric beside "34% faster quote turnaround" and "3 legacy systems retired" on the "Suzuki" card.
Related sections
Built for complex products and long relationships
What to do
Confirm with the customer marketing team which cost or payback results can be published for manufacturing customers.
Add a financial metric to the Suzuki card and, where available, to the other manufacturing stories.
Done when: At least one manufacturing story on /solutions/manufacturing shows a cost saving or payback period.
Answer full page
A CFO usually pushes back on three things: cost, the risk of switching and proof of payback. Your best answer is that one platform replaces overlapping tools and their bills, there are no setup fees, you can move one brand or team at a time with history intact, and marketing reporting ties straight to revenue. This page lays out each point so you can build the case.
“How do I stop my team being the bottleneck for marketing's board reports?”
Answer
Partly answered
The site covers syncing ERP and other systems into one record, campaign reporting tied to pipeline and revenue, leadership views across units and a Data Agent that answers questions in plain words. It never says whether marketers can build their own custom reports without IT help, or how executive or board-level reports are scheduled, shared or exported.
Add self-serve and executive reporting detail to /products/marketing
Who needs it: CTOs and IT or data teams supporting marketing (this visitor: Whirlpool Corporation)
What is missing
Whether marketers can build and edit custom reports and dashboards without help from IT or data teams is not stated.
How reports are scheduled or shared with executives and boards is not described.
Whether reports can be exported for board packs, and in which formats, is not mentioned.
Whether one report can roll up several brands or business units is not stated.
Where
Update this section: add lines under the "Reporting tied to revenue" card, after "Dashboards marketing and sales both trust".
Related sections
Reports · Many teams, one platform · What your data team notices
What to do
Confirm with product which report-building, scheduling, sharing, export and cross-brand rollup features exist and on which plans.
Add confirmed lines on self-serve report building, scheduled delivery to leadership, exports and multi-brand rollups to the card.
Link the card to /solutions/enterprise for organizations reporting across many brands.
Done when: /products/marketing states whether marketers can build reports without IT, how reports reach executives and whether they can be exported or rolled up across brands.
Answer full page
Move the data into one record your marketing team can report from on their own, so they stop waiting on your team. This page shows how Data Hub syncs your systems like SAP into the Smart CRM, how Marketing Hub ties reporting to revenue, and how the Data Agent answers questions in plain words with the records behind each answer.
“If marketing switches on AI agents, what customer data can they see, and can I turn it off?”
Answer
✓Answered well
The site says you choose which records and fields each agent can read, by team and role, and that every agent has a pause switch to turn it off in one click. Approval steps and an activity log of every action are also covered.
Answer full page
You decide what each agent can read, down to the field, so marketing's agents only see the customer data you allow. You can also require approval before anything reaches a customer, review every action and pause any agent at once. This page shows those controls in Agent Hub and the field-level permissions in Data Hub.
“Can I use clients' life events or account details to personalize campaigns without creating a compliance problem?”
Answer
Partly answered
The site covers approval steps and an audit trail for financial-services campaigns, segments built from any record field and field-level permissions. It never says whether client life events or account details can be used in segments, how consent and marketing preferences are honoured, or how sensitive fields can be kept out of campaigns and the Campaign Agent.
Add compliant personalization with client data to /solutions/financial-services
Who needs it: Financial services marketing teams (this visitor: Charles Schwab)
What is missing
Nothing says whether client life events or account details can be used to build campaign segments.
No mention of how consent and marketing preferences are recorded and respected in campaigns.
No way is described to keep sensitive account fields out of segments or away from the Campaign Agent.
No mention of the regulations or policies these controls help financial firms meet.
Where
Update this section: add a third card beside "Approvals where you need them" and "The service members expect".
Related sections
Security and control, built into every hub · From the right audience to revenue you can trace
What to do
Confirm with product and compliance which client fields can be used in segments, how consent and preferences are handled and how sensitive fields can be restricted.
Add a card on personalizing campaigns with client data, covering allowed fields, consent and restrictions on segments and agents.
Link the card to the field-level permissions on /security.
Done when: /solutions/financial-services explains how client account details can be used in campaigns, how consent is respected and how sensitive fields are restricted.
Add sensitive-field and consent controls for segments to /products/marketing
What is missing
No mention of limiting which sensitive fields can be used in segment rules.
No mention of honouring opt-outs, consent or marketing preferences when segments send.
Where
Update this section: add lines to the "Segments that update themselves" card, after "Rules based on any field on the record".
Related sections
Field-level permissions
What to do
Confirm with product how admins restrict fields from segment rules and how consent and opt-outs apply to sends.
Add one line on restricting sensitive fields and one on consent to the card's list.
Done when: The "Segments that update themselves" card on /products/marketing says how sensitive fields are restricted and how consent is respected.
Answer full page
Yes. Hourglass lets you build segments from the customer record while adding approval steps and an audit trail your compliance team can check, and field-level permissions limit who, and which agents, can see sensitive account details. Whether a specific use of client data meets your regulations is for your compliance team to decide, and this page shows the controls that help them sign off.