Ranla is the email platform, so inbound is part of the product: conversations in one inbox, intent classification, drafts in your voice, and a confidence gate before anything goes out.
Replies to campaigns and transactional mail land as threads you can read and answer from the same place you send. Archive, unread, and reply-all work like a mail client. Outbound replies go through the normal send path so suppression and domain rules still apply.
Inbound joins the conversation that started the email. Your reply uses proper threading headers so it stays in the recipient's client too.
Lifecycle and transactional share the stack. Someone writing back about a campaign or a receipt shows up in the same inbox.
Open the thread, edit the draft, send. No copy-paste into a separate support tool for the replies your campaigns create.
Ranla classifies intent (pricing, how-to, unsubscribe, complaint, and more), scores confidence, and drafts in your voice from the business brief and thread history.
High-confidence pricing and product questions can go out on their own when you turn auto-send on. Refunds, churn, legal, and complaints always escalate with a draft ready.
An unsubscribe intent suppresses the address and confirms. It is never answered with a sales pitch.
Out-of-office, auto-responders, and spam do not burn a reply slot or hit your customers with a bot answer.
Auto-reply starts off until you choose draft-only or send. Confidence is a per-account threshold. Cooldowns and daily caps stop runaway loops. Every auto-sent reply is logged with the draft, confidence, and decision.
What people ask back feeds segments and the next campaign. A pricing question is not only a thread to close; it is signal for who was close to buying.
Yes. Inbound lands in a conversation inbox. Ranla classifies intent, drafts in your voice, and either sends when confidence clears your gate or escalates with a draft ready for you.
Only if you turn auto-send on and the intent clears your confidence threshold. Refunds, churn, legal, and complaints always escalate. Auto-reply starts off.
Yes. Lifecycle and transactional share the stack, so someone writing back about a campaign or a receipt lands in the same inbox.
Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.