MAYAConnecting WhatsApp or Telegram
WhatsApp connects through a Meta window when the installation offers it (as on maya-erp.com), or with your own Meta credentials; everything is tested before being stored, encrypted.
Conversations and channels
The articles in this topic, each naming the exact screen where the action happens.
Conversations and channels
11 articlesConnecting my company mailbox
One Microsoft 365 account (or a Gmail mailbox) for the company, tested before being stored; sending addresses are set per entity.
MAYA is not replying to my customers
Possible causes, in this order: channel not connected, the channel's automatic reply turned off, AI replies exhausted, subscription read-only, conversation taken over by a person.
Following a conversation and taking over from the agent
When a person takes over a conversation, the agent goes quiet; it takes it back after a delay you set, unless you turn that return off.
Handling support tickets
One queue per entry point, each with its mailbox; without an assignment rule, a ticket arrives unassigned.
MAYA Chat: your team's internal assistant
MAYA Chat carries out your instructions with YOUR rights: it only sees and does what you could see and do yourself.
Connecting Facebook and Instagram
The connection goes through a Meta window, for one entity; there you choose the Pages and Instagram accounts MAYA manages.
Why MAYA does not reply to some messages
Some silences are on purpose: a person took over, the sender is a bot, or a cold caller is writing by email.
The chat on your website
A chat bubble is switched on site by site; MAYA answers there as on WhatsApp, and the exchanges arrive in the Sales Agent.
Answering customer questions on time
A question MAYA cannot answer waits for a person; beyond the delay, in business hours, the owner then the lead are notified.
Measuring what MAYA resolves on its own
The autonomous resolution rate counts conversations settled without a person; with no conversation judged, it is not shown rather than saying zero.