Unified operations
Bring supported social conversations into the same operating model as other customer channels instead of creating a separate social CRM.
MAY Social connects supported activity across Instagram, Facebook, LinkedIn, YouTube and X to the same governed customer and content operations your business already uses.
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.
MAY does not promise feature parity where the networks themselves do not provide it. Connected capabilities are shown and enforced per provider.
Supported messaging, comments and publishing through Meta connections where the account type and granted permissions allow them.
Supported Page messaging, comments and publishing through Meta connections, subject to Meta permissions and messaging rules.
Supported posts, comments and reactions subject to approved LinkedIn access. MAY does not present LinkedIn as a generic DM inbox.
Supported video publishing plus comments, replies and moderation workflows. YouTube is not represented as a generic private-message channel.
Supported posts, replies and mentions. Direct messages are available only when the connected API tier and approved access permit them.
What MAY can do is resolved from the provider connection and permissions rather than inferred from a network name.
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.
MAY drafts ideas and network-specific content. A person approves each item before supported scheduling or publishing.
Approve a planned calendar, then allow MAY to execute supported scheduled actions inside the approved plan and provider permissions.
Enable configured automated planning and publishing only after the business deliberately turns it on for eligible connected networks.
Social is most useful when creation, engagement and customer operations live in one lifecycle instead of separate tools.
A useful customer question arrives from a supported social surface.
MAY uses approved business context and captures what matters.
Provider policies, supported messaging windows, API tiers and channel permissions still apply. MAY does not claim an action a connected provider has not granted.
Choose where AI may suggest, where it may act automatically and when a person must take over.
Social Engage and Social Autopilot can be included by plan, added later or configured as part of an Enterprise agreement.
No. Capabilities depend on the provider API, account type, approved access and granted permissions.
Yes. Human control and takeover remain part of the operating model wherever a supported engagement flow is connected.
No. Social Engage and Social Autopilot are separate commercial capabilities. Some configured flows can depend on another capability being active.
Into MAY customer operations, including Inbox, qualification, CRM and follow up where the tenant and provider capabilities support them.
See the active Social Engage and Social Autopilot options in the live MAY commercial catalogue.