How to manage a shared inbox with a small SaaS team

At UserJot, customers can reach us by email or through the chat widget inside our product. We bring both kinds of messages into a shared inbox, where our team can read and answer them from one place.

Juno, the AI support agent built into UserJot, handles the first response. We give it documentation about our product, which it uses to answer customer questions. When that information is enough to help, the customer gets an answer without waiting for someone on our team to open the message.

Some questions need more than instructions, though. A customer might have followed the docs and still be having trouble. Juno can then bring in a teammate, who can read the exchange and continue helping in the same conversation.

That's the setup behind our support inbox. If you're running support with a small team, the useful part is understanding how a message moves through it: who answers first, when a person takes over, and how to keep track of anything that needs another reply later.

What is a shared inbox?

A shared inbox is a place where teammates can read and respond to the same customer messages. Everyone with access sees the conversation history, including replies from other people on the team. You can pick up a conversation without asking a colleague to forward their copy of it.

We connect our support email by setting up forwarding in our mail provider. Customers keep writing to our usual support address, and a copy of each incoming email goes to UserJot. It appears in the inbox alongside messages sent through the widget.

From there, we can reply inside UserJot. The customer receives an email, replies from their mail app, and their response returns to the same thread. Forwarding changes where we work on the message; the customer can keep using email as usual.

You need to check that forwarding is working before relying on this setup. Send a test message from another address, make sure the original sender appears correctly, and reply to check the return path. Our email forwarding guide covers the provider-specific steps.

With messages arriving in one place, you can decide how they should be answered. In our case, that starts with Juno.

How an AI agent answers shared inbox messages

Juno uses the product knowledge you give it. You can upload documents or have it read pages from your website. Those sources might explain how to get started, where to find a setting, or what a particular feature does.

The detail in those documents matters. If a setting is available only to admins, the instructions should say so. Otherwise, a customer can follow an answer correctly and still be unable to find what they're looking for.

Suppose a customer emails because they aren't receiving notification emails from your product. Your documentation explains where to enable notifications, so Juno can use that information to help them check their settings.

That may solve the problem. The customer turns notifications on, receives the next email, and has no further questions.

It may also reveal that the instructions aren't enough. The customer could reply that notifications are already enabled and the emails still aren't arriving. You now have a specific problem to investigate, rather than a question about where a setting lives.

That is why an AI agent needs a clear way to bring in a person. Juno hands over when it lacks the knowledge or confidence to help, when the topic needs human judgment, or when the customer asks for a teammate. It cannot fix your product, change account settings, or issue a refund.

I'd rather make that handoff early than have a customer repeat themselves through several rounds of unhelpful instructions. If the same questions keep reaching your team, you can review the conversations and add the missing information to Juno's knowledge.

The basic flow looks like this:

Support email       Widget Messages
       \                 /
        UserJot Conversations
                  |
                 Juno
            /           \
    Answers from     Hands off to
    your knowledge   the team's Queue

The last part of that diagram is where your team starts working.

Pick up the conversation where the AI left off

In UserJot, conversations that need a person appear in a view called the Queue. It's the team's list of conversations that need attention. Messages Juno is still handling stay out of that list until they need a human.

For the notification problem, a teammate would open the conversation and read the exchange. They could see that the customer has already checked the setting, so there is no reason to send those instructions again.

The next reply can ask for information needed to investigate, such as which notification the customer expected and when it should have arrived. Explain why you're asking. That helps the customer understand what you're checking and gives them a more useful request than "can you provide more details?"

Once a teammate replies, Juno steps back. It stays out of the thread unless someone explicitly hands the conversation back to it. The teammate can continue the investigation without the agent adding another answer.

For a small team, agree on who is watching the Queue during each part of the day. That person can pick up new conversations or ask a colleague to help. If someone else takes over, make sure they know they're responsible for the next customer update.

Our current dashboard doesn't have a teammate-assignment control, so this agreement needs to be made between people. An internal note helps record it.

Leave enough context for the next teammate

An internal note is a message in the conversation that only your team can see. It lets you keep the investigation beside the customer's messages, without sending your internal discussion to them.

For the notification example, a useful note might look like this:

The customer has notifications enabled but didn't receive yesterday's update. They confirmed the email address is correct. I'll check the delivery history and send them an update tomorrow morning.

That gives another teammate the facts already established, the next step, and the commitment you've made. You don't need to repeat the entire conversation.

If you'll be away tomorrow, speak to the teammate who will cover that update and add their name to the note once they've agreed. A note asking someone to take over can be missed, so don't treat writing it as confirmation that the handoff happened.

Keep the customer informed too. They should know you're investigating and when to expect another reply. An internal note preserves context for your team; the customer still needs a message explaining what happens next.

Set a follow-up before leaving the conversation

After promising an update tomorrow, you need a way to remember it. The conversation may be quiet for the rest of the day while newer messages arrive.

In UserJot, you can set a personal reminder on the thread. Choose when you want it to return and add a short note, such as "Check notification delivery and update customer." When that time comes, the conversation appears in your Queue with the reminder.

The reminder belongs to the person who created it. If a colleague takes over the investigation, they should set their own reminder. Yours won't appear in their Queue.

There are also times when the whole team needs to put a conversation aside. Perhaps the customer says they can test again on Monday, and you've agreed to check back then. For that, UserJot has snooze, which hides an open conversation from the active inbox until the time you choose.

The difference is who needs to act:

Snooze affects the shared conversation, so leave a note explaining why you're deferring it. A personal reminder can bring the thread back for you even if it has since been resolved.

For the notification problem, your promise should be something you can keep. You might not know when delivery will be fixed, but you can commit to checking the investigation and updating the customer tomorrow. Send that update even if you haven't found the cause yet.

Our reply and follow-up guide explains where to find notes, reminders, and snooze in the inbox.

Close the conversation when the support work is done

Suppose you've found the notification problem and made a fix. Tell the customer what changed and how they can check that emails are arriving again. Give them a chance to confirm it worked.

You can then resolve the conversation to move it out of the active inbox. The history remains available, and if the customer replies later, UserJot reopens the thread.

This is different from waiting. If you've asked the customer for a detail and they haven't replied yet, the issue may still be open even though nobody on your team needs to answer right now. In UserJot, the Open view lets you see those conversations alongside other open work.

That also explains why an empty Queue doesn't mean every issue is solved. Some conversations are waiting on customers, and others have been snoozed until later. The inbox guide explains what each view includes.

Before you move on, consider whether the conversation exposed a gap in your documentation. A clearer explanation might help the next customer and give Juno a better answer to work with. If it revealed a product problem, preserve that feedback for the team deciding what to improve.

A daily shared inbox routine for a small team

You can use this workflow without both teammates watching every message all day. Agree on coverage that fits the rest of your work, and make sure customers know when they can expect a human response.

At the start of your support window, check the Queue for new conversations and due reminders. Before you finish, review the updates you've promised and confirm any handoffs to a colleague.

A short checklist can help:

Common questions about managing a shared inbox

How do you prevent duplicate replies in a shared inbox?

Agree on who is handling the conversation and check the latest messages before sending. Use an internal note to record a handoff. Reading and typing indicators help with coordination, but they don't guarantee that two people won't reply.

Should an AI agent answer every support email?

Use it for customer questions it has the knowledge and ability to handle, with a clear route to a person. Juno skips spam and automated messages such as receipts. Receiving an AI reply doesn't necessarily mean the customer's issue is resolved.

Is an unread message the same as a conversation needing a reply?

No. Unread means you haven't read a message. It doesn't tell you whether a teammate has answered or whether the customer is waiting for an update. UserJot keeps unread state personal, while the Queue shows conversations waiting on the team and your due reminders.

To set up the email-and-chat workflow described here, start with turning on Conversations, then give Juno the documentation it needs. Conversations is currently in beta.