Skip to main content
Each prompt below is something you can paste into Rippit chat, or give to your own assistant with “use Rippit to” in front. Change the source, the schedule, and the destination to match your workspace. Rippit asks about anything it still needs, then builds the pipeline as a draft for you to test.

​
Enrich every record

Add the columns your source systems never recorded, on every row, and keep them filled as new rows arrive.
Once the columns exist, ask about them in chat (“which contact reason grew fastest this month?”), chart them on a canvas, or build the next pipeline on top of them.

​
Report and alert on a schedule

Anything you would want to know regularly, delivered where your team already works. Each prompt names a period that matches its schedule, so every run reports on its own window and nothing is repeated. Understand what support is dealing with
Watch revenue and churn risk These depend on what your workspace brings in. Sales call transcripts and account data open up the accounts and calls angle. With support conversations alone, stick to the sentiment and complaint versions.
Track what the product gets wrong
Notice that some prompts say what to do when nothing matches. That is the difference between a quiet week and a pipeline that silently stopped working.

​
Research the outside world

Bring in what your own data can’t tell you, and keep it current.
See External research for what each search method returns and which providers it can use.

​
Combine them

The steps compose, so one pipeline can carry a job from raw data to a finished action. Describe the whole job and Rippit works out the chain. Churn briefs for each account owner
What Rippit builds:
  1. AI columns on conversations: a churn-risk score and the reason behind it.
  2. A lookup that adds each conversation’s account owner and renewal date.
  3. A weekly rollup with one row per account, kept only when it has two or more high-risk conversations.
  4. An agent run on each of those rows that researches the company and writes the brief.
  5. An action that emails each brief to the account’s owner at 8am.
Issues from bug reports
The overview walks through one more: bug triage with account context.

Pipeline building blocks

What each kind of step can do.

Build, test, and run

Test safely, check the cost, and go live.