Speak instead of typing. Your CRM keeps itself up to date.
Whether a voice note on the smartphone, a Teams meeting or a phone call: ZiyaOS matches every conversation to account, contact and opportunity and updates Dynamics 365. Whatever matters, a human confirms.
Voice noteright after the meeting„They want to start line 2 in early Q2, volume closer to 145 than 120. Quote by Friday.“
ZiyaOS Guard · checks every change
Dynamics 365Müller GmbH · Line 2 expansion
New note addedOn-site meeting with Julia Schneiderautomatic
New contactJulia Schneider, head of purchasingautomatic
New taskSend offer, by Fridayautomatic
New stageProposeawaiting confirmationconfirmed
New amount€145,000awaiting confirmationconfirmed
Confirmation neededConfirmed by you
5 changes · 3 automatic · 2 to confirm
Speak instead of typing
A few sentences after the meeting, in the car or on the way. No form, no catching up in the evening.
Matched correctly
The agent finds account, contact and opportunity in Dynamics 365 and only creates what is missing.
Clean data
Notes and tasks go into the CRM automatically. Amounts and stages only change once the sales rep confirms.
Complete audit trail
For every change it is clear which agent proposed it and who confirmed it.
The Guard keeps your CRM clean.
AI in the CRM is only as good as the data it leaves behind. In the ZiyaOS Guard you decide per action what the agent may do in Dynamics 365: notes and tasks automatically, amounts and stages only with confirmation, deleting never. Every decision is logged.
Confirmation neededAgent “Sales” wants to change the opportunity “Line 2 expansion”.
Amount€120,000€145,000
StageQualifyPropose
Confirmed by Lisa M.AdjustConfirm
Log
10:41Delete duplicateBlocked, no rule
10:42Opportunity changedConfirmed: Lisa M.
The briefing before the next meeting.
One sentence is enough. The agent reads account, opportunities, recent meetings and open tasks from Dynamics 365 and sums up what you need to know before the conversation. It only reads, so it runs without asking.
Agent “Sales”Dynamics 365
Prepare my technical meeting with Müller GmbH.
Agent working …
Read accountDynamics 365 · automatic
Read opportunitiesDynamics 365 · automatic
Read recent meetingsDynamics 365 · automatic
Read open tasksDynamics 365 · automatic
Müller GmbH · technical meeting, Thu 10:00
Open: “Line 2 expansion”, €145,000, stage Propose
Offer with the customer since Friday, no response yet
New: Julia Schneider, head of purchasing, co-decides
Suggestion: clarify maintenance questions first, then follow up on the offer
Message the agent…PreparemytechnicalmeetingwithMüllerGmbH.
4 reads · 9 s
Once the data is right, more becomes possible.
All on the same foundation, with the same rules and the same audit trail.
Next best actions
The agent suggests the next sensible step for each account, based on history and pipeline.
Next step · Müller GmbHFollow up on the offer to Müller GmbH
New leads and projects
Signals from meetings and emails turn into suggestions for new opportunities.
Becker KG · new plant planned
Schmidt AG · tender in May
Market and competition
What customers say about competitors no longer stays in someone's head, it is collected and analysed in the CRM.
Competitors in meeting notesCompetitor A14Competitor B9Competitor C4
Beyond Dynamics 365
ERP, email and SharePoint: agents connect what used to be separate.
Dynamics 365ERPEmailSharePoint
Frequently asked questions
Does the AI change my CRM without confirmation?
The AI does not make important changes to your CRM without confirmation: ZiyaOS only applies them after you confirm. You define which changes need a confirmation through rules.
Can ZiyaOS connect to SAP, M365, DATEV or our ERP?
Yes, ZiyaOS can connect to SAP, M365, DATEV or your ERP, as to every system that has an API (MCP, REST). Even without an API, an agent may be able to operate the software.
How do I make sure nobody does what they aren't allowed to?
The ZiyaOS permission check makes sure nobody does what they aren’t allowed to. Every action runs through it: who may do what with which resource? This applies equally to people, agents, workflows and apps. For each endpoint you decide whether access is allowed automatically, needs a confirmation or is forbidden. You separate permissions and resources by department or person.