Every WhatsApp message, every email reply and every SMS your customers send lands in one list your whole team can work from. Each conversation gets an owner, a status and a place it belongs — and the chatbot hands over to a person the moment the customer asks for one.
Most small teams can answer any question a customer asks. What they cannot do is see all the questions at once, know whose job each one is, and be sure none of them went quiet. That is the part this fixes.
One customer asks on WhatsApp. Another replies to the order email. A third texts the number on the receipt. Three apps, three logins, three people watching them — and the one nobody was watching is the one that waited all afternoon.
When a shared phone is the queue, the awkward question gets left for someone else. Two people answer the easy one, and the customer gets two different answers from the same business.
Delivery times, return rules, where the shop is, what the account number is. Your team types them out again every morning, and each retype is a chance to get a detail wrong.
Conversations from every connected channel sit in the same list, newest first. The tabs across the top split them by channel when you want that; most of the time you leave it on All and work down.
A conversation carries a channel, a status, a priority and whoever owns it. The counts above the list tell you what is open, what is pending and what nobody has picked up yet, so the first thing anyone sees in the morning is the size of the day.
There is no separate ticket to raise and no second system to keep in step with the first. The message is the ticket, and it moves through the same four states whichever channel it came in on.
A customer writes on WhatsApp, replies to one of your emails, or texts your number. QuickGrow matches the contact behind it — or creates one — and opens a conversation. Everything that person sends after that joins the same thread.
Each connected account can hand new conversations out on a rota, or to whoever has the fewest open right now. Leave it off and the team takes from the unassigned list instead. Whoever it lands on is told by name.
Reply in the same box you read it in and it goes back out on the channel it came in on. Press / to drop in a saved reply, attach a photo or a document, set the priority, add a tag so you can find it again.
Park it as pending while you wait on the customer, and it jumps back to the top of the list the moment they reply. Mark it resolved when it is done. If a resolved customer writes again, that arrives as a fresh conversation — the old one keeps its full history, so nothing is lost.
A chatbot flow answers on WhatsApp and SMS: a message, a set of buttons, a menu, a question whose answer it remembers, a branch on what it was told, or a call out to a system of yours. When it reaches the end of what it can do, it hands over.
You decide where the bot steps aside by putting a handoff block into the flow. The bot session ends there, the conversation stays exactly where it is, and a person picks it up with the whole exchange above them.
A shared inbox is only shared if the sharing has rules. These are the three that matter, and all three are yours to set.
Replying is not the same on all three, and the difference matters most when a customer is waiting. This is what changes.
| SMS | |||
|---|---|---|---|
| Replying in your own words | Within 24 hours of their last message. After that, an approved template | Any time — the reply threads onto the subject | Any time |
| What you can send back | Text, photos, video, documents and audio | Text, on your mail server or ours | Plain text |
| Chatbot answers here | Yes | No | Yes |
| How it is paid for | Volume per Meta template category — Utility, Authentication or Marketing | Bulk and transactional, on your own mail server or ours | Masking volume, non-masking volume, or both — metered separately |
| What it is best at | The back-and-forth | Long answers and a record of them | Reaching a handset with no data on it |
Support software that charges per agent punishes you for putting a second person on the inbox. This does not work that way.
The inbox, the chatbot, saved replies, roles and the rest sit behind a single platform fee. There is no charge per agent seat and no charge per conversation, so putting one more person on the inbox costs nothing extra.
Buy managed sending on a channel and part of the platform fee falls away. Buy enough across email, SMS and WhatsApp together and it is waived entirely. A longer billing term discounts the fee and the volume on their own separate ladders.
Already have a mail server, an SMS account or a WhatsApp number? Bring them, pay the platform fee only, and settle the traffic with your provider directly. The inbox works the same either way.
The pricing page builds the plan with you and shows the real blended saving as you go. If you send another business our way, both of you earn credit — see how the referral works.
WhatsApp, email and SMS are the three most teams run on. Telegram, Facebook Messenger, Instagram direct messages and the live chat on your own site land in the same list once they are connected, with a tab each and a count beside it. A tab only appears once that channel has conversations, so the rail stays short.
No. Team members are invited from your account settings and there is no per-seat charge for the inbox. Give a new starter the Inbox Agent role and they can read and reply to conversations and look up contacts — nothing more.
You put a handoff block into the flow at the point you choose. The bot session ends there and the conversation stays in the inbox with the whole exchange intact, ready for a person. Who it goes to is decided by the inbox itself — on a rota, or to whoever has the fewest open conversations, or left unassigned for the team to pick up. Note that the bot does not currently watch for a customer typing agent or human; put the handoff block where you want the exit to be.
The conversation is queued rather than dropped. The customer is told they are in the queue, everyone on the account gets a high-priority alert with the position, and the conversation sits in the pending list until someone takes it. Agents mark themselves available or away, and only the available ones are handed chats.
Yes. Once the person is done they can return the chat to the automated assistant, which tells the customer and clears the assignment. It is one action from the same conversation.
Within 24 hours of the last message the customer sent you, you can write back in your own words. After that Meta only allows an approved template, which is why WhatsApp is sold by template category. Email and SMS have no such window.
Each saved reply is tied to the channels you choose and grouped into a category, with a short slash-command of your own naming. Press / in the reply box and the matching ones come up; picking one drops the text into the box so you can change it before it goes.
It stays, with its whole message history, its tags and the person who handled it. If that customer writes again it arrives as a new conversation rather than reopening the old one, so use tags to tie the two together — and if you are expecting a reply, leave it pending instead of resolved, because a pending conversation does come back to the top of the list on its own.
WhatsApp, email and SMS in one list, roles for the people who answer, and a chatbot that hands over the moment it is out of its depth.
CyberCraft BangladeshQuickGrow AIRun every channel from one platform. Bring your own SMTP, SMS gateway, and WhatsApp number — or use ours.
See pricing →