Customer support

One inbox for every conversation. Chat on your site. Your team replies from the same thread.

Visitors write on your site. Your team replies from one inbox. Help articles open in that same window.

whatsappinstagramtelegrammessengerslackdiscordshopifystripelinearChat. Email and SMS when connected. Slack two-way with bot scopes.

The desk

Live chat, inbox, help, and the tools beside them

The chat on the site, the list of conversations, and the help articles in that same window.

Amelia RoweInvoice seatsGBwhatsapp
Jonas MeierOrders missingCHemail
Sofia AlvarezPedido 8821MXinstagram
Shared inbox

Website chat lands in one queue. Email and SMS land when you connect them. Assign the thread, leave a note the visitor never sees, and keep the history on a single conversation.

slackshopifystripetelegrammessengerlinearwebhookinstagram
Integrations

Slack (two-way with bot scopes), Shopify, Stripe, Meta, Telegram, Linear, and a signed webhook. Not a 100-app store. Website chat is included.

yourstore.com

Ask about shipping or the plan.

How can we help today?

ShippingSeats
A messenger you can brand

Theme, glass, radius, and launcher on every plan. Suggested questions and help articles in the same panel. Hide the Cove mark on Plus.

On the page they opened

The messenger sits on the page they are already reading. If they leave, the same thread is still there when they come back.

ES → EN

¿Pueden confirmar el envío a CDMX?

|

Translate

Customers write in their language. The inbox shows a translation on the same message. Locale sits on the contact. The original is never replaced.

From “Returns under $40”

Maya
Draft from your articles

Cove matches the thread against help pages you published. If nothing matches, you get an error — not a guessed policy. A person still sends.

Same product

Inbound email, operator sign-in, and public help

Mail lands on the thread. The team opens the desk with Google or Microsoft. Visitors read help — and People sits beside every conversation.

Save Email. Forward the public inbox. Reply-To keeps the next reply on the thread.

Inbound email

Google or Microsoft. An invite is still required to join a workspace.

Google and Microsoft SSO

atlas.coveinbox.co — a FAQ site, not a setup clock.

Help · People

Built for the team that answers

Cove is the desk: the messenger on the site, the shared inbox, help in the same panel, and the contact beside the thread.

  1. 01

    On the site in two minutes

    Most visitors never email. Paste one script. The messenger opens on the page they are already reading. If they leave, the same thread is still there when they come back.

  2. 02

    One inbox for the conversation

    Website chat lands in the same queue. Email and SMS land when you connect them. A teammate assigns, notes, and replies once. The customer sees one history — not a restart in another tool.

  3. 03

    Help articles in the same panel

    Publish a page once. Visitors search it on the Articles tab. Your team can draft a reply from those pages. A person still sends.

  4. 04

    Translate the conversation

    Customers write in their language. The inbox shows a translation on the same message. Locale sits on the contact. The original is never replaced.

First afternoon

Twenty minutes to the first live chat

The loop that ships. Paste the snippet, set the look, publish one article, take a test chat. Read Switch to Cove and Cove vs Intercom.

  1. 01

    Create a workspace

    Sign up and open the inbox.

  2. 02

    Paste the snippet

    The chat appears on the site. Replies land in the inbox.

  3. 03

    Match the chat to your site

    Set the colors, the corner roundness, and the button.

  4. 04

    Publish one article

    Visitors can read it in the chat.

  5. 05

    Send a test message

    Open the site as a visitor. Reply from the inbox.

What you open

Inbox, help, and a campaign compose

Three desk surfaces. Captures match the shipped UI — queue, public help host, Broadcasts compose.

One queue. An owner. Resolve ends that visitor thread.

Shared inbox

atlas.coveinbox.co — a FAQ site, not a setup clock.

Helpdesk

Broadcasts. Sequential send. Cap 200. RFC 8058 unsub.

Campaigns

FAQ

Before you start a trial

Card, day 15, inbound email, and how you switch.

Yes for Mini, Essentials, or Plus. Checkout collects a card. Cancel before day 14 and you are not charged. Free does not require a card. See pricing.

Free stays open. If a paid trial ends without an active subscription, the dashboard locks and the website widget stops (the public script returns 402). Owners upgrade from Billing.

No. Plus drafts from published help articles and macros. A person still sends. Visitors can always talk to a person. See Cove Agent.

Not as Gmail OAuth. Save Email on Channels, then forward your public support inbox to `{slug}@inbound.coveinbox.co`. That address appears after Email is connected and MX is live. Attachments and quote-strip are not shipped. Steps: Connect email.

When you connect them. Website chat is the channel that ships. Slack writes back only with Events and a bot token that includes `channels:history`. See integrations.

Paste the Cove snippet, remove the old tag, then import people, help markdown, and optional thread transcripts. The walkthrough is Switch to Cove.

Start a 14-day trial of Cove

Create an account, paste one script on your site, and take your first live chat. Card required for the trial. Cancel before day 14.