A chatbot answers questions. Workup Agent qualifies the person asking.
It greets every visitor the second they land, holds a real conversation by text or voice, asks the questions your intake team would ask, and hands you a finished file on someone worth your time. At three in the morning, on a Sunday, in whatever language they opened with.
The problem, named plainly
You are not losing leads. You are losing the race to answer them.
Someone in pain, or someone with a budget, fills in a form at 9:40pm. Your team sees it at 8:15 the next morning. By then they have filled in three more forms, and whoever called back first is already talking to them.
The firm that responds first usually wins the client. Not the best firm, the fastest one. That is unfair, and it is how the market actually behaves.
Every enquiry gets the same questions, in the same order, with nothing skipped because it was late or the phone was ringing.
What reaches your team is a person who has already been through the questions, not a name and a number to start from scratch on.
What it does
Six things, and it does all of them without you there
Qualifies properly
Runs your real qualification criteria, not a generic form. Branching questions that adapt to the answers, so an auto collision and a workplace injury go down different paths and both arrive complete.
Talks out loud
Natural voice conversation, not a phone tree. People who will not type three paragraphs about what happened to them will happily say it, and someone with a broken wrist cannot type at all.
Watches who is on your site
Sees the pages a visitor read, how long they stayed, where they came from and what they looked at twice, then opens the conversation already knowing what they care about.
Routes to the right desk
Sends each finished file to the right person or team by practice area, service line, territory or whatever rule you set, and pages someone when it is genuinely urgent.
Hands over a built file
Not a transcript. A structured record with the facts, the dates, the documents requested and the consent trail, in your system, ready to act on.
Lands in your stack
Writes into Salesforce, Litify and the case and CRM systems your team already lives in, so nobody has to re-key anything or learn another inbox.
How a conversation runs
Greet, Qualify, Verify, Route, Brief
Five stages, every time, whether it took ninety seconds or twenty minutes.
Greet
Opens the moment someone lands, in context, referencing what they were reading rather than asking what brought them here.
Qualify
Works through your criteria conversationally. Branches on the answers. Never skips a required field because the conversation wandered.
Verify
Confirms the details that matter, captures consent with a full evidentiary record, and flags anything that needs a human immediately.
Route
Applies your rules and delivers to the right owner. Urgent files page. Everything else queues in priority order.
Brief
Writes the file into your system with a short human summary on top, so the first person to open it already knows the story.
Two jobs, one agent
The same engine, pointed at whoever walks in
A law firm needs intake. A services business needs a first line sales rep. Underneath, both are the same problem: qualify the person in front of you, fast, and hand the right ones to a human.
For law firms
A 24/7 intake agent
Every enquiry worked up before anyone in the firm has looked at it.
- Runs your intake questionnaire for personal injury, workers compensation, mass tort or whatever you practise, with the branching a real intake specialist would use.
- Catches the deadline risks your night staff miss, and marks the file urgent when the clock is the problem.
- Captures consent properly, with the exact text, version, timestamp and device details preserved as evidence.
- Stops where it should. It gives no legal advice, does not evaluate anyone's claim, and says so plainly.
For service teams
A first line sales rep
Every enquiry scoped and scored before it reaches a person who costs money.
- Scopes the work the way your best rep does: platform, size, timeline, budget range, who actually decides, and what has already been tried.
- Separates the real from the curious so your senior people spend their hours on the enquiries that can close.
- Books the meeting against live calendars while the prospect is still interested, instead of starting a week of email tag.
- Answers the technical question that would otherwise have needed a solutions engineer on a discovery call.
Voice
Most people would rather talk than type
Especially the ones worth talking to. Someone describing a car accident, a workplace injury or a complicated project will say in forty seconds what they would never write out. Workup takes the call, holds the thread, and asks the follow up question a form cannot.
- Answers inbound calls and web voice, and can call back on request
- Handles interruptions, corrections and people who talk over it
- Switches to text mid conversation when someone would rather type
- Every call transcribed, structured into the same file as a chat
- Says it is an automated assistant up front, every time
Visitor intelligence
It knows why they are there before it says hello
A visitor who read your workers compensation page three times and came from a search about reporting deadlines is not a general enquiry. Workup sees the whole visit and opens accordingly, instead of asking a question the person has already answered with their behaviour.
- Full session path, referrer, search terms where available, and dwell time per page
- Returning visitors recognised across sessions
- Intent signals surfaced to your team on the file, not just in an analytics dashboard
- Anonymous until the visitor identifies themselves, and only ever with consent
The handoff
What actually lands on someone's desk
This is the part that decides whether the tool was worth buying. A transcript is not a deliverable. A workup is.
In the file
- A short written summary a human can read in twenty seconds
- Every answer, structured into your fields, not free text
- Dates, deadlines and anything computed from them
- Flags for what needs attention now and why
- Documents requested, and which ones arrived
- The consent record with text, version, timestamp, IP and device
- Full transcript, attached rather than pasted
Where it goes
- Into Salesforce, Litify or your case management system as a real record
- Into your CRM as a scored, owned opportunity
- To the right person by your routing rules
- Paged to a human when the file is urgent
- Mirrored to email for anyone who prefers it
Say it plainly
Why this is not a chatbot
The word has been worn out by ten years of deflection widgets whose job was to stop you reaching a person. This does the opposite job.
| A support chatbot | Workup Agent |
|---|---|
| Exists to deflect contact and reduce tickets | Exists to capture contact and create qualified opportunities |
| Answers the visitor's questions | Asks the questions your team needs answered |
| Follows a decision tree someone drew | Holds a real conversation and adapts to what it hears |
| Hands over a transcript | Hands over a structured, routed, consented file |
| Text in a widget | Text or natural voice, whichever the person prefers |
| Knows nothing about the visitor | Knows what they read, searched and returned for |
| Measured on containment | Measured on qualified files and booked meetings |
Everything it says is bounded by rules you set, and in regulated work those boundaries are the product. It gives no advice it is not permitted to give, and it tells people plainly that it is automated.
Put it in front of your next visitor
A walkthrough takes about thirty minutes. We will run it against your own intake questions and your own site, so you are looking at your business rather than a canned demo.