finnCustomer operations
The work starts after the answer.
A helpful reply is a beginning. Here’s how to design the work that comes next, across customers, teams, and company software.
“Can you send me a quote for 200 custom pieces?” It sounds like one question. Behind it are product details, pricing, delivery dates, and someone who can approve the deal. The customer should not have to manage all of that.
Write down what “done” means.
For this illustrative wholesale order, the goal is an approved quote saved against the right customer and delivered to the right person. A friendly explanation of wholesale pricing does not finish that job. Neither does a draft that nobody knows is waiting for review.
Define the result before you design the conversation. Which record changes? Who needs to decide? What should the customer receive? These questions make a vague promise of automation into something a team can test.
Keep the customer and the team in the same story.
The customer may start in email while the account manager works in Slack. Finn’s customer and employee agents serve both sides of that exchange. The useful handoff includes the request, the proposed quote, the pricing source, and the decision required. The employee should not need to interview the customer again.
Approval needs to refer to the exact proposal. If the quantity or discount changes afterward, the earlier approval is no longer enough. The customer conversation can stay simple even when the work behind it requires care.
Check the result before announcing it.
Suppose the quote saves successfully but the email service rejects the recipient. The correct status is “quote saved; delivery needs attention.” Calling the entire job complete would hide the one step that still matters to the customer.
The same distinction applies to a hotel’s late-checkout request or a property repair. A message to housekeeping is not a confirmed room release. A contractor assignment is not a completed repair. Each business decides which recorded result closes the job.
Start with the handoff you repeat every day.
Choose a familiar request, connect the records it needs, and make the approval step clear. In Finn, that means giving the agent the right knowledge and permitted actions, then testing the journey from both the customer’s and employee’s perspective.
A useful test includes an ordinary request, a missing detail, a rejected approval, and a failed action. You should be able to see what happened and who owns the next step in every case. That is a better foundation for growth than a perfect opening reply.