English
Request a call Open the demo
Internal system for SMEs

Internal communication

Chat, the message board, notifications and comments are in the same system as the tasks, the projects and the customers. A comment goes on the ticket it is about, and a notification takes you straight to the work in one click. That way nothing important is left behind in a separate exchange.

Why this page exists

What does it actually fix?

Decisions nobody can reconstruct

The customer complains, and you cannot show what was agreed. The change came up in a chat, the revised drawing arrived as an attachment, and the task still carries its original wording. All three exist, but none of them knows about the other two.

Conversations in three places

The agreement happens in a message, the file goes to a drive, and the task sits in a third program. The problem is not anyone's memory, but the fact that the three pieces never come together.

Information that depends on forwarding

“Nobody told me.” That is usually true, because one colleague was supposed to pass it on and was at a customer site that day. A company should not depend on somebody remembering to say something.

Announcements that sink

The summer hours went out in an email in April. In July nobody can find it, and anyone who joined since does not know it existed.
Our approach

Communication inside the work, not beside it

Dedicated team messaging tools are deep, with threaded replies, bots and multi-step integrations. Most of that depth is neither understood nor used by most of the people who have it. In a growing company the real difficulty is that the conversation and the work happen in two different places. That is why IntrApp keeps it simple, and communication is part of the work rather than a separate channel beside it.

0 separate chat subscriptions
1 notification centre for every module
~30 min automated setup
Chat

A quick question that does not break your focus

You can start one-to-one conversations and named group rooms, in the same window where you work on customers and tasks.

Read receipts in real time

You can see that a message has arrived and been read, and in a group, who has read it so far. That removes a whole category of messages, the ones that only ask “did you get this?”

Files saved to the central storage

Anything sent over chat is also in the file manager. Nobody has to scroll back three hundred messages to find last week's spreadsheet.

Internal messages stay out of the log

The system logs what changed and who changed it across every module. The text of chat messages is deliberately left out, because an internal message is not a business record.
Message board

One company feed

Announcements, changes to working hours and company news appear on a shared surface instead of sinking to the bottom of individual mailboxes.

History anyone can read back

A colleague who joined last month can scroll back through what happened before them. With a circular email that is impossible, because they were not on the April recipient list.

Colour-coded priorities

The type of each post is shown by colour on the board. Information does not look like a warning, so nobody has to read everything to work out what is urgent.

Optional moderation

Moderation is a single switch. If you turn it on, new posts wait for approval, and the moderator can send a post back with a reason. If you leave it off, colleagues' posts appear without approval.
Notifications

One notification centre

Every module reports to the same place, whether it is a task assigned to you, a deadline coming up, a file shared with you or a calendar invitation.

Channels you set per event

There are more than twenty event types, and for each one you decide separately whether you want it in the app, by email or as a browser notification. A system that tells everybody about everything teaches people within a fortnight to stop reading it.

It takes you to the thing

A notification is more than a line of text telling you something happened. Click it, and you are on the task, the ticket or the customer's record it refers to.

Cleared in one action

The number of unread notifications is shown in the header, the full list is on one page, and a single action marks everything as read.
Comments

Remarks that keep their context

A comment goes on the thing it is about, whether that is a customer, a task or a ticket. That is why whoever opens it six months later finds the whole history there.

History on the record itself

The history is not in your mailbox but on the ticket or the task itself. Whoever takes over the work sees exactly what you saw, without you having to hand anything over.

Targeted mentions (@name)

When you mention a colleague, they are notified. You do not need to send a separate message on another channel to bring somebody into the conversation.

Private or shared, comment by comment

For each comment you decide whether the team sees it or it stays your own working note.
A ticket in IntrApp, with the correspondence with the customer below it, showing your colleagues’ and the customer’s messages in order.
How it fits together

Four tools tied to the work, instead of scattered programs

These four tools are connected to the daily work rather than sitting beside it:

Who sees what

Different levels for different conversations

Who sees what depends on the kind of exchange. Chat messages are seen by the recipients and the members of the room. For each comment you choose whether it is private or visible to the team. Message board posts are open to the whole internal team, and files are shared with named people, with read or edit access.

What you will not find here

Clean handling instead of unnecessary complexity

Chat messages cannot be edited afterwards, there are no threaded replies, and there is no typing indicator. There are no voice or video calls, and posts on the message board cannot be scheduled in advance. If your company genuinely relies on external bots and integrations, a dedicated tool will serve you better.

Frequently asked

What most people ask at this point

We did not make these questions up; they are the ones prospective customers ask us most often. None of the answers is that you will get used to it.

What if the team keeps chatting where they already do?

Informal day-to-day chat can stay where it is. What moves here on its own is the conversation about the work, the kind that belongs to a project, a customer or a ticket, because its place is next to the task.

Do we need training?

No. IntrApp has a built-in manual and a step-by-step walkthrough, so people find their own way in. There are no training days, and nobody has to become the in-house expert.

What does it cost to start?

The automated setup takes about half an hour. There is no implementation fee and no compulsory consulting day.

How flexible is the trial?

During the trial you work in your own system with your own data, and if it turns out not to be right for you, you can cancel at any time.
If something is missing

Ask, and you may not have to pay for it

If a notification or a view is missing, tell us. If roughly three quarters of our customer base would use it, we build it for free, and every customer gets it. We decide whether a request falls into that group, because we can see the whole customer base. We do not promise a delivery date, but we do promise that the request goes into development. Anything specific to your company is built under a separate agreement.

Take a look inside

The demo shows the whole system with sample projects, sample customers and sample documents, with no sign-up and no card, and you cannot break anything because it resets every night. To try it with your own data, that is what the trial is for.

Want to see how this would work for you? We will call you back.

Got a question? Rather talk to someone?

One of our team will get in touch within one working day.

When can we call?

If you add it, we send you a summary of our call.