One sign-in, and that is the setup
Your Salesforce instance address and an access token for the org. QuickGrow calls the Salesforce REST API with that token and nothing else. No Salesforce login is handed over, and nothing is deployed into your org.
Salesforce
Salesforce holds the record. You still have to reach the person.
QuickGrow signs in to your Salesforce org with an access token and reads two things — your Contacts and your Leads — every six hours, on its own. Nothing is written back. What you do with those people afterwards is the point: WhatsApp, SMS and email to Bangladeshi handsets, from one account, billed in taka.
Read-only — nothing written to your orgContacts and LeadsRead again every 6 hoursSign-in encrypted when saved
01What the connector does
Two objects, read on a schedule.
Be clear about the shape of it before you connect. The connector authenticates against your org, queries Contacts and Leads, counts what came back and records the run. It writes nothing into Salesforce, and it does not build your QuickGrow contact list for you — that list stays yours to fill, by upload, by form, or through the API.
The people already on your books
Each Contact comes back with its name, email address, phone number and mailing city, state and country. The first read takes every one of them. After that QuickGrow asks Salesforce only for the Contacts whose record changed since the last successful read.
And the ones who have not bought yet
Each Lead comes back with its name, email address, phone number, company, status and lead source. Same rule: everything on the first read, then only what has changed since the last good one.
02Connect
An address and a token. Nothing to install.
No package to deploy, no consultant, no change to the way your team uses Salesforce. If someone on your side can produce an access token for the org, the whole job is two fields and one save.
Take your instance address
The address your team already uses to reach Salesforce — the one shaped like https://your-org.my.salesforce.com. Copy it as it is, with no path on the end.
Get an access token for the org
From whoever administers your Salesforce. Read access to the Contact and Lead objects is all the connector ever uses, and it never asks for anyone’s Salesforce login.
Paste both into QuickGrow
Settings → Integrations → Salesforce. Two fields: the instance address and the token. Both are encrypted the moment they are saved, and neither is ever sent back to a browser afterwards.
Leave it alone
The connection joins the schedule. Every six hours QuickGrow reads your Contacts and your Leads again, records how many of each it found, and moves the last-read time forward only when the run actually succeeded.
03What a read asks for
Exactly which fields leave your org.
Worth knowing before you hand over a token, and worth knowing if your org is a big one: a repeat read is cheap, because it only asks for the records changed since the last run that finished cleanly.
| Contacts | Leads | |
|---|---|---|
| Direction | Salesforce → QuickGrow | Salesforce → QuickGrow |
| First read | Every Contact in the org | Every Lead in the org |
| Every read after that | Only the ones changed since the last successful read | Only the ones changed since the last successful read |
| What comes back | Name, email, phone, mailing city, state and country | Name, email, phone, company, status and lead source |
| Most recently changed first | Yes | Yes |
| Read page by page until Salesforce says there are no more | Yes | Yes |
| Created, edited or deleted in Salesforce | No | No |
04Then what
Reading the org is the small half of the job.
Knowing who is in Salesforce is worth something once you can talk to them. Everything below runs on your QuickGrow contact list — brought in by upload, by a form or popup, or pushed from your own code — and reaches those people on email, SMS and WhatsApp from a single account.
Groups
Send to the slice, not to everybody.
A group is a few rules, and it counts the people it matches before you send a thing. Add a rule, watch the number move, then send to exactly those contacts.
- Rules on tags, contact status, where the contact came from, an engagement score, when they last engaged, and when they were added
- Join the rules with and / or
- Anything from Salesforce you want to segment on — a lead status, a territory, an owner — has to arrive as a tag you set; rules match tags, not Salesforce fields
The channels
Reach them where they actually reply.
This is the part a Bangladeshi team needs and the part a record in a CRM cannot do by itself. Three channels, one account, one bill, and every reply landing in the same shared inbox.
- WhatsApp on the official Meta Cloud API, billed by Meta directly at Meta's own rate — utility, authentication or marketing — with zero QuickGrow markup
- SMS volume bought as masking or non-masking. A masking sender name is 1 to 11 letters or digits and goes in as an approval application first; until it is approved, sends fall back to the default sender
- Email in bulk or one message at a time, on our mail server or on yours
05The detail
What you can see, and what happens when a read breaks.
On every read
- The connection shows what it is doing: syncing, completed, or failed
- Contacts and Leads are asked for together, in the same pass
- A long result set is read page by page until Salesforce says there are none left
Keeping the sign-in safe
- The instance address and the token are encrypted when saved and never returned to a browser
- The address is checked before every call, so a connection cannot be pointed at a private address inside a network
- Redirects are not followed, so a call cannot be quietly sent somewhere else
When a read fails
- The connection is marked failed
- Your account owners and admins are notified, with the reason it failed
- The last successful read time stays where it was, so the next run asks for the same window again and nothing is skipped over
Automatic every 6 hours Admins told when a read fails Token encrypted at rest Read-only against your org
06Cost
What connecting Salesforce costs you.
Nothing on its own. What you pay depends on how much you send, and on whether you bring your own mail server or SMS account.
The connector is not a line item
It comes with the platform. You pay a platform fee that covers the tooling — contacts, groups, journeys, the shared inbox, the reports — and then you pay for the messages you actually send.
Buying volume cuts the fee
Managed volume waives part of the platform fee. Buy across email, SMS and WhatsApp at a high enough tier and it is waived in full. A longer billing term discounts the fee and the volume on separate ladders.
Already have a mail server?
Bring your own mail server or SMS account and the platform fee is all you pay. WhatsApp runs on your own number too — you pay Meta directly, at Meta's own rate, with zero QuickGrow markup and no monthly commitment.
07Questions
Before you hand over a token.
Does QuickGrow change anything in my Salesforce org?
No. The connector only reads. It queries the Contact and Lead objects and takes the answer away; it never creates, edits or deletes a record in Salesforce, and it touches no other object. Give it a read-only token and it will still work exactly as described here.
Does a Salesforce Contact become a QuickGrow contact automatically?
Not today. A read tells QuickGrow who is in your org and records how many Contacts and Leads it found; it does not file them into your contact list. That list is built inside QuickGrow — upload a spreadsheet and map the columns, capture people with a form or a popup, or push them in from your own code through the API. If automatic contact creation is the piece you are waiting on, say so on the contact page and we will tell you where it sits.
How often does it read, and can I force one right now?
Every six hours, automatically, for every connection that is switched on. There is no button that forces an immediate read: Settings → Integrations gives you Connect and Disconnect, and the schedule does the rest. A newly connected org is picked up by the next scheduled run.
What exactly does it ask Salesforce for?
Two queries against the REST API. Contacts, with first and last name, email, phone and mailing city, state and country. Leads, with first and last name, email, phone, company, status and lead source. Both come back most recently changed first, and after the first run both are filtered to records modified since the last successful read. A long result is paged through until Salesforce reports there are no more.
What happens when the access token expires?
The read fails, the connection is marked failed, and your account owners and admins are told why. The last successful read time does not move, so nothing is skipped: reconnect from Settings → Integrations with a fresh token and the next scheduled run asks for the same window it would have read anyway.
Can a change in Salesforce start a message straight away?
No. The read is on a six-hour schedule, and journeys in QuickGrow start from QuickGrow’s own events: a contact created or updated, a tag added or removed, a form submitted, a campaign opened or clicked, a date you set, or a manual start. The date-based trigger is the strong one — it watches a date field on the contact and fires a set number of days before or after it, which is how renewal notices, appointment reminders and birthday messages go out without anyone pressing anything.
I want to send based on something that lives in Salesforce. Can I?
Only once it arrives as a tag. Group rules in QuickGrow match on tags, contact status, where the contact came from, an engagement score, when they last engaged and when they were added. A Salesforce lead status, a territory or an owner is not one of those fields, so carry it across as a tag you set on the contact — then the rules can match it and a journey can start from it.
Can I connect more than one org?
Yes. Each org is its own connection with its own name, its own address and its own token, and every switched-on one is read on the same six-hour schedule. Disconnect one and its scheduled reads stop; nothing further is read from it.
Read the org. Then go and talk to the people in it.
Connect Salesforce with an instance address and an access token, and reach the same Contacts and Leads on email, SMS and WhatsApp from one account, billed in taka.