The questions people ask before they pay.

A channel has to be connected — our gateway, or your own SMTP server, SMS gateway or WhatsApp number — and you need contacts in the system. Email is the fastest to get live. Branded SMS is the slowest, because the sender name is reviewed by a person before you can use it.

Three ways: a CSV import, a QuickGrow form or landing page, or the API. That is the whole list. Connecting your store or CRM does not add anybody — see the integrations questions below, because this is the most common wrong assumption about the product.

No. Email, SMS and WhatsApp campaigns have no test-send button, and we would rather say so now than let you find out at five hundred recipients. Scheduling is real on all three, so a campaign can be set to go at a chosen time. In practice people keep a small segment holding their own number and address, and send to that first.

A new account starts on a lower daily and hourly sending ceiling, and it lifts on its own as the account ages and builds a sending record. It exists so bought lists and burnt sender reputations do not ride the same routes as everyone else. If a launch cannot wait for it, tell us before you buy volume.

There is a platform fee that covers the platform and the tooling. Buying managed volume waives part of it, and buying enough Email and SMS volume at a high enough tier waives it entirely — WhatsApp doesn't count toward this, since Meta bills it directly and QuickGrow adds no markup to credit. Bring your own infrastructure and the platform fee is all you pay us — traffic you settle with your own provider.

Yes, and the saving differs by what you buy. The platform fee falls on one ladder and managed volume on another, per channel. The pricing page shows your actual blended saving as you build the plan rather than a headline percentage.

Sends beyond the volume you bought are billed at the base rate from your prepaid wallet. If the wallet is empty the send stops rather than being billed — nothing quietly charges you more, and no invoice arrives that you did not plan for. You top up, add volume, or wait for the next period. Volume belongs to the month you bought it in; unused volume does not carry forward.

Yes. Each has its own volume slider, and they are metered separately. One subscription pools its volume across every brand it covers.

There is nothing to run out of. WhatsApp has no package to buy and no wallet to drain — Meta bills you directly for anything outside a free 24-hour window, at Meta's own rate, set by destination country and message category. QuickGrow adds no markup and never blocks a send over balance.

Your organisation’s billing currency, which for Bangladeshi customers is BDT. Prices shown to you are already converted. Taxes are not included.

It authenticates once, then reads on a schedule — every six hours — and reports what it found: how many products, orders and customers. It does not write those records into your contacts, and it is not live. If you expected your storefront customers to appear as contacts, that does not happen today. Import them, or send them through the API.

No. There is no order, cart or purchase trigger in automations. Store webhooks are received and their signature is verified, but the payload is not acted on — nothing is stored and no journey starts. An abandoned-cart flow in QuickGrow is a tag-triggered journey: your system tags the contact, the journey runs.

Shopify, WooCommerce, HubSpot, Salesforce and Zapier. All five behave the same way — one authenticated connection, a scheduled read, and a record of what came back. Credentials are encrypted where they are stored and are never handed back to the browser, and outbound calls are checked before they leave.

Send on any of the three channels, either with text or by referencing a stored template by id and passing variables. Read a message back with its delivery state — queued, sent, delivered, failed — with the time of each, and a failure reason and code when it fails. List and filter messages. Subscribe to webhooks for sent, delivered, failed and bounced.

No, and this is the one that catches teams out. A send through the API resolves the recipient to a contact, which puts it through the same guardrails as a campaign: SMS needs an active consent record for that contact, quiet hours apply, and the per-contact caps count it. WhatsApp through the API is treated as a regular message rather than a template, so it only goes out inside the 24-hour window. Plan login codes and receipts around that rather than assuming transactional traffic is exempt — and if that rules out your use case, better to know today.

A thousand requests a minute per key by default, and you can issue several keys with different rights — reading the inbox, writing to it, sending campaigns and exporting contacts are separate permissions. A retry carrying the same retry key is recognised for 24 hours, so a network timeout does not send the message twice.

Yes. The Partner API provisions and manages client accounts — creating them, moving their subscriptions, offboarding them — and each client is a separate brand, so their contacts, inbox and messages never mix with another client’s.