Account transactions.
Pulls and summarizes transaction history from your data warehouse: Snowflake, Redshift, BigQuery, Azure Synapse.
INTEGRATIONS · DYNAMICS 365 + BUSINESS CENTRAL
Your CRM shows the relationship.
Business Central shows reality.
Pull up any account by voice. See the relationship picture from Microsoft Dynamics 365 andthe operational truth from Business Central (open invoices, payment behavior, order volume, fulfillment status) in the same answer. Henoyo reads both, joins them, 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 Cascade Industries, one of your top ten customers, starts in ten minutes. You’re walking from the parking lot. You ask Henoyo:
“Pre-call brief on Cascade.”
Thirty seconds later, your AirPods say:
Cascade Industries is a $1.2M renewal closing April 30. The relationship side looks fine: Lisa Cho is still your champion, the QBR went well in March, no escalations open. Business Central tells a different story. Four invoices are 60+ days overdue, totaling $84,000. Order volume is down 28% quarter-over-quarter. They ran a big project last cycle and went quiet after. And two of their last six shipments missed the committed date. Recommended: bring AR into this conversation, and acknowledge the late shipments before they do. A small make-good on payment terms might be worth more than the math suggests.
You walk into the call with both halves of the picture. Forty minutes later, the call ends:
“Log next steps from that call: extend net-60 terms on the next two POs, expedite Cascade’s open backorder, schedule a finance touchpoint with Mark by Friday.”
The activity lands on the Account in Dynamics, the priority flag goes onto the open Sales Order in Business Central, owners set on both sides. The audit trail your manager already trusts. You never opened either app.
What changes about your week.
Three things, mostly.
Account briefs include the side your CRM doesn’t see.
The relationship lives in Dynamics 365: open opportunities, recent activities, last touch, primary contacts. The operational reality lives in Business Central: orders, invoices, payment behavior, fulfillment. Henoyo reads both and gives you the joined story, in one paragraph, before you walk into the call.
Renewal risk surfaces from the back office, not the forecast.
The Renewal Assessment prompt joins Dynamics relationship signals to Business Central order and invoice health. An account that looks healthy in the CRM but has overdue AR, falling order volume, or recent backorders gets flagged early, usually a quarter before it would have shown up in your forecast.
Service and finance work from the same record.
A support agent opens a billing dispute. Behind it, Henoyo pulls the invoice, the credit memos, the payment history, and the related orders from Business Central. Your AR team, your account team, and your service team see the same account truth, without anyone exporting a spreadsheet.
That’s three. Ten others ship wired to BC today. Twenty-four more on the way.
Day-one prompts. The hard parts already done.
Thirteen prompts ship live, wired to Business Central and your data warehouse, ready the day you deploy. 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 Microsoft-connected app.
Data warehouse.
3 promptsFinancial and operational data already lives in Snowflake, Redshift, BigQuery, or Synapse. Henoyo reads it directly into the workflow.
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 Dynamics CPQ quote in a side-by-side table. Catches discrepancies before they're disputes.
On the roadmap.
Two more libraries are next on the wiring list.
ACCOUNT MANAGER + SALES REP
Sales · 15 (coming for D365 CRM)
The full Sales library (Account 360, Renewal 360, Hunter 360, Deal Coach, Opportunity 360, Stakeholder Brief, At-Risk Detection, QBR Prep, and the rest) runs against Salesforce today. The same use cases against Dataverse, for Dynamics 365 Sales customers, are next on the wiring list. If your CRM is Salesforce and your ERP is Business Central, you have the full library today.
SUPPORT AGENT
Service · 9 (coming for D365 CS)
Same shape as Sales. The Service library (case follow-up, root-cause analysis, KB-article generation, intent analysis) runs against Salesforce today, with Dataverse wiring for Dynamics 365 Customer Service on the roadmap.
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, list customers whose order volume is down more than 20% quarter-over-quarter and who have overdue AR over $25k,” and the assistant drafts the prompt, runs it on real Business Central data, shows you the output. You refine it the same way: “add the primary contact and the last shipment date.” When you like it, you deploy it. Your team has access the next time they open Outlook, Teams, or their phone.
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, or one prevented bad-debt write-off.
What your IT team will ask. The short version.
We get this from every customer. Three answers, in case you’re forwarding this page.
“Where does the install actually live?”
In your Azure subscription (separate from your Microsoft 365 tenant) or your AWS account, your choice. ARM or CloudFormation template, deployed by your DevOps lead in about an hour. Henoyo doesn’t run inside your M365 tenant boundary.
“What does Henoyo see of our Dynamics and Business Central data?”
Only what your admin pins to each prompt. Nothing implicit, nothing environment-wide. Henoyo authenticates through an application registration in your Microsoft Entra ID tenant, scoped to the Dynamics environments and Business Central tenants you configure. Tokens stay in your Azure Key Vault (or AWS Secrets Manager); nobody at Henoyo sees them. Revocation goes through Entra admin like any other registered application.
“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 Dynamics and Business Central continue to apply. Henoyo doesn’t change your sub-processor relationship with Microsoft.
Common questions.
We’re a manufacturer running Dynamics 365 Sales and Business Central. Does this work end-to-end today?
The Business Central side is fully wired. All ten ERP prompts and the warehouse prompts are live the day you deploy. Your Dynamics 365 Sales side connects through the same Entra ID auth, but the Sales-specific prompts (Account 360, Renewal 360, etc.) are still being wired against Dataverse. If you’re willing to start with the BC and warehouse prompts and add the CRM-side library as it lands, you’re a great fit. If you need full CRM coverage on day one, talk to us. We’re prioritizing based on customer pull.
What if our ERP is Dynamics 365 Finance or Supply Chain Management, not Business Central?
Same connector pattern, same Entra ID auth. The entity surface is different (D365 F&SCM uses a richer OData model than BC) and we map the prompt library to it during onboarding. Most customers see the same use cases work the same way: renewal assessment, revenue reconciliation, WISMO.
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 Teams 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. For Business Central customers, the first wins are usually Renewal Assessment (catches at-risk accounts your forecast was missing) or Backorder Alert (proactive customer comms that prevent escalations). 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 the YTD spend trend to the Renewal Assessment readout”. It updates the prompt, shows you the new output, and you redeploy. Two minutes if you know what you want.
Does this replace Business Central or Dynamics 365?
No. It reads them and writes back through them. Your reports still run, your dashboards still work, your reps still log in when they need to. Henoyo is the layer that makes the data answerable from anywhere your team already is.
How does this differ from Microsoft Copilot Studio or Sales Copilot?
Copilot runs inside the Microsoft 365 boundary, uses Microsoft’s models, and sees primarily Dynamics and the M365 graph. Henoyo runs in your own Azure subscription (or AWS), lets you pick the model (Claude, GPT-4o, Bedrock, Azure OpenAI), and reads Dynamics + Business Central + your warehouse + Salesforce + anything else your team uses, all from the same governed prompts. If your stack is fully Microsoft and you don’t need cross-CRM, Copilot Studio is a strong native option. If your reality is Dynamics + a different ERP, or Salesforce + Business Central, or a multi-vendor mid-market mess, Henoyo handles it the same way.
Ready to see it on your data?
Book thirty minutes. We’ll deploy the demo install while you watch, run the Renewal Assessment prompt against one of your Business Central accounts, and you’ll have a working pilot before the meeting ends.