Skip to content
RevXAI
Pillar 3 · Execution

Multi-channel sequences, drafted in Arabic, launched as one.

Email via Instantly. LinkedIn connection requests and follow-ups. WhatsApp opening messages. Calendar booking via Cal.com, Google, Outlook. One launch flow. Reply-assist with AI-suggested drafts that an operator reviews before send.

The four V1 channels

Channel-specific drafts. One launch flow.

Each channel inherits tone, CTA strategy, and banned phrases from the brief. Samples below are generated in Arabic by default. (PRD §22.2 + §23.2)

  • Email

    via Instantly v2

    Subject + body, persona-aware, segment-aware, with variants. Replies sync back for reply-assist.

    Sample · subject + opener
    سؤال سريع حول معالجة بيانات العملاء غير المقيمين

    أهلاً أبا فيصل، رأيت إعلانكم الأخير عن توسعة قاعدة العملاء خارج السعودية. لاحظنا أن ٧ من ١٠ فرق فينتك بحجمكم تواجه فجوة في معالجة بيانات غير المقيمين بعد تحديث PDPL. هل عندكم فرصة لمكالمة قصيرة الأسبوع القادم؟

  • LinkedIn

    connection + first DM

    Connection request copy plus follow-up message copy. State tracking — sent, accepted, replied, blocked. (PRD §27.2)

    Sample · connection note
    Connection note

    أبا فيصل، شغلكم في توسعة عمليات الفينتك خارج السعودية لافت. عندي ملاحظة موجزة عن متطلبات PDPL لغير المقيمين، أحب أشاركها لو يناسب.

  • WhatsApp

    opening + follow-up

    Sequence step type with copy generation, delivery and reply ingestion where available, opt-out handling. As a sequence channel, not autonomous. (PRD §28.1)

    Sample · opening message
    Opening message

    السلام عليكم أبا فيصل، معك سامي من RevXAI. أرسلنا قبل أيام عبر LinkedIn. لو تناسبك مكالمة ١٥ دقيقة عن فجوة PDPL، عندي رابط Cal.com جاهز.

  • Calendar booking

    Cal.com · Google · Outlook

    Meeting-booking prompt and CTA copy. Owners and routing rules defined per agent. Booked meetings terminate the sequence. (PRD §29)

    Sample · booking CTA
    Booking CTA

    احجز ١٥ دقيقة على التقويم — Cal.com — وسأحضر معي ملخص الفجوة كما رصدناها على ملفكم.

Sequence orchestration

One brief. Five steps. Four channels.

A V1 sequence has ordered steps, channel per step, delays, fallback logic, stop logic on reply or booking, and meeting-booked termination. (PRD §23.1)

  1. Day 0
    Email· Instantly

    PDPL angle opener. Subject + body in Arabic.

  2. Day 2
    LinkedIn· connection request

    Connection note tied to the email angle.

  3. Day 4
    LinkedIn· first DM after accept

    Follow-up DM with a content link.

  4. Day 7
    WhatsApp· via provider path

    Direct opening message — short, single ask.

  5. Day 10
    Calendar· Cal.com link

    Booking offer. Replied / booked terminates the sequence.

Readiness checks fire before the launch CTA

If anything's missing, you see exactly what to fix — instead of a launched-but-broken campaign. (PRD §23.4)

  • Company profile exists
  • Brief approved
  • Target list has sufficient valid contacts
  • At least one live channel configured
  • Sending and warmup readiness passed (Instantly)
  • Billing and package state valid
  • Email steps have a usable agent with a valid email binding
  • Data wallet sufficient for required actions
Reply-assist

Operator-reviewed. Never autonomous.

When a prospect replies, the inbox surfaces the thread with the profile, brief, and contact in context. RevXAI suggests one or more reply drafts in Arabic. The operator edits, sends, or discards. (PRD §24.3 + §36.5)

Prospect reply · Arabic
ف
أبو فيصل · CFO · فينتك الرياض

شكراً لرسالتك. عندنا فعلاً نقاش داخلي حول PDPL وغير المقيمين، لكن الأولوية الآن لإغلاق الربع. ممكن نتأخر شهر؟

AI-suggested drafts · review before send
  • Concise · accept timing

    تماماً، الإغلاق أولاً. أحجز لك مكالمة بداية الشهر القادم على Cal.com، وأرسل قبلها ملخصاً مختصراً عن الفجوة وكيف تتعامل بنوك مماثلة معها. هل ١٢ نوفمبر مناسب؟

  • Value-first · send asset now

    أحترم أولوية الربع. أرسل لك اليوم ملخص نصف صفحة عن خيارات معالجة غير المقيمين كما تتعامل معها بنوك ٥٠–٢٠٠ موظف، ونرتّب مكالمة بعد الإغلاق.

  • Champion path · find tech lead

    مفهوم. هل تقترح أبدأ النقاش مع المسؤول التقني عندكم بالتوازي، حتى لا نضيف على وقتك الآن؟

Per PRD §24.3 and §36.5, an operator action is required before any reply is sent. We do not ship autonomous reply.

Agents + bindings

Each channel binds to an agent identity.

An agent is the operator-facing unit you pay for: it has its own auth state, its own sending identity, its own deliverability profile. Add a LinkedIn agent to run LinkedIn steps. Add an email agent to run email steps. (PRD §26)

See agent pricing
Agent bindings
  • Email agent → mailbox + warmup readiness via Instantly
  • LinkedIn agent → authenticated LinkedIn account + invite quota
  • WhatsApp agent → WhatsApp number + provider connection
  • Calendar agent → owner identity + Cal.com / Google / Outlook link
Quality safeguards

What stops a campaign from sending into a wall.

Sending operations live with Instantly. RevXAI surfaces the gates so you do not launch into a poor mailbox. (PRD §24.2 + §25)

  • Warmup readiness

    Surfaces Instantly's mailbox readiness in-product. Steps gate on it.

  • Domain reputation guard

    Domains and subdomains tracked per agent. Reputation drift is visible before send.

  • Deliverability gate

    Send rates, bounce rates, and reply rates monitored per agent. Anomalies pause steps.

  • Per-account opt-out

    Opt-outs persist per workspace per channel. WhatsApp and email opt-outs are honored across sequences.

Draft an Arabic sequence in your first session.

Start free. Generate a profile, get a brief, draft a sequence — in under 20 minutes.