Hourglass Content Intelligence
Website ↗
← All conversations

Conversation

23 Oct 2026, 12:40 UTC · 2 questions · ID 89cb8e6eec9e
Who asked
Profile
We don’t have a profile for this visitor.
Pages visited (27)
  1. /
  2. /chat-response
  3. /chat-response
  4. /chat-response
  5. /chat-response
  6. /chat-response
  7. /chat-response
  8. /
  9. /chat-response
  10. /
  11. /chat-response
  12. /chat-response
  13. /chat-response
  14. /chat-response
  15. /chat-response
  16. /
  17. /chat-response
  18. /chat-response
  19. /
  20. /chat-response
  21. /chat-response
  22. /
  23. /chat-response
  24. /chat-response
  25. /chat-response
  26. /Question 1 asked here
  27. /chat-responseQuestion 2 asked here
Question 1

“Our business wants to use AI on customer data, but compliance keeps saying no. What are other companies doing?”

Answer
Partly answered

The site covers the controls compliance teams ask for: agent permissions, approval steps, an activity log with exports, a pause switch, encryption and audit history. Financial services stories show compliance signing off on agent messages. No story explains how a company won its compliance team's approval to use AI on customer data, or what that team required first.

Section on the siteStatusTicket
/solutions/govern-aiRemarkable results, in every industryMissing here
Add stories of compliance approving AI agents to /solutions/govern-ai

Ticket

Paste this into your ticketing tool.

Add stories of compliance approving AI agents to /solutions/govern-ai

Who needs it: Compliance, risk and IT leaders weighing AI on customer data
Section: /solutions/govern-ai › Remarkable results, in every industry

What is missing:
- No customer story describes how a company got its compliance team to approve agents working on customer data.
- The stories shown here do not say what compliance required before agents went live, such as narrow permissions, approval on every send or audit log exports.
- No story shows how agent permissions were widened over time as trust grew.

Where: Update this section: replace or extend the cards "Allica Bank", "KeepCup" and "Suzuki" in this section on /solutions/govern-ai with stories about winning compliance approval.
  Related sections: Four controls for every agent · Agents that earn trust over time · How banks, credit unions and insurers grow with Hourglass

What to do:
1. Confirm with customer marketing which illustrative customers, such as the regulated ones on the financial services page, can be told as stories of winning compliance approval.
2. For each story, add what compliance asked for, which controls met it and how agent scope widened afterwards.
3. Give /solutions/govern-ai its own story slider so these stories don't replace the shared home page stories.

Done when: /solutions/govern-ai shows at least one customer story explaining how its compliance team came to approve agents on customer data and which controls made the difference.

From: conversation 89cb8e6eec9e, question 1: "Our business wants to use AI on customer data, but compliance keeps saying no. What are other companies doing?"
Who needs it: Compliance, risk and IT leaders weighing AI on customer data
What is missing
  • No customer story describes how a company got its compliance team to approve agents working on customer data.
  • The stories shown here do not say what compliance required before agents went live, such as narrow permissions, approval on every send or audit log exports.
  • No story shows how agent permissions were widened over time as trust grew.
Where
Update this section: replace or extend the cards "Allica Bank", "KeepCup" and "Suzuki" in this section on /solutions/govern-ai with stories about winning compliance approval.
Related sections
Four controls for every agent · Agents that earn trust over time · How banks, credit unions and insurers grow with Hourglass
What to do
  1. Confirm with customer marketing which illustrative customers, such as the regulated ones on the financial services page, can be told as stories of winning compliance approval.
  2. For each story, add what compliance asked for, which controls met it and how agent scope widened afterwards.
  3. Give /solutions/govern-ai its own story slider so these stories don't replace the shared home page stories.
Done when: /solutions/govern-ai shows at least one customer story explaining how its compliance team came to approve agents on customer data and which controls made the difference.
Answer full page
Many teams get compliance on board by putting clear controls around their AI agents: set what each agent can read, require approval where it matters, and review every action. This page draws on our Run AI agents safely page to show those controls, what changes as trust grows, and a customer story of agents at work.
Open the answer page ↗
Sections in the answer pageStatus
/solutions/govern-aiFour controls for every agentAnswers it
/solutions/govern-aiAgents that earn trust over timeAnswers it
/securitySecurity and control, built into every hubAnswers it
/solutions/financial-servicesBuilt for regulated teamsAnswers it
/solutions/financial-servicesHow banks, credit unions and insurers grow with HourglassAnswers it
/solutions/govern-aiRemarkable results, in every industryMissing here
Question 2

“Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?”

Answer
Partly answered

The site explains how two-way syncs, matching and field rules build one customer record while existing systems stay in place. No customer story shows a company that unified its data while keeping its existing systems, and the syncs never name the sales and marketing tools they connect to.

Section on the siteStatusTicket
/products/dataTwo-way syncs, without custom code (card)Partly answers it
Name the sales and marketing systems Data Hub syncs on /products/data

Ticket

Paste this into your ticketing tool.

Name the sales and marketing systems Data Hub syncs on /products/data

Who needs it: IT and data teams connecting sales and marketing systems
Section: /products/data › Two-way syncs, without custom code (card)

What is missing:
- The syncs name warehouses, ERPs and billing tools but not which sales or marketing systems, such as other CRMs or email and ad tools, can be synced.
- There is no mention of whether existing sales and marketing tools can keep running alongside Hourglass while synced.

Where: Update this section: add lines to the card "Two-way syncs, without custom code" beside "Ready-made syncs for warehouses, ERPs and billing".
  Related sections: Four steps to one trusted customer record

What to do:
1. Confirm with product and engineering which sales and marketing systems have ready-made two-way syncs.
2. Add the confirmed system types to the card and note that they can run alongside Hourglass.

Done when: /products/data names the sales and marketing systems Data Hub syncs with in both directions.

From: conversation 89cb8e6eec9e, question 2: "Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?"
Who needs it: IT and data teams connecting sales and marketing systems
What is missing
  • The syncs name warehouses, ERPs and billing tools but not which sales or marketing systems, such as other CRMs or email and ad tools, can be synced.
  • There is no mention of whether existing sales and marketing tools can keep running alongside Hourglass while synced.
Where
Update this section: add lines to the card "Two-way syncs, without custom code" beside "Ready-made syncs for warehouses, ERPs and billing".
Related sections
Four steps to one trusted customer record
What to do
  1. Confirm with product and engineering which sales and marketing systems have ready-made two-way syncs.
  2. Add the confirmed system types to the card and note that they can run alongside Hourglass.
Done when: /products/data names the sales and marketing systems Data Hub syncs with in both directions.
/solutions/unify-customer-dataRemarkable results, in every industryMissing here
Add stories of unifying data without replacing systems to /solutions/unify-customer-data

Ticket

Paste this into your ticketing tool.

Add stories of unifying data without replacing systems to /solutions/unify-customer-data

Section: /solutions/unify-customer-data › Remarkable results, in every industry

What is missing:
- No customer story shows a company joining sales and marketing data from separate systems into one record while keeping those systems.
- The stories shown are about cross-sell, repeat orders and quotes, not about connecting existing systems.

Where: Update this section: add a story card beside "Allica Bank", "KeepCup" and "Suzuki" in this slider as shown on /solutions/unify-customer-data, or swap the slider for one focused on data unification.
  Related sections: What one record changes · Keeping what you built

What to do:
1. Confirm with the customer marketing team which customers synced existing sales and marketing systems instead of replacing them.
2. Add one or two such stories with the systems kept and the results, to the slider on this page.

Done when: /solutions/unify-customer-data shows at least one customer story about building one record while keeping existing systems.

From: conversation 89cb8e6eec9e, question 2: "Our sales and marketing data sits in different systems. How do others get one view without ripping everything out?"
What is missing
  • No customer story shows a company joining sales and marketing data from separate systems into one record while keeping those systems.
  • The stories shown are about cross-sell, repeat orders and quotes, not about connecting existing systems.
Where
Update this section: add a story card beside "Allica Bank", "KeepCup" and "Suzuki" in this slider as shown on /solutions/unify-customer-data, or swap the slider for one focused on data unification.
Related sections
What one record changes · Keeping what you built
What to do
  1. Confirm with the customer marketing team which customers synced existing sales and marketing systems instead of replacing them.
  2. Add one or two such stories with the systems kept and the results, to the slider on this page.
Done when: /solutions/unify-customer-data shows at least one customer story about building one record while keeping existing systems.
Answer full page
Here's a page built around your question.
Open the answer page ↗
Sections in the answer pageStatus
/solutions/unify-customer-dataOne record for each customer, built from every system you runAnswers it
/solutions/unify-customer-dataFour steps to one trusted customer recordAnswers it
/compare/build-your-ownKeeping what you builtAnswers it
/products/dataTwo-way syncs, without custom code (card)Partly answers it
/solutions/unify-customer-dataRemarkable results, in every industryMissing here

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.