MAY Social

From social attention to customer action.

MAY Social connects supported activity across Instagram, Facebook, LinkedIn, YouTube and X to the same governed customer and content operations your business already uses.

Social Engage

Turn supported social interactions into real customer context.

Engage is capability-aware. MAY can work with comments, replies, mentions and private messages only where the connected provider, account type, API access and permissions support that action.

Provider aware by design

One Social layer. Different network capabilities.

MAY does not promise feature parity where the networks themselves do not provide it. Connected capabilities are shown and enforced per provider.

IG

Instagram

Supported messaging, comments and publishing through Meta connections where the account type and granted permissions allow them.

FB

Facebook

Supported Page messaging, comments and publishing through Meta connections, subject to Meta permissions and messaging rules.

IN

LinkedIn

Supported posts, comments and reactions subject to approved LinkedIn access. MAY does not present LinkedIn as a generic DM inbox.

YT

YouTube

Supported video publishing plus comments, replies and moderation workflows. YouTube is not represented as a generic private-message channel.

X

X

Supported posts, replies and mentions. Direct messages are available only when the connected API tier and approved access permit them.

API

Capability truth

What MAY can do is resolved from the provider connection and permissions rather than inferred from a network name.

Social Autopilot

Create once. Adapt deliberately. Publish where supported.

Autopilot supports provider-aware content planning and adaptation, so a single idea can become network-appropriate content without pretending every network accepts the same format or action.

01

Approval Required

MAY drafts ideas and network-specific content. A person approves each item before supported scheduling or publishing.

02

Calendar Approved

Approve a planned calendar, then allow MAY to execute supported scheduled actions inside the approved plan and provider permissions.

03

Full Autopilot

Enable configured automated planning and publishing only after the business deliberately turns it on for eligible connected networks.

The connected loop

Content becomes interaction. Interaction becomes customer context.

Social is most useful when creation, engagement and customer operations live in one lifecycle instead of separate tools.

SOCIAL SIGNAL

“Can I get this in automatic?”

A useful customer question arrives from a supported social surface.

→
→
NEXT ACTION

Customer lifecycle continues.

CRMHuman handoffFollow up
Human control

Automation remains governed.

Provider policies, supported messaging windows, API tiers and channel permissions still apply. MAY does not claim an action a connected provider has not granted.

Business rules first

Choose where AI may suggest, where it may act automatically and when a person must take over.

Commercial access stays explicit

Social Engage and Social Autopilot can be included by plan, added later or configured as part of an Enterprise agreement.

FAQ

MAY Social, clearly.

Does MAY support the same actions on every network?

No. Capabilities depend on the provider API, account type, approved access and granted permissions.

Can a person take over?

Yes. Human control and takeover remain part of the operating model wherever a supported engagement flow is connected.

Is Autopilot required for Social Engage?

No. Social Engage and Social Autopilot are separate commercial capabilities. Some configured flows can depend on another capability being active.

Where does social customer context go?

Into MAY customer operations, including Inbox, qualification, CRM and follow up where the tenant and provider capabilities support them.

MAY Social

Connect social attention to the customer lifecycle.

See the active Social Engage and Social Autopilot options in the live MAY commercial catalogue.