Hourglass Content Intelligence
Website ↗
← All conversations

Conversation

23 Oct 2026, 13:26 UTC · 2 questions · ID 355865064a44
Who asked
Persona
CFO (Chief Financial Officer)
Company
Whirlpool Corporation
Industry
Manufacturing
Pages visited (40)
  1. /chat-response
  2. /chat-response
  3. /chat-response
  4. /chat-response
  5. /chat-response
  6. /chat-response
  7. /
  8. /chat-response
  9. /
  10. /chat-response
  11. /chat-response
  12. /chat-response
  13. /chat-response
  14. /chat-response
  15. /
  16. /chat-response
  17. /chat-response
  18. /
  19. /chat-response
  20. /chat-response
  21. /
  22. /chat-response
  23. /chat-response
  24. /chat-response
  25. /
  26. /chat-response
  27. /chat-response
  28. /
  29. /chat-response
  30. /chat-response
  31. /
  32. /chat-response
  33. /chat-response
  34. /
  35. /chat-response
  36. /
  37. /chat-response
  38. /chat-response
  39. /Question 1 asked here
  40. /chat-responseQuestion 2 asked here
Question 1

“Is there a revenue risk if ChatGPT starts recommending our competitors' appliances instead of ours?”

Answer
Partly answered

The AI Search Visibility page explains how Hourglass tracks mentions, citations and how often others are recommended instead of you. The site never says whether this ties to pipeline or revenue, or how to gauge the revenue at risk when assistants favour competitors.

Section on the siteStatusTicket
/products/ai-searchFrom mentions to better answersPartly answers it
Tie AI answer share to pipeline and revenue on /products/ai-search

Ticket

Paste this into your ticketing tool.

Tie AI answer share to pipeline and revenue on /products/ai-search

Who needs it: CFOs and finance leaders weighing revenue risk (this visitor: Whirlpool Corporation)
Section: /products/ai-search › From mentions to better answers

What is missing:
- Nothing says whether AI Search Visibility links assistant mentions or citations to visits, pipeline or revenue in the CRM.
- No way is described to estimate the revenue at risk when assistants recommend competitors instead.

Where: Update this section: add a third card beside "Track mentions and citations" and "Write what assistants need".
  Related sections: Campaign reporting · Reporting tied to revenue

What to do:
1. Confirm with product whether AI Search Visibility reports connect assistant-referred visits and citations to pipeline and revenue on the customer record.
2. Add a card describing what revenue or pipeline view is available and what it measures.
3. Link the card to the revenue reporting described on /products/marketing.

Done when: /products/ai-search states whether and how AI answer share is connected to pipeline and revenue.

From: conversation 355865064a44, question 1: "Is there a revenue risk if ChatGPT starts recommending our competitors' appliances instead of ours?"
Who needs it: CFOs and finance leaders weighing revenue risk (this visitor: Whirlpool Corporation)
What is missing
  • Nothing says whether AI Search Visibility links assistant mentions or citations to visits, pipeline or revenue in the CRM.
  • No way is described to estimate the revenue at risk when assistants recommend competitors instead.
Where
Update this section: add a third card beside "Track mentions and citations" and "Write what assistants need".
Related sections
Campaign reporting · Reporting tied to revenue
What to do
  1. Confirm with product whether AI Search Visibility reports connect assistant-referred visits and citations to pipeline and revenue on the customer record.
  2. Add a card describing what revenue or pipeline view is available and what it measures.
  3. Link the card to the revenue reporting described on /products/marketing.
Done when: /products/ai-search states whether and how AI answer share is connected to pipeline and revenue.
Answer full page
AI Search Visibility, part of Content Hub, tracks how often AI assistants mention and cite your brand for the questions your buyers ask, so you can see where competitors are showing up instead. It checks those questions every week, finds the gaps and suggests the pages that would earn a better answer. Your editors review every draft before anything goes live.
Open the answer page ↗
Sections in the answer pageStatus
/products/ai-searchShare of answers (card)Answers it
/products/ai-searchSee the answer. Write the better page.Answers it
/products/contentShow up in search and AI answers (card)Answers it
/products/ai-searchFrom mentions to better answersPartly answers it
Question 2

“If we sign and the migration goes badly, what's our exposure, and how would we get out?”

Answer
Partly answered

The site explains how a migration limits risk with a test import, team-by-team go-lives and history kept, says monthly plans have no long-term contract, and notes data is exportable at any time. It never explains how to cancel, what happens to annual commitments, how to take a full export on leaving, what happens to data after cancelling, or how to roll back if a go-live fails.

Section on the siteStatusTicket
/pricingStart free, and pay for more only when you need itPartly answers it
Add a contract, cancellation and exit section to /pricing

Ticket

Paste this into your ticketing tool.

Add a contract, cancellation and exit section to /pricing

Who needs it: CFOs and finance leaders assessing vendor risk (this visitor: Whirlpool Corporation)
Section: /pricing › Start free, and pay for more only when you need it

What is missing:
- How to cancel a plan is not explained.
- Terms for annual or Enterprise contracts, including early exit, are not stated.
- How to take a full export of the workspace on leaving is not described.
- What happens to customer data after cancellation, and for how long it is kept, is not stated.

Where: New section on /pricing, placed after "Moving from your current CRM".
  Related sections: Start free, and pay for more only when you need it · Pick the plan that fits today · Moving from your current CRM
  Main topics: Monthly versus annual commitments · How to cancel · Early exit on annual and Enterprise contracts · Full workspace export formats · Data retention and deletion after leaving

What to do:
1. Confirm with the revenue team and legal the cancellation process and the exit terms for monthly, annual and Enterprise contracts.
2. Confirm with engineering what a full workspace export includes and how long data is kept after cancellation.
3. Add the section to /pricing and link it from the plan cards.

Done when: /pricing explains how to cancel each plan type, how to export all data and what happens to data after leaving.

From: conversation 355865064a44, question 2: "If we sign and the migration goes badly, what's our exposure, and how would we get out?"
Who needs it: CFOs and finance leaders assessing vendor risk (this visitor: Whirlpool Corporation)
What is missing
  • How to cancel a plan is not explained.
  • Terms for annual or Enterprise contracts, including early exit, are not stated.
  • How to take a full export of the workspace on leaving is not described.
  • What happens to customer data after cancellation, and for how long it is kept, is not stated.
Where
New section on /pricing, placed after "Moving from your current CRM".
Related sections
Start free, and pay for more only when you need it · Pick the plan that fits today · Moving from your current CRM
Main topics
Monthly versus annual commitments · How to cancel · Early exit on annual and Enterprise contracts · Full workspace export formats · Data retention and deletion after leaving
What to do
  1. Confirm with the revenue team and legal the cancellation process and the exit terms for monthly, annual and Enterprise contracts.
  2. Confirm with engineering what a full workspace export includes and how long data is kept after cancellation.
  3. Add the section to /pricing and link it from the plan cards.
Done when: /pricing explains how to cancel each plan type, how to export all data and what happens to data after leaving.
/pricingMove one team at a time (card)Partly answers it
Add rollback and fallback detail to the migration section on /pricing

Ticket

Paste this into your ticketing tool.

Add rollback and fallback detail to the migration section on /pricing

Section: /pricing › Move one team at a time (card)

What is missing:
- What happens if a test import or a team's go-live fails is not explained.
- Whether the old system can stay in use, and for how long, is not stated on this page.

Where: Update this section: add lines under the "Move one team at a time" card, beside "Each team moves when it's ready".

What to do:
1. Confirm with the onboarding team how a failed go-live is rolled back and what support is given.
2. Add the rollback and side-by-side running points to the card.

Done when: The "Move one team at a time" card on /pricing says what happens if a go-live goes wrong.

From: conversation 355865064a44, question 2: "If we sign and the migration goes badly, what's our exposure, and how would we get out?"
What is missing
  • What happens if a test import or a team's go-live fails is not explained.
  • Whether the old system can stay in use, and for how long, is not stated on this page.
Where
Update this section: add lines under the "Move one team at a time" card, beside "Each team moves when it's ready".
What to do
  1. Confirm with the onboarding team how a failed go-live is rolled back and what support is given.
  2. Add the rollback and side-by-side running points to the card.
Done when: The "Move one team at a time" card on /pricing says what happens if a go-live goes wrong.
/solutions/switch-crmGo live team by team (card)Partly answers it
Explain rollback options in the migration playbook on /solutions/switch-crm

Ticket

Paste this into your ticketing tool.

Explain rollback options in the migration playbook on /solutions/switch-crm

Section: /solutions/switch-crm › Go live team by team (card)

What is missing:
- How a team returns to its old system if go-live fails is not explained.
- Who is accountable for fixing a failed migration is not stated.

Where: Update this section: add to the "Go live team by team" card, after "Old and new run side by side for a while."
  Related sections: Run a test import

What to do:
1. Confirm with the onboarding team the rollback process and responsibilities during a migration.
2. Add the rollback step and a link to the exit terms on /pricing.

Done when: /solutions/switch-crm says what happens and who acts if a team's go-live fails.
Depends on: Add a contract, cancellation and exit section to /pricing

From: conversation 355865064a44, question 2: "If we sign and the migration goes badly, what's our exposure, and how would we get out?"
What is missing
  • How a team returns to its old system if go-live fails is not explained.
  • Who is accountable for fixing a failed migration is not stated.
Where
Update this section: add to the "Go live team by team" card, after "Old and new run side by side for a while."
Related sections
Run a test import
What to do
  1. Confirm with the onboarding team the rollback process and responsibilities during a migration.
  2. Add the rollback step and a link to the exit terms on /pricing.
Done when: /solutions/switch-crm says what happens and who acts if a team's go-live fails.
Depends on: “Add a contract, cancellation and exit section to /pricing”
Answer full page
This page shows how a move to Hourglass is planned to limit risk: a test import before go-live, one team at a time, and your records arriving with their history. Monthly plans carry no long-term contract. The docs below explain how to cancel, what happens to your data and how to take a full export of your workspace.
Open the answer page ↗
Sections in the answer pageStatus
/compare/build-your-ownYour data (card)Answers it
/pricingStart free, and pay for more only when you need itPartly answers it
/pricingMove one team at a time (card)Partly answers it
/solutions/switch-crmGo live team by team (card)Partly answers it

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 23 Oct 2026.