Teams running sales or support out of Salesforce often end up bolting on a separate texting tool, which means conversations live outside the records they're supposed to update. 360 SMS App is an AppExchange package that puts SMS, WhatsApp, and several other channels natively inside Salesforce, so texting triggers from workflows and every reply logs against the contact or case that started it. This review covers what's verifiable from the vendor's own site, what pricing looks like, and where the evidence runs thin.
| Best for | Salesforce-native sales/support teams that want SMS and WhatsApp texting tied to CRM records |
| Starting price | Not published — vendor requires a quote; free trial advertised with a roughly 2-minute install |
| Real cost | Unknown; depends on users, channels, and message volume, none of which the vendor discloses publicly |
| Setup speed | Installed as an AppExchange package; vendor claims a 2-minute setup |
| Standout feature | 11 messaging channels (SMS, WhatsApp, WeChat, Viber, Kakao, LINE, Instagram, Messenger) plus AI translation and sentiment analysis, all inside Salesforce |
| Biggest caveat | No public pricing, and we could not independently verify third-party review data at time of writing |
| Third-party rating | Not independently verified — see below |
It's a Salesforce AppExchange application, not a standalone platform — you install it into an existing Salesforce org rather than sign up for a separate account. Once installed, it adds SMS and MMS sending, plus channels like WhatsApp, WeChat, Viber, Kakao, LINE, Instagram, and Facebook Messenger, as native record types and automation triggers inside Salesforce. Messages send from Process Builder or Apex-driven workflows, from bulk actions on reports and list views, or as live two-way conversations from a rep's console. The vendor also advertises a set of AI add-ons: auto-drafted replies, real-time translation, sentiment analysis, and message template quality scoring.
Because it's a managed package, setup starts on the Salesforce AppExchange listing rather than a normal signup form; the vendor claims installation takes about two minutes, with a free trial to test the core texting flow. From there, admins configure automation (which numbers send from which flows, what triggers a text) and reps work conversations from a threaded inbox view layered on top of standard Salesforce records. Teams that already run their pipeline through Process Builder or Flow get the most value, since 360 SMS App plugs texting into logic that already exists rather than requiring a parallel automation system.
360 SMS App does not publish pricing on its website, its pricing-page URLs return 404, and no plan tiers, per-user costs, or message-volume pricing are disclosed anywhere in the public site. The vendor points prospects to a quote request instead. That's consistent with a lot of enterprise Salesforce AppExchange tooling, where list price varies by seat count, channel mix (adding WhatsApp or other channels typically costs more than SMS alone), and message volume — but it also means there's no way to do the real-cost math we'd normally run here. Budget for a sales conversation, and push specifically on per-channel and per-message costs, since those are the line items most likely to surprise you later.
The vendor's own site claims "1,200+" positive reviews, and 360 SMS App has an AppExchange listing and appears on review aggregators, but we could not pull a verified star rating or review count from G2, Capterra, or the AppExchange listing itself — those pages render client-side and returned no usable content through our research tools, and we won't cite a number we can't confirm. We also found no accessible Reddit or Trustpilot threads discussing the product specifically. In short: there's a real user base behind this app based on how long it's been on AppExchange and the breadth of its feature set, but we don't have independently verifiable sentiment data to report, positive or negative. Treat the vendor's own review count as a vendor claim, not a verified third-party figure.
Pros
Cons
Good fit: Salesforce shops already running sales or support workflows through Process Builder or Flow that want texting to inherit that automation instead of living in a separate app; teams needing more than SMS (WhatsApp, Instagram, Messenger) attached to CRM records; regulated industries where a message needs to be logged against a case or contact automatically.
Poor fit: teams not on Salesforce (this only works as an org add-on); anyone who needs pricing certainty before a sales call, since nothing is published; teams that just want simple standalone SMS without CRM automation, where a lighter tool will be cheaper and faster to stand up.