Account 360.
Pulls open opportunities, recent cases, owner, and last activity into a one-paragraph account brief.
INTEGRATIONS · SALESFORCE
Stop opening Salesforce to ask Salesforce a question.
Pull up any account by voice. Get the renewal brief in thirty seconds. Log post-call notes without opening the app. Henoyo reads your Salesforce, your ERP, and your warehouse, and answers in plain English, on whichever screen you’re already on.
About $20–$40 a month for a ten-person pilot. An hour to deploy, on standard cloud controls your IT team already approves.
What it actually does on a Tuesday.
It’s 10:50am. Your renewal call with Acme starts in ten minutes. You’re walking from the parking lot to the office. You ask Henoyo:
“Pre-call brief on Acme.”
Thirty seconds later, your AirPods say:
Acme is a $480k renewal, closing March 31. Two cases opened in the last quarter, both resolved within 24 hours. Last touch was Maria’s QBR on February 12. Risks: their API usage is up 40%, they may be ready to expand, but their primary champion moved to a different team last week. Recommended next step: confirm the new champion before the renewal conversation.
You walk into the call already briefed. Forty minutes later, the call ends:
“Log next steps from that call: confirm new champion by Friday, send the expansion deck, schedule technical review for the week of the 22nd.”
The Task lands on the right Account, owner set, in the same audit trail your manager already trusts and IT already audits. You never opened the app.
What changes about your week.
Three things, mostly.
Account briefs stop taking thirty minutes.
The Account 360 prompt reads open opportunities, recent cases, last touch, and contract data, and gives you the one-paragraph readout. Same data your CRM already had. Just answered, instead of clicked through.
Stuck deals surface themselves.
A prompt called Stuck Deals lists every opportunity over $50k that hasn’t moved in two weeks, sorted by close date. Run it Monday morning. Forward the list to your team. Done.
Renewal risk becomes proactive, not retroactive.
Henoyo joins your CRM relationship signals to your support data and your usage data, and flags accounts where the pattern points to churn (declining engagement, open tickets, lost champions) before it shows up in your forecast.
That’s three. There are thirty-four others.
Day-one prompts. The hard parts already done.
Thirty-seven prompts and skills ship in the box. Your team picks the ones that matter and starts using them the same week, because the work that used to require a six-month project (connect the systems, write the prompts, expose them across channels) is already done. You’re configuring, not engineering. Your IT team signs off on the standard controls they already approve for any other Salesforce-connected app.
Sales.
15 promptsAccount intelligence, pipeline coaching, proactive outreach. Reads from your CRM; writes only when the Skill is approved.
Renewal 360.
Surfaces relationship history, open risks, and timely talking points so a renewal conversation walks in fully briefed.
Hunter 360.
Profiles a prospect account against similar won customers, surfaces relevant contacts, sets up the first outreach.
Analyze contract terms.
Reads contract PDFs attached to an account, extracts key terms, flags collection-relevant clauses for review.
Sentiment analysis.
Reads recent activity and email threads, returns a Positive / Negative / Neutral signal so at-risk accounts surface early.
Email-thread context.
Pulls Microsoft Outlook email threads linked to the account's contacts so the rep has full context without leaving Salesforce.
Deal coach.
Evaluates an open opportunity against stage, contact engagement, and recent activity. Returns concrete next steps.
Opportunity 360.
Builds a comprehensive deal brief: history, current state, next steps. Built for pipeline reviews and rep handoffs.
Outbound lead follow-up email.
Drafts a concise, professional follow-up for outbound leads. Lands in your drafts; never sends automatically.
Inbound lead follow-up email.
Drafts a personalized response to an inbound lead inquiry while the lead is still warm. Lands in drafts.
At-risk detection.
Flags accounts showing churn signals (declining engagement, open cases, relationship gaps) before they become lost revenue.
Stakeholder brief.
Lists the key stakeholders on an account with role, engagement history, and influence. Reps know who matters.
QBR prep.
Assembles the quarterly business review (performance highlights, open issues, strategic talking points) into one shareable brief.
Cross-sell on purchase history.
Reads transactional data from the connected ERP, surfaces whitespace and ROI-aligned cross-sell opportunities for the account.
YoY customer spend.
Compares year-over-year spend trends for an account. Highlights growth, decline, and seasonal patterns for renewal conversations.
Data warehouse.
3 promptsFinancial and operational data already lives in Snowflake, Redshift, BigQuery, or Synapse. Henoyo reads it directly into the workflow.
Account transactions.
Pulls and summarizes transaction history from your data warehouse: Snowflake, Redshift, BigQuery, Azure Synapse.
Account holdings.
Reads holdings data from the connected source so advisors can talk through portfolio positions in the same flow as the CRM.
Search-to-insight engine.
Connects an inbound case question to the knowledge base in your data warehouse, returns a precise answer with citations.
ERP and operations.
10 promptsOrder, invoice, and fulfillment intelligence. Henoyo joins ERP records to the CRM record so account, support, and finance teams see one truth.
Renewal assessment.
Joins CRM relationship signals to ERP order and invoice health. Returns an evidence-based view of where the account stands.
Revenue reconciliation.
Reconciles revenue across systems. Surfaces discrepancies and gives finance one trusted view of invoiced vs. recognized.
Financial readiness.
Reads payment history, outstanding balances, and credit indicators ahead of a renewal, upsell, or contract expansion.
Credit memo lookup.
Retrieves and summarizes open credit memos for an account so the team can resolve billing disputes faster.
Invoice dispute resolution.
Cross-references open cases with invoice and order data, surfaces the root cause of a billing dispute.
WISMO resolution.
Answers “Where is my order?” inquiries by pulling live order and fulfillment data. No manual lookup, no escalation.
Backorder alert.
Detects open backorders and flags at-risk fulfillment commitments so account managers communicate before customers ask.
Delivery timeline.
Consolidates expected delivery dates and order statuses. Sets accurate expectations and reduces inbound status inquiries.
Order status check.
Summarizes all active orders for an account with quantities, stages, and expected ship dates. Anyone can answer order questions.
Compare quote to PO.
Lays a customer's purchase order alongside the CPQ quote in a side-by-side table. Catches discrepancies before they're disputes.
Service and case management.
9 promptsFaster resolution, smarter routing, higher CSAT. Drafts, classifies, and closes cases with the audit trail still in place.
Case follow-up email.
Drafts the right email for any case state, addresses open issues with empathy, and requests feedback once a case is resolved.
Case intent analysis.
Reads the closed case across activities, emails, and tasks. Identifies customer intent and recommends next best action.
Case root-cause analysis.
Produces a structured root-cause write-up for any case with corrective-action recommendations. Helps support resolve recurring issues.
Escalated case.
Triggers a focused root-cause analysis the moment a case is escalated and closed. Every escalation documented.
Case-close form completion.
Populates root-cause reason, root-cause analysis, and case summary at closure. Eliminates manual data entry.
Routing information.
Assigns routing on inbound email-to-case records so each case reaches the right team and SLAs are met from the start.
Proposed resolution.
Generates a suggested resolution for inbound support emails. Agents get a strong starting point, not a ghost-written reply.
Document analysis.
Turns a PDF attached to an account into an interactive knowledge resource: concise summary plus the questions teams actually ask.
Generate KB articles.
Turns resolved cases into publish-ready knowledge-base articles with title, summary, problem statement, and a stable URL slug. PII stripped.
Build new ones in conversation.
Had an idea at 9am? Demo it by lunch.
Henoyo’s prompt builder is a chat. You describe what you want, “every Monday, give me the deals I should focus on this week, ordered by what’s about to close,” and the assistant drafts the prompt, runs it on real data, shows you the output. You refine the same way: “add the last two notes from the account.” When you like it, you deploy it. Your team has access the next time they open Outlook, Teams, or their phone.
This is the part that’s hard to explain until you see it. Other tools want you to configure prompts in a form. Henoyo lets you write them by talking.
Voice. Outlook. Teams. Mobile. The phone.
Same prompts, every channel.
- Voice in the browser, today
- MCP for any AI agent that speaks it (Claude, Cursor, Copilot when MCP-routed)
- RESTfor your team’s automations
- Microsoft 365 Copilot: coming next quarter
- Mobile app: this quarter
- Teams · Slack · Telephony: on the roadmap
What it costs.
About $20 to $40 a month for a ten-person pilot. That’s what you’ll pay AWS or Azure directly, for the compute. Henoyo’s subscription is a separate per-tenant number, set in conversation when you scale up.
No per-seat math, no per-message metering, no surprise bill at the end of the quarter. The pilot is small enough to expense. Big enough to prove the ROI on one renewal.
What your IT team will ask. The short version.
Henoyo runs inside the AWS or Azure account your IT team already manages. Three answers to the questions that come up first.
“Where does the install actually live?”
In your AWS or Azure account, not on Henoyo’s servers. CloudFormation or ARM template, deployed by your DevOps lead in about an hour.
“What does Henoyo see of our Salesforce data?”
Only what your admin pins to each prompt. Nothing implicit, nothing org-wide. Henoyo runs as a Connected App authorized by your admin, with the same OAuth controls and revocation path as any other Salesforce integration. Tokens stay in your AWS Secrets Manager or Azure Key Vault; nobody at Henoyo sees them.
“What about audit and compliance?”
Every read and every write is logged immutably in your account, retained for six years by default. The GDPR, HIPAA, CCPA, and DPDP controls you’ve already configured for Salesforce continue to apply. Henoyo doesn’t change your sub-processor relationship with Salesforce.
Common questions.
Will my reps actually use this, or will it sit unused like the last AI tool?
That's the right question. The answer is: they'll use it on the channel they already work in. You don't tell a sales rep to learn a new app. You give them voice in their car, Copilot in Outlook, and a slash command in the team channel they're already typing in. Adoption is a function of zero new tabs.
How long until I prove it's working?
Two weeks, if you pick the right prompt. Stuck Deals or Pre-call Brief are the usual first wins. You measure rep hours saved, or deals that moved that wouldn't have. The pilot pricing makes that easy to justify on one quarter's data.
What if I want to change how a prompt works?
You change it in the chat. Tell the assistant “add ARR to the Account 360 readout”. It updates the prompt, shows you the new output, and you redeploy. The whole cycle is two minutes if you know what you want.
What if it gets the answer wrong?
Tell the assistant what you wanted instead. It updates the prompt. Same fix for the next time, same fix for everyone on your team, because there's one prompt, not fifty rep-specific copies.
Does this replace Salesforce?
No. It reads your Salesforce and writes back through it. Your reports still run, your dashboards still work, your reps still log into Salesforce when they need to. Henoyo is the layer that makes the data answerable from anywhere your team already is.
Will my IT team actually accept this?
They usually accept it faster than they accept the alternative. The alternative is another SaaS vendor with another trust review, another sub-processor, another data egress story. Henoyo runs inside your AWS or Azure account on infrastructure your DevOps team already manages. There's no new vendor relationship, no customer data leaving your boundary, and the OAuth, audit, and IAM controls you've already built for Salesforce keep working unchanged. The first question your security team usually asks is "where does this run," and "in your account, on your tenant" is the answer that ends most reviews quickly.
How does this differ from Salesforce Agentforce?
Agentforce runs inside Salesforce, uses Salesforce's models, sees only Salesforce data. Henoyo runs in your cloud, lets you pick the model (Claude, GPT-4o, Bedrock, Azure OpenAI), and sees Salesforce plus your ERP, your warehouse, and any other system your team already lives in. If you're 100% Salesforce, Agentforce is a strong native fit. If your team's reality is Salesforce + Outlook + Slack + an ERP, Henoyo is the layer that handles all of it the same way.
Ready to see it on your data?
Book thirty minutes. We'll deploy the demo install while you watch, into your AWS or Azure account, with your IT lead in the meeting if you want. Run the Account 360 prompt against one of your accounts, and you'll have a working pilot your security team can review on the same install before the meeting ends.