Authorize mailbox
Connect the support mailbox using the configured Gmail connection path.
Gmail threads enter Replofy with routing, summaries, ownership, AI drafts, approved-source replies, and human send control.
OAuth authorizes the mailbox and selected labels.
Inbound email becomes a ticket with owner and tags.
Operators send approved responses from Replofy.
Gmail threads enter Replofy with routing, summaries, ownership, AI drafts, approved-source replies, and human send control.
email messages synced
Connect the support mailbox using the configured Gmail connection path.
Assign by topic, sender, priority, sentiment, or ticket status.
Let Aura summarize and draft from approved sources while humans keep send control.
Confirm thread continuity, replies, and ownership state in the Replofy inbox.
Thread body
Summarize, classify, draft
Review before reply
Sender identity
Match customer context
Assign owner or team
Subject and history
Detect topic and urgency
Merge or route ticket
Attachments
Provide context when permitted
Inspect and escalate
Connect the support mailbox using the configured Gmail connection path.
Assign by topic, sender, priority, sentiment, or ticket status.
Let Aura summarize and draft from approved sources while humans keep send control.
Confirm thread continuity, replies, and ownership state in the Replofy inbox.
Do not route all email to one owner
Do not enable drafts without approved sources
Check attachment handling for sensitive data
Verify reply identity before launch
SMTP lets branded sender and domain workflows feed Replofy while preserving routing, ownership, deliverability awareness, and approved answers.
Web chat captures visitor intent, page context, contact data, and issue details, then routes the case into inbox, Aura, knowledge, or human escalation.
WhatsApp messages can be triaged, summarized, routed, drafted, and escalated without isolating mobile conversations from the rest of support.
Connect Gmail to the same workflow as chat, social, knowledge, and Aura.