🛠️ How-to tutorials

Turning your support mailbox into a channel alongside WhatsApp

Updated 2026-09-24 · 5 min read · By the Convo360 team

In short

Connect your existing support mailbox over IMAP and SMTP so incoming emails become tickets and your replies go back out from that same address. Customers notice nothing, but your team stops working in two places and email stops being the channel where things get forgotten.

Key takeaways
  • Keep the address customers already know rather than announcing a new one.
  • Use an app password, never your main mailbox password.
  • A new connection should start from today, not import years of archive.
  • Auto-replies and bounces must be ignored or they create phantom tickets.

Why email is the channel that goes quiet

Most Indian businesses run support on WhatsApp and keep a support email address because customers expect one. The WhatsApp number is watched constantly. The mailbox is watched by whoever remembers.

That asymmetry is where things get lost. An email arrives on Friday evening, somebody reads it on their phone, thinks they will handle it Monday, and by Monday it is under thirty newsletters. Nobody is at fault and nothing alerts anyone.

It is also where your slowest responses live, which matters more than volume. A customer who emails is often the one with a longer, more considered problem, frequently a business customer, and frequently the one worth most.

Bringing the mailbox into the same place as everything else does not make the emails more important. It makes them visible on the same list, with the same deadline, owned by a named person.

There is a compliance angle for some businesses too. If a customer sends a complaint by email and it goes unanswered for two weeks, the fact that nobody meant to ignore it is rarely a defence. Anything that must be answered within a stated period belongs in a system that counts, not in a mailbox somebody checks.

What connecting actually does

Convo360 polls your mailbox over IMAP, turns each genuine customer email into a ticket, and sends your replies back through your own SMTP server so they arrive from the address the customer wrote to.

Several details matter more than they sound:

Threading is handled properly as well. Replies carry the right headers, so the customer's mail client groups your answer with their original message rather than starting a new conversation. It sounds trivial until you have dealt with a customer who has six separate threads about one order.

Photos are worth a particular mention. For damaged goods, email remains the channel customers use to send several large images at once, and losing those attachments on the way into a ticket makes the whole channel useless.

Setting it up safely

In Convo360, open Support Desk and find the mailbox settings. You will need the IMAP host, the SMTP host, the address and a password.

Use an application-specific password rather than your main one. Google and Microsoft both issue these, they can be revoked individually, and they cannot be used to sign in to the account itself. If your provider does not support them, create a dedicated mailbox for support rather than connecting a personal account.

Use Test connection before saving. One security detail worth knowing: the saved password can only be reused to test the same mailbox. Change the host and you must enter the password again, which prevents anyone pointing the test at a server they control and collecting your credentials without ever seeing them.

Consider which mailbox to connect as well. A shared support address is right; a named person's mailbox is not, because it mixes their private correspondence into a system your whole team can read. If you currently run support from an individual's account, this is a good moment to create a proper shared address and forward the old one.

Starting from today, not from 2019

A newly connected mailbox will happily read everything in it, which is almost never what you want. Years of archived threads becoming open tickets is a genuinely miserable morning.

Convo360 starts from the moment you connect. Older mail stays where it is, untouched, and only new arrivals become tickets. If you do need history, keep it in the mailbox and search there; it is not worth importing.

Give the first week a light touch. Watch what becomes a ticket and what does not. Every business has some automated mail nobody thought about, such as order notifications from a marketplace or alerts from a payment gateway, and the tidiest fix is usually a mailbox rule that files those elsewhere before they ever reach the desk.

Watch out for mailing lists and no-reply senders in that first week. Convo360 ignores obvious automated mail, but a newsletter your business subscribed to years ago can still look like a genuine message. A single mailbox rule solves it permanently and takes a minute.

Setting expectations differently from chat

Do not apply your WhatsApp reply targets to email. Customers who email expect a slower, more complete answer, and a two-minute email reply can read as dismissive where the same speed on chat reads as attentive.

A practical split for a small Indian team: one working hour for WhatsApp, four for email, with the same resolution targets for both. Because Convo360 counts deadlines in your working hours, a Saturday evening email does not arrive already overdue on Monday morning.

Watch one number specifically for the first month: how many email tickets get a first reply at all on the same day. That figure is usually the one that shows how invisible the mailbox had become, and it is the most satisfying one to watch improve.

Tell your team the mailbox is now on the desk, and then actually close the old habit. If two people still open the webmail directly, you will get duplicate replies and the tickets will show a first response that never happened. Removing the shortcut from everyone's browser is a cruder fix than it sounds and it works.

After a month, compare email and chat side by side on the dashboard. Most businesses are surprised by how much of their genuinely difficult work arrives by email, and how little of it they were measuring.

Step by step

  1. Create an app passwordIn your mail provider's security settings, issue an application-specific password for Convo360. Never use the main account password.
  2. Enter the mailbox detailsSupport Desk → mailbox settings. Add the IMAP host, SMTP host, address and app password.
  3. Test the connectionUse Test connection before saving, and check that a reply sent from the desk arrives from your own address.
  4. File automated mail elsewhereAdd mailbox rules so marketplace notifications and gateway alerts never reach the desk as tickets.
  5. Set an email-specific deadlineFour working hours for first response is usually right, against one hour for chat.

Bring your mailbox into the same list

Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.

Frequently asked questions

Will replies come from Convo360 or from my address?

From your own address, because the reply is sent through your SMTP server. Customers see the same support address they wrote to, and threading works normally in their mail client.

Does it import my old emails?

No. A newly connected mailbox starts from the moment you connect it, so years of archived threads do not suddenly appear as open tickets. Older mail stays in the mailbox untouched.

What about out-of-office replies and bounces?

They are recognised and ignored, so they do not create tickets or reopen resolved ones. Without that, a single bounce loop can generate dozens of phantom tickets overnight.

Can I connect more than one mailbox?

One mailbox per workspace is supported today. If you run separate addresses for sales and support, connect the support one and forward anything relevant from the other.

Is my mailbox password stored safely?

It is encrypted at rest and never shown back to you in the interface. Using an app password is still the right choice, because it can be revoked on its own without changing your main account credentials.

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.