finnUse cases
From new lead to booked meeting: an AI sales workflow.
See an AI inbound sales journey from a prospect’s first question to qualification, calendar booking, CRM updates, and a useful handoff to your team.
“We manage three properties. Can your service cover all of them, and can someone walk me through the setup?” A lead has arrived with a requirement and a question. The following illustrative workflow shows how Finn can connect that first exchange to approved information, the right salesperson, and a confirmed meeting. It is a workflow example, not a customer performance claim.
Start with the question and the current record.
Identify the channel and check whether the person already has a customer or prospect record. Use only information available to the workflow with the appropriate permissions. Preserve what the prospect has already told you: three properties, a need for coverage, and an interest in understanding setup. Do not ask for the same details again simply because a form has empty fields.
Check the current product and service information before answering. If coverage depends on location, property type, or account setup, explain that dependency and ask for the relevant missing detail. Keep unverified assumptions separate from facts in the prospect record.
Answer before turning the exchange into an interview.
A qualification process should help the buyer reach a relevant next step. Answer what can be answered from approved information, then ask the smallest useful set of questions. For this inquiry, location and the kind of setup may matter more than an exhaustive profile. Give a reason when a detail is needed.
OpenAI’s inbound-sales example describes providing relevant answers and transferring appropriate conversations to representatives with context. This journey applies that pattern to a service business. It does not assume that another company’s accuracy, response time, or revenue results will transfer to Finn.
Choose the next owner and next step.
Apply the business’s routing rules: territory, service expertise, existing account ownership, or availability. A qualified inquiry might move to a demonstration; an unusual requirement might first need a specialist review. A current customer seeking help should reach the service team rather than restart as a new sales lead.
Keep a named owner even when scheduling is not possible immediately. A calendar link can be useful, but dropping one into a conversation should not erase the team’s responsibility to answer an unresolved question.
| Inquiry state | Next action | Recorded result |
|---|---|---|
| Standard fit; ready to meet | Offer eligible calendar slots | Confirmed meeting and owner |
| Missing a necessary detail | Ask a focused question | Open inquiry with the missing field identified |
| Unusual requirement | Request specialist review | Assigned review with context |
| Existing service problem | Route to support | A service owner and linked conversation |
Book against current availability.
Read the correct calendar, meeting duration, timezone, and scheduling rules. Offer times that satisfy those rules. When the prospect selects a time, recheck it before creating the event. Another booking may have arrived during the conversation. If the slot is gone, explain the change and offer current alternatives.
Verify that the event was saved with the intended participants and meeting details. Then send the permitted confirmation. Keep a distinction between an event created and a confirmation delivered. If delivery fails, show the remaining work to the owner rather than telling everyone the entire job is complete.
Give the salesperson a useful starting point.
Save the buyer’s need, relevant account details, questions answered, sources used, outstanding questions, meeting time, and next owner. Identify any commitment made during the exchange. The handoff should make preparation easier without burying the salesperson in an unfiltered transcript.
In Finn, the customer conversation and the employee’s next step can remain connected through the workspace, email, or team channels. If the requirement changes before the meeting, update the record and alert the owner where appropriate. Continuity is valuable when it keeps the current need clear.
Measure progression and the quality of the handoff.
Track eligible inquiries, useful answers, meetings booked, meetings attended, time to the next step, and employee corrections. Record cases that could not be booked and why. A positive reply is not a meeting, and a meeting is not revenue. Keep each stage connected to its actual business record.
Test an existing account, a duplicate inquiry, a timezone misunderstanding, unavailable calendar access, a canceled meeting, and a request for an unapproved commitment. Start with one route and a team that can review the exchanges. Expand when the results and the remaining employee work are understood.
Common questions
What systems does an inbound sales agent need?
Typically it needs approved product information, relevant prospect records, routing rules, calendar access, and permitted communication channels. The exact access depends on the actions included.
When is an AI-booked meeting complete?
The intended event is saved, the correct owner and participants are recorded, and the confirmation step has succeeded or any delivery problem has an assigned owner.
Should AI qualify every lead the same way?
No. Collect information needed for the next decision. Existing customers, standard inquiries, and unusual requirements often need different routes.