AI sales assistant. Reads, scores, writes the reply.
Every lead from your site forms is scored and answered in your own language. The draft is waiting before your rep opens the thread, and the rep is the one who sends it.
On requestUsed on our own brands; built for your company on request. The role that answers web chat and email itself is the AI inbound sales manager.
What it does
Inbound qualification
Every form fill lands as one record and is scored against the three questions that decide fit.
Draft-first replies
The answer is written in your approved language before a rep opens the lead, and it waits for them to send it.
Handoff with context
The rep gets the draft, the score and the reason in one place, so nothing is retyped and nothing is guessed at.
Nothing invented
A price or a promise the assistant was never given comes back marked as pending you, with the gap named.
How it works
Capture
A lead fills the form and the record lands with an email to you.
Qualify
The lead is scored against your ICP and your three fit questions.
Draft
The first reply is written and waits in the queue, price claims flagged.
Send
A rep reads the draft, sends it, and takes the conversation from there.
0
Messages that leave without a person on the send
24/7
Inbound form leads accepted, weekends included
3
Fit questions every lead is scored against
1
Record per lead, with the form answers and where it came from
What the first week changes
The wait between a lead arriving and an answer being ready shrinks to the time it takes a rep to read the draft. The rep still decides what goes out.
Every run is written to the journal with its inputs and its outcome, failures included, so a week of work can be read back rather than reconstructed from memory.
Evidence · AI SDR
What it is built on
The pieces of the platform this role is built on, each marked with the site's three words: Live works in the product today, On request is built with you during a setup, Planned is on the roadmap.
Live
Any form on your site can post a lead into one record
The intake endpoint runs in production on our own sites today. It caps the request body before parsing it, absorbs bot submissions on a hidden field without writing anything, and stores the lead in Postgres. A submission that fails validation gets a reason back instead of a silent success. For your site, the form is connected during an on-request setup.
On request
The reply is written ahead of the rep, and the rep sends it
Speed to first contact comes from having the answer ready, so the draft is composed before anyone opens the lead. The role has no send path of its own. The phone number, the email address and the full name stay out of the prompt — it works from an initial and the answers on the form.
Planned
CRM and calendar connections are planned
No CRM, calendar or sequencer connector ships today. Until one does, the rep works from the lead record and the email. We name the connectors we have built and leave the logo wall to someone else.
The gates behind the drafts — approvals, spend caps, the kill switch — are listed on the product page.
Frequently asked questions
Every send, every call and every negotiation. It scores the lead and drafts the first reply; a rep decides what goes out.
You brief it in plain language. It scores leads against your rules and escalates edge cases.
None today; CRM sync is planned. Leads arrive as one record with an email to you, from any form that posts to the lead endpoint. We would rather say that than print a logo wall.
The record is stored and you get an email. The assistant scores the lead against your criteria and writes the first reply, so the answer is waiting when a rep opens it.
A hard rule in the role: any price it was not given has to carry a pending-owner marker, and a draft that states a number without one is rejected before you ever see it.
It flags the lead instead of drafting a routine reply, and hands over the answers, the score and the reason behind it. Your rep picks up with the context already assembled.
No. Unistaff pricing is per AI employee per month. There are no per-message, per-minute, or per-lead surprise charges.