Agent

Website visitor & enquiry follow-up

Inbound enquiries wait while someone works out whether they matter. This agent researches each enquiry, demo request and waitlist sign-up against your criteria, writes a short qualification note with the evidence, drafts a reply and recommends who should own it. A person still decides and sends.

How it runs

Step by step

01

Agree the criteria and routes

ICP rules, disqualifiers and the routing map, such as enterprise, self-serve or not a fit, are written down together.

02

Take the enquiry as it arrives

Form submissions, demo requests and waitlist sign-ups reach the agent through your existing automation.

03

Research the organisation and the person

Approved sources are used to establish who this is, with each fact linked to where it was found.

04

Qualify against the written criteria

The note says which criteria are met, which failed and which could not be established, rather than producing a bare score.

05

Draft the reply and the route

A response is drafted in your tone, with a recommended owner and the reason for that routing.

06

A person sends and routes it

Nothing is sent to the enquirer and no record is created until someone accepts the recommendation.

The harness

Exactly what this agent can see, touch and change

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

Context

What reaches the model

Marketing and demand generation teams handling a mixed inbound flow, where genuine enterprise enquiries sit alongside noise and everything waits for the same manual triage.

Escalation

When it asks a person

A person approves the reply and the routing before anything is sent or recorded

Applications & Rights

Which tools it uses, and what it may do in each
NotionRead only
Google DriveRead only
SlackRead only
GmailWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.
ZapierReadWrites 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

Marketing and demand generation teams handling a mixed inbound flow, where genuine enterprise enquiries sit alongside noise and everything waits for the same manual triage.

What you’ll need

  • Enquiry forms feeding into a connected system
  • Written ICP and disqualifier rules
  • A routing map with named owners
  • An approver before replies are sent

What you get

  • A qualification note with evidence per enquiry
  • A drafted first reply
  • A routing recommendation with the reason

What it doesn’t do

It qualifies from what the enquirer told you and what approved sources say. It cannot see budget or intent, so the note names what it could not establish, and it never replies on its own.

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 inbound triageLead scoring nobody can explainDelayed first responses to enquiries
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

How quickly does an enquiry get a reply?

The draft is ready as soon as the research finishes; the reply goes when your approver sends it. Teams that keep an approver close to the queue get a fast, personal response, which is the point of doing the research at all.

Can it reply automatically for obvious cases?

Some teams enable it for a narrow, clearly defined case such as an existing customer asking for support. We would rather start with everything gated and open it up once you trust the qualification notes.

What about enquiries from personal email addresses?

They are flagged as unverifiable rather than dismissed. A good enquiry from a personal address is common, and a rule that bins them all costs more than the noise it removes.

Does it replace our scoring model?

It replaces the part nobody can explain. Instead of a score you get the criteria met, the criteria failed and the evidence, which is easier to argue with and easier to improve.

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.

Website visitor & enquiry follow-up | ollo