Email supports up to ten Server-owned IMAP/SMTP mailboxes. Each mailbox can have its own queue, approved sender aliases, time zone and weekly routing hours, polling state, and retention policy. Mail is still imported while routing is closed; automatic routing follows the selected mailbox or workspace schedule. Customer-owned mailbox permissions are required; uncertain sends need review.
Website chat needs an exact allowed HTTPS origin and a public HTTPS proxy to the running host's chat listener. Its governed scripted bot requires an explicitly authorized published flow and human handoff; it is not an autonomous LLM agent.
SMS/WhatsApp options include Twilio, Telnyx, Vonage, AWS SMS, Meta WhatsApp Cloud, and a bounded HTTP SMS adapter as applicable to each channel. A Twilio account can register up to ten senders per SMS and WhatsApp channel, with each inbound sender routed to a queue, published channel flow, or direct Agent and fallback queue. Replies stay with the original sender; STOP blocks the customer's channel address across senders. Consent, quiet hours, WhatsApp templates/windows, authenticated callbacks, and provider charges apply.
Reviewed campaigns support up to 100 existing scoped opted-in conversations across SMS, WhatsApp, and private Social conversations on Telegram, LINE, Messenger, and Instagram where the provider account and policy are configured. Drafts require a fresh, single-use review before queueing or scheduling; consent, sender, policy, reply windows, and quiet hours are checked again before dispatch. Public comments, groups, imported contacts, and automatic catch-up after missed schedules are excluded. Delivery acceptance is not proof of receipt; uncertain sends need individual review.