Skip to content
Two people at a desk, one handing a request over to the other.

The help desk for your team

Requests — A request sat in the inbox for three days because Lena was on vacation, and the customer called to ask whether his email had arrived. With the CIRO NOISE help desk your customers write through the form on your website. Every request sits with a number, a status and an owner in a list your whole team sees. The AI suggests a priority and a reply, the reply goes out by email, and the customer sees where things stand in the support portal.

GDPR-compliantServers and AI in the EU

One help desk everyone sees

Requests arrive through the form on your website, and every organization has a public address for it. Every request gets a number, a priority, an owner, a history and attachments such as images or PDFs. Its status runs from New through Open, In progress and Resolved to Closed. Confirmation and replies go out by email on behalf of your organization, with its short name as sender. On her page in the support portal the customer also sees how quickly your team usually replies, calculated from your real response times over the last 90 days.

Three requests as they come in every week

An outage on Friday, a question from last month and one that needs an appointment.

Friday, 4:40 pm: Ms. Sommer reports an outage

The request comes in through the form, with a screenshot attached. The AI rates it urgent and explains that with the word “outage” and the time of day. Lena has already left, so Pascal takes the request from the list and sets himself as owner. The reply goes out by email, the state is in the support portal, and Ms. Sommer does not have to call on Monday.

Priority with a readable reason

Attachments right on the request

Reply by email, state in the support portal

Change owner with one click

Tuesday: the question that came up last month

A customer asks about the credit note for a canceled invoice. The AI finds the resolved request from March and the wiki page on it and attaches a reply proposal to the request. Lena reads, changes one sentence and sends. The customer clicks “This solved my problem” in the support portal and gives five stars.

Proposal from the wiki and resolved requests

Sent only after a person clicks

“Solved” click by the customer

Rating with one to five stars

Thursday: the request needs a conversation

Ms. Sommer wants to discuss the new form on the website. Lena sets up a meeting right from the request. It sits in her calendar, and Ms. Sommer gets the invitation. The request already hangs on the Brandt & Söhne record, because CIRO NOISE recognized the company by the email address. At month end Kira sees in the reports how fast the team replied and how satisfied the customers were.

Meeting right from the request

Customer record by email domain

Reports only for those with permission

Response time and satisfaction as figures

Requests in detail

Form, support portal, AI suggestions and reports at a glance.

Contact form for your website
Requests arrive through the form on your website. Every organization has a public address for it.
Tickets with status and priority
Number, status from New to Closed, priority, owner, history, attachments as image or PDF.
Support portal without an account
No account needed, opened with a PIN or secure link. The customer sees the state, replies and attaches files.
Emails in your company’s name
Confirmation and replies go out with your organization's short name as sender. The response time the customer sees in the support portal comes from real figures.
AI reply suggestions
Suggestions for priority and reply, plus translation and summary. A reply goes out only after your click.
Response time and satisfaction
“My requests” shows every person their own. Only people with the permission see the reports on response time and satisfaction.

Tell Claude. CIRO NOISE records it.

Claude connects to your organization through MCP, the open standard for AI tools. Every feature lives in one system, so one sentence from you is enough for Claude to look up the customer, draft a quote, create a task and update the wiki. It works with exactly the permissions you grant.

Claude in support

  • Find earlier solutions and proven answers to a question

  • Read the customer record with open requests, invoices and history

  • Turn a request into a task for the team, with the invoice and the proven reply linked

  • Log what you promised the customer on their record

Frequently asked questions

Yes, for the customer service of small teams. Every request becomes a ticket with a number, priority, status, owner and history. Replies go out by email, and the customer follows her ticket in the support portal. Requests come in through the form on your website, not through a forwarded mailbox.

In a few minutes. You embed the request form on your website as a snippet of code or send it as a link, and every request lands right away in your team's list. Replies go to the customer by email.

In the support portal, protected by a PIN or a secure link, with no account needed. There she sees the status, replies, attaches files and rates at the end how satisfied she was.

It suggests a priority and a reply, based on your wiki and on resolved requests, and explains both. Your team checks, adjusts and sends. Every reply goes out faster and still sounds like your team.

Yes. Once a request is resolved, the AI turns it into a draft knowledge entry without personal data. As soon as someone on your team approves it, the AI draws on it for a similar question and suggests the earlier reply. Internal notes on the request stay within the team.

With one click on the request: the task lands with its own number in the board you choose, and the link works both ways. The customer keeps following the state in the support portal, your team works in the board.

In the reports on response time and satisfaction, calculated from the history and your customers' ratings. Every reply sits on the request with name and time, and “My requests” shows each person their own.

And everything else is already included

Every feature shares one login and one permission system. A request sits in the customer record, becomes a task and lands on the invoice without anyone retyping it. Here is what else is included:

Two seats are free

With up to two people, you use CIRO NOISE for free, all features included. From the third person on, each seat is €25 per month plus VAT.

No credit card needed to get startedGDPR-compliantServers and AI in the EU