Digital operations, on autopilot.
An AI assistant in your Microsoft Teams that runs the routine: service desk, SEO and accessibility monitoring, security watch, content drafting and client-ready reporting. Scoped, audited, and approved by humans.
- CVE2 critical advisories ticketed to JiraDone
- SEOWeekly audit posted. 3 fixes recommendedDone
- WCAGAccessibility scan clean on 12 changed pagesDone
- CMS2 page drafts awaiting your approvalYours
- REPORTMonthly status report delivered to SharePointDone
Every action logged. Humans approve anything irreversible.
Not another chatbot
Chatbots wait to be asked. Noice Assistant turns up with the work already done.
Typical AI chatbot
- Answers questions when someone remembers to ask
- No access to your service desk, CMS or analytics
- No idea what changed on your sites overnight
- Trusted with nothing, so it does nothing
- Shared platform, your data in someone else’s pool
Noice Assistant
- Watches your sites, stack and tickets on a schedule
- Works your actual tools: Jira, your CMS, SharePoint, analytics
- Posts digests, audits and alerts before you ask
- Drafts the work; a human approves anything irreversible
- Dedicated single-tenant deployment, in the region you choose
Scoped, deployed, operating
01 / Scope
We map your estate
Your sites, CMS, service desk, and the stack behind them go into an asset register, along with what the assistant is allowed to do and for whom.
02 / Deploy
Your assistant, your tenant
A dedicated, single-tenant deployment in the cloud region you choose, wired into your Microsoft Teams. Nothing shared with other clients. Live in about a week.
03 / Operate
It runs the routine
Daily digests, scheduled audits, security alerts and monthly reports arrive on their own. Chat with it in Teams for everything in between. We maintain and improve it monthly.
One assistant, six jobs
Every module is the same assistant wearing a different hat: scheduled, scoped, and reporting back in Teams. Run the ones that matter to you.
Service desk
Raise, triage, comment and transition Jira tickets from chat. Anything outside scope is logged as a ticket for a human, never dropped. Answers questions from your own docs and procedures.
SEO watch
A weekly technical and content audit of your sites: crawl health, schema, performance, rankings and Search Console data, delivered as a branded report to Teams with fixes ranked by impact.
Accessibility watch
WCAG 2.2 audits across your pages with findings ranked by user impact. Know your conformance position before an audit or a complaint finds it for you.
Security watch
Daily critical-CVE monitoring against your actual stack and a monthly end-of-life review. New advisories are ticketed to Jira automatically, with no duplicates and no silent days.
Content operations
Drafts pages and edits in your CMS from a chat message or an attached brief, and hands you a preview link. Publishing is always a human decision.
Reporting
A client-ready monthly status report, generated from your live delivery data, on brand, delivered to SharePoint and summarised in Teams. Quarterly review packs on request.
The first demo runs on your public website. No access required.
Built for organisations that have to say no to most AI tools
The interesting question is not what an AI assistant can do. It is what yours provably cannot. Security posture documentation is available for your IT review.
Humans approve anything irreversible
The assistant drafts; it does not send. It stages content; it does not publish. Destructive actions are blocked at the framework level, not by a polite instruction it could ignore.
Full audit trail
Every tool call is logged: what was read, what was created, what was blocked. A monthly audit report of everything your assistant did is available as an add-on.
Single-tenant, in your region
Each client gets a dedicated deployment in the cloud region of your choice. Your data never shares infrastructure with another organisation, and it never leaves the jurisdiction you pick.
Your choice of model
The assistant runs on the AI model your organisation approves. For data sovereignty requirements, in-region options such as Claude via Amazon Bedrock keep inference inside your jurisdiction, with no third-party model host and no training on your data.
Frequently asked questions
01
What is Noice Assistant?
Noice Assistant is an AI operations assistant that lives in your Microsoft Teams and runs the routine work of a digital estate: service desk triage, SEO and accessibility monitoring, security watch, CMS content drafting and monthly reporting. It is deployed as a dedicated, single-tenant service per organisation and maintained by Noice as a managed subscription.
02
Where does it run and where does our data go?
Each deployment is a dedicated environment that serves only your organisation, hosted in the cloud region you choose. Your data is not shared with other clients and is not used to train models. The assistant runs on the AI model your organisation approves, and for sovereignty requirements model inference can also run in-region, for example via Claude on Amazon Bedrock.
03
Can it take destructive actions in our systems?
No. The assistant operates behind framework-level write gates: it drafts emails but cannot send them, stages CMS content but cannot publish it, and cannot delete tickets or records. Anything irreversible requires a human. These controls are enforced in code, not by prompt instructions.
04
How do we know what it has been doing?
Every tool call is written to an audit log: what was read, what was created, what was refused. Scheduled jobs are never silent; if a daily security check finds nothing, it says so. A monthly audit report of all assistant activity is available as an add-on.
05
What does it integrate with?
Microsoft Teams for chat and delivery, Jira and Confluence for service desk and documentation, SharePoint for reports, your CMS or DXP for content operations (Magnolia, Adobe Experience Manager and others), and Google Search Console and Analytics for SEO. If your estate runs on something else, integrations are scoped per client.
06
Do we have to take every module?
No. Modules are bolt-on. Most clients start with the service desk, security watch and reporting, then add SEO, accessibility or content operations as they see value. Your subscription is scoped to the modules you run.
07
How long does deployment take?
A scoped demonstration against your public website can be ready in days, because the SEO, accessibility and security audits need no access to your systems. A production deployment, including Teams rollout and security review with your IT team, typically takes about a week.
08
Who controls what our staff can ask it to do?
Access is allowlisted: only nominated people in your organisation can use the assistant, and its scope of work is agreed and enforced per deployment. Requests outside that scope are politely declined and logged as tickets for a human.
09
Is this a chatbot?
It chats, but the value is in what it does unattended: scheduled audits, security monitoring, ticket hygiene and reporting that arrive without anyone asking. The chat surface is how you steer it and ask for more.