Agent

Personalised outbound drafting

Personalisation usually stops at the first name. This agent researches each account against the reason you think they need you, then drafts an email or a sequence that refers to something true and specific, using messaging your team has already agreed. A rep edits and sends. Nothing goes out without a person reading it.

How it runs

Step by step

01

Load the approved messaging

We connect your positioning, proof points and the phrases legal and marketing have signed off.

02

Research the account first

The agent gathers what your allowed sources say about the account and the person, recording where each fact came from.

03

Choose the angle to write

It selects the reason to write from your list of use cases, rather than inventing a rationale to fit the research.

04

Draft the message and follow-ups

The email is written in your team's register, kept short, with the personal detail cited so a rep can check it.

05

Mark anything it cannot confirm

Facts the agent could not verify are flagged in the draft instead of being smoothed into the prose.

06

The rep edits and sends

Drafts land in the rep's mailbox. The agent does not send, and it does not enrol anyone in a sequence.

The harness

Exactly what this agent can see, touch and change

The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.

Context

What reaches the model

Teams selling into named accounts where a generic sequence gets ignored, and where reps spend more of the day researching than writing.

Escalation

When it asks a person

The rep edits and sends every message; the agent never sends

Applications & Rights

Which tools it uses, and what it may do in each
NotionRead only
Google DriveRead only
ZapierRead only
GmailReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.

Who it’s for

Teams selling into named accounts where a generic sequence gets ignored, and where reps spend more of the day researching than writing.

What you’ll need

  • Approved messaging and proof points
  • Agreed research sources
  • Mailbox connected for drafts
  • A rep who sends every message

What you get

  • A per-account research note with sources
  • A drafted first message and follow-ups
  • A list of claims the agent could not verify

What it doesn’t do

It writes drafts and stops. It does not send, schedule or enrol contacts in sequences, and it will not make a claim about a prospect that it cannot show you the source for.

How you get it

We build the first one with you

Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

Co-build

Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Manual account research before outreachTemplated merge-field personalisationRep-by-rep messaging drift
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

Will this get us marked as spam?

That depends on your volumes and your consent position, which are your decisions rather than the agent's. What it changes is quality: a rep sends fewer, better messages because the research is already done. It will not enrol anyone or send on its own.

How do we keep it on-message?

It writes from your approved positioning rather than general knowledge of your category, and the co-build session is largely about loading that material. When marketing changes the messaging, the drafts change with it.

Can it write in a rep's own voice?

To a degree. We can tune the register per rep from their sent mail, with their agreement. Most teams find one house voice with room to edit is easier to keep on-brand.

What about follow-ups?

It drafts the sequence, follow-ups included, and updates them when something changes at the account. Sending stays manual, so a deal that has moved on does not keep receiving a sequence written before it moved.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.