Knowledgeinbox

Bring email and messaging together: answer customer enquiries consistently

Connect your message channels through a complete response process, with a channel inventory and an example enquiry arriving by email and messaging.

A customer sends an enquiry by email, then adds an important detail through a messaging channel. For them, both belong to the same issue. Inside the business, the information may reach two people in separate applications. If each person only considers their own incoming messages, they may ask for details already explained or send two answers based on different information. A shared working process helps you turn the available details into a relevant reply.

Bringing email and messaging together therefore means more than reducing the number of open windows. Your team should understand what the customer actually wants, which update arrived most recently and who is handling the next answer. Each message remains understandable in its original channel. The connection comes from organising the business’s work around the customer’s issue.

The following example uses a fictional service business arranging a meeting room for a customer. The company initially needs details about the intended layout and later receives a change. We follow the enquiry from its first arrival through internal coordination to the reply. Times and content are illustrative suggestions for this business, rather than a real customer reference.

Identify the channels through which real work arrives

Start with the routes customers actually use today. These might include a general email mailbox, an individual business email address and a messaging channel used by the organisation. Record the real accounts specifically enough to check them later. The heading “messaging” alone does not identify which connection your business needs.

Three questions are particularly useful for each entry point. What issues arrive there? Who handles them now? Where is information transferred into another application or passed to another person? The last question shows where context can be lost. A channel with few messages can still matter if it carries decisive changes to ongoing customer work.

Example entry point Typical content
General email New enquiry with attachment
Business email Questions about current offers
Used messaging channel Brief update on the same issue

This inventory describes the fictional business’s current work. It is not an instruction to open additional contact routes. If customers already use suitable channels, the first benefit comes from handling those reliably. New channels can become a separate business decision later. They are not automatically necessary for a workable response process.

During the inventory, also record which accounts a cover person can actually access. An entry point reached by only one person needs different handover planning from an account available within the organisation. What matters is whether the responsible people can do the work, rather than whether another address simply exists.

See how webRichtung Inbox makes email mailboxes and connected messaging channels accessible in one application.

Check required connections against the actual account

The inventory produces a short, verifiable list. For each account needed, establish whether and how it can be connected within your organisation. Check the service and account actually used. Similar names or a general statement about message channels do not establish that a particular connection is configured.

Also decide who needs the account for which work. The office may need to read and answer new enquiries. A specialist needs information to prepare a relevant response. That does not mean everyone in the business should see every connected channel. Available access and permissions should fit actual responsibility.

For the initial trial, choose one business email entry point and one connected messaging channel that is genuinely available. With an agreed internal test contact, check whether the relevant messages can be read and the intended answer can be prepared from the correct channel. The sender and associated conversation history should also be unambiguous.

Record the result for each account. If a required route cannot yet be connected, keep its current handling explicitly organised. You can begin with entry points already usable while clarifying the missing connection separately. A useful start needs a complete process for the selected channels, rather than a general claim covering every conceivable communication service.

Follow one enquiry across both entry points

In the fictional business, an email arrives at 10 am. The customer wants to furnish a meeting room and attaches a room sketch. The message mentions eight intended places and asks for an initial response about how to proceed. The office reads the context and identifies which specialist should assess the enquiry.

At 11:20 am, the customer adds through the messaging channel that twelve places will probably be needed. They refer to the morning enquiry. This update changes the basis of the work. The first email alone is therefore no longer sufficient for the answer. The office needs to associate the update with the known issue and record the current requirement clearly.

Check the available clues: who is writing, which proposed work the message concerns and whether it fits the earlier conversation. If the association remains unclear, the responsible person asks a specific clarifying question. An assumption then becomes a reliable connection. The shared application makes the channels accessible; interpreting the issue remains a task carried out deliberately.

In the example, the result is one meeting-room enquiry with a sketch and an update from eight to twelve places. Two incoming messages therefore do not mean two new customer enquiries. This distinction also matters later when reviewing the work. Above all, it prevents two people from independently continuing with different requirements.

Prepare the answer using the current customer situation

For the substantive work, the responsible person needs the original reason and the relevant change. In the example, they should assess which further information is needed for sensible planning. They consider the existing sketch and the twelve places now intended. The follow-up question can then focus on what remains open rather than requesting details already supplied.

One possible open question is whether all twelve places are permanently required or only needed for certain meetings. This distinction is a professional consideration by the fictional service business. The customer has not already answered it. Preparing the response therefore separates what is known from what still needs to be clarified together.

A suitable wording might be: “Thank you for the sketch and the update. We are now allowing for twelve places. Should these be set up permanently or only be available for particular meetings? That detail will help us prepare the next planning step appropriately.” The text confirms the current position and explains why the question is useful.

This answer refers to both entry points without asking the customer to assemble their information again. It also shows that the change has been received. The business does not yet promise a completed room design; it identifies the next useful step. The customer can understand why their additional answer is needed.

Agree who will reply through which route

Before sending, the team clarifies responsibility for the reply. In the example, the office handles the agreed response while the specialist provides the necessary assessment. It is then clear who actually prepares and completes the message. Another person does not need to answer the same enquiry again as a precaution.

The response channel depends on the actual agreement and content. If further planning alongside the sketch is to continue by email, the substantive question can remain there. A brief message in the other channel can explain that route when useful within the real contact process. Two detailed parallel conversations are not automatically required.

The customer needs to recognise the next step. They should know what to answer and where further coordination will take place. Internally, it must also be clear whether the question is prepared or already sent, and who will handle the later answer. Record that working state within the process your team actually uses.

Shared access alone does not allocate responsibility. For the first case, therefore explicitly agree who owns the issue and who provides cover. When a message changes channel, responsibility remains traceable at the level of the customer’s concern. This is the foundation for additional contact routes to improve accessibility without producing conflicting answers.

Make the attachment available for further work

The room sketch continues to be needed in the example. Authorised people should be able to find it where the business works with documents. In webRichtung Inbox, email attachments can be transferred through Documents into the shared document collection. The attachment can then remain useful throughout subsequent handling.

Maintain an understandable connection to the customer’s issue. The responsible person should be able to identify which sketch forms the basis and whether a new version has arrived later. A copied file without context does not settle which information is current. The transfer therefore comes with a clear association in the actual working process.

If a changed drawing arrives later, the office checks what it replaces and which information remains valid. In the example, a new sketch might show the arrangement of twelve places. The next response then refers to the version actually available. The team should not have to decide from memory which document was used most recently.

One completed case with a relevant attachment is enough for the first trial. Check whether the person preparing the substantive answer can find and interpret it correctly. That demonstrates the practical value of connecting incoming messages with document work. The number of transferred files alone says little about whether the enquiry is being handled better.

Assess the process through answered customer issues

After the first cases, focus on whether the customer received a coherent answer. Were additions from the second channel considered? Was the next question genuinely still open? Could the responsible person use the available attachment? These observations reveal whether the shared process helps in everyday work.

Distinguish message volume from customer issues handled. Our example initially contains two incoming messages but one enquiry. A later customer answer to the follow-up question still belongs to that issue. Counting every incoming message as a new enquiry creates a different picture from examining the actual customer work.

A manageable comparison can consider three similar cases before and after the change. Note where information already supplied was requested again, whether two answers arose in parallel and whether the next responsibility remained clear. This can identify which handover still needs improving. The limited observation is a working aid, rather than a general success statistic.

If a problem arises, identify the specific transition. Was access to the messaging channel missing? Was the association unclear? Or did nobody know who would answer? Each cause needs a different correction. This lets you improve the process where your customer or team actually loses time.

Start with one complete response process in Inbox

webRichtung Inbox brings email mailboxes and connected messaging channels into one application. You read, reply to and compose messages within your organisation’s context. Message types remain distinguishable, and email attachments can be transferred through Documents into the shared document collection.

For the first use, choose a frequent enquiry type and the channels actually used for it. Clarify access, identify response responsibility and walk through the route with a specific update. Then check whether both entry points produce one accurate, understandable answer. This gives you a tangible first benefit in your work.

The module page lets you explore Inbox and create your platform account. Begin with connected entry points you can handle reliably, then extend the process through real customer cases. The aim remains a relevant answer that lets your customer and business move forward.

Explore Inbox, create an account and prepare your first shared response process.

Frequently asked questions

What does bringing email and messaging together mean?

For the business, it means handling connected channels through a traceable working process. The customer receives a relevant answer to the same issue even when they add information through different routes.

Are several messages automatically combined into one customer case?

Initially plan association as a deliberate task: check the sender, reason and existing agreements. Check the functions available in your configured process against a specific case. A shared application alone does not establish automatic case association.

How should I check the channels I need?

Create an inventory of the mailboxes and message channels actually used for business. For each required account, check whether and how it can be connected in your organisation and who should work with it.

What does webRichtung Inbox provide?

Inbox makes email mailboxes and connected messaging channels accessible in one application. You can read, reply to and compose messages. Email attachments can be transferred through Documents into the shared document collection.

webRichtung Inbox

Handle messages as a team

Work on emails and messages in the context of your customers and your team’s tasks.