Getting Started with
Lumver Capture

Note. This page describes how a Lumver Capture setup is structured. Configuration is currently done together with us during onboarding rather than through a self-serve dashboard. Request a demo to get started.

What is Lumver Capture?

Lumver Capture is a system for handling customer inquiries. It watches the channels a business uses, records every inquiry that arrives, works out what is being asked, and passes an organized version to the right person.

It is not a chatbot placed in front of your customers, and it is not a replacement for your team. It is the layer that makes sure an inquiry is never sitting somewhere unnoticed, and that whoever handles it has the context ready.

How it works

Every inquiry moves through the same sequence:

• Capture — the inquiry is recorded with its channel, sender, timestamp and content.
• Understand — the message is read to determine what is actually being asked.
• Qualify — the inquiry is classified against rules you define, such as intent or urgency.
• Organize — the details are turned into a structured record rather than a raw thread.
• Notify — the right person is told, with the context attached.

Your first setup

A first configuration usually takes one working session. The sequence is the same regardless of which channel you start with.

1. Choose a customer inquiry source Start with one channel — ideally the busiest, or the one where inquiries are most often missed. Adding a second channel later is straightforward; starting with four at once is not.
2. Connect the source to the system The connection method depends on the channel. Some connect through an official platform integration, others through a form endpoint or a forwarding rule. We handle this step with you during onboarding.
3. Define the information that should be captured Decide what you need to know about every inquiry. Usually this is the contact's name, how to reach them, what they are asking about, and any detail specific to your business — a date, a location, a product, a budget range.
4. Configure qualification logic Set the rules for sorting inquiries. This can be as simple as separating genuine inquiries from routine questions, or more detailed if your team handles different categories of work. Keep the first version simple; refine it once you have seen real inquiries pass through.
5. Choose where notifications should be sent Decide who is told, and where. This might be an email address, a messaging channel, or a shared destination the whole team watches. Where possible, name a person per category rather than notifying everyone about everything.
6. Test the workflow Send several inquiries through the connected channel yourself, including an awkward one. Confirm that each is captured, classified sensibly, and delivered to the right place. Adjust the qualification rules based on what you see.
7. Go live Turn the workflow on for real traffic. Review the first week closely — early inquiries are the best material for refining rules, and it is normal for the initial configuration to need adjustment.

After going live

Two habits make the difference in the first month. Check that notifications are reaching a person who acts on them, not an inbox nobody owns. And review the inquiries that were classified incorrectly — those are where the rules need work.

If you have not yet mapped your existing process, the Customer Inquiry Audit is a useful thing to do before configuring anything.