RaabtaHQ

Sales & pipeline

When a deal is won, the handover starts itself

The welcome, the note and the next step, on the drag

The gap between winning and onboarding is where new customers form their opinion, and it is almost always the least designed part of the process because the person who won them has moved to the next deal.

  • Starts on the stage change itself, not a nightly sweep
  • Welcomes, sets expectations and offers the first date
  • Retags the contact so segments stay accurate
  • Works on any stage, not just Won

Today

A won deal, a quiet week, and a customer wondering whether anything is happening.

With this running

A welcome inside a minute of the card moving, with the first appointment already on offer.

Step by step

What actually happens

  1. Your team

    Drags the deal from Negotiation to Won.

  2. Assistant

    Wakes on the stage change, reads the deal and the contact.

  3. Assistant

    Sends the welcome, offers the first available onboarding slot, and swaps the prospect tag for a customer one.

  4. Assistant

    Leaves an internal note so whoever picks this up knows what was promised.

01 / 02

It reacts to the board, wherever the board is dragged

The stage change fires the same way whether the card was moved in the app, by a colleague on their phone, or by another system — because the event comes from the data changing rather than from the screen it changed on. There is no path that bypasses it.

02 / 02

Any stage, not just the happy one

The same trigger handles a deal moving backwards. A card dropping from Negotiation to Qualified can quietly retag the contact and note why, so the segment you broadcast to next month is not full of people who already said no.

How this is put together

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

What starts it

Something changing in your CRMA deal moves to a new pipeline stage

Where it runs

WhatsAppFacebook MessengerInstagram DM

What it can do

  • Looked up a deal
  • Looked up the contact
  • Tagged the contact
  • Removed a tag from the contact
  • Added a note
  • Checked the booking types
  • Checked what times are free
  • Replied
  • Checked who is on the team

What it uses

Your instructions libraryInstant hand-off

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.