Salesforce-Driven Messaging Built Into Your Platform
Your customers already run sales and support in Salesforce. The Salesforce Connector Plugin lets licensed and rented SMPP Center operators offer CRM-triggered messaging: connect Salesforce once, pick objects such as Accounts, Leads, and Contacts, and send SMS, WhatsApp templates, Voice calls, or RCS when a new record is created. No AppExchange package. No Zapier. No custom Apex to maintain.
SMS WhatsApp Voice RCS
Get a QuoteWhat Your Users Can Automate, Per Salesforce Object
Each connected Salesforce object gets its own independent mix of outbound and inbound automations.
Send on New Record
Trigger SMS, WhatsApp templates, Voice calls, or RCS the moment a record is created on objects with a phone field, including Accounts, Leads, Contacts, and eligible custom objects.
Log Replies as Chatter Posts
Inbound SMS, WhatsApp, and RCS replies are matched by mobile number and posted as a Chatter post on the Salesforce record, keeping context in one place.
Personalize From Fields
Use Salesforce field API names as placeholders in SMS, or map WhatsApp and RCS template variables to object fields through a visual mapping UI.
Delivery Status on Chatter
After every send, delivery status (SENT, DELIVERED, FAILED, ANSWERED) can be posted as a Chatter feed item on the Salesforce record, with no custom fields required.
Which Salesforce Objects Can You Connect?
The object picker is dynamic. It fetches objects from the connected Salesforce org that support record create and have at least one phone-type field. Accounts, Leads, and Contacts are the most common starting points for sales and support alerts.
Accounts
Send a welcome SMS, WhatsApp, RCS, or Voice alert when a new Account is created. Replies and delivery statuses can be logged as Account Chatter posts.
Leads
Reach a new Lead the moment the record lands in Salesforce. Ideal for first-response SMS or WhatsApp templates and reply logging as Chatter posts on the Lead.
Contacts
Trigger onboarding or service alerts when a Contact is created. Inbound SMS, WhatsApp, and RCS replies post back as Contact Chatter posts.
Other Eligible Objects
Additional standard or custom objects appear in the picker when they allow create and include a phone-type field for mobile mapping.
Objects without a phone-type field are excluded from the picker. The list refreshes from the connected Salesforce org whenever the user opens Connect an Object.
Channel Capabilities at a Glance
| Capability | What Happens |
|---|---|
| Send SMS on new record | Messages the record mobile using Sender ID, optional DLT template, and freeform text with Salesforce field placeholders. |
| Send WhatsApp on new record | Sends an approved WhatsApp template. Header, body, media, and button variables map to Salesforce object fields or fixed values. |
| Send Voice call on new record | Places a call and plays an approved audio clip from the voice library, with optional voice status Chatter write-back. |
| Send RCS on new record | Sends an approved RCS template from a verified bot, with per-variable Salesforce field mapping. |
| Log incoming SMS / WhatsApp / RCS | Appends inbound replies as Chatter posts on the matched Salesforce record, showing channel, message text, and timestamp. |
| Delivery status Chatter posts | SENT, DELIVERED, FAILED, ANSWERED, PENDING, or UNDELIVERED posted as a Chatter post automatically after every send. |
| Recent Activity | Shows object, mobile, channel badge, transaction ID, delivery status, and timestamp so operators can confirm automations are running. |
How Resellers Set Up Salesforce for Downline Clients
Resellers own the Connected App credentials and channel permissions. Downline clients never need to create their own Salesforce Connected App to start automating.
Connected App in White Label
- Create a Salesforce Connected App and note the Consumer Key and Consumer Secret.
- Save those credentials under White Label for the Salesforce CRM OAuth section.
- Once configured, downline users can complete Salesforce OAuth from the panel.
Per-Account Channel Flags
- Enable or disable Send SMS, Send WhatsApp, Send Voice, and Send RCS per customer account.
- Enable or disable Log Incoming SMS, Incoming WhatsApp, and Incoming RCS independently.
- Customers only see the automation cards for channels you have provisioned.
Downline Client Integration
- Clients connect their Salesforce org with one OAuth consent.
- They connect objects (Accounts, Leads, Contacts, and other eligible objects) and map the mobile field.
- If OAuth is not configured, users see a clear “contact your representative” message instead of a broken flow.
Reseller Visibility
- Recent Activity shows object, mobile, channel, transaction ID, delivery status, and timestamp.
- Usage follows the same delivery reports and credit ledger as other channels.
- No separate Salesforce reporting stack to maintain.
How End Users Set Up Alerts in Four Steps
Once the reseller has enabled OAuth and channels, typical setup takes a few minutes.
Connect Salesforce
One-time OAuth from Connected Services. The panel shows the connected Salesforce identity, with Disconnect available once all object connections are removed.
Connect an Object
Choose Accounts, Leads, Contacts, or another eligible object, then select which phone field holds the mobile number used for messaging.
Turn On Automations
Flip outbound send and inbound logging toggles for SMS, WhatsApp, Voice, and RCS. Each toggle expands to configure templates, sender IDs, and variable mapping.
It Runs Automatically
New records and replies are picked up on a short polling cycle, about once a minute. Check Recent Activity to confirm sends and delivery statuses.
Send Alerts the Moment a Record is Created
Four outbound channels, each independently toggled per connected Salesforce object such as Account, Lead, or Contact.
SMS
- Choose a registered Sender ID for the account.
- Write a free-text message using {FieldApiName} placeholders from the Salesforce object.
- Optionally attach a pre-approved DLT template for Indian traffic.
- Delivery status posted back as a Chatter post automatically.
- Select from approved WhatsApp templates on the account.
- Map header, body, media, and button variables to Salesforce fields or fixed values.
- Supports text headers, image/video/document media headers, and URL buttons with dynamic suffixes.
- Delivery status and replies logged as Chatter posts.
Voice
- Select an approved audio clip from the voice library.
- Places an outbound call and plays the clip when the recipient answers.
- Call status (ANSWERED, NO ANSWER, FAILED) posted as a Chatter post.
- Works on any mobile number in the mapped Salesforce phone field.
RCS
- Select a verified RCS bot and an approved RCS template.
- Map each template variable to a Salesforce object field or a fixed value.
- Supports rich cards, carousels, and action buttons.
- Inbound RCS replies logged as Chatter posts on the matched record.
Log Every Reply Back into Salesforce
Three inbound channels, each independently toggled. Replies are matched by mobile number to the CRM record and posted as Chatter posts.
Incoming SMS
Inbound SMS messages from the record mobile are matched to the Salesforce record and posted as a Chatter post showing channel, message text, and timestamp. Keeps the full SMS conversation in CRM context.
Incoming WhatsApp
WhatsApp replies from the contact number are appended as Chatter posts on the matched Account, Lead, or Contact. Text, media captions, and interactive button replies are captured.
Incoming RCS
Inbound RCS messages and button responses from the record number are logged as Chatter posts on the matched Salesforce record, giving sales teams full reply visibility inside CRM.
Want this plugin on your SMPP Center license or rental?
We will walk through enablement, Connected App OAuth, per-account channel permissions, and how your downline clients connect Accounts, Leads, and Contacts.
Talk to a SpecialistWhy Licensed Customers Choose Salesforce-Triggered Messaging
No AppExchange Dependency
- No AppExchange package install on the customer Salesforce org.
- No custom Apex, Flow packages, or middleware to maintain for the create-to-message path.
- Works with Salesforce orgs that allow Connected App OAuth.
Multi-Object Flexibility
- Start with Accounts, Leads, and Contacts, then add other phone-enabled objects as needed.
- Each object keeps its own independent automation mix.
- Pause, configure, or remove connections without disrupting other objects.
Compliant Messaging Path
- Uses the same DLT, sender ID, and approval workflows already on the platform.
- WhatsApp templates and RCS bots follow the same approval process as manual sends.
- No parallel messaging stack to audit.
Before You Enable the Plugin
Platform checklist
- Active SMPP Center license or rental with the Salesforce Connector enabled
- Credits or post-paid capacity for the channels you open
- Salesforce Connected App Consumer Key and Secret configured in White Label
Salesforce readiness
- Active Salesforce org with OAuth consent allowed for the Connected App
- Phone fields available on Accounts, Leads, Contacts, or other objects you plan to connect
- Field API names noted for SMS placeholder and template variable mapping
Per-channel readiness
- DLT Sender ID and Entity ID for SMS
- Approved WhatsApp templates for WhatsApp sends
- Approved audio clips in the voice library for Voice calls
- Verified RCS bot and approved RCS templates
FAQ
Frequently Asked Questions
Ready to connect Salesforce CRM to your messaging stack?
Chat with usClient Feedback
What Our Clients Say
Our clients run regulated, high-volume messaging infrastructure and prefer not to be named publicly. These testimonials are shared with permission while keeping commercially sensitive details confidential.
Excellent documentation, responsive technical support, and an enterprise-grade platform that scales as our business grows.
We evaluated several messaging platforms before selecting SMPP Center. The deployment flexibility and API capabilities matched our enterprise requirements.
API integration was straightforward and the support team assisted us throughout deployment. We now manage multiple operator connections from a single platform.
High throughput, intelligent routing, and detailed monitoring have significantly simplified our messaging operations.
Names and company details are withheld at our clients' request. This is common among telecom providers, SMS aggregators, fintech companies, and enterprises that consider their messaging infrastructure commercially sensitive.