23 Oct 2026, 16:36 UTC · 2 questions · ID d197b421980d
Who asked
Persona
Head of Business Development
Company
Charles Schwab
Industry
Financial services
Pages visited (2)
/Question 1 asked here
/chat-responseQuestion 2 asked here
Question 1
“If my team uses AI to draft outreach, what will compliance and IT ask for before they approve it?”
Answer
Partly answered
The site covers approval before any send, per-agent read permissions, an activity log with audit exports, single sign-on, encryption and data region choice. It never names compliance certifications or the financial regulations it supports, says nothing about how agent-drafted messages are retained or whether customer data is used to train AI models, and offers no single list of what reviewers will
Add regulatory recordkeeping detail to /solutions/financial-services
Who needs it: Financial services, including brokerage and wealth management (this visitor: Charles Schwab)
What is missing
No financial regulations or communications rules Hourglass supports are named.
How approved outreach and approvals are archived and retained for regulators is not explained.
Whether audit logs can be exported to a firm's archiving or supervision tools is not stated here.
Where
Update this section: add a line under "Approvals where you need them" after "Ready when your auditors ask".
Related sections
Security and control, built into every hub · Four controls for every agent
What to do
Confirm with compliance which financial regulations and recordkeeping requirements Hourglass supports.
Add the supported regulations, retention of approved messages and audit export options to the card, linking to /security.
Done when: /solutions/financial-services names the regulations supported and explains how approved outreach and approvals are retained and exported. Depends on: “Add certifications and AI data handling to /security”
Add a compliance and IT review checklist to /solutions/govern-ai
Who needs it: Compliance and IT reviewers approving AI tools
What is missing
No single list of what compliance and IT reviewers typically ask for before approving AI-drafted outreach.
No pointer to the documents reviewers can request, such as certifications and data handling details.
Where
New section on /solutions/govern-ai, placed after "Agents that earn trust over time".
Related sections
Four controls for every agent · Security and control, built into every hub · AI on customer data, with people approving
Main topics
approval and supervision of messages · what agents can read · activity log and audit exports · identity and access controls · encryption and data region · AI model data handling · certifications and how to request reports
What to do
Confirm with the security and compliance teams the questions reviewers ask most and the documents available.
Build the checklist section linking each item to the matching control on /security and /products/agents.
Done when: /solutions/govern-ai has a section listing what compliance and IT review, each item linked to where the site answers it. Depends on: “Add certifications and AI data handling to /security”
Answer full page
Compliance and IT will usually want to know who approves each message, what the AI can read and how every action is recorded. This page shows how the Prospecting Agent drafts but sends nothing until a rep approves it, the four controls you set for every agent, and the security and approval features regulated teams ask for first.
“We've taken on a book of clients from another CRM. How fast can we get them into one pipeline without losing history?”
Answer
Partly answered
The site says a planned move takes weeks, keeps every record with its history, runs a test import first and goes live team by team, and the Eventus story cites five weeks. It never gives typical durations for each migration step, how timing scales with record volume, or how an acquired book merges into an existing pipeline without duplicates.
Add typical timelines to the migration steps on /solutions/switch-crm
What is missing
No typical duration is given for planning, the test import, go-live or retiring old tools.
Nothing explains how the timeline changes with the number of records and the amount of history.
Nothing explains how imported clients are added to an existing workspace's pipeline and checked against records already there for duplicates.
Where
Update this section: Add a typical duration to each of the cards "Plan the move", "Run a test import", "Go live team by team" and "Retire the old tools", and a line under the section heading on overall range.
Related sections
Why software projects stall, and how a planned move avoids it · Four steps to one trusted customer record
What to do
Confirm with the onboarding team the typical duration of each step and how it varies with record volume and history.
Add the confirmed durations to each step card and a line on what makes a move faster or slower.
Add a line to "Run a test import" on mapping imported records into an existing pipeline and running duplicate checks.
Done when: /solutions/switch-crm shows a typical duration for each migration step and explains how imported records join an existing pipeline without duplicates.
Add moving acquired client books to /solutions/financial-services
Who needs it: Brokerage and wealth management firms (this visitor: Charles Schwab)
What is missing
Nothing covers bringing a transferred or acquired book of clients from another CRM into Hourglass with its history.
The page does not link to the migration playbook or say how long such a move takes.
Where
Update this section: add a third card beside "Approvals where you need them" and "The service members expect".
Related sections
Four steps to a calm switch
What to do
Confirm with the onboarding team how acquired client books are imported, merged with existing clients and assigned to advisers or owners.
Add a card on bringing in a client book with its history, linking to /solutions/switch-crm.
Done when: /solutions/financial-services has a card on bringing an acquired client book over with its history, linking to the migration playbook. Depends on: “Add typical timelines to the migration steps on /solutions/switch-crm”
Answer full page
A planned move to Hourglass takes weeks, not months, and your clients arrive with their full history. This page walks through the four steps of a calm switch, including a test import before anything goes live and moving one team at a time, plus stories from Eventus, Suzuki and Mercantile Bank, who made the switch and kept their history.