How to set up shared inbox for telehealth ops team inbox

You need a Chatref account with an AI agent already trained on your telehealth platform’s content — practice hours, services, intake steps, and common patient questions. The shared inbox is available on every account, with no per-seat charges. Make sure you have admin access to invite team members and adjust agent settings.

The shared inbox works best when your AI agent can handle the bulk of routine questions automatically and only flags conversations that need a human. This keeps your ops team focused on high-value interactions while maintaining a full history of every chat thread.

1. Open your workspace settings Log into Chatref and navigate to the workspace where your telehealth agent lives. Under Team or Inbox, you will find the option to add members.

2. Invite your ops team Enter the email addresses of every team member who should monitor the shared inbox. They will receive an invitation to join the workspace. Once accepted, each member can view all active and past conversations, take over a chat from the AI, and reply directly inside the same thread — the full context stays attached.

3. Configure the AI agent to hand off intelligently Go to your agent’s behavior settings and set a handoff rule. For example, route a chat to the shared inbox when the visitor asks for a manager, when the AI cannot find an answer in your content, or after collecting preliminary information via a custom action. This prevents the AI from stalling and ensures your team only sees conversations that genuinely need a person.

4. Set up a pre-handoff custom action (optional) Use custom actions to gather key details before the handoff — such as patient name, provider name, inquiry type, or reference number. The collected data appears in the inbox thread, so your ops team can pick up the chat without asking the patient to repeat themselves. This is particularly useful for telehealth platforms where every second counts during a care interaction.

5. Test the flow yourself Before going live, open your widget on your site and simulate a patient inquiry that should trigger a handoff — for example, ask “I need to speak with someone about my billing.” The AI should route the chat to the shared inbox, where you should see it appear as a new conversation with a clear handoff label.

Run through a realistic patient scenario from start to finish:

• Start a chat on your telehealth platform and ask a question the AI can answer on its own (“What are your clinic hours?”). Confirm the AI replies correctly from your content.
• Ask a question that should hand off (“Can a human review my test results?”). The conversation should land in the shared inbox with the full question and any collected context visible.
• Log in as a team member, open the inbox, and take over the chat. Reply as if you were assisting the patient. Verify that the AI does not interrupt and that the thread preserves the entire history.
• Close the chat from the inbox to mark it resolved. The AI stays quiet on that thread afterward.

If any step fails, double-check your agent’s handoff rule and confirm that the team member has accepted the workspace invitation and is logged into the same workspace.

Team members cannot see the inbox.
Make sure they accepted the invitation to the correct workspace. If the invitation expired, remove the pending member and re-invite them. Also confirm they are logged in with the invited email address.

The AI never hands off, even when it should.
Check your agent’s handoff rule. A common cause is a rule triggered only by a specific phrase but the patient wording varies. Use a broader trigger like “I need a person” or set the agent to always hand off when its confidence in the answer drops below your defined threshold.

Handoff happens too often on routine questions.
If the AI lacks sufficient training content for the patient’s question, it will escalate. Add more detailed info about that topic to the agent’s knowledge base. The shared inbox should be reserved for truly complex cases, not for gaps in your documentation.

Collected details are missing from the handoff note.
Review the custom action configuration. Ensure the action runs before the handoff rule triggers. The sequence matters: the agent should collect info, then hand off with that info appended.

What causes telehealth ops team inbox problems for Telehealth Platforms?

Common causes include scattered communication channels where the same patient inquiry reaches email, phone, and chat with no shared view, leading to duplicated work and dropped context. Another is an overload of routine questions — scheduling checks, hours inquiries — that fill the inbox and hide urgent cases. Without a centralized handoff mechanism that attaches the full chat history, ops team members waste time asking patients to re-explain their situation.

How do I improve telehealth ops team inbox for Telehealth Platforms?

Use Chatref’s shared inbox as a single place to monitor all AI-handled conversations. Route only conversations that need a human — not every message — by setting sensible handoff rules on your AI agent. Before a handoff, collect essential context (patient info, question type) via custom actions so your team can assist immediately. Finally, review the insights that Chatref generates from your chats; you can spot recurring patient issues and train your agent on them, reducing future handoff volume.