# Omnichannel Inbox for E-Commerce Support | Chatarmin

> Email, WhatsApp, Instagram, Facebook, TikTok and phone in one inbox. One profile per customer and AI that sorts, answers and hands off.

Source: https://chatarmin.com/en/features/omnichannel-inbox

## Every channel. One inbox. Nothing slips through.

Email, WhatsApp, social and phone land in one inbox, attached to one customer profile. AI sorts every ticket, fills in your fields, answers what it can and hands off the rest with a reason.

- Email, WhatsApp, Instagram, Facebook, TikTok and phone
- One profile per customer
- Replies go out in the original channel

- [Book a demo](https://chatarmin.com/en/demo)

## Support spread across five tabs: something always slips

- **Messages wait where nobody is looking**: Instagram DMs and Facebook comments sit in a separate app. By the time someone checks, the customer has already asked again somewhere else.
- **The same customer, three tickets**: They email, then message on WhatsApp, then call. Three people answer the same question without knowing about each other.

## One place. For every message your customers send.

Every channel becomes a ticket, every ticket hangs on one customer, and your team works in one interface instead of five.

### Every channel lands as a ticket

Email, WhatsApp, Instagram, Facebook, TikTok and calls in one inbox. Even ad comments.

### One customer, one history

Every channel attaches to one profile. Duplicate tickets merge in a click.

### A queue you can read at a glance

Priority, an SLA countdown on every row, and a live marker so two people never answer one customer.

### Duplicates become one ticket

Email and WhatsApp about one order, merged in a click.

### On hold, with a way back

Put a ticket on hold until a set time. It reopens on its own, or when the customer replies.

### A draft waiting in every ticket

Torben drafts the reply from your order data and help center. Your agent edits and sends.

[Book a demo](https://chatarmin.com/en/demo)

## What the AI does before your team steps in

Every ticket is read, answered where it can be, handed off with a reason and counted in your reports.

### The AI reads and analyzes every ticket

Before anyone opens it, the ticket is sorted: team, priority and sentiment set, and your own ticket fields filled in from the message and the order, each with how sure the AI was.

### Handoff and automation request

When the AI can’t fully automate a ticket, it tells you why: asked for a human, policy exception, missing knowledge or an upset customer. Your teammate sees what was already checked and picks up from there.

### Analytics show your next levers

Every resolved ticket is sorted into a topic, with multi-level drilldown. When a product problem starts to grow, you see it in the numbers before it shows up in your reviews. And we either automate the problem away or let you know.

## What changes for your team

The same requests as before, without the tab switching.

### Reply where the customer wrote

Your team answers from one composer. The reply goes back out on WhatsApp, Instagram, email or wherever the conversation started, so customers never get asked to switch channels.

- One composer for every channel
- Replies land in the original channel
- Internal notes stay inside the team

#### Instagram

#### WhatsApp

#### Notes

- Lisa: @Tim can you check the DHL tracking?
- Tim: Arrives tomorrow, customer not told yet.

### Answer in the customer’s language

Incoming messages are translated for your team, and your reply goes out in the language the customer wrote in. One team covers every market.

- Language detected automatically
- Reply translated before sending

#### French

Français: Est-ce que vous livrez en France ?
Français: Oui ! Livraison en 2 à 4 jours.

#### Dutch

Nederlands: Kan ik de hoodie ruilen voor maat M?
Nederlands: Ja, natuurlijk! We sturen je een retourlabel.

#### Detection

### Phone calls in the same queue

Calls show up next to chats and emails. While you talk, the ticket with the customer’s orders is already open, and the call is logged on their profile.

- Calls become tickets
- Customer context during the call

#### Call

Ticket #4821: Where is my order #10482?

#### Queue

#### Profile

### Rules send every ticket to the right team

Route by channel, language, sentiment or priority. Assign to a person or team and set tags in the same step.

- Conditions on channel, language, sentiment or priority
- Assign, prioritize and tag in one step

#### Routing rule

#### Round robin

- Lisa (Online · 4 open)
- Tim (Online · 5 open)
- Sarah (Online · 6 open)

### SLA targets that count down on every ticket

First response, next response and resolution targets, with a warning before anything goes overdue. Weekends never breach.

- First response, next response and resolution
- Business hours only, warning at 80%

#### SLA policy

#### Business hours

- Monday to Friday (08:00 to 18:00 · clock runs)
- Saturday and Sunday (Closed · clock paused)

## Nothing slips back in unnoticed

See which tickets come back, which promises are at risk and where to merge.

- **Reopened tickets, counted**: When a customer replies to a solved ticket, it reopens with full history. Reopen rate shows which topics never really got solved.
- **SLA targets you can see**: First response and resolution targets run on your business hours. Breaches show on the ticket and in reports.
- **One customer, one ticket**: The same question by email and WhatsApp? Merge both into one ticket so nobody answers twice.

## One inbox or one tool per channel?

| Feature | armincx | Separate tools |
| --- | --- | --- |
| Day to day: All channels in one queue | Yes | No |
| Day to day: One customer profile across channels | Yes | No |
| Day to day: Shop and order data next to every ticket | Yes | No |
| Day to day: Views and assignment rules per team | Yes | No |
| Day to day: AI reply drafts on every channel | Yes | No |
| Day to day: Ticket fields filled in by AI | Yes | No |
| Day to day: Handoffs with a stated reason | Yes | No |
| Day to day: Topic reports across all channels | Yes | No |

## E-commerce teams that work from one inbox

From supplements to fashion to food.

> All channels, one AI, ERP integration with billbee and hands-on support from the founders on Slack Connect, plus WhatsApp marketing and email. Switching from Gorgias to armincx was a no-brainer for us.
>
> — Philipp Riedl, Founder, vetain

> Finally an AI that does not hallucinate.
>
> — Eren Karacabay, Team vitabay, vitabay

[Book a demo](https://chatarmin.com/en/demo)

## Support that comes together

Every channel, every customer and every reply in one place.

- [Book a demo](https://chatarmin.com/en/demo)

## Frequently asked questions about the omnichannel inbox

### Which channels can I connect?

Email, WhatsApp, Instagram DMs and comments, Facebook, TikTok and phone. Comments under your ads are captured as tickets too.

### What happens when a customer writes on two channels?

Both conversations attach to the same customer profile, so your team sees the full history. If two tickets are about the same request, you can merge them.

### Does my reply go out on the channel the customer used?

Yes. You answer from one composer and the reply is sent back on the channel the conversation came from.

### Can different teams or brands work in the same inbox?

Yes. Saved views by channel, brand, language or topic give every team its own queue, and assignment rules decide who picks up what.

### What happens to our old tickets?

We migrate your tickets and customer history, so you start with full context. [Zelesta](/en/case-studies/zelesta-cx) brought over two years of history when they switched.

### Does the AI send replies on its own?

You decide. Torben can prepare drafts that your team sends with one click, or answer routine questions like order status on its own.

### Which ticket fields can the AI fill in?

Any field you mark as AI-enabled: dropdowns like return reason, text, numbers, yes/no, products and orders. Torben fills them when the ticket comes in and tries again for required fields before the ticket is resolved.

### How do I know why the AI handed a ticket over?

Every handoff carries a category, such as asked for a human, policy exception or missing knowledge, plus a short reason. You can report on those categories to see where the AI needs more knowledge or rules.

### Which statuses and priorities does a ticket have?

A ticket is open, on hold, resolved or closed, and has a priority from urgent to low. You can filter, sort and build views on both.

### How does automatic assignment work?

Routing rules match on channel, language, tag, sentiment or priority and assign to a person or a team. Teams can rotate round robin, or only between agents who are online.

### Can SLAs respect our business hours?

Yes. Each SLA policy sets first response, next response and resolution targets, a warning point, and whether only business hours count.

### What happens to a ticket on hold when the customer writes back?

It reopens straight away. Otherwise it comes back on its own at the time you picked.

### Can two agents end up answering the same ticket?

Everyone sees in the list and in the ticket when a teammate already has it open, so the work does not get done twice.
