RaabtaHQ

Sales & pipeline

The deals nobody followed up

Found every Monday, chased with your approval

Nobody decides to abandon a deal. It just stops being the most urgent thing, fourteen times in a row, and then it is too late to message without it being strange.

  • Finds what has gone quiet, by your definition of quiet
  • Writes a follow-up that refers to the actual conversation
  • You approve each one — or approve the batch
  • Notes what it sent, so the next chase is not identical

Today

A pipeline where a third of the value has not been touched in three weeks, and nobody can face starting.

With this running

A Monday-morning queue of ready-to-send follow-ups, each one specific to that deal, that takes ten minutes to approve.

RaabtaHQ — Inbox · Ayesha K.
The dress arrived damaged. Can I get a refund?
I'm sorry about that — let me check this with the team and come straight back to you.
That's approved — I've refunded PKR 4,500 to your original payment method. It should land within 3 working days.
Approved by SanaRefund issued

It asked, it waited, and it said so meanwhile

Silence is never read as approval, in either direction

Step by step

What actually happens

  1. Assistant

    Wakes on a schedule — nobody asked it to — and plans out the steps it intends to take.

  2. Assistant

    Reads the pipeline, finds nine deals untouched for fourteen days, and reads the last exchange on each.

  3. Assistant

    Drafts nine different messages, each referring to what was actually discussed, and stops.

  4. Your team

    Approves seven, edits one, rejects one — from a phone, over coffee.

  5. Assistant

    Sends the approved ones, notes each on the deal, and updates what it saw.

01 / 02

It reads the conversation before it writes

A follow-up that says “just checking in” is worse than none, because it tells the customer nobody remembers them. This reads the last exchange on the deal first, so the message refers to the thing that was actually being discussed — the quote, the date they said they would decide, the question they left unanswered.

02 / 02

Nothing leaves without you

Outbound sales messages are the clearest case for an approval gate: the cost of one bad message is your name, and the cost of waiting an hour is nothing. So the sending action is gated. The assistant does all the work, then stops with everything ready and waits. If nobody answers, the requests expire — they are never sent on a silence.

  • Each message reviewable on its own, with the deal in front of you
  • Edit before approving, and it sends what you wrote
  • Reject one without stopping the rest
  • An unanswered request expires rather than proceeding

How this is put together

The same building blocks every assistant is made of. Nothing here is bespoke to this scenario.

What starts it

A scheduleEvery Monday at 09:00, in your timezone

Where it runs

WhatsAppFacebook MessengerInstagram DM

What it can do

  • Checked the time
  • Checked the pipelines
  • Looked through the deals
  • Looked up a deal
  • Looked up the contact
  • Read the notes on the contact
  • Planned out the steps
  • Replied— needs your approval
  • Added a note
  • Updated the deal

What it uses

Approval gatesYour instructions libraryLong-term memory

Every action above is a real capability, and every run keeps a record of which ones it used. How the engine holds this together →

More like this

Other things it does

Browse the whole library

Would this work for how you actually operate?

Tell us the scenario you have in mind. If it needs a building block we do not have, we would rather say so than sell you a demo.