Admin Manual

How Lukriton
Works.

This is the admin manual for the real Lukriton workflow: AI Voice Intake & Routing OS setup, website widget deployment, hosted Lukriton pages, request intelligence, translation, request statuses, service network routing, optional provider-choice routing, customer tracking, recipient history, and what to do when a request needs follow-up. Lukriton comes ready with the admin dashboard, notifications, routing rules, invites, suggested-provider outreach, and follow-up tools already in place. You customize entry points, prompts, recipients, departments, routing, tracking, and alerts. People say what they need without an account, Lukriton organizes the request, and the admin can notify, route, track, accept, complete, or keep working the request.

Deploy OS View Pricing

Four configurations

OS, deployment,
service network routing.

The operating system is already assembled. You choose the configuration and customize only what matters for your website widget, hosted Lukriton page, service network, or provider-choice routing.

AI Voice Intake & Routing OS

Core platform

The operating layer that captures spoken demand, structures it, translates it, prioritizes it, routes it, and keeps follow-up trackable.

Website widget or hosted page

Website, QR, page

Deploy the OS on an existing website as a widget, or use a hosted Lukriton page. QR codes and direct links feed the same dashboard, translation, summary, priority, and follow-up controls.

Service network routing

Operational routing

For cities, chambers, BIDs, agencies, businesses, associations, schools, and organizations routing requests to approved staff, departments, vendors, members, desks, or providers.

Provider-choice routing

Optional responder mode

For networks where customers can choose how many approved providers may contact them while contact details stay protected until acceptance rules are met.

The basic flow

From voice request
to routed follow-up.

The same ready OS works through a website widget, hosted Lukriton page, QR code, direct link, service network, or provider-choice workflow. People tap the mic, Lukriton prepares the intake, and the network admin decides whether to receive, assign, route, or track it.

Launch the OS

Start with the AI Voice Intake & Routing OS, then choose website widget, hosted Lukriton page, service network, or optional provider-choice routing. The request flow, dashboard, translation, priority, tracking controls, and routing tools are already included.

Deploy entry points

Deploy Lukriton wherever people already look for help: existing website widget, hosted Lukriton page, QR code, direct link, storefront, flyer, social page, email, group, or printed material.

People tap and talk

The requester taps the mic, says what they need naturally in any language, and can add contact details for updates. No requester account is required.

AI prepares the intake

Lukriton transcribes, detects language, translates when needed, summarizes, classifies the request, and flags urgency so the network admin receives a clean intake record.

Notify or route

A simple OS launch can notify the admin directly. A service network can use the built-in routing engine to send requests to approved staff, departments, vendors, members, desks, or providers.

Track and manage

The admin dashboard keeps the original request, translation, summary, status, routing path, accepted responders when used, and follow-up actions in one place.

The automatic engine

The operating system
behind the mic.

The AI Voice Intake & Routing OS, website widget, hosted Lukriton page, QR code, direct link, dashboard, multilingual intake, tracking controls, routing, recipient lists, network rules, and follow-up tools are already connected.

AI OS workspace

The OS brings the ready mic-based request flow, AI analysis, dashboard, tracking, and routing controls together.

Deployment surfaces

Website widgets, hosted Lukriton pages, QR codes, and links all include the mic, request flow, dashboard connection, tracking controls, and brand details.

Admin dashboard

Network admins review requests, transcripts, translations, summaries, urgency, status, contacts, routing decisions, and follow-up from one dashboard.

Routing rules

The routing engine is already there. Network admins can adjust who receives requests by service type, location, language, availability, department, provider profile, or admin rules.

Service networks

Operational networks route demand to approved staff, departments, vendors, members, providers, desks, or community resources without needing provider monetization.

Provider-choice mode

Provider-choice routing lets customers cap how many approved providers may contact them while the network admin controls approval, routing, and notifications.

Customer tracking

When tracking is enabled, Lukriton can send a secure status page. Simple organization-routing pages can turn this off.

Suggested outreach

If a provider-choice request has no match, the network admin can search nearby outside providers, fill the provider outreach form, edit the email body, and send a secure accept-or-decline lead offer.

Admin operations manual

The real workflow
inside the dashboard.

This is the practical dashboard map. It explains where each action lives and what the network admin should do when a request has no matching provider yet.

Start here

Overview

Shows whether the network is active, how many requests are waiting, how many recipients are ready for routing, and how many members or join requests need review.

Entry points

Website widget

Controls the website widget, hosted Lukriton page, image, logo, greeting, languages, visitor links, QR-style sharing, and the tools that collect voice or typed requests.

Rules

Network settings

Sets visibility, service area, service map, lead routing mode, first offer batch size, alerts, daily digest, and whether routing stays inside the service area.

Lead worklist

Requests

Groups every request into active routing states so the network admin can start with requests that still need follow-up.

Provider outreach

Route requests

Opens the routing panel for internal assignment, approved recipients, one-provider email, or outside provider search and outreach.

Profiles and history

Providers

Shows provider or recipient profiles, approval, Add / edit, and Sent leads, where providers are ranked by how many lead offers they have received.

Network members

Invite and review

Invite providers or members, review submitted profiles, accept members, and decide who becomes visible or eligible for routing.

Shutdown

Remove

Hides or disables the network when the admin no longer wants the public network and routing tools active.

Request organization

Start with
No Providers.

The Requests tab is intentionally a set of links first. Open the status you need, then work the requests in that category.

First priority

No Providers

Active requests with no matching provider action yet. These are the leads the network admin should open first, because the customer still needs someone to receive the offer.

Offers sent

Routed

Lead offers were already emailed or sent to providers. The detail view shows which providers received the lead and whether each one is sent, accepted, declined, or filled / expired.

Contact unlocked

Accepted

At least one provider accepted the secure offer and unlocked the customer contact. The request can still accept more providers until the customer cap is full.

Closed work

Completed

Requests the admin has finished, closed, or no longer needs to route. Keep completed requests out of the active routing worklist.

If a lead has no provider

What to do
step by step.

Use this sequence when the request is real, the customer is waiting, and Lukriton did not find a matching provider automatically.

Open Requests, then No Providers

This view is the admin worklist for active requests that still need routing. Open the newest or most urgent request first, then click Details to see the transcript, translation, summary, urgency, service, location, customer contact, and AI status.

Confirm the request can be shared

Before sending provider emails, confirm the request has provider-sharing consent and enough public detail for a provider to decide. If sharing is not allowed, keep the request as an admin follow-up instead of routing it to providers.

Check the provider cap

Provider-choice mode lets the customer allow a limited number of providers to accept and unlock contact. Simple organization routing skips this step.

Use existing approved providers first

Choose Manual - existing providers when the right providers already exist in the network. Select the providers, edit the subject and body, then send the lead offer email.

Email one provider who is not saved yet

Choose Send email - one provider when you know a provider but they are not in the network yet. Enter the business name, email, optional phone, service, and service area. Lukriton saves the provider in the network and sends the secure lead offer.

Find outside providers when the network has no fit

Choose Find providers + email to search nearby outside providers for the request. Pick a suggested provider, review the filled-in details, edit the email draft, and send the offer.

Send another batch if nobody answers

In provider-choice mode, if the first providers do not accept, send another batch. The app can send up to 10 offers per batch, and only the first providers who accept up to the customer cap can unlock contact.

Move the request as the outcome changes

Once offers are sent, the request appears under Routed. When providers accept, it appears under Accepted. When the admin is done with the request, mark it completed so it leaves the active routing queue.

Route this lead

The routing
options.

The routing panel is where the network admin chooses how to contact providers. All provider emails include editable subject and body fields before sending.

Best for approved network providers

Manual - existing providers

Select saved providers from the network list. The app shows whether each provider has already received this lead, so the admin does not accidentally resend the same active offer.

Best for a provider you already know

Send email - one provider

Enter one provider directly from the lead. If the email or phone matches an existing provider, Lukriton uses that profile. If not, Lukriton creates an approved manual lead provider and sends the offer.

Best when nobody matches

Find providers + email

Search outside nearby providers, fill the provider form from a result, edit the email, and send. This is the admin fallback when the network does not yet have enough providers.

Optional setting

Auto-route matching leads

When enabled in Network settings, Lukriton can send offers to approved matching providers without admin handoff. Auto-route still respects provider approval, service fit, location rules, and the offer batch size.

After emails are sent

Offers, caps,
and provider statuses.

In provider-choice mode, sending to providers is outreach. Accepting the lead is what unlocks the customer contact, and that is controlled by the customer cap.

Every lead email is editable

Before sending, the admin can edit the subject and body. The default subject is practical, like Need help with childcare in Lincoln, CA, and the draft explains the network, the request, the no-obligation accept step, and the secure offer link.

Accept and decline are secure

The provider email includes a secure accept-or-decline button. Customer contact details stay hidden until a provider accepts the lead.

Send count and accept count are different

In provider-choice mode, the admin can email up to 10 providers per batch. The customer cap decides how many providers may accept and unlock contact.

Late providers see the lead is filled

If the allowed number of providers already accepted, later providers who open the link see that the lead has already been accepted by the allowed number of providers. No customer contact is unlocked for them.

Statuses stay visible

The lead detail shows Providers sent this lead with counts for sent, waiting, accepted, declined, and filled / expired. The Providers > Sent leads page shows each provider and every lead they received.

Provider manual

Profiles and
sent leads.

Providers are the network supply. Keep profiles clean so routing can match by service, area, approval, and contact method.

Profiles

Use Providers > Profiles to review each provider, see services, service area, radius, email, phone, approval status, and whether they are auto-ready.

Add / edit

Use Providers > Add / edit to add business name, description, services, service area, radius, email, phone, website, approval status, and whether automatic matching is allowed.

Sent leads

Use Providers > Sent leads to see providers ranked by lead count. Click a provider to see the provider details, then click a sent lead to open that lead information.

Approval

Approved providers can be selected for routing. Auto-routing also requires approval, auto-route opt-in, services, service area, and a lead contact email or phone.

Settings manual

Rules and
notifications.

These controls decide how aggressive routing should be, who can receive offers, and how the admin and customer receive updates.

Routing mode

Manual review keeps the admin in control. Assisted suggestions helps find likely matches. Auto-route sends offers to approved matching providers without admin handoff.

First offer batch

In provider-choice mode, this controls how many providers receive the first automatic or matching batch. Simple organization routing can skip provider batches.

Service area

The service map and route-only-inside-service-area setting keep poor-fit location requests from being sent to providers who should not receive them.

Recipients

The admin can include accepted network members, saved approved providers, or both in matching and auto-routing.

Alerts and digest

Lead emails can be every lead, only urgent or unmatched, daily digest only, or none. Digest time and urgent provider SMS are also controlled from settings.

Tracking

When tracking is enabled and the requester leaves email, Lukriton sends a secure status page that shows request progress, accepted providers when used, or routed follow-up.

Why customers use it

The old search process
wastes too much time.

Every person needs help all the time: repairs, cleaning, moving, tutoring, events, purchases, and local services. The painful part is finding someone who can help, reaching them, explaining the same thing again and again, and not being able to track what happens next.

Search is work

Google, Yelp, LinkedIn, Facebook groups, and local directories still make the customer search, hope someone knows the right provider, hope that provider replies, and then wait without a request to track.

Outreach is work

The customer has to call, text, email, submit forms, leave messages, and hope someone calls back. Friends may know someone, but friends are busy too.

Repeating is work

When someone finally responds, the customer has to explain the same request again. Then they do it again with the next provider.

Lukriton captures the request

No account is required. The requester tells Lukriton what they need in their own language. Lukriton analyzes, translates, summarizes, and prepares the request for follow-up.

Responders already know

When the admin, staff, department, vendor, provider, or member receives the request, they already understand the context and urgency.

The request can be tracked

If tracking is enabled and the requester leaves email, they can see request status, accepted responders, or routed follow-up from a secure page.

Multilingual routing

One request.
Many languages.

Visitors can speak naturally in their language. Lukriton detects the spoken language, keeps the original transcript, translates it, and can show follow-up prompts in that language.

Original and translation

Visitors can leave a request through any OS entry point in their own language. Lukriton keeps the original and prepares an English version for follow-up.

Language-aware routing

Service networks can use language preferences when routing to providers, staff, members, vendors, desks, or departments.

Localized prompts

After the visitor speaks, Lukriton can show the contact prompts in the detected language so the request is easier to finish.

Admin setup manual

From first click
to live routing.

A practical admin path from the first Deploy OS click to a ready AI Voice Intake & Routing OS, website widget, hosted Lukriton page, service network, or provider-choice workflow. Most of the system is already set up; these are quick customization choices.

Open the ready system

Click Deploy OS from the menu or this page. The first screen opens the already assembled system and asks only for the basic admin details, like the name of the business, organization, website, or network.

Choose the ready configuration

Pick the configuration that matches your use case. The OS, deployment surfaces, dashboard, intake flow, translation, priority, tracking, notifications, and routing controls are already part of the system.

Customize the OS launch

The OS workspace and deployment surfaces are already created with the mic and request flow. You can keep the default version or spend a few minutes changing the name, logo, image, greeting, service area, and request prompt.

Deploy the entry point

If you want the mic on your existing website, use the Website Widget kit so visitors can tap and talk without leaving your site. The hosted Lukriton page and QR code are ready when you need another entry point.

Review the connected dashboard

The dashboard is already connected. Every intake lands there with the original voice request, transcript, translation, summary, urgency flag, contact details, status, and follow-up actions in one place.

Turn on routing if you want it

Admin notifications are ready by default. If you want service network routing, use the built-in controls to choose approved staff, departments, vendors, members, providers, advertisers, or other responders.

Adjust rules and tracking

The rule system is ready. You can customize service type, location, language, urgency, availability, recipient status, notifications, whether customers choose provider count, and whether requesters can track the request.

Run a quick test

Submit test requests in different languages. Check that Lukriton captures the request, translates it when needed, marks urgency correctly, sends the right notification, routes to the right recipient, and creates tracking when enabled.

Go live and refine

Deploy the OS entry point and share the hosted Lukriton page, QR code, or direct link where needed. Real intakes appear in the dashboard. You can adjust prompts, rules, images, notifications, tracking, and approved recipients anytime.

Important details

Things admins
should know.

A few practical rules about OS deployment, hosted Lukriton pages, service networks, provider-choice routing, tracking, language handling, and contact protection.

What are the main ways to use Lukriton?

Use the website widget when you want the ready OS entry point on an existing website. Use the hosted Lukriton page when you need one public link for requests. Use QR codes or direct links when people need a simple entry point. Use a service network when requests need to route to staff, departments, vendors, members, providers, desks, or community resources. Turn on provider-choice routing only when approved outside providers may contact the customer under customer caps.

Does an OS launch need providers?

No. An OS launch can simply notify the admin with a clean intake record. Providers or other routed recipients are only needed when the admin chooses to turn on network routing.

What is different about a service network?

A service network is for operational routing. Cities, chambers, BIDs, agencies, schools, businesses, associations, and nonprofits can route requests to approved people, departments, vendors, members, desks, or providers without charging providers to join.

What is provider-choice routing?

Provider-choice routing is an optional network mode for admins who invite approved providers, vendors, advertisers, or members into a controlled request flow. The customer can cap how many providers may contact them, and Lukriton keeps contact details protected until acceptance rules are met.

Can a customer limit who contacts them?

Yes, when provider-choice mode is enabled. The customer cap controls accepted providers, not outreach attempts. Simple organization-routing pages skip provider caps and send the request to the admin for internal routing.

Who receives the request?

That depends on the setup. A simple OS launch can notify the admin. A service network can route to staff, departments, vendors, members, desks, providers, or community resources. Provider-choice routing can notify participating providers, advertisers, vendors, or members under the admin's approval rules.

Can requesters track the request?

Yes. If tracking is enabled and the requester leaves email, Lukriton can send a secure tracking link so they can see request status, accepted responders, or routed follow-up.

Where do routing rules live?

The rule controls are already in the admin dashboard. Network admins can adjust service area, service type, language, availability, recipient status, optional customer caps, notifications, and workflow.

Can the admin edit provider emails?

Yes. Every provider lead email has editable subject and body fields before sending. The default copy introduces the network, explains the request, includes the no-obligation accept or decline action, links to the network, and adds the secure offer button.

What happens if no one matches?

Open Requests > No Providers, review the lead, then use Route this lead. The admin can send to existing approved providers, send one direct provider email, search nearby outside providers and email them, or add a provider profile first. If nobody accepts, the admin can send another batch while the customer accept cap stays protected.

How do I know which providers already received a lead?

Open the lead detail and look at Providers sent this lead. It shows sent, waiting, accepted, declined, and filled / expired statuses. Providers > Sent leads also ranks providers by total leads received and lets the admin click into each provider and lead.

Does it work in other languages?

Yes. Visitors can speak in their own language. Lukriton detects the language, keeps the original request, prepares a translation, and can use language preference for routing.

Does Lukriton take commissions on provider work?

No. Lukriton provides the intake, routing, tracking, and notification system. Outside provider terms are controlled by the admin or organization and provider, not by Lukriton taking a job commission.

Who pays Lukriton?

The admin or organization pays Lukriton for the platform. If the admin or organization has separate participation terms with providers, vendors, advertisers, or members, those terms are controlled by that admin or organization.

Choose the
ready setup.

Use Lukriton as an AI Voice Intake & Routing OS with a website widget, hosted Lukriton page, QR/link intake, service network, or provider-choice routing workflow. The system is already connected; you customize the details, and people tap and talk.