Where does your call data actually go?
Almost every AI receptionist stores your calls on the vendor's platform. Enquiry 360 does not, and this page explains exactly what that means in practice.
Short answer. Enquiry 360 installs into your own Microsoft tenant. Your enquiry records, transcripts and reporting live in your Dataverse environment, running on your Azure subscription in the region you choose, under your access controls and your retention policy. Maya Information Systems holds no copy of your data, and if you leave, it stays where it already is.
Why does it matter where an AI receptionist stores your calls?
Because a phone call to a business is rarely trivial data. A caller gives a name, an address, a phone number, sometimes a medical concern, a legal matter, a financial difficulty or a safeguarding issue. Under UK GDPR that is personal data, and in several cases it is special category data, and you are the controller of it.
If your AI receptionist is multi-tenant software as a service, that data is processed and stored on the vendor's infrastructure. That is not automatically wrong, and plenty of organisations accept it, but it makes the vendor a processor of your callers' personal data and it puts your records inside somebody else's platform. For a council, a housing association, a law firm or a clinic, that is a procurement question that has to be answered before anything else gets discussed.
What does "in your own Microsoft tenant" actually mean?
It means the software runs in your Microsoft environment rather than ours. Concretely:
- The Enquiry 360 solution is installed into your Microsoft Dataverse environment, from Microsoft AppSource.
- The voice agent runs as a container in your own Azure subscription, in the Azure region you select.
- The language model is your own Azure OpenAI resource, in your Microsoft Foundry, on your bill.
- The voice agent writes directly into your Dataverse tables, one structured record per enquiry, which you can query, report on and delete under your own retention policy.
It keeps running if you delete our Microsoft account. There is no dependency on a Maya-hosted platform, because there isn't one.
What sits in your environment
There are two separate things on any call: the call itself, and the record it produces.
A caller's voice reaches you across the public telephone network, through their mobile carrier, exactly as it would with any phone system on earth. The processing and the resulting records sit inside your Microsoft environment, in a region you choose, rather than on a vendor's multi-tenant platform. That is the distinction a data protection officer cares about.
How does this compare with other AI receptionists?
| Typical AI receptionist (multi-tenant SaaS) | Enquiry 360 | |
|---|---|---|
| Where call records are stored | The vendor's platform | Your Microsoft Dataverse |
| Who chooses the region | The vendor | You |
| Which AI model account is used | The vendor's | Your Azure OpenAI resource |
| Access to your records | Through the vendor's portal | Your own system, directly |
| If you stop being a customer | Request an export | Nothing moves, it is already yours |
| What you end up with | Messages and call logs | A structured business system |
This table describes the standard multi-tenant SaaS model rather than any named competitor, because architectures differ and you should ask each vendor directly. The useful question to put to any of them is simply: in whose tenant does this run, and who can read the records?
Does this make Enquiry 360 GDPR compliant?
It removes a category of problem. Your records are not sitting in a third-party platform, so the questions of international transfer, sub-processor sprawl and vendor lock-in get considerably shorter. You remain the controller, you set retention, and Enquiry 360 honours the retention and bulk-delete policy you configure in your own Microsoft Dataverse. No product can make an organisation compliant on its own, and any vendor claiming otherwise is overselling.
Who is this actually for?
It matters most where the caller's data is sensitive or the buyer is regulated: local government and social housing, law firms, clinics and veterinary practices, and financial services. It matters least to a sole trader who wants messages taken.
Can I hear it before I believe any of this?
Yes, and that is the fastest way to judge it. There is no form and no demo to book.
From £99 + VAT a month. Free setup, cancel anytime. Or email us a direct question about data residency.
Frequently asked
Where is my call data stored with Enquiry 360?
In your own Microsoft tenant. The solution is installed into your Dataverse environment and runs on your Azure subscription, in the region you choose, under your access controls and retention policy.
What happens to my data if I stop being a customer?
It stays where it already is, because it never lived anywhere else. There is no export to request and no vendor to ask.
Can Maya Information Systems see my call data?
Only where you grant access. Where we help set up or change your forms, that access is granted by you, operates under your controls, and is revocable at any time.
Which Azure region does it run in?
The one you select, because the components sit in your own Azure subscription.
Do I need my own Microsoft account to use it?
Yes. That is the trade-off. You need a Microsoft tenant and an Azure subscription, and we walk you through opening them. In exchange you own the system rather than renting access to someone else's.
Is it on Microsoft AppSource?
Yes. Enquiry 360 is published on Microsoft AppSource, which is how the Dataverse solution is distributed into your environment.
Is there a Microsoft AI receptionist?
Yes, and this is one. Microsoft itself does not publish an AI receptionist under that name: it provides Copilot Studio, a toolkit for building agents, and Dynamics 365 Contact Center for large contact centres. Enquiry 360 is the finished application, published on Microsoft AppSource and installed into your own Microsoft Dataverse, answering your phone line and writing each enquiry straight into your own tables. An AI receptionist that runs on Microsoft rather than one bolted onto it.
Where does an AI receptionist store call data in Microsoft Dataverse?
In the tables of your own environment. Each call becomes a structured record, with the transcript held against the session, in the same Dataverse environment your Power Apps and Dynamics 365 already run on. Nothing is copied to a vendor platform, so retention, access and data residency stay under your own policy rather than ours.
Can an AI receptionist work with Microsoft Teams?
Yes. It works alongside Microsoft Teams rather than living inside it, which is usually what people are after when they ask. Calls arrive on an ordinary number through Azure Communication Services, and the enquiry lands in the same Microsoft Dataverse your Teams users already work in. A Power Automate flow posts it into a Teams channel the moment it is captured, so the record reaches your team where they already are, without anyone answering the phone.
Is this a voicebot, and where does a voicebot keep what it hears?
It is a voicebot, a virtual agent and the thing an IVR was trying to be, all at once. What separates it from most is where the words go: into Microsoft Dataverse in your own tenant, on your own Microsoft agreement, in the region you choose.