System of record first
the CRM is read before anything is written.
Use caseSales
Your top rep's prep, in every rep's agent.
Every rep preps from the CRM the way your best rep does. Customer data stays in scope. New reps start with the team's habits, and you can see the playbook reach every rep's agent.
The problem
Every rep has AI, and every rep uses it differently. Top reps' agents start from the CRM. New reps paste email threads and send whatever comes back. Your data rules live on an onboarding slide, and AI spend is one number on a bill.
Example power-user workflow
CRM-first account brief
Who it serves
Sales managers and RevOps leaders who own methodology, enablement, CRM access and sales AI policy.
Start with the CRM
Read the stage, stakeholders, activity and call notes.
Write the account brief
Use one format and flag what is still unknown.
Capture call insights
Map what you learned to your sales methodology.
Draft the follow-up
Include the agreed next steps.
Update CRM and review
Log next steps. Review the follow-up before sending.
Learning from sessions
Example signals to surface
Illustrative signals. Availability varies by connected agent and workflow.
Buying-group coverage
the brief names the decision-maker and the stakeholders, not just the contact.
Methodology completeness
qualification fields are filled, and the gaps are listed.
Follow-up speed
follow-ups are drafted soon after the call, not days later.
CRM write-back
next steps are logged to the CRM, not left in a chat.
Review before send
a human review happens before anything reaches the customer.
Account-scoped data
only the current account's details appear in the draft.
How Halofy makes it repeatable
Sales
The approved setup
A playbook bundle, backed by team rules.
In the playbook
- The account-brief and post-call-follow-up recipes
- Her brief format and skill files
- The CRM MCP settings
Team guardrails
- Required Protect customer data and Review before sharing policies
- The CRM on the MCP allowlist
- Read only / Read & write agent badges
- Budgets per rep and per agent
Every rep's agent receives it. New reps' agents get the bundle on day one.
What they use
- power-user signals
- playbooks (bundled setup)
- skills
- instructions
- Required policies
- MCP allowlist
- agent badges
- team memory
- Sales team space
- budgets
- compliance standing
- adoption tracking.
Outcomes
What your team can work toward
Adoption, output and time-saving figures are targets, not measured customer results.
~5% → ~80% power-user coverage.
Your top rep's prep and follow-up becomes every rep's default.
Output up ~18% across the sales team
on prep and follow-up workflows.
~22% less time on repeat prep and follow-up
for every rep who adopts the playbook.
Make your best team's habits everyone's default.
One approved playbook. Every connected agent on the team.