Internal notes and handoffs in a shared inbox

A handoff inside a shared inbox works when the next person can read one internal note and know what to do, and the customer sees one continuous conversation rather than a restart. That needs three things: internal notes that live in the thread and are never sent to the customer, a way to mention a colleague so they are pulled in, and a habit of writing the handoff note before reassigning. The customer should never be asked to repeat themselves.

Internal notes

A note on the conversation that the customer cannot see: "Patient says the crown feels high; Dr Lee wants to see her this week, offer Thursday." It sits in the thread, in a visibly different style, with the author and the time. The next person reads it in the place the conversation is, not in a separate tool or a group chat. Notes are where the reasoning goes; messages are where the outcome goes.

Mentions

"@Dana can you confirm whether we have a Thursday slot for a crown adjustment?" pulls Dana into the conversation without reassigning it. She sees the mention, answers in a note, and the owner replies to the customer. Mentions are for a question to a colleague; reassignment is for changing who owns the reply.

The handoff note

Before reassigning, write what the next person needs: who the customer is, what they want, what has been said, what has been promised, and what to do next. Four lines. "New patient, wants a cleaning and mentioned sensitivity on the lower left. Told her someone would text this morning. Please book the cleaning and ask Dr Lee whether to add an exam." A reassignment without a note makes the next person read the whole thread or, worse, ask the customer.

The customer-facing handoff

The customer is told once, plainly: "I am passing this to Dana at the front desk, she will text you this morning." Then Dana's first message picks up where the conversation left off: "Hi Maria, Dana here. I have Thursday at 10 for the cleaning, and Dr Lee would like to take a quick look at the sensitive area while you are in." No "how can I help you today?", no asking for the phone number again.

Handoffs from the AI

The AI's handoff note is automatic: why it handed off (which rule), what the customer said, what it already answered, and what it told the customer to expect. It should be the same shape as a human handoff note so the next person does not have to learn two formats. The customer-facing message from the AI is the same as above: who, and when.

What the next person needs to see

The whole thread, all channels, in order. The record beside it: appointments, consents, past conversations. The notes. The reason for the handoff. And what was promised, highlighted, because the promise is the thing that gets broken when it is missed.

Notes are not a chat room

A thread with fifteen internal notes debating what to do is a meeting that should have been a phone call. Notes are for facts and decisions. If a conversation needs a discussion, have it and write the decision as one note.

Frequently asked questions

Can the customer ever see internal notes?

They must not. Notes are stored separately from messages and never sent. Ask your vendor to show you the distinction in the interface and to confirm that exports to customers exclude notes.

Should notes be kept forever?

They are part of the record and useful later ("last time she asked about X"). Keep them with the conversation, subject to your retention policy.

What about a handoff to someone at another branch?

Same note, and the conversation is reassigned to that branch's queue. The other branch's manager sees it because it is now theirs.

What Frontiva does here

Frontiva's unified inbox keeps internal notes in line with the conversation, visible only to your team, and each contact's CRM timeline records staff actions alongside messages. Mentions and automatic handoff notes are not built, so the four-line note above is the habit to keep. See inbox assignment for who the next person is.