Omnichannel inbox

The omnichannel inbox with one history

Website chat, email and SMS land in one queue, and your team can answer from Slack too. Every customer’s past conversations sit beside the reply, and Pengo Intelligence answers on every channel.

Website chat and email on every planFree forever plan14-day Growth trial

Animation: Kettlewell Outdoor’s omnichannel inbox. An Instagram message from Annika asking whether the Fellside daypack ships to Denmark arrives in the queue beside WhatsApp, email, Messenger and website chats. Her thread shows her website chat about merino socks and her email from earlier in the week above the new message. Pengo Intelligence answers on Instagram that EU orders arrive in three to five working days, citing the delivery guide.

  1. How it works
  2. How it works
  3. How it works

What is an omnichannel inbox?

An omnichannel inbox brings every way customers reach you, such as website chat, email and SMS, into one queue with one history per customer. Pengo’s omnichannel inbox routes every channel with the same rules, SLAs and saved replies, and Pengo Intelligence answers on all of them.

Every plan
Website chat, email, a hosted chat page and the mobile apps
From Starter
Slack, with two-way threads
From Growth
SMS
One history
Each customer’s chats, emails and messages in order
01 Every channel

Meet customers wherever they already are

Every channel gets the same routing, saved replies, SLAs and AI, and every message lands in the same shared inbox.

Every plan

Website chat

A widget under 5 KB gzipped

  • AI answers with citations
  • Rich messages and file uploads
  • Chat triggers, plus booking on Growth
Every plan

Email

Inbound email and reply-by-email

  • Forward your support address
  • CC, BCC and send later
  • Send from your own domain
Starter+

Slack

Notifications and two-way threads

  • New chats post to a channel
  • Reply in the Slack thread
  • Your reply reaches the customer
Growth+

SMS

Two-way texting via Twilio

  • Use your Twilio number
  • Plain-text rich fallbacks
  • Routing, SLAs and workflows
Every plan

Chat page

A hosted chat link and QR code

  • No website needed
  • For bios, signatures and packaging
  • Your own domain on Scale
02 One history

Every conversation with a customer, in one place

When Annika comes back to the chat after emailing on Monday, her earlier conversations sit beside the reply box, so your team picks up where the last one left off.

  • Contacts merge across channels

    Duplicate suggestions help you combine the same person’s email, phone and social handles into one profile.

  • One set of rules

    Take turns, least busy or one person first, with a fallback to anyone available: the same rules for every channel.

  • SLAs follow the conversation

    Due-in chips and breach alerts work the same whether it started in the chat or by email.

03 Email, built in

Conversations that survive a closed tab

Email in Pengo is the same conversation, continued, with replies that always thread back to the right place.

Inbound email to the inbox

Forward your support address and every email becomes a conversation, routed like a chat.

Signed reply-to addresses

Each reply carries a signed address, so customer answers thread back into the right conversation.

Real threading

Replies, forwards and follow-ups stay in one thread, not scattered across tickets.

“Continue in chat” links

Visitors who left the site get your reply by email and can jump back into live chat in one tap.

04 Rich messages

Send it once. It looks right everywhere.

Buttons, cards and carousels render natively where a channel supports them, and turn into clean, usable text where it doesn’t.

ButtonsCardsCarouselsFormsArticlesProducts
ChannelCustomer sees
Website chat Product card with image, price and a “View” button
SMS Plain text: name, price, link, “Reply 1 or 2”
Email Plain-text summary with the link
05 By plan

Which channels each plan includes

Website chat, email, the chat page and the mobile apps on every plan. Slack from Starter. SMS from Growth.

Channel FreeStarterGrowthScaleEnterprise
Website chat Included Included Included Included Included
Email + reply-by-email Included Included Included Included Included
Hosted chat page and QR code Included Included Included Included Included
Mobile apps (iOS, Android) Included Included Included Included Included
Slack (two-way threads) –Not included Included Included Included Included
SMS (Twilio) –Not included –Not included Included Included Included

Routing, workflows and Pengo Intelligence work the same on every channel. All integrations →

06 Questions

Omnichannel inbox FAQ

Which channels are on which plan?
Website chat, email and the mobile apps are on every plan. Slack starts on Starter. SMS are on Growth and up.
Do all channels share one inbox?
Yes. Every channel lands in the same shared inbox with the same routing rules, saved replies, SLAs and AI. Each conversation shows the customer’s past chats, emails and messages from every channel beside the reply box.
How does reply-by-email work?
When a visitor leaves before you answer, your reply goes to their email with a signed reply-to address. Their answer threads back into the same conversation, and a “continue in chat” link takes them back to live chat.
Can email go out from our own domain?
Yes, on every plan. Add your domain in Settings, publish the DKIM and SPF records Pengo gives you, and replies go out from your own address. Your team can CC and BCC anyone, and schedule a reply to send later.
Is there a chat link I can share without a website?
Yes. Every workspace gets a hosted chat page with its own link and a branded QR code, ready for your email signature, social bios, packaging or a printed sign. On Scale, put it on your own domain.
Can my team reply from Slack?
Yes. New conversations post to a Slack channel, and replies in the thread are sent to the customer. Everything is mirrored in the Pengo inbox.
What happens to buttons and cards on SMS or email?
Rich messages (buttons, cards, carousels, forms, articles and products) render natively where the channel supports them and fall back to clean plain text where it doesn’t, so nothing breaks.
Do workflows and routing apply to every channel?
Yes. Assignment rules, team routing, SLA policies and workflows (AI triggers, conditions, waits and actions, on Scale) run on new chats and messages from every connected channel, not just the website.

Bring every channel into one inbox

Install in five minutes. Your AI agent is answering before your coffee cools.

Free plan forever · 14-day Growth trial · Cancel anytime

Start free