Skip to content

Customer enquiries · 5 min read

Who is answering that customer?

A customer emails the office, then phones with another detail. One colleague thinks the enquiry is being handled. Another has sent a reply and moved on. You can all see the messages, but you still have to ask what happens next. Would a shared inbox solve it?

Start here.

A shared inbox can help when several people answer the same customer address and need to see who is handling each conversation. Before choosing one, check whether your problem is a missed reply or unfinished work after the reply. Those need different ways of keeping track.

  • Being able to read an email does not show who owes the next action.
  • Keep a customer conversation connected to any work that continues after the reply.
  • Try a handover between two colleagues before committing to another tool.

Find the enquiry that made you chase a colleague

Choose a recent enquiry where someone had to ask, “Has anybody replied?” Follow the messages and the work they led to. Did no one take responsibility, did two people answer, or did a useful reply leave something unfinished?

Imagine a small furniture repair business. This is a hypothetical example. A customer emails about a damaged chair. The office asks for a photo. The customer phones with a collection address, then emails the photo the following morning. The person who took the call is away that day.

All three messages belong to one enquiry. Reading the email is only the start: somebody must see the address, assess the photo and tell the customer the next step. If that person cannot see the phone note, another inbox alone will not fill the gap.

Give the next action a name and a date

Agree what your team needs to see without asking around. A useful starting point is the customer’s request, one person responsible for the next action, and when to look at it again. Keep the original message available so the next person can check the detail.

The responsible person does not have to do every part of the job. They need to know what is waiting and arrange the next handover. “I asked someone else” should leave a visible next step.

Use a short card like this in whatever shared place your team already checks. The entries below continue the hypothetical chair enquiry; they are a planning example, not records from a client.

Example handover card for the hypothetical chair enquiry
What to keep visibleExample entry
RequestAssess whether the chair can be repaired; link to the email and photo
Next actionAlex checks the photo and sends the next step
Waiting forAlex’s assessment; the customer has supplied the photo
Check againThis afternoon, before the reply we promised
Useful contextCollection address was supplied by phone; note attached
Work after the replyIf accepted, link to the repair job and its collection arrangements

Check what your current email setup can already do

Ask whoever looks after your business email whether people can assign conversations, see shared replies and find requests that still need attention. Separate sign-ins let you give each colleague the access they need without passing around one password.

For example, Google documents a Collaborative Inbox in Groups where members with the right permissions can take or assign conversations and mark them complete. That is a reason to check existing options before buying a new service. It is not a recommendation that every Google account or email setup will suit your team.

If everyone can read the same mail but responsibility is still hidden in personal folders or memory, look for a tool that makes the handover visible. Ask to see what happens when no one is available to take a new request. Automatic assignment still needs someone watching for work left unassigned.

Keep the shortlist tied to the problem. If customers mainly email you, you do not need to open more contact channels just because a demonstration includes them.

Try a handover with two colleagues

Use invented customer details in a trial or demonstration. Give one colleague the first email from the chair example and ask the other to pick it up after the phone call. Then introduce the photo as a later reply. Let the people who would use the inbox do the exercise themselves.

Ask the second colleague to find the next action without help from the first. Can they see that the photo arrived, the address came by phone and an assessment is still owed? Can they tell the difference between a private staff note and a message the customer will receive?

Now have both colleagues open the same enquiry. Ask each who should reply, and check the tool’s way of showing that someone is handling it. Finish by moving responsibility to the other person and finding the enquiry again from their view.

Finally, send another customer reply after the conversation was marked complete. Does it return somewhere the team checks? Decide who reviews new, unassigned and waiting enquiries during an absence. A tool can display those lists; your team still needs an arrangement for using them.

Choose what needs to stay open after you reply

For a simple question, sending the answer may finish the work. In the chair example, sending a repair estimate may only begin it. The customer could still need a collection date, and the repairer needs a job to work from.

Decide where that continuing work belongs. If your team already uses a job system, ask whether the conversation can link to the correct job, and who checks that the handover happened. Keep one agreed place for the current collection date rather than maintaining competing dates in an inbox note and a job record.

A clearer daily handover may be enough if the existing email tools let everyone find and finish the work. A shared inbox is worth trying if assigning replies and covering absences remain awkward. A connection to existing job software becomes relevant when people keep copying commitments out of email to make the work happen.

Bring the handover card and the awkward reply to a supplier conversation. Ask them to show the complete enquiry, including what remains after the customer gets an answer. That gives you a concrete way to judge whether an existing product fits or a small addition needs to be built.

Bring one enquiry to the conversation

You do not need a list of software features. Show where the next action becomes hard to find.

Where it arrives
Which address or contact route starts the enquiry, and where do phone updates get recorded?
Who picks it up
Who owns the next reply, and who checks work left waiting during an absence?
What finishes it
Does an answer complete the request, or does a job continue elsewhere?
What to demonstrate
Ask two colleagues to try a handover, a simultaneous reply and a late customer response.

Planning something with a similar workflow?

Discuss your project with us

A couple of common questions.

Do we need to move every customer conversation at once?

Start a trial with one clearly defined address or type of enquiry. Agree where replies will be sent and checked during the trial so customers do not end up with two separate conversations. Keep access to the history people need, and check any import or export requirements before changing the wider process.

Should we choose software by how many emails we receive?

Email count is useful context, but it does not show what the team must do. A few enquiries that require several people and follow-up can be difficult to manage. Many simple questions may be straightforward. Choose using examples of the handovers and unfinished work you actually need to handle.

Have something in mind?

Tell us what you want to build or improve. We’ll work out a useful first step together.

Discuss a project