Configure sender domain
Set the support address and sending identity.
SMTP lets branded sender and domain workflows feed Replofy while preserving routing, ownership, deliverability awareness, and approved answers.
Admins verify sender identity before production replies.
Replofy records delivery state and warnings.
Support email remains visible inside the inbox lifecycle.
SMTP lets branded sender and domain workflows feed Replofy while preserving routing, ownership, deliverability awareness, and approved answers.
custom email sending
Set the support address and sending identity.
Confirm expected authentication and bounce handling.
Route custom-domain messages into teams and workflows.
Confirm customers receive replies from the right identity.
Inbound support message
Classify and summarize
Assign or reply
Custom sender
Preserve channel identity
Verify from-address
Thread headers
Maintain continuity
Merge duplicate tickets
Delivery state
Surface send issues
Adjust configuration
Set the support address and sending identity.
Confirm expected authentication and bounce handling.
Route custom-domain messages into teams and workflows.
Confirm customers receive replies from the right identity.
Keep support and marketing sender identities separate
Validate thread continuity before production
Review bounce and failure handling
Use approval on sensitive replies
Gmail threads enter Replofy with routing, summaries, ownership, AI drafts, approved-source replies, and human send control.
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.
Use branded email with routing, approvals, and thread continuity.