23 Oct 2026, 16:33 UTC · 3 questions · ID 90f04ae45098
Who asked
Persona
CIO (Chief Information Officer)
Company
Charles Schwab
Industry
Financial services
Pages visited (3)
/Question 1 asked here
/chat-response
/chat-responseQuestions 2 and 3 asked here
Question 1
“The business keeps asking for AI. Which AI uses have actually paid off for firms like ours, so I know what's worth governing?”
Answer
Partly answered
Bank and insurer stories show agent results: Allica Bank's Data Agent cross-sell gains, Mercantile Bank's Customer Agent reply speed and Alacrity Solutions' approved claim outreach. There is no story from a brokerage or wealth management firm, and no summary of which agent uses paid off for financial firms.
Add a brokerage or wealth management AI story to the home page stories
Who needs it: Brokerage and wealth management firms (this visitor: Charles Schwab)
What is missing
The only financial story on the home page is Allica Bank; no brokerage or wealth management firm shows results from agents.
There is no link from the home stories to the fuller set of financial services agent stories.
Where
Update this section: add a fourth card beside "Allica Bank", "KeepCup" and "Suzuki".
Related sections
How banks, credit unions and insurers grow with Hourglass
What to do
Confirm with the customer marketing team whether an illustrative brokerage or wealth management story with agent results can be added.
Add the story card naming the agent used and its measured result.
Link the card to /solutions/financial-services.
Done when: The home page stories include a brokerage or wealth management firm with the agent it used and its result. Depends on: “Add a brokerage or wealth management story to /solutions/financial-services”
Tie each agent to its financial services result on /solutions/financial-services
Who needs it: CIOs and IT leaders at regulated financial firms deciding which AI uses to govern
What is missing
The agent cards describe what each agent does but not which uses have paid off for financial firms.
No card links an agent to a measured result such as Allica Bank's cross-sell gain or Mercantile Bank's faster replies.
Where
Update this section: add a result line under "Customer Agent", "Prospecting Agent" and "Data Agent".
Related sections
How banks, credit unions and insurers grow with Hourglass
What to do
Confirm with product marketing which story result belongs to each agent.
Add one financial services result and the customer it came from under each agent card.
Done when: Each agent card on /solutions/financial-services shows a result from a financial services customer.
Answer full page
Here are stories from Mercantile Bank, Allica Bank and Alacrity Solutions, regulated teams that serve members and clients faster with every message reviewed. After them come the four controls you can set on every agent, and the security controls your compliance team will ask about first. A practical place to start is narrow: let agents draft from the customer record and have a person approve what goes out.
“If Hourglass runs next to leading Financial Services Cloud, where does each customer record live, and how do we avoid two versions of the truth?”
Answer
Partly answered
The site covers two-way syncs, duplicate merging, field rules that decide which system wins and a change log. It never says Hourglass can sync with another CRM that stays in use, or how to decide which system holds each record.
Add running alongside an existing CRM to the Data Hub syncs on /products/data
Who needs it: IT and data teams running Hourglass next to another CRM
What is missing
Two-way sync with another CRM that stays in use is not mentioned; only warehouses, ERPs and billing tools are named.
There is no guidance on which system holds the master record for each object or field when two CRMs run side by side.
How duplicates are prevented across both CRMs during ongoing sync is not explained.
Where
Update this section: In the card "Two-way syncs, without custom code", add a line beside "Field rules that decide which system wins" and "Read-only fields where you need them".
Related sections
Bring every source into one record · Match and merge
What to do
Confirm with product and engineering whether Data Hub syncs two-way with other CRMs kept in use, and how record ownership is set per object and field.
Add a line on running alongside an existing CRM, naming how the system of record is chosen and how cross-system duplicates are matched.
Link the line to the field rules and duplicate checks already described in this section.
Done when: /products/data says whether Hourglass can sync with a CRM that stays in use and how the system of record and duplicates are handled.
Add working alongside existing client systems to /solutions/financial-services
Who needs it: Financial services (banks, credit unions, insurers, brokerages and wealth managers)
What is missing
The page does not say how Hourglass works next to the CRM and client systems a financial firm keeps.
It does not explain where each client record lives or how one version of client data is kept for compliance.
Where
Update this section: Add a third card beside "Approvals where you need them" and "The service members expect".
Related sections
Two-way syncs, without custom code
What to do
Confirm with product which financial services systems Hourglass syncs with and how the system of record is set.
Add a card on running alongside existing client systems, with a link to the Data Hub sync details.
Done when: /solutions/financial-services has a card explaining how Hourglass keeps one client record alongside a firm's existing systems. Depends on: “Add running alongside an existing CRM to the Data Hub syncs on /products/data”
Answer full page
I can't speak to another vendor's product, but I can show how Hourglass works alongside the systems you keep. Data Hub syncs those systems two-way into one Smart CRM record, matches and merges duplicates, and records every change with field-level permissions, so each team works from the same facts. Mercantile Bank is one of the teams that kept its branch systems and synced them into one record.
“If Hourglass runs next to Salesforce Financial Services Cloud, where does each customer record live, and how do we avoid two versions of the truth?”
Answer
Partly answered
The site covers two-way syncs, field rules that decide which system wins, read-only fields, and duplicate matching and merging. It never says whether Hourglass can sync with another CRM running alongside it, or which system holds the master customer record when both stay in use.
Who needs it: CIOs and IT or data teams keeping an existing CRM (this visitor: Charles Schwab)
What is missing
There is no statement on whether Hourglass can sync two-way with another CRM that stays in use.
Nothing says which system holds the master customer record when both run side by side.
Field rules that decide which system wins are described on /products/data, not here where IT and data teams look.
Where
Update this section: add to the "Bring every source into one record" card, beside its points on two-way syncs and duplicate checks.
Related sections
Two-way syncs, without custom code
What to do
Confirm with product and engineering whether another CRM can be a sync source and how the master record is set per object or field.
Add a point on running beside an existing CRM and choosing the system of record, linking to the Data Hub syncs detail.
Done when: /platform says whether Hourglass syncs with a CRM that stays in use and how the system of record is chosen. Depends on: “Add running alongside an existing CRM to the Data Hub syncs on /products/data”
Add running alongside a legacy suite to /compare/legacy-crm
What is missing
Only a phased move off a legacy suite is described, with no account of running both long term.
Nothing says where each customer record lives while a legacy suite and Hourglass run together, or how conflicting edits are settled.
Where
Update this section: add after the sentence on moving in phases in "Moving from a legacy suite".
Related sections
Hourglass and legacy CRM suites, side by side
What to do
Confirm with product whether long-term coexistence with a legacy suite is supported and how record ownership is set.
Add a short passage on coexistence, record ownership and conflict rules, linking to /products/data.
Done when: /compare/legacy-crm explains how records stay consistent when a legacy suite and Hourglass run side by side. Depends on: “Add running alongside an existing CRM to the Data Hub syncs on /products/data”
Answer full page
I can't speak to Salesforce's product, but here is how Hourglass keeps one version of the truth beside the systems you keep. Data Hub syncs your systems two-way into one Smart CRM record, matches and merges duplicates, and logs every change behind field-level permissions, so you control who sees and edits each field. Mercantile Bank is one of the teams that kept its existing systems and synced them into one customer record.