Your customers set vendor terms
Each of your customers can charge its approved vendors a monthly membership, a fee per accepted job, or an approval fee.
AI Voice Intake & Routing OS for software companies
Add voice intake and routing
to your own app.
Your customers' users describe a problem in any language. Your system gets a clean, routed request. Their vendors can pay for it.
Lukriton is the AI Voice Intake & Routing OS you build into your product. One line of code adds the request button for each of your customers. Every request arrives in your system as a signed event with a summary, category, urgency, and translation, and can go on to that customer's own approved vendors.
- One script tag per customer
- Voice or text, any language
- Your customer's logo and colors
- Signed events into your system
What it does
From a spoken sentence
to a work order in your app.
Five steps, and none of them need a person to retype, translate, or forward anything. Your team only sees finished, organized requests.
- 1
Their users speak or type
A tenant, homeowner, or member taps the request button inside your app and explains the problem in their own language, with photos if they want. No download, no account.
- 2
AI organizes it
Lukriton transcribes, translates into English, writes a summary, picks the category, and flags the urgency. The original words stay with the request.
- 3
It lands in your system
Your server gets a signed event with the full request and the property, unit, or customer ID your page signed. It becomes a work order or ticket without anyone retyping.
- 4
Vendors accept or decline
If a customer turns on vendor matching, the right vendor gets the job by email and accepts or declines. One vendor at a time, and the next one after a timeout you choose.
- 5
Everyone sees where it stands
Status changes you make in your app show on the requester's private tracking page. Each of your customers has its own inbox, vendors, and reviews, and never sees another customer's.
Beyond intake and routing
Your app
pays for itself.
Intake and routing are the visible part. The bigger change is that each of your customers gets a vendor network it can charge, and those fees can cover what the customer pays you.
Vendor fees can cover your app
Those fees can cover what your customer pays for your app, so your app can cost them little or nothing out of pocket.
An edge over competitors
Most maintenance and intake tools are only a cost to the customer. Yours can pay for itself, which makes it the easier one to buy.
Nothing to build or run in-house
Voice capture, transcription, translation, AI analysis, vendor emails, tracking pages, and reminders already run. You connect them to your records.
A separate network for every customer
One call creates a widget, a hosted request page, and a vendor network for each company you serve. Requests, vendors, and reviews never cross between them.
White label from the first request
Requesters and vendors see your customer's name and logo in the form, the emails, the tracking page, and the browser tab. Lukriton is never shown.
Example: if your app costs a property manager $900 a month, 20 vendors paying $45 a month would cover it.
You keep what you charge. Lukriton charges a flat software plan and takes no commission on vendor fees, jobs, or leads. Actual results depend on each customer's vendors and terms.
Lukriton is software. It does not promise leads, income, vendor participation, or results. You and your customers are responsible for your own vendor terms and for the rules that apply in your industry.
How to incorporate it
Eight steps,
one to three days.
A plain REST API and signed webhooks, the same pattern as a payments integration. No SDK to install and nothing to run on your servers. With an AI coding agent, a first working version takes a few hours, and the full integration takes 1 to 3 days.
- 1
Create the account and keys
Sign up with a company email, set a workspace notification email, and in Integrations create a Full partner access API key and copy the integration secret. Both stay on your server, never in browser or mobile code. About an hour.
- 2
Create a customer for each company
When a company starts using your app, call POST /api/v1/customers with your ID, its name, its inbox email, and the domains where your app runs. You get back a widget embed code, a hosted request page link, and a vendor sign-up link. Pause or change it with PATCH. Two to three hours.
- 3
Put the widget in your app
Add the embed code to the page where users report problems. Your server signs a reference such as property, unit, and tenant IDs with HMAC-SHA256, so every request comes back tagged and verified. Mobile apps, text messages, and QR codes use the hosted page link with the same signed reference. Two to three hours.
- 4
Receive events
One public HTTPS endpoint receives request.created, request.updated, and request.no_vendor with the full request. Check the signature, skip duplicates by event ID, answer within 6 seconds, and create or update your work orders from a queue. About half a day.
- 5
Catch up once an hour
Events are retried once and are not stored. An hourly call to GET /api/v1/requests with createdAfter fills any gap after an outage on your side. One to two hours.
- 6
Send updates back
Set in_progress, completed, or archived from your app and email the requester in the company's name through the API. The tracking page updates at once. Two to three hours.
- 7
Add vendors if you want matching
Import each company's vendors with categories and service areas, approve vendors who sign up through the company's link, and turn on vendor matching with a response time of 1 to 72 hours. Optional. About half a day.
- 8
Test and go live
Run the 12 checks in the Partner Integration Guide with a test company, confirm no Lukriton name or logo shows to users, then switch on your first real customer and watch its first ten requests. Two to three hours.
The Partner Integration Guide has the full API reference, the signature test values, and code samples in Node.js, Python, PHP, and C#.
Book a presentation and we send the guide to your team, together with a step-by-step plan for your product.
What the API covers
Four areas,
fourteen calls.
Everything your product needs to run request intake for many companies from one workspace, with one API key and one webhook address.
Customers
Create, read, change, and pause a company. Each one gets its own widget, hosted page, vendor network, and inbox.
Requests
List and read requests with the AI summary, category, urgency, translation, and your signed reference. Change status, message the requester, and download photos.
Vendors
Add vendors to one or more companies, approve sign-ups, verify, pause, or move them. One vendor can serve several companies.
Events
Three signed webhook events cover a new request, every status change, and the case where no vendor takes a job.
Plans
Pay a flat plan.
Keep what you charge.
Every plan includes the widget, the hosted request page, transcription, translation, summaries, and the dashboard. Sending requests into your own system starts on the Growth plan. Software companies with many customer companies get a partner plan sized for them: up to 500 widgets and pages, 10,000 vendors, and 1,000,000 requests a month.
Questions
Straight answers
Do we have to build voice, translation, or AI ourselves?
No. Voice capture, transcription, translation, summaries, categories, urgency, vendor emails, and tracking pages all run in Lukriton. Your developers connect a REST API and one webhook endpoint.
Can our customers' users see Lukriton?
No. White label is on by default. The form, emails, tracking page, browser tab, and link previews show your customer's name and logo.
How long does the integration take?
With an AI coding agent, a first working version with companies, the widget, and the webhook takes a few hours. The full integration takes 1 to 3 days, including vendor matching and the test run.
What languages does it handle?
Any language the user speaks or types. Lukriton keeps the original, adds an English translation, and can use the language to pick the vendor.
Does Lukriton charge vendors or take a commission?
No. Lukriton charges a flat software plan. If you or your customers charge vendors, you bill them in your own system and keep what you charge.
What happens if our server is down when an event is sent?
The event is retried once about a second later. After that, your hourly catch-up call reads any requests you missed, so nothing is lost.
Let's map your product
and your customers' vendor networks.
Book a presentation and we will walk through your product: where the request button goes, what your system should receive, which of your customers want vendor matching, and how they can set vendor terms.