How does the email inbox work?
The email inbox is not a separate product—it is the same merchant dashboard inbox you use for chat. Incoming support emails become conversations with the same sections, search, and staff tools.
That design keeps one source of truth per customer instead of splitting context between a mailbox and a chat tool.
From customer email to dashboard conversation
When a message arrives at your configured support address:
- Simple Chat ingests the email and opens (or continues) a conversation in the dashboard.
- The thread shows message history, customer context, and order information where available—just like chat.
- The AI can triage and respond automatically according to your instructions and workflow settings.
- Staff can read, reply, and manage the thread without leaving Simple Chat.
Customers experience normal email on their side; your team experiences a structured support ticket in the inbox.
What your team can do in email threads
Staff workflows mirror chat:
- Reply with customer-visible messages—sending a reply can hand the thread from AI to your team, same as chat takeover rules.
- Forward conversation threads to external addresses when you need input from a supplier, carrier, or another department.
- Search past messages and customers when an email references an older issue.
- Use inbox sections (Open, Monitoring, Closed, Pinned, Spam) to prioritize work across channels.
Because email and chat share one inbox, a shopper who chats Tuesday and emails Friday still lands in one operational system.
AI’s role on email
For many stores, the AI handles first response and routine follow-up on email:
- Answers policy and product questions when your knowledge and tools support them.
- Escalates or monitors threads based on your workflow configuration.
- Leaves clear message history so humans can override tone, refunds, or exceptions.
Review Monitoring and Open sections regularly—email volume often spikes after shipping delays or launches, and the unified inbox makes that visible in one place.
Day-one checklist for managers
- Confirm test inbound mail creates a visible conversation.
- Verify AI instructions mention email-appropriate tone (often slightly more formal than chat).
- Train agents that reply in the dashboard is the customer-facing email send—not a separate mail client.
- Document when to forward externally versus resolve inside Simple Chat.
Once those habits are set, email behaves like chat with a different transport: same dashboard, same accountability.
Changelog releases
This topic appears in the following release notes: