Workflows
Let’s suppose that Acme is an online e-commerce company selling homeware goods to customers across Australia. Most of their support questions cluster around one of three requests: Where is my order, How do I change my delivery address, and What is my refund status. When Acme started on Lorikeet, their team built three workflows to handle each of the three requests, plus an FAQ workflow to answer remaining questions from their knowledge base. When a new message landed in Acme’s support desk, Lorikeet’s first job was to figure out which workflow should handle the task. We called this topic matching, and it had two steps: First, topic detection would read the incoming message and summarise what the customer was asking about. Then, workflow matching would try and choose the most applicable workflow by comparing this summary with each of their descriptions. If nothing matched, the conversation would typically fall back to a catch-all FAQ workflow to handle everything else. This works well when a customer’s request is clearly stated in their first message:





Concierges
What if Acme moved their support over to a concierge? During migration, their three workflows became skills: one for refunds, one for address changes and one for order tracking. Instructions that were common to each workflow found their new home inside the concierge prompt. This included their style guidelines, how Acme support greeted customers, when to hand off to their team, access to their knowledge base, and other rules about their business and what not to say. With concierges, there is no topic matching that runs at the start of every conversation. Instead, the concierge takes on the ticket directly, works out what the customer needs, and loads the skills it needs to help. Once a skill is loaded, it stays loaded for the rest of the ticket, and the concierge can keep bringing in more as the conversation moves. So what happens to our two difficult tickets? Here’s a customer who opens with something vague, and then asking about a refund and an address change in the same message:

Comparing them side-by-side
Here’s how a single message moves through the two agent architectures:

- Tools are the actions Lorikeet takes in your systems: look up an order, issue a refund, update an address. Both concierges and skills can reference the same tools that your workflows did, so everything you’ve built comes with you. Mention a tool in the skill that uses it, or in the concierge’s prompt if any conversation might benefit from it.
- Message checks screen every customer message before Lorikeet replies. Keep them for the few things that must be caught on the way in, such as messages with regulatory or compliance implications.
- Triage workflows are structured workflows that run once per ticket, on the first message, before Lorikeet replies. Keep them for fixed checks that must route a ticket up front, such as handing off every message from a flagged account.
- Guardrails check every reply before your customer sees it. A guardrail can steer the concierge to rewrite its intended reply, escalate a ticket to your team, or raise an alert.
What goes where?
With concierges, you can configure overarching instructions that apply to every conversation. This provides a natural home for global rules that your conversations need to follow. However, message checks and guardrails are also a place where you can implement these global rules. How should you decide what goes where? Let’s suppose that, before migrating over to concierges, Acme had a total of five message checks and guardrails:- Guardrail: Never promise a specific date that a customer’s refund will arrive by.
- Guardrail: Never use em-dashes or emojis in your reply.
- Message check: Questions about bulk orders are sent to our sales team.
- Message check: Escalate the conversation if a customer threatens legal action
- Message check: Escalate the conversation if the customer asks for a human
During and after your move
Each ticket runs on workflows or on Concierge 2, never a mix of both.- During the rollout, Lorikeet moves a growing share of new tickets to Concierge 2. A ticket stays on whichever one it started on.
- After your move, every new ticket goes to your concierge.
Related
- : where each part of your setup went
- Concierge 2 FAQ
- : where each kind of rule goes
- : how a concierge resolves or hands off a conversation