Somosmate: What the Name Means, and What SocialMate Actually Does

What is somosmate?

Somosmate is almost certainly a misspelling of SocialMate, produced by dictation or by phone autocomplete. SocialMate is self-hosted WhatsApp automation: it runs on your own computer or server, sends from your own WhatsApp number, keeps chats in local storage, and is sold as a flat licence with no per-message fee.

The drift is ordinary. Said aloud, "SocialMate" lands close to "somosmate", so voice search and dictation produce the variant. Typed on a phone, "soci" and "somo" sit one thumb-slip apart, and "somos" is a common word in Spanish and Portuguese, which is what autocomplete reaches for first.

We know of no separate Somosmate app. If you arrived at this spelling looking for a person or an unrelated brand, this page does not describe it. It defines one entity, with sources named in the prose rather than assembled into a footnote.

What SocialMate is not matters as much as what it is: not the official WhatsApp Business API, not a Cloud API reseller, not a cloud service, and not a bulk-messaging product. The long product-and-price explanation lives in what SocialMate is and what it costs; this page answers the name.

Is SocialMate affiliated with WhatsApp or Meta?

No. SocialMate is an independent product — not affiliated with, endorsed by, or partnered with WhatsApp or Meta, and holding no Business Solution Provider status. It speaks the WhatsApp Web client protocol from the user's own machine, which is why it needs no Meta business verification and no dedicated number. "WhatsApp" and "Meta" appear on the site only to identify the platform.

That distinction explains most marketing in this category. A Business Solution Provider inherits Meta's approval process and quality-rating model because its customers' numbers live inside Meta's system. Their copy says "official" and "approved" for a structural reason: those words are true for them and cannot be true for anyone outside that system.

The account structure underneath is reported to be moving. According to Salesforce's help article on WhatsApp Business Platform account-model evolution, published 15 October 2026, Meta began introducing an evolved WhatsApp Business account structure in October 2026; the published excerpt is truncated where it addresses existing accounts, so treat the direction as reported and read the source yourself. Practitioner analysis such as IAGENTE's article, first published 21 May 2026 and updated 9 November 2026, discusses BSUID, flexible limits and a max-price mechanism — secondary reporting, not confirmed specification.

A self-hosted app does not sit downstream of that structure. No templates, no quality rating, no verification queue, no vendor holding your conversations. The trade is real: you give up the official badge and the vendor SLA, and you take on the pacing work — which SocialMate ships as software rather than a paragraph in its docs.

What does SocialMate cost, and why is there no per-message fee?

SocialMate is a flat licence with no per-message fee on any tier. Free is $0 forever with no card; Pro is $99 a year ($8.25 a month equivalent) or $10 a month, cancel anytime. It is priced per device because the sends run on your machine, from your connection, through your number — there is no relay to meter.

One licence includes one device, machine-bound; extra seats are $4 a month or about $40 a year each. The 7-day Pro trial is opt-in from inside the app, asks only for an email, and is limited to one trial per machine.

The Free tier carries 200 messages a day on one account, human-like pacing, a real typing indicator, read receipts before replying, the duplicate-content guard, session warming and live risk scoring. Pro lifts the ceiling to a safe 500 a day per account and, after 72 hours of warming, High-Volume Mode scales to 5,000 a day per account.

On the other side of the table sits a meter. Meta's utility rate has been quoted at $0.0034 per message and Twilio's platform fee at $0.005, per SocialMate's published pricing analysis; both figures move, so check the live Meta rate card and Twilio pricing page before you budget.

The per-message versus flat-licence breakdown does the arithmetic. The honest summary is that per-message pricing is small at low volume and becomes the entire cost at high volume. Current figures, seat terms and trial conditions are on pricing.

How is SocialMate different from the WhatsApp Cloud API?

The Cloud API is Meta's official route: business verification, a dedicated number, per-message billing, and conversations held by Meta or a Business Solution Provider. SocialMate is the unofficial, self-hosted route: your own number, no approval, a flat licence, local storage. Neither is better in the abstract — but a meter is the wrong shape for messaging people who already ordered, booked or asked.

Send rate is set differently on each side. Meta controls throughput through messaging limits, tiers and template quality, with no pacing dial for the sender to tune, as set out in who sets your WhatsApp send rate. Qontak's guide to WhatsApp message limits, tiers and throughput, published 5 October 2026 and updated 27 October 2026, treats those tiers as a live operational constraint for businesses rather than a solved problem.

Where conversations live is the third difference. With a Cloud API provider, message content and contact data sit in the vendor's cloud and in Meta's system. With SocialMate they sit in local storage on your machine. Only one of those models means no third party holds your customer list.

The protocol itself moves without notice: WABetaInfo reported on 9 November 2026 that WhatsApp was testing a Contacts tab in place of Communities in Android beta, and on 10 November 2026 for iOS beta — unreleased, and it changes nothing about today's features here. The full side-by-side is at SocialMate vs the Cloud API.

How is SocialMate different from Evolution API and WAHA?

Evolution API and WAHA are open-source WhatsApp APIs you host yourself. Both are free to license and genuinely capable, and both leave pacing, storage, search and interface to you — SocialMate ships those as the product. Docker is SocialMate's option; for a bare API project it is the obligation. All three speak the unofficial protocol, so all three carry ban risk.

Evolution API is a widely used open-source REST API. You get endpoints; you write the anti-ban logic, operate the database and build the interface. Best for an infrastructure team that wants to own the stack end to end. The licence is $0 and the running cost is not — Evolution API Free sets out the server, database and engineering hours the price tag omits. Head-to-head: SocialMate vs Evolution API.

WAHA is a focused WhatsApp HTTP API with solid developer experience. It still leaves pacing, history search and the GUI to you. Best for a developer who wants a lean API and no desktop app; risk-based slowdown is yours to design. Head-to-head: SocialMate vs WAHA.

SocialMate is the same self-hosted shape with the missing half included: an engineered anti-ban pipeline, local history with full-text search on Pro, a GUI, a headless server option and a desktop build that needs no DevOps. It is a licensed product, not a free library, and its defaults are harder to gut than a bare API. Category view: SocialMate vs self-hosted APIs.

No credible per-provider ban rate is published for any of these projects, so this page does not quote one. Inventing a figure would be the fastest way to lose your trust.

Will I get banned using SocialMate?

Bans are always possible on any unofficial WhatsApp route, and no vendor can honestly promise otherwise. SocialMate reduces risk with a specific, listable set of controls and says plainly that it cannot remove it. No credible per-provider ban rate is published for any tool in this category, including this one.

Put the legal position first, because it belongs to the reader. Automating WhatsApp through the unofficial Web protocol may breach WhatsApp's Terms of Service. Read the current terms yourself; that risk is yours to weigh. SocialMate's own terms state it is "not a bulk-messaging, broadcast, or spam platform".

What the anti-ban engine does

• Randomised delays and jitter, so sends do not fall on a metronome.
• Pacing profiles — Safe, Balanced, Fast — that set an account's tempo.
• Per-number rate limits, plus a burst ceiling of 3 per 10 seconds on Free and 5 on Pro.
• Session warming for new numbers, ramping over 72 hours before High-Volume Mode opens.
• A real typing indicator and read receipts before replying: the app reads, then types, then sends.
• An adaptive throttle that slows sends as computed risk climbs.
• A duplicate-content guard that blocks identical text or images going to many contacts.
• Live 8-factor risk scoring, including cold-outreach detection.
• Risk-based auto-resume for accounts that were cooled.

The desktop advantage, stated carefully

Run on your own computer, SocialMate connects from your own residential IP — ideally the same home network as the phone that owns the number. That is the network picture WhatsApp already associates with the number, so it reduces one risk factor. It is not ban-proof and it does not permit faster sending. A VPS uses a datacenter IP; per-account proxy routing on Pro lets a VPS account egress through your own residential or mobile proxy. It changes the network path only — rate limits and warming still apply.

Consent-first messaging, a gradual ramp and modest volume remain the safe default. Send batches of individual, personalised messages to people who expect to hear from you. Higher volume is never risk-free.

Does SocialMate have an API, and is it Pro-only?

No — the local HTTP API runs on Free. It ships 64 documented endpoints and 35 webhook events, nine of them free. Plain-text send, quoted replies, emoji reactions, mark-as-read and the typing indicator all work on Free. Pro adds media send, polls, locations, contact cards, group operations, the smart queue, scheduled messages, the named tunnel, unlimited webhooks and Agent Memory.

Reactions, mark-as-read and the typing indicator produce no chat bubble, so they cost no message budget and do not raise the risk score. One setup detail explains most support tickets: the local API server is off by default. Switch it on under API & Integrations, create a key (it looks like sm_… and is shown once), then point your code at http://127.0.0.1:3456.

Exactly two things are native

• n8n. A first-class community node, n8n-nodes-socialmate, version 2.7.1 on npm today, with a scope-aware credential, an action node, a trigger node, and every operation usable as an n8n AI-Agent tool. Its Get AI Context operation returns a whole conversation, role-mapped and token-windowed, replacing the fragile memory node. Start at the n8n hub.
• MCP. A native Model Context Protocol server, socialmate-mcp, version 1.2.3 with 44 tools, so Claude Desktop, Cursor, Cline and any MCP client can control WhatsApp as tools. Guide at the MCP server docs.

Make, Zapier, Shopify, HubSpot, Pipedrive and Google Sheets all connect through the HTTP API plus outbound webhooks. There is no one-click connector for any of them. MCP is an open protocol surface like the REST API, not a per-service integration, and not a way around limits: every tool call passes the same anti-ban, key-scope and tier checks.

Developers can read the full reference — authentication, errors, webhooks, recipes — at docs.

What arrives with SocialMate 3?

Two things arrive with SocialMate 3, and neither is in today's download: the Claude Agent, SocialMate Pro's built-in WhatsApp AI agent, and the free WordPress plugin "SocialMate – Messaging & AI Agent". No date is promised. Everything else on this page describes the current 2.x release.

The Claude Agent is one agent per WhatsApp number, running inside the app on your own machine. It is built on Anthropic's Claude Agent SDK — the model is your choice, a separate setting on your own key: Claude, DeepSeek, OpenRouter, Ollama, Kimi, GLM, MiniMax or a custom endpoint. It replies like a person with quoted replies, reactions, photos, voice notes and polls, hands chats to a person, asks approval before risky actions, and keeps to budgets with usage and cost stats. Details at the Claude Agent section.

The WordPress plugin links a site to the app with one connection token: order updates, basket reminders, back-in-stock alerts, WhatsApp sign-in codes and chat buttons, on every plan. On Pro it connects the agent to a WooCommerce store. It is not on WordPress.org — download the zip from the WordPress plugin section and install it with Plugins, Add New Plugin, Upload Plugin.

Same rule on safety: every message the Claude Agent sends goes through the same anti-ban pipeline — rate limits, jitter, warming, risk checks — as any other send. It does not make a number ban-proof, and it is not built to message many people at once. It answers people who write in, plus opted-in event messages. The launch page is at what's new.

Option	Pricing model	Approval / verification required	Where conversations live	Who sets the send rate	Ban / account risk
SocialMate (self-hosted desktop or VPS)	Flat licence, per device. Free $0 forever; Pro $99/year ($8.25/mo) or $10/month. No per-message fee on any tier.	None from Meta. Link your own number via QR, as WhatsApp Web does.	Local storage on your own machine or server; nothing routed through SocialMate's servers.	You do — pacing profiles, per-number limits, jitter, warming and an adaptive throttle ship in the app.	Unofficial client protocol, so bans are always possible. Risk reduced by the anti-ban engine and, on desktop, by egress from your own residential IP. Not eliminated.
WhatsApp Cloud API (Meta direct, Twilio, 360dialog, WATI)	Metered per message. Meta's utility rate has been quoted at $0.0034 per message and Twilio's platform fee at $0.005, per SocialMate's pricing analysis; both figures move, so re-verify the live rate cards.	Meta Business account and business verification; a dedicated number.	Meta's system and the provider's cloud.	Meta — through messaging limits, tiers and template quality. No pacing setting for the sender to tune.	Sanctioned route with no unofficial-protocol exposure, but policy enforcement and quality ratings still apply to the number.
Evolution API (open source, self-hosted)	Free to license. You pay for the server, database, TLS and engineering time.	None from Meta.	Your server; you build and operate storage and search.	You do — risk-based pacing is not the product, so that logic is yours to write and maintain.	Unofficial client protocol. Bans are possible; no per-provider ban rate is published.
WAHA (open source, self-hosted)	Free to license. You pay for the server, TLS and engineering time.	None from Meta.	Your server; you operate storage and history.	You do — adaptive slowdown is yours to design.	Unofficial client protocol. Bans are possible; pacing and risk controls are yours to build.

Frequently asked questions

Is Somosmate the same as SocialMate?

Almost certainly. Somosmate is most likely a misspelling of SocialMate, usually produced by voice search or phone autocomplete, where "somos" pulls the suggestion. We know of no separate Somosmate app.

Is SocialMate an official WhatsApp Business API provider?

No. SocialMate is independent and holds no Business Solution Provider status. It is not affiliated with, endorsed by, or partnered with WhatsApp or Meta. It speaks the WhatsApp Web client protocol from your own machine, which is why it needs no Meta business verification and no dedicated number — and why it ships an anti-ban pipeline instead of a compliance guarantee.

Does SocialMate charge per message, and is there a free plan?

No per-message fee on any tier. Free is $0 forever with no card and allows up to 200 messages a day on one account. Pro is $99 a year ($8.25 a month equivalent) or $10 a month, starting at a safe 500 a day per account and, after 72 hours of warming, scaling to 5,000 a day per account via High-Volume Mode. One licence includes one device; extra seats are $4 a month each.

Will I get banned using SocialMate?

Bans are always possible on any unofficial WhatsApp route, and no tool can promise otherwise. Automating WhatsApp over the Web protocol may breach its Terms of Service. SocialMate reduces risk with randomised delays, Safe/Balanced/Fast pacing, per-number limits, 72-hour warming, a real typing indicator, read receipts, an adaptive throttle, a duplicate-content guard and live risk scoring. It does not eliminate the risk.

How is SocialMate different from a WhatsApp bulk sender?

A bulk sender optimises for volume to a list. SocialMate's terms state it is "not a bulk-messaging, broadcast, or spam platform", and the product enforces that: the duplicate-content guard blocks identical text or images going to many contacts. The unit of work is a batch — many individual, personalised messages to people already waiting on you, each paced through the anti-ban pipeline. Consent is required; a bought or scraped list is not a use case.

Is the WordPress plugin or the Claude Agent available now?

No. Both arrive with SocialMate 3, coming soon and not in today's download. The plugin is not on WordPress.org: download the zip from the /wordpress/ page and install it with Plugins, Add New Plugin, Upload Plugin. When it ships it sends WooCommerce order updates, basket reminders, back-in-stock alerts, sign-in codes and chat buttons on every plan, and connects the Pro Claude Agent to the store.

Does SocialMate have an API, and is it Pro-only?

The local HTTP API runs on Free — 64 documented endpoints and 35 webhook events, nine of them free, including plain-text send, quoted replies, reactions, mark-as-read and the typing indicator. Pro adds media send, polls, locations, contact cards, group operations, the smart queue, scheduled messages, the named tunnel, unlimited webhooks and Agent Memory. The API server is off by default; switch it on under API & Integrations first.