Skip to content
AI Chat

One sentence is enough. The chat picks the tool and the source.

The AI chat in the neuland.ai HUB queries systems such as SharePoint, Confluence, your CRM or your databases itself and names the source for every statement. You get the result as Excel, Word, email or Teams post, and it is only sent after your approval.

neuland.ai HUB · Chat

  • and more systems

Nordhafen has been waiting three days for an answer: what delivery time did we promise, and where does the current order break it?

Tools chosen automatically

  • SharePoint · Contract Nordhafen 2025read
  • Confluence · Customer service manualread
  • Salesforce CRM · Order Nordhafenread

The 2025 contract guarantees a delivery time of 10 working days [1]. According to the manual, custom-made products are an exception with 15 working days [2]; the current order, however, is standard goods and has already been open for 12 working days [3]. Suggestion: explain the delay to the customer and offer a credit note.

  • [1] Contract Nordhafen 2025 · § 4 Delivery times
  • [2]Customer service manual · ch. 3
  • [3] Order Nordhafen · Status

Turn this into a draft reply and invite sales and customer service to a meeting on Thursday.

  • SharePoint · Template_reply_letter.docxread
  • Outlook · Invitation for Thu 10/8, 10:00 AMDraft

The draft reply follows your template from SharePoint. The invitation is ready; it only goes out once you approve it.

Reply_draft.docxWord · based on your template

Invitation

Draft
To
Nordhafen sales team, Customer service
Subject
Customer meeting Nordhafen on Thursday
Event
Thu, Oct 8, 10:00 AM
Attachment
Reply_draft.docx
Awaiting your approvalApprove

General AI chats don't know your company. The answers are in your own systems.

Contracts, customer data, manuals, and much more live in systems like SharePoint, CRM, or Confluence, and your access rights apply there. A general AI chat sees none of it; the AI Chat in the neuland.ai HUB reads there with exactly the permissions of the person asking.

Example: customer service

Every detail leads to its source. Contract, manual, and CRM, word for word.

Customer service at Brenntal Antriebstechnik GmbH is preparing Thursday's meeting with Nordhafen Maschinenbau AG. Below the answer are the verbatim excerpts: section 4 of the contract, chapter 3 of the manual, and the order status from the CRM.

Prepare complaint
EU operation
What delivery time did we promise Nordhafen, and where does the current order break it?

The 2025 contract guarantees a delivery time of 10 working days [1]. According to the manual, custom‑made products are an exception with 15 working days [2]; the current order, however, is standard goods and has already been open for 12 working days [3]. Suggestion: explain the delay to the customer and offer a credit note.

Source [1]

SharePoint · Contract Nordhafen 2025

Section 4 Delivery times

Delivery time of 10 working days from receipt of order

Source [2]

Confluence · Customer service manual

Chapter 3 Custom-made products

For custom-made products, a delivery time of 15 working days applies.

Source [3]

Salesforce CRM · Order Nordhafen

Order date and status

Standard goods, order open for 12 working days

Tool choice

The chat chooses which system answers. No one needs to know where things are.

Each person connects their accounts once. After that, the chat decides for every question whether SharePoint, Confluence, the CRM, or the database answers, for example. The web only comes in when you turn on web search.

Result

The answer lands where your team keeps working. As a file, email, post, or page.

The answer becomes what your team needs next, for example the overview as Excel, the draft as Word or PDF, the email in Outlook, the post in Teams, the page in Confluence, or the text for your website. Every result goes out only once you confirm it.

The customer list

All open requests with contract, status, and commitment, as Excel or CSV, ready to import into the next tool.

The draft reply

The reply for Thursday and the summary for division management, as Word or PDF.

The email to the customer

The reply as an email in Outlook, with subject and attachment. It goes out only when you click Send.

The Teams post

After your confirmation, the chat posts the list to the customer service Teams channel, with a link to the file.

The Confluence page

The summary as a page in the customer service space, with sources and date, so the team can find it again.

The text for the website

The clarified answer as an FAQ entry for your website, ready for approval in your content management system.

Control

One chat for everyone. With the approvals of your admins.

Admins enable models, tools and integrations per group and set a default model. After that, everyone works with exactly these approvals, signed in via your existing directory.

ModelsYour choiceYou choose from the models your admins approve, per chat, and can switch even mid-conversation; in Auto mode, the chat chooses on its own, based on the complexity of the question.
PermissionsPer personThe chat reads contracts, manuals, orders, and more in systems like SharePoint, Confluence, or the CRM with the permissions of the person asking; whatever they may not see there stays hidden in the chat too.
TrainingExcludedContracts, customer requests, and chat histories are never used to train language models.
Web searchOff until you turn it onWithout the toggle, the chat answers only from your systems and documents.

Among other things, a DPA under Art. 28 GDPR, TOMs, a DORA addendum, and the ISO 27001 certificate are available for download in the Trust Center.

FAQ

What your rollout team wants to know first.

  • Because it doesn't know your systems and doesn't check your permissions. The AI Chat in the neuland.ai HUB answers from systems like SharePoint, Confluence, your CRM, or your databases, with the login and access rights that already apply there to the person asking. Your data is never used to train language models.

Ask once. The chat searches all your systems.

We show you live, with your own question.

After your request

  1. 01You name a question and the systems behind it
  2. 02We show it live in the neuland.ai HUB, with sample data
  3. 03You learn which integrations you need first

Page footer