Nectar Social

The vendor documents its agents taking authenticated action inside systems it does not own: replying one-on-one in DMs, comments and stories on the connected platforms, moderating and triaging those conversations, and running giveaways, product drops and opt-in capture that convert engagement into subscribers. Official data partnerships across Meta, TikTok, LinkedIn, Reddit and X carry comments, DMs, stories, video frames and audio into one engine, deep integrations are named with Klaviyo and Attentive for downstream retargeting, and CRM and revenue attribution sync ties conversations to sales and lifetime value, so the reach extends beyond the social channel into email and SMS marketing and into CRM.

Sourcenectarsocial.com Engage, Deploy and platform sectionsread 2026-09-01

A flow the brand configures across several agents and people: teams adjust workflows with the AI Assistant, set channel and topic specific autopilot modes, and Collaborative AI Routing hands conversations between agents and people with the reason for each hand off, while agents run engagement, moderation, campaigns and giveaways side by side (nectarsocial.com Train, Test and Deploy and Engage sections).

Sourcenectarsocial.comread 2026-10-01

Replies are grounded in maintained structures the brand curates rather than assembled per request. A brand voice studio with tone calibration holds the voice the agent writes in, custom topic classification and auto-tagging give it the brand's own taxonomy rather than a generic one, and customer history and prior conversation records are read at reply time.

Feeding all of it is a real-time engine that ingests every comment, message, story, video frame and audio clip across the connected platforms, including untagged mentions, so the agent answers from what is actually being said about the brand down to the SKU rather than from tagged content alone. The vendor's own phrase is that agents are trained on tone, content and customer history, which reads as fine tuning rather than retrieval. No knowledge base, ingestion or retrieval configuration surface is documented publicly, since the product documentation sits behind a login.

Sourcenectarsocial.com Engage and listening sectionsread 2026-09-01

Autonomy is configurable per channel and per topic as a setting in the shipped product. The vendor names channel and topic specific autopilot modes, so a brand decides where the agent may act unattended and where it may not, and gates that decision on accuracy scoring and confidence thresholds established during the Test stage.

Around it sit human-in-the-loop validation before deployment, a Copilot that drafts on-brand replies and translations for a person to send, brand-safety guardrails applied across all automated interactions, and Collaborative AI Routing that hands off to a named person with the reason attached.

Sourcenectarsocial.com Engage section, Train, Test and Deploy stagesread 2026-09-01

The vendor's own security block states SOC II Type 2 compliance as the attestation and names single sign-on plus role-based access control as customer-facing controls, and the platform is elsewhere described as built with compliance, data integrity and role-based access controls. These claims sit in a badge row on the marketing homepage. No trust center, security page, named audit firm, report request path or sub-processor list is published, and the SOC 2 Type 2 report itself is not public.

Sourcenectarsocial.com security sectionread 2026-09-01

One genuine visibility mechanism, and the rest is reporting. Collaborative AI Routing is documented as explaining every hand-off, so when an agent passes a conversation to a person or another queue the reason is surfaced.

Everything else is campaign measurement: sentiment shifts, emerging topics, community health, share of voice, virality, earned media value, unified KPI and revenue dashboards and attribution from conversation to purchase.

No audit log, agent run history, per-conversation action trail or record of what an agent did and when appears on any public surface, and the product documentation is login-gated.

Sourcenectarsocial.com Engage and Performance sectionsread 2026-09-01

Agents read the platform's own data at reply time, meaning customer history, community profiles and conversation records, along with the brand voice configuration. Real-time learning appears as a single bullet under the Train stage with no mechanism, scope or retention attached, and the vendor's own phrasing elsewhere is that agents are trained on tone, content and customer history, which is training rather than runtime memory. The product documentation sits behind a login, and the public product material describes no memory feature with its own scope and lifetime apart from that data.

Sourcenectarsocial.com Engage sectionread 2026-09-01

Cloud SaaS with nothing the customer selects. No region choice, no residency commitment, no data center disclosure, no sub-processor list, no VPC, private tenancy, self-hosted or on-premises option appears on the homepage, in the privacy policy or anywhere else on the public site, and the privacy policy addresses sharing, cookies and children's privacy without locating processing. Where conversation data is processed and stored is not published.

Sourcenectarsocial.com and nectarsocial.com/privacy-policyread 2026-09-01

Ready-to-use capability without adoptable packaged assets. The Nectar Agent, the Copilot and the Community Hub ship working, and Campaigns and Opt-Ins provides automated replies, giveaways and product drops as named capabilities, so a brand gets agent output without building anything. No library of prebuilt agents, template gallery, importable starting configurations or browsable catalog appears on any public surface, and the customization the vendor emphasizes runs toward a brand voice studio with tone calibration and custom topic classification the customer defines.

Sourcenectarsocial.com Engage section and platform overviewread 2026-09-01

Inbound messages from the brand's audience start the agents: they answer DMs and comments one on one in real time across the connected social platforms, and campaign automation runs giveaways and product drops without a person starting each one (nectarsocial.com home page).

Sourcenectarsocial.comread 2026-10-01

Nectar runs on its own multimodal AI stack and does not document customer choice of underlying model or routing across external model providers.

Sourcenectarsocial.comread 2026-10-01

Nectar runs its own MCP server and publishes its discovery document: the RFC 9728 protected resource metadata on mcp.nectarsocial.com declares the endpoint https://mcp.nectarsocial.com/mcp, an OAuth authorization server at beta-api.nectarsocial.com, bearer authentication by header and two scopes, content:read and analytics:read. No tool list is published, the declared scopes are read only, so no tool is shown creating or changing the platform's own objects, and the product documentation is login gated with no public API reference (mcp.nectarsocial.com metadata and nectarsocial.com).

Sourcemcp.nectarsocial.com/.well-known/oauth-protected-resourceread 2026-10-01

A documented way to evaluate a change, run before deployment.

The product ships a dedicated Test stage between Train and Deploy, and the vendor names historical message replay for training validation, so a candidate configuration is run against the brand's own real message history before it goes live, with accuracy scoring and confidence thresholds applied to the result and channel and topic specific autopilot modes determining where the agent is then allowed to act unattended.

What is replayed and scored is the agent's own responses, so the check covers the agent rather than the campaign. The vendor's own framing is validating response quality and building confidence with human-in-the-loop before deployment.

Sourcenectarsocial.com Engage section, Test stageread 2026-09-01

Nectar engages through social platform integrations rather than driving a browser or operating a computer interface.

Sourcenectarsocial.comread 2026-10-01