Botseon for sales

The promise

By the end of this guide a bot has researched a prospect from public pages and written you a short summary, a second bot has found the deals that went quiet and drafted a follow-up for each, and nothing has been sent to anyone until you approved it.

Who this is for

A salesperson or a founder who sells. One person is enough. Start with the researcher; add the pipeline bot once you have a pipeline board or deal file for it to read.

Set up

Sign in and create a bot from Prospect Researcher. It reads public web pages and what is already on file, so connect the storage or notes tool where your prospect files live from Plugins, and read the scopes before you agree. The bot uses your connection, never a copy of your credentials. New to Botseon? Botseon 101 covers the first ten minutes.

The jobs

Research a prospect

Prospect Researcher reads public pages about a company and what you already have on it, and writes a short research summary for you to review before any outreach goes out. It has no schedule: you hand it a name.

Read the first summary against what you already know about the account. A summary is only as good as the pages the bot could reach, and a claim with no page behind it is worth checking before you rely on it.

Chase the pipeline

Pipeline Chaser runs every Monday. It reads the pipeline board for deals with no activity in two weeks, updates the deal file with the last known status, and drafts a follow-up for each stalled deal.

Approve every follow-up

This job is yours. The bot drafts; sending a follow-up email stops at a card with the draft, the resource and the reason. You have three answers: "Allow once", "Always allow" and "Deny". Whether a follow-up fits the relationship, and whether this is the week to send it, is a judgement the bot cannot make for you.

Now let it run

The pipeline job is already a weekly clock. Open Routines in the bot's details pane, choose "+ Add trigger", then "On a schedule", and pick a preset such as "Every week" so the chase is waiting on Monday morning. Use "Test run" once before the first scheduled one, and know that a test run does the real work and costs the same.

What the bot may not do

Sending a follow-up carries the external_send permission tag and stops at a card. Updating the deal file and drafting the summary carry write, and reading carries read. The four tags whose always-allow rule is never honoured, spend, sign_in, delete and decides_about_person, appear in neither job. Neither bot uses a computer.

Where your data is

Prospect files and the pipeline board are read and written through your own connection. On the managed service everything the bots read and store follows the same rule as the rest of the product: EU/EEA storage, no non-EEA egress by default, US sub-processors under SCCs. The full position is on the data residency and rights page.

What can go wrong

      allowOnce: 'Allow once',

      firstSeen: 'First time this bot has acted on this.',

      alwaysAllow: 'Always allow',

Do it yourself in 10 minutes

1. Create a bot from Prospect Researcher and connect where your prospect files live.
2. Read the scopes before you agree.
3. Give it one company name and read the summary it drafts.
4. Create a second bot from Pipeline Chaser and point it at your pipeline board and deal file.
5. Run it once by hand and read the job-reply moment on the desktop and on a phone.
6. When a follow-up card appears, read the draft and answer it yourself.
7. Open Routines and read the routine-editor moment on the desktop and on a phone.
8. Add a weekly schedule and use "Test run" once.
9. Let one Monday run go by and read the transcript.

Read next