StoryOS

Agents · For sales

Lead Triage & Follow-up

New lead in → enriched, scored, routed — with the first reply drafted for your approval.

A sales pipeline board in StoryOS with opportunities in columns

Triage feeds the pipeline: routed leads arrive in the right column with the follow-up drafted.

Trigger

A record is created — from a form submission, an import, or the API.

MCP tools it uses

get_recordupdate_recordquery_recordslink_recordsadd_commentrun_button

Reads

  • The inbound lead record: source, company, message
  • Your accounts database, to catch existing relationships
  • Your routing rules — owners by territory or specialty, stored as data

Writes

  • Score, segment and owner onto the lead record
  • A relation to the matching account, if one exists
  • A drafted first reply as a comment, waiting for approval

Human checkpoints

  • The first reply is always approved by a human before it goes out
  • Disqualification is proposed with a reason, never silent

The loop, step by step

1

A lead lands

The form submission becomes a structured record, and record-created fires the agent.

2

It enriches and scores

It cross-references your accounts, fills the missing fields it can justify, and scores against the criteria you keep as workspace data.

3

It routes

The right owner is assigned by your rules; the lead appears in their queue view immediately.

4

It drafts the follow-up

A first reply tailored to the source and segment waits as a comment. You approve; it moves to “Contacted”.

Runs on the AI you already have

This loop runs today with your own Claude or ChatGPT connected over MCP — you drive it assistively, or wire the trigger with an automation. StoryOS never meters or marks up your own AI, on any plan. No AI subscription? The optional StoryOS AI add-on covers you at near-cost credits.

Templates this agent works well with

Run Lead Triage & Follow-up on your data.

Start free — 30 days of Pro, no card. Your own AI is never metered.