Protected credentials
Provider credentials stay in protected integration settings, not public website code or AI instructions.
Integrations
Keep your systems. Connect the customer journey.
Connect customer channels, supported social networks, calendars, APIs, webhooks and business systems while keeping one customer context in MAY.
Every channel
One customer context across the places customers already use.
Website, WhatsApp, email, social messaging, voice and external systems can connect to the same business intelligence and customer journey.
WEBWebsite
MESSAGINGWhatsApp
INBOXEmail
ONE CUSTOMERSame contextacross every channelSOCIALMessages
CONVERSATIONVoice
SYSTEMSAPI / DMS
Integration principles
Connect deliberately. Keep credentials protected.
MAY presents business-facing integration settings while authenticated APIs and signed webhooks support custom paths where needed.
API-first design
Authenticated APIs and signed webhooks support controlled integrations with external systems.
Clear business settings
Teams configure the integration through understandable fields rather than raw internal keys.
Website widgetWhatsApp BusinessInstagramFacebookLinkedInYouTubeXGoogle CalendarMicrosoft CalendarAPISigned webhooksCRMERP / DMSEmailVoice-ready architecture
Social capabilities vary by official provider API, account type, approved access and granted permissions. MAY exposes only supported connected actions.
Make AI Yours.